Re: Web Application Internalization Best Practices -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Have you considered putting the language-specific items in a language_en.css file and other languages in their own language_xx.css file with
rel="alternate stylesheet"?
That would seem fairly easy to implement and allow adding client/site .css language files with ease. I do this to provide different color themes and it is fairly quick and is superb for offering the ability to change items without a programmer being involved.

----- 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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.