You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Hugo Palma <hu...@gmail.com> on 2011/02/23 12:40:45 UTC
Localization resources precedence
Hi,
i was hopping to clarify if the following is expected behavior or if it's
some kind of bug.
My application is running on the locale "pt_PT", and some component in a
library doesn't have a SomeComponent_pt_PT.properties but has a
SomeComponent.properties 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 on defined
in SomeComponent.properties takes precedence even though it's less specific
localization wise.
So, any idea if this is by design or should i file an issue for this ?
Thanks.
--
LinkedIn <http://www.linkedin.com/in/hugopalma>
Twitter<http://twitter.com/hugompalma>
Re: Localization resources precedence
Posted by Hugo Palma <hu...@gmail.com>.
I've created an issue for this here
https://issues.apache.org/jira/browse/TAP5-1498
On Fri, Feb 25, 2011 at 16:11, Everton Agner <to...@gmail.com> wrote:
> Hey
>
> Does anybody know the answer for this question? I was hoping to understand
> the mechanics for this case too... Since I might have coded some things not
> exactly safe, depending on the answer.
>
> Thanks!
>
> _______________________
> Everton Agner Ramos
>
>
> 2011/2/23 Hugo Palma <hu...@gmail.com>
>
> > Hi,
> > i was hopping to clarify if the following is expected behavior or if it's
> > some kind of bug.
> >
> > My application is running on the locale "pt_PT", and some component in a
> > library doesn't have a SomeComponent_pt_PT.properties but has a
> > SomeComponent.properties 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 on defined
> > in SomeComponent.properties takes precedence even though it's less
> specific
> > localization wise.
> >
> > So, any idea if this is by design or should i file an issue for this ?
> > Thanks.
> >
> > --
> >
> > LinkedIn <http://www.linkedin.com/in/hugopalma>
> > Twitter<http://twitter.com/hugompalma>
> >
>
--
LinkedIn <http://www.linkedin.com/in/hugopalma>
Twitter<http://twitter.com/hugompalma>
Re: Localization resources precedence
Posted by Everton Agner <to...@gmail.com>.
Hey
Does anybody know the answer for this question? I was hoping to understand
the mechanics for this case too... Since I might have coded some things not
exactly safe, depending on the answer.
Thanks!
_______________________
Everton Agner Ramos
2011/2/23 Hugo Palma <hu...@gmail.com>
> Hi,
> i was hopping to clarify if the following is expected behavior or if it's
> some kind of bug.
>
> My application is running on the locale "pt_PT", and some component in a
> library doesn't have a SomeComponent_pt_PT.properties but has a
> SomeComponent.properties 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 on defined
> in SomeComponent.properties takes precedence even though it's less specific
> localization wise.
>
> So, any idea if this is by design or should i file an issue for this ?
> Thanks.
>
> --
>
> LinkedIn <http://www.linkedin.com/in/hugopalma>
> Twitter<http://twitter.com/hugompalma>
>