[T4.1.3] problems with localisation and possibly Prototype

[Henrik Schlanbusch <he...@enovate.no>]

Hi

I have to do some of the localisation
work in the java code, and run this
simple method:

public String getLocalisedMessage
      (String key) {
      return getMessages().getMessage(key);
}

The method does only return strings in 
english locale. 

The only special thing with my pages is that
they are loaded via the Ajax.Updater (Prototype).


So my question is, when loading pages through
Prototype, will the application servlet in some
way lose control over the users locale and reset
it to the default one?

The localisation works fine in the container page
that is not loaded through the Ajax.Updater.

Henrik



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: [T4.1.3] problems with localisation and possibly Prototype

[Henrik Schlanbusch <he...@enovate.no>]

The problem was that we had the two 
following files:

trans.properties (default locale)
and trans_no.properties

This always ended up with values from
the first file.

Then we renamed the files:

trans_en.properties
trans_no.properties

and it worked, why - I do not know...


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org