You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hugo Palma (JIRA)" <ji...@apache.org> on 2011/04/05 14:41:05 UTC
[jira] [Created] (TAP5-1498) Localization resources precedence is
not processed correctly
Localization resources precedence is not processed correctly
------------------------------------------------------------
Key: TAP5-1498
URL: https://issues.apache.org/jira/browse/TAP5-1498
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.2.5
Reporter: Hugo Palma
I think this is best illustrated by an example:
My application is running on the locale "pt_PT", and some component in a library doesn't have a SomeComponent_pt_PT.properties file but has a SomeComponent.properties file with the property "someProperty" set.
I was hoping to localize "someProperty" by including it in my app_pt_PT.properties but it seems that the property defined in SomeComponent.properties takes precedence even though it's less specific localization wise.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1498) Localization resources precedence is
not processed correctly
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1498.
--------------------------------------
Resolution: Invalid
This simply isn't how Tapestry message inheritance works, and to change it would break existing programs. Each component's message catalog delegates to its super-class, and eventually to the global message catalog. Perhaps we could open up the APIs so that you could walk up the message catalog inheritance heirarchy, as a way to introduce your own inheritance rules.
> Localization resources precedence is not processed correctly
> ------------------------------------------------------------
>
> Key: TAP5-1498
> URL: https://issues.apache.org/jira/browse/TAP5-1498
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.5
> Reporter: Hugo Palma
>
> I think this is best illustrated by an example:
> My application is running on the locale "pt_PT", and some component in a library doesn't have a SomeComponent_pt_PT.properties file but has a SomeComponent.properties file with the property "someProperty" set.
> I was hoping to localize "someProperty" by including it in my app_pt_PT.properties but it seems that the property defined in SomeComponent.properties takes precedence even though it's less specific localization wise.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1498) Localization resources precedence is
not processed correctly
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1498.
--------------------------------------
Resolution: Invalid
This simply isn't how Tapestry message inheritance works, and to change it would break existing programs. Each component's message catalog delegates to its super-class, and eventually to the global message catalog. Perhaps we could open up the APIs so that you could walk up the message catalog inheritance heirarchy, as a way to introduce your own inheritance rules.
> Localization resources precedence is not processed correctly
> ------------------------------------------------------------
>
> Key: TAP5-1498
> URL: https://issues.apache.org/jira/browse/TAP5-1498
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.5
> Reporter: Hugo Palma
>
> I think this is best illustrated by an example:
> My application is running on the locale "pt_PT", and some component in a library doesn't have a SomeComponent_pt_PT.properties file but has a SomeComponent.properties file with the property "someProperty" set.
> I was hoping to localize "someProperty" by including it in my app_pt_PT.properties but it seems that the property defined in SomeComponent.properties takes precedence even though it's less specific localization wise.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira