Ok i see now i understand, indeed to think of a plugin that works with the cms content types would be the direction to go, thanks.
On Aug 5, 3:19 am, Blair McKenzie <[email protected]> wrote: > Core internationalisation only applies to webtop elements. Translating > content managed text is a different problem to translating static text. A > plugin to make the CMS content types multi-language would probably get a lot > of use, but it hasn't been something we've needed. If either of you guys > have some ideas about it you should through something together and get some > feedback from the list. > > On Wed, Aug 5, 2009 at 11:10 AM, Marco van den Oever < > > [email protected]> wrote: > > > Isn't internationalization a core feature? So the navigation should > > also to be translated? > > Or do you have to draw a line somewhere because else it all gets to > > heavy? > > > On Aug 5, 1:28 am, Blair McKenzie <[email protected]> wrote: > > > You could put them in the wiki too, and use the mockup tools. In the > > cage, > > > or under tutorials or something. Since they looks like changes you would > > > make on a project by project basis they probably couldn't go into core. > > > > Blair > > > > On Tue, Aug 4, 2009 at 9:11 PM, Marco van den Oever < > > > > [email protected]> wrote: > > > > > Hi Chris, i was also thinking about how to make that working, to be > > > > honest it's a bit over my head so to speak. For now I'll go and use > > > > the "if language is then show" method. > > > > > It might be an idea to include your thoughts in a feature improvement > > > > bug, it really would be an improvement for the internationalization > > > > part, I'll vote for it, idea? > > > > > Thanks. > > > > > On Aug 4, 9:38 am, Chris Kent <[email protected]> wrote: > > > > > 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 -~----------~----~----~----~------~----~------~--~---
