[ http://jira.magnolia.info/browse/MAGNOLIA-1431?page=comments#action_13916 ] Philipp Bracher commented on MAGNOLIA-1431: -------------------------------------------
I commited a first version (so that it goes into the M1 release). It works as such: - You call your page with a selector - example mypage.de.html - After calling a page with a selector the creates links uses the selector as well - cms:out tag uses support to get a nodedata - i18n support checks if the nodedata exists with the lanugage extension - example: title_de - if it doesn't exist the normal nodedata is returned --> title - in your dialog you define the controls for the languages you support (normal you will do a tab per language) > i18n: basic content support > --------------------------- > > Key: MAGNOLIA-1431 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1431 > Project: Magnolia > Issue Type: New Feature > Components: templating > Affects Versions: 3.0 Final > Reporter: Philipp Bracher > Assigned To: Philipp Bracher > Fix For: 3.1 > > > Currently magnolia does not give any advise how to implement i18n support for > content. In cases where you have a single page structure with translations > you have to come up with a custom solution. Till now the philosophy was that > we can not solve this problem in general and that each setup has other needs. > This is still our opinion but we think it is time to deliver basic support > for facilitate implementations. More sophisticated all-over approaches may > follow in later version. > The framework will support > - i18n url building (/en/*, page.en.html, ...) > - multilanguage content > - all mechanism should be replaceable > The first very basic implementation will do: > - create url using the separator technic (pagename.en.html) > - cache is automatically supported by this approach > - bookmarking is possible > - cms:out tag extension > - text_de, text_en fields are used according to the current language if > present > - default language (fallback if content is not translated) > - cooky (remember selected language) > This allows: > - build paragraphs with tabs per language just by having language suffixes in > the names -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
