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>

Reply via email to