We're internationalizing in English and German (for now -- more languages may come later); we generally use the practices recommended in the Cocoon docs (master dictionary), but in addition, we split the master dictionary into several parts, a main dictionary and a subdictionary for each semantic area. The subdictionaries are referenced in the main dictionary as entities. Splitting it up helps keep things manageable if you have more than a couple of dozen translation keys.

I also recommend writing tests to make sure you don't have any duplicate keys, and if you use i18n parameters checking for mismatched brackets (cost me 2 hours recently when this happened, Tomcat crashed every time with an OutOfMemoryError without giving a clue where the actual problem was).

I find it's hard after a while to keep the dictionaries up to date - old translations that aren't used any more as the webapp evolves tend to hang around. Anyone have any experience dealing with that?

John

Dean West wrote:

I have been tasked with internationalization for the company I work for, and
since we already use Cocoon in our current appliction - I am thinking that
the "I18n Transformer" should do the job?

I like the concept of the I18n Transformer because it seperates the
different langues into their own source XML documents... this SEEMS to be
way more efficient than having 1 xml source doc with a plethora of
"xml:lang" tags for each language translation.

Can anyone offer their expertise on this subject (best practices)? - it
just seems really heavy on the xml engine to have to parse huge xml files
(containing all language translations).



--
---------------------------------------------------------
Jentro Technologies GmbH
John L. Webber, Software Development
---------------------------------------------------------
Rosenheimer Str. 145e 81671 M�nchen
Tel. +49 89 189 169 80 mailto:[EMAIL PROTECTED] Fax +49 89 189 169 99 http://www.jentro.com
---------------------------------------------------------
NOTICE: The information contained in this e-mail is confidential or may otherwise be legally privileged. It is intended for the named recipient only. If you have received it in error, please notify us immediately by reply or by calling the telephone number above and delete this message and all its attachments without any use or further distribution of its contents. Please note that any unauthorised review, copying, disclosing or otherwise making use of the information is strictly prohibited. Thank you. ---------------------------------------------------------



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to