I haven't made much attempt to support multiple languages except we're using an API to retrieve all user messages from a DB table. Our applications generate HTML from templates which include a fair amount of embedded English text for field labels and hyperlinks which would need to be translated to other languages. We could probably write a utility to do a translation.
During development, we use a CL command to parse and pre-load all of our HTML templates into a multi-member PF-SRC file, so we could use a Job's library list to point to language-specif HTML templates.
My rationale for NOT storing UI elements in some sort of database repository or "resource bundle" is because I didn't want our applications to take an admittedly small performance hit in order to dynamically insert language-specific text into the output stream.
-Nathan
----- Original Message -----
From: "Holm, Paul" <pholm@xxxxxxxxxxxxxxxxx>
To: web400@xxxxxxxxxxxx
Cc:
Sent: Monday, February 4, 2013 11:48 AM
Subject: [WEB400] Web Application Internalization Best Practices
All,
We are reevaluating our approach to I18N for web applications. This
involves supporting multiple languages for all our browser UI labels and
messages and error messages.
Our requirements are to be Operating System and Database Independent.
Today we utilize Java and resource bundles but want to see if there are
better approaches.
What are others doing?
What are the other best practices? Gotchas?
Thanks, Paul Holm
www.planetjavainc.com
midrange.com
