Marco The method for multi-lingual sites that I have sees most frequently suggested is to duplicate the site tree for each language, this may work for you, but could prove to be a major admin task to keep track of if there are many languages with frequent updates.
I have been planning a future (long way off) requirement that uses a single site tree structure and extends the navigation and html content types to each include a language array property. • It would be easy to add new languages. • For the navigation node the language array property would include the language code, label ... • For the html content type the language array property would include the language code, label, seo stuff, language specific teaser and body content. • You would probably need to extend the farFU processing to auto create the language specific friendly URLs. • It would be fairly easy to create simple reports to highlight navigation/html items that do not have the require language entries and also translation verification reports listing content items with two or more languages side by side to allow translators to check the translations. I have not yet thought through how this would work regarding performance and any content caching. Chris On Aug 4, 12:10 am, Marco van den Oever <[email protected]> wrote: > I know there was a previous post on this matter, can't find it. > Can someone give me any directions on how to setup the translation > structure for the navigation? > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
