----- Original Message -----
From: "John Colvin" <[EMAIL PROTECTED]>
> I have devloped an application, though, not in turbine that had 3
> languages
> associated with it.
[...]
> String lang = (String) session.getAttribute("UserLanguage");
> Properties props = (Properties)
> session.getAttribute("LangaugeProperties");
> String title = props.getProperty(lang + "_TITLE");
I don't understand why you did this instead of using the Turbine
localization service ? Is there any reason ?
The localization service allows you to pick up the right bundle based on a
locale and even the Accept-Language header. As a standard the localization
for bundles follow a naming pattern with region and language and fallback to
the default one as described here:
http://java.sun.com/j2se/1.3/docs/api/java/util/ResourceBundle.html
Stephane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
