Hi Klug.
I've also think about zimlets translations. In my opinion, Zimlet languages and/or country specific issued shoud be tied to WebUI language.
I think is better having a zimlet with a country specs (language, date format, etc) instead several zimlets. Maintenance would be easiest specially in international companies (having six zimlets for same function is not specially easy to mantain in my opinion). I would use same model used today with WebUI internationalization. For example, one zimlet with several "zimlet_COUNTRY.properties". If a country code fails, it would revert to a default country properties that could be english, of course.
Quote:
|
Originally Posted by Klug Should we take the existing Zimlet and add into this single zimlet the other languages (then deploy a single Zimlet) ?
Should we create a brand new Zimlet per language (based on the english one) and deploy a Zimlet per language ?
Any other suggestion ?
In any case, how should we handle the "right click" in the UI ?
Can the language of the contextual menu change like the language for rest of the UI changes ? |