El Mié 19 Nov 2008 a las 11:42:34 Hugo Palma escribió: > Hi Jorge, > > tapestry already provides an Errors_es.properties, Errors_pt_PT.properties > and an Errors_pt_BR.properties. So you should see the localized message > just fine. Are you sure your using the correct locale ?
That is strange. This is what I see in the tapestry core jar that maven
downloaded:
[EMAIL PROTECTED] lib]# jar tvf tapestry-core-5.0.15.jar | grep Errors
org/apache/tapestry5/corelib/components/Errors.class
org/apache/tapestry5/corelib/components/Errors.properties
org/apache/tapestry5/corelib/components/Errors_da.properties
org/apache/tapestry5/corelib/components/Errors_de.properties
org/apache/tapestry5/corelib/components/Errors_fi_FI.properties
org/apache/tapestry5/corelib/components/Errors_fr_FR.properties
org/apache/tapestry5/corelib/components/Errors_hr.properties
org/apache/tapestry5/corelib/components/Errors_it.properties
org/apache/tapestry5/corelib/components/Errors_pt_PT.properties
org/apache/tapestry5/corelib/components/Errors_ru.properties
org/apache/tapestry5/corelib/components/Errors_sv_SE.properties
org/apache/tapestry5/corelib/components/Errors_zh_CN.properties
Are those translations in tapestry 5.0.16?
>
> For example, if you provide a localized message resource for a component or
> page of ur own application does it get picked up ?
The localization for the rest of the components is working fine. Only this
error header message remains in english all the time.
Regards
Jorge
signature.asc
Description: This is a digitally signed message part.
