You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Sjur N. Moshagen (JIRA)" <ji...@apache.org> on 2006/09/25 13:17:50 UTC
[jira] Created: (FOR-935) i18n in dispatcher sitemap non-standard
i18n in dispatcher sitemap non-standard
---------------------------------------
Key: FOR-935
URL: http://issues.apache.org/jira/browse/FOR-935
Project: Forrest
Issue Type: Bug
Components: Dispatcher (aka views), Internationalisation (i18n)
Affects Versions: 0.8-dev
Reporter: Sjur N. Moshagen
The present dispatcher sitemap internal.xmap is taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction. This leads to inconsistent behaviour: the standard messages (Last updated, Search, etc.) follows the best browser locale available, whatever happens, and appears "fixed" in its locale selection — it isn't possible to change it, even if other aspects on the current page changes locale.
The fix is to insert LocaleAction action wrapper, and use the locale provided by it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-935) i18n in dispatcher sitemap non-standard
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-935?page=all ]
David Crossley closed FOR-935.
------------------------------
Fix Version/s: 0.8-dev
Resolution: Fixed
Patch applied, thanks.
> i18n in dispatcher sitemap non-standard
> ---------------------------------------
>
> Key: FOR-935
> URL: http://issues.apache.org/jira/browse/FOR-935
> Project: Forrest
> Issue Type: Bug
> Components: Dispatcher (aka views), Internationalisation (i18n)
> Affects Versions: 0.8-dev
> Reporter: Sjur N. Moshagen
> Fix For: 0.8-dev
>
> Attachments: internal.xmap
>
>
> The present dispatcher sitemap internal.xmap is taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction. This leads to inconsistent behaviour: the standard messages (Last updated, Search, etc.) follows the best browser locale available, whatever happens, and appears "fixed" in its locale selection ? it isn't possible to change it, even if other aspects on the current page changes locale.
> The fix is to insert LocaleAction action wrapper, and use the locale provided by it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-935) i18n in dispatcher sitemap non-standard
Posted by "Sjur N. Moshagen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-935?page=all ]
Sjur N. Moshagen updated FOR-935:
---------------------------------
Attachment: internal.xmap
The attached sitemap contains all and only the necessary changes to fix this bug.
It replaces the one in:
whiteboard/plugins/o.a.f.plugins.internal.dispatcher/
> i18n in dispatcher sitemap non-standard
> ---------------------------------------
>
> Key: FOR-935
> URL: http://issues.apache.org/jira/browse/FOR-935
> Project: Forrest
> Issue Type: Bug
> Components: Dispatcher (aka views), Internationalisation (i18n)
> Affects Versions: 0.8-dev
> Reporter: Sjur N. Moshagen
> Attachments: internal.xmap
>
>
> The present dispatcher sitemap internal.xmap is taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction. This leads to inconsistent behaviour: the standard messages (Last updated, Search, etc.) follows the best browser locale available, whatever happens, and appears "fixed" in its locale selection ? it isn't possible to change it, even if other aspects on the current page changes locale.
> The fix is to insert LocaleAction action wrapper, and use the locale provided by it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira