Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
0.8
-
None
-
None
Description
The i18n functionality uses the LocaleAction and LocaleMatcher components, but instead of being configured in a single place, there are several instances of these components' configurations.
The LocaleAction, in particular, is configured in i18n.xmap, forrest.xmap, tabs.xmap. Currently it uses default settings so it's not really a problem, but becomes one if people want to change the settings.
Also, the i18n transformer sometimes takes its locale from {request:locale} and sometimes from an enclosing LocaleAction. I think this explains the discrepancies observed in some cases, for example having tabs in one language and the content in another.
I'm going to commit changes that move all the LocaleAction and LocaleMatcher configuration to the main sitemap, and always use the LocaleAction to provide the locale for the i18n transformer.
The LocaleAction, in particular, is configured in i18n.xmap, forrest.xmap, tabs.xmap. Currently it uses default settings so it's not really a problem, but becomes one if people want to change the settings.
Also, the i18n transformer sometimes takes its locale from {request:locale} and sometimes from an enclosing LocaleAction. I think this explains the discrepancies observed in some cases, for example having tabs in one language and the content in another.
I'm going to commit changes that move all the LocaleAction and LocaleMatcher configuration to the main sitemap, and always use the LocaleAction to provide the locale for the i18n transformer.