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