The more I try with Locale / multi-language support, the more I'm convinced that it will need further extensions...
To start with, consider this use case:
:arrow: you have 3 BO's which need the attribute Country. The Country Names are different in various languages.
The choice list is hardly an option because you would have to enter 150 countries in the configuration tool and then translate them in each Locale...
Today, you can solve this type of requirement with a BO, say pCountry, and a reference attribute in the 3 BOs.
pCountry has attributes Name_EN, Name_FR, Name_GE + a few others and you have a csv file with all countries to import into pCountry.
The only "problem" with regard to multi-language support is :
in the 3 BOs form, to display the Country reference attribute as a Drop-down, you must choose either Name_EN, Name_FR or Name_GE.
One way to make it dynamic, ie. recognized as Locale dependent could be:
:idea: when you create a plain text attribute, you can select in a combo from one of the defined Locale object.
Maybe that property would only be available for a specific type of BO created with "Add pLocale_ Object" to satisfy those requirements behind the scene ...
Does it make sense or should I stop dr(inking)eaming ?
