cancel
Showing results for 
Search instead for 
Did you mean: 

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

jbaton
Champ in-the-making
Champ in-the-making
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 declared and thus not available in the drop list, it is still used.

Removing the webclient_fr_FR.properties and restarting makes thing back to EN usage


Environment
Server/JVM locale is FR
web browser accepts FR first
web browser cache is clean
bundle is 1.0
server is a rebuilded 1.1.1 OS version


Jerome
7 REPLIES 7

lgr
Champ in-the-making
Champ in-the-making
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.

jbaton
Champ in-the-making
Champ in-the-making
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

lgr
Champ in-the-making
Champ in-the-making
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 . Smiley Happy

Laurent.

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

Thanks!

Kevin

kevinr
Star Contributor
Star Contributor
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

kevinr
Star Contributor
Star Contributor
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

lgr
Champ in-the-making
Champ in-the-making
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.