Modifying Text and Error Properties Files for New Languages

The text.properties and errors.properties files are located in PS_HOME\webserv\web_server\applications\peoplesoft\PORTAL.war\WEB-INF\psftdocs\DBdomain.

To modify text.properties and errors.properties files for new languages:

Edit the base text.properties file to add a language title for the new language title in the correct alphabetical position in the file.

For example, for Quechua, its language title is entered in the following position:
```
#language titles
...
psNOR=Norwegian
psPOL=Polish
psPOR=Portuguese
psQUE=Quechua
psROM=Romanian
psRUS=Russian
...
```
Copy the modified base text.properties and errors.properties to two files named after your three-letter language code in this format: filename_XXX.properties in which XXX is the three-letter language code.

For example, for Quechua, the file names would be text_QUE.properties and errors_QUE.properties.
Set language-specific properties in the text_XXX.properties file.

See Understanding the Addition of New Language Definitions.
Translate the non-setting specific information in the text_XXX.properties and errors_XXX.properties files as needed for your new language.
Run the native2ascii utility to convert your translated properties files if needed.

See Adding New Language Codes to the System.
Add the new language to each of the language-specific versions of text.properties files that are relevant to your system.

Note:

Translate the new language title to each relevant language, run native2ascii on a temporary file that includes the translated language title, and copy and paste each encoded translated language title into the appropriate text_XXX.properties file.
After you have modified the text and error properties files, you must restart the web server.

Text Property File Variables

You must set the following properties in the text_XXX.properties file:

Note:

Do not translate any of the values you enter for these properties.

Variable	Description
active	Set the ISO language code. Preface the active variable with the two character ISO code for the language and set the variable equal to -s. For example: qu_active=-s
direction	Set the direction that text is read. The valid options are: ltr. Left to right. rtl. Right to left.
alignstart	Set the starting point. The valid options are: right left The value you select must be consistent with the directionality that you specify. For example, if you set the direction variable to ltr, then you must set the alignstart variable left. If you set the direction variable to rtl, then you must set the alignstart variable to right.
alignend	Set the ending point. The valid options are: right left The value you select must be consistent with the directionality that you specify. For example, if you set the direction variable to ltr, then you must set the alignend variable right. If you set the direction variable to rtl, then you must set the alignend variable to left.

The following example shows a text.properties file entry for French:

fr_active=-s
direction=ltr
alignstart=left
alignend=right

File Format

Properties files are saved in a special format. US-ASCII Unicode characters must be represented by a Java-style Unicode escape sequence in the format \udddd, where dddd represents the hexadecimal value of the Unicode character.

native2ascii

The native2ascii utility, a part of the JDK (Java Development Kit), can be used to transform your properties files into the correct format after it has been translated.

For example, to convert a non-European text.properties file, you will need to run the following:

native2ascii −encoding encoding sourcefile destinationfile

Note:

Use the destination properties files that have the Java-style encoding.

Note:

For more information about the native2ascii utility, refer to the oracle's online documentation.