I'm facing the exact same problem. I have a WEB-INF/AppName.properties
properties file that works fine, but as soon as I localise it - for
example renaming it to WEB-INF/AppName_sv.properties - it's not found
or not used and I end up with missing messages.
Is this a bug? I'm using 5.0.6 by the way.
/Olof
On 8/27/07, Nick Westgate <[EMAIL PROTECTED]> wrote:
> It works fine for me using the following files/code:
>
> app_ja.properties
> app_en.properties
>
> AppModule.java:
> configuration.add("tapestry.supported-locales", "en,ja");
>
>
> Page.html:
> <a t:type="ActionLink" t:id="jaLocaleLink" href="#">Japanese</a><br/>
> <a t:type="ActionLink" t:id="enLocaleLink" href="#">English</a><br/>
>
> Page.java:
> @Inject
> private PersistentLocale persistentLocaleService;
>
> ...
>
> void onActionFromJaLocaleLink()
> {
> persistentLocaleService.set(Locale.JAPANESE);
> }
>
> void onActionFromEnLocaleLink()
> {
> persistentLocaleService.set(Locale.ENGLISH);
> }
>
> Cheers,
> Nick.
>
>
> matt22 wrote:
> > I have similar problem.
> > I set locale in _persistentLocale, and cookie saved correctly, but no
> > more...
> > Injectes locale=en always
> >
> > Any idea?
> >
> >
> > Janko Muzykant wrote:
> >> hi there, i tried to localize my application putting all messages into 3
> >> global resource files:
> >>
> >> WEB-INF/app.properties [English messages]
> >> WEB-INF/app_pl.properties [Polish messages]
> >> WEB-INF/app_de.properties [German messages]
> >>
> >> according to documentation all these files should be named exactly like a
> >> filter ('app' in my case). i have added simple action links
> >> (http://www.nabble.com/T5---Changing-Locale-tf3376399s302.html#a9605166)
> >> to switch between languages. Additionaly i modified my AppModule to look
> >> like this:
> >>
> >> public static void
> >> contributeApplicationDefaults(MappedConfiguration<String, String>
> >> configuration)
> >> {
> >> configuration.add("tapestry.supported-locales", "pl,en,de");
> >> }
> >>
> >> Unfortunately no matter what language i set, everytime only app.properties
> >> file is taken into account. What's more interesting if I add localized
> >> template file for given component (eg. MyComponent_pl.html) it is
> >> recognized correctly so it is not a matter of bad language settings.
> >>
> >> Do you have any idea why global resource files with language appendixes
> >> (_en, _pl, _de) are ignored?
> >>
> >> jm.
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
