To use the intl object input you need to enable it for your object type field, which will contain all the translatable fields in your document.
To me, that sentence says that to use intl-input for fields, we must create an object to hold all translations of every field at the document root. My understanding is that instead this plugin is used to create an object that has multiple translation properties for specific fields, like an improved UI for "localeString". From the example given, I don't fully understand the structure that is going to be created or how to use it with my own fields.
I think it would be helpful if you could please add some concrete examples of using it on a few fields, such as the "title" field shown in the "default solution" and maybe a more complex type like the image field shown in the "simple translated object field" example.
I had trouble understanding the sample given for using the intl object input. I also found this sentence a bit confusing:
To me, that sentence says that to use intl-input for fields, we must create an object to hold all translations of every field at the document root. My understanding is that instead this plugin is used to create an object that has multiple translation properties for specific fields, like an improved UI for "localeString". From the example given, I don't fully understand the structure that is going to be created or how to use it with my own fields.
I think it would be helpful if you could please add some concrete examples of using it on a few fields, such as the "title" field shown in the "default solution" and maybe a more complex type like the image field shown in the "simple translated object field" example.