Darren Petrie <[EMAIL PROTECTED]> wrote:
>
> 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 do almost exactly the same, with one difference that we put
translated content xml files into {$lang} directories, ex:
content/en/somePageContent.xml
content/de/somePageContent.xml
content/ru/somePageContent.xml
etc..
This is of course all about simple sites with no db-based
CMS which handles language version of content itself.
--
Tomasz Nowak
Netventure, http://www.netventure.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
