Introducing a New Language

You can introduce new properties that target a language, a country, and a variant.

You need to provide a LANGUAGE and a VARIANT. LANGUAGE is the language code defined by the ISO-3166 standards. For example, "en" is English and "es" is Spanish. COUNTRY is the country code defined by the ISO-639 standard. For example, US is for the United States and UK is for the United Kingdom. VARIANT is up to you.

When introducing new languages, it is preferable to use the language extension only. Unless there is a need for translations for different countries, the translation should be done at the language level only.

Copy the original string resource properties file and rename it using the following convention:

ORIGINAL_FILENAME_LANGUAGE_COUNTRY_VARIANT.properties

For example:

emxEngineeringCentralStringResource_en_us_win.properties

Edit the properties in the file as needed for the language variant.
Save the string resource property files in the application server directory structure, for example, Apps/Framework/VERSION/UserInterface.

Depending on the request received from the user's browser, the program will look for:
```
emxEngineeringCentralStringResource_en_us_win.properties
```
then for:
```
emxEngineeringCentralStringResource_en_us.properties
```
then for:
```
emxEngineeringCentralStringResource_en.properties
```
then for:
```
emxEngineeringCentralStringResource.properties
```
When a string resource file for the language specified by the browser is not available, the string resource file for the language specified in Regional Options is used instead of the expected default .properties file. The system does not default to English.