topic Re: 1.1.1 - I18N misbehaving : using JVM's default locale ? in Alfresco Archive

1.1.1 - I18N misbehaving : using JVM's default locale ?

jbaton — Tue, 20 Dec 2005 16:09:02 GMT

Hi all,The misbehaviour is that UI is automatically localized and login's language selection is not taken into account.On a fresh rebuild, if ever a webclient_fr_FR.properties file is present it is used no matter what I select on the login page (btw, changing lang resets password).If FR lang. is not

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

lgr — Tue, 20 Dec 2005 19:50:08 GMT

Hello Jerome,

This were a bug, but i don't know if it has been resolved since v1. I've not seen any issue about it in Jira.

http://www.alfresco.org/forums/viewtopic.php?t=347&start=0&postdays=0&postorder=asc&highlight=frfr
and
http://www.alfresco.org/forums/viewtopic.php?t=148&highlight=enen#2171

Laurent.

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

jbaton — Wed, 21 Dec 2005 08:51:10 GMT

Laurent,

Thanks for the URLs.

As for what I've cross-read, all default files should be renamed but that causes an issue (not explained) and lots of stack traces at start + CIFS access KO.

It was quite a surprise for me to see that I18N does not work properly in Alfresco. I intended to deploy it in FRench as the users are FR-speaking but I think the start will be in EN. That's a pity indeed however in a technical area people are used to EN.

I was using version 1.1.1 when I got this error.

Jerome

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

lgr — Wed, 21 Dec 2005 10:01:44 GMT

Jerome,

Because of the issue, the start will be in french, and the whole Alfresco will be in french.
You won't notice any word in english, even if you want to .

Laurent.

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

kevinr — Wed, 21 Dec 2005 10:41:28 GMT

Oui. We'll take a look at this issue today.

Thanks!

Kevin

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

kevinr — Wed, 21 Dec 2005 11:15:00 GMT

Hi,

OK we've found the problem. You need all the "default" properties files (with no locale extension) to be duplicated to have an "_en_US" extension e.g.

webclient.properties

copied to a new file:

webclient_en_US.properties

We tested this and it fixed the problem.

Applogies for this problem. I think we will create an ant task as part of our build scripts that duplicates the default language files to add the _en_US onto each.

Thanks,

Kevin

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

kevinr — Wed, 21 Dec 2005 12:38:28 GMT

I've improved our ANT build scripts to perform the copy of the default properties files to _en_US as part of the build process.

Cheers,

Kev

Re: 1.1.1 - I18N misbehaving : using JVM's default locale ?

lgr — Wed, 21 Dec 2005 12:40:06 GMT

I confirm, that works well on v1.1. I haven't checked it on v1.1.1, but i'm also sure it works.

(and when you modify the language selection box, it changes every message on connection screen as well, that's perfect !)

Thanks a lot,

Laurent.