topic After installing Lang pack, which lang setting gets english? in Alfresco Archive

After installing Lang pack, which lang setting gets english?

teemus — Wed, 09 Dec 2009 14:52:23 GMT

Background:I have installed a translation pack for Share. Properties are in xx_XX format.Problem:I can't get default English translation anymore. I've tried 'en', 'en_EN' and 'en_US' settings and none works. If I replicate all default files to en_US format, then 'en_US' setting works and I can swap

Re: After installing Lang pack, which lang setting gets english?

gronfelt — Wed, 09 Dec 2009 16:44:35 GMT

If I select English as the preferred language in my browser I get the strings from the default files (the ones without any language and location codes). This works in Firefox at least, no matter if I select en or en-us as preferred language.

I have only one language pack installed, besides the default files and that language pack is non-english.

Re: After installing Lang pack, which lang setting gets english?

mrogers — Wed, 09 Dec 2009 17:47:07 GMT

Is it a typo en-us? Should it not be an underscore character in a locale?.

Re: After installing Lang pack, which lang setting gets english?

gronfelt — Wed, 09 Dec 2009 18:22:56 GMT

Firefox calls it [en-us].

Re: After installing Lang pack, which lang setting gets english?

teemus — Thu, 10 Dec 2009 10:10:58 GMT

Is it a typo en-us? Should it not be an underscore character in a locale?.

Firefox sends locales with hyphen but DispatcherServlet replaces '-' char with '_', so that's not a problem.

If I select English as the preferred language in my browser I get the strings from the default files (the ones without any language and location codes). This works in Firefox at least, no matter if I select en or en-us as preferred language.

That's because Share can't find translation you requested and defaults to default files (English in this case). I'm guessing your JVM's default locale is 'en_US'. Try to change it to say, se_SE.

But if your JVM's locale isn't en_US (or any en_XX?) you can't get English anymore. On Web Client (legacy(?) browser) v1 they had issue with same kind of problem. They solved it with build script that replicates all properties to en_US (don't remember for sure, but some English locale) files as well.