forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <>
Subject [jira] Commented: (FOR-887) Make i18n more consistent
Date Mon, 22 May 2006 15:48:30 GMT
    [ ] 

Bertrand Delacretaz commented on FOR-887:

The result is that switching languages works more consistently, i.e. on a "forrest seed" fresh


show the translated versions of the content, tabs and menus.

Should also with browser headers detection, but it is disabled by default (see FOR-888).

I have set project.i18n=true in fresh-site to make these examples visible without configuration.
This shouldn't be a problem as the locale must now be specified explicitely, so the change
should be invisible to users who don't care about i18n.

> Make i18n more consistent
> -------------------------
>          Key: FOR-887
>          URL:
>      Project: Forrest
>         Type: Improvement

>   Components: Internationalisation (i18n)
>     Versions: 0.8-dev
>     Reporter: Bertrand Delacretaz
>     Priority: Minor

> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message