cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Petrie <>
Subject Re: Cocoon and Internationalization
Date Tue, 11 May 2004 12:53:59 GMT
We have successfully used Cocoon on several "DOCUMENT oriented"  
multi-lingual sites.  In our experience we have found that i18n is good  
for internationalizing our application but not our content.   The text  
that is part of the APPLICATION (menu bars, headings, navigation aides  
etc) is all controlled under the i18n umbrella.   The CONTENT however  
is simply marked up with language identifying tags.   We did this for a  
couple of reasons.   One was outlined below in that i18n isn't really  
designed for whole documents but rather bits and pieces.  The second  
reason was that we wanted to keep our content "pure" separate from any  
application specific mechanisms.  This way our content stands alone and  
is ready to be used or served by any system.  Whether or not the  
translated content is in a single file per document or individual  
language files is completely a design choice.  We have done it both  


On May 11, 2004, at 2:54 AM, Sjur Nørstebø Moshagen wrote:

> På 11. mai. 2004 kl. 02.07 skrev Joerg Heinicke:
>> On 10.05.2004 21:55, 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).
>> Yes, you should use multiple files. They offer as additional value  
>> the fallback from the language_country_variant to language_country to  
>> language to default if a key is missing in the more detailed variant.  
>> Did you read the documentation on I18nTransformer? I think it  
>> explains the details very well:
>> transformer.html
>> The documentation on the wiki can probably not add much more, but the  
>> URL is:
> You should be aware that the present i18n support in Cocoon (2.1.4) is  
> missing one major i18n feature: whole-document i18n. The present  
> features are geared towards database-driven sites where you need to  
> translate table headings, menues, and other smaller pieces of texts as  
> part of a generated site. If your site is document-heavy in the sense  
> that you have largeish documents in several languages (each language  
> in a separate file, as you describe it above), there presently is no  
> way to select _documents_ (ie files) based on locale/language, at  
> least I have not been able to find a way of doing it.
> BUT: Upayavira has implemented an i18n-ed file selector which does  
> proper fallbacks (lang_country_variant -> lang_country -> lang). I  
> haven't tried it yet myself, but I believe it is available in the  
> latest CVS versions. With it you can also easily select whole  
> documents/files based on locale.
> Sjur
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message