Re: Web Application Internalization Best Practices

css is Cascading Style Sheets, so lets cascade them? :)

<link type="text/css" rel="stylesheet" href="Website.css">
<link type="text/css" rel="stylesheet" href="Website-en.css">
<link type="text/css" rel="stylesheet" href="Website-brown.css">

The first .css file provides the universal elements (sizes, locations, etc).
The second .css file would be where I would put language elements.
The third .css file would be for color themes.

This allows the programmer to walk away from the completed application and let the artsy-fartsy people add their colors, illuminations, etc. Also it allows each branch office to create and maintain their own language files.

FWIW.


On 2/5/2013 5:34 PM, Nathan Andelin wrote:

Booth Martin just shared a technique off-line, using the CSS "content" property. w3schools has some good references. The idea is to use external .css files to define language specific content.

http://www.radile.com/rdweb/temp/content.html


View the page source to see how field labels are pulled from an external .css file by using a "class=" reference. Since "class=" supports a list of classes, one set could be used for traditional styling, and a different set for language-specific content.

Nice find, Booth.

-Nathan