Considerations for a system with more than one language

Identifying the code page in docCustomDefinitions.xml

At the top of the docCustomDefinitions.xml file, make sure you correctly identify the code page so that the file can be processed correctly when you update configuration files. Here are some examples of valid code page declarations:

• <?xml version="1.0" encoding="UTF-8"?> (specified in the sample file)
• <?xml version="1.0" encoding="iso-8859-1"?> (Latin-1)
• <?xml version="1.0" encoding="shift_jis"?> (Japanese)

Making sure the document properties names files are in ISO-8859-1 format

The docCustomDefinitions.properties file and docCustomDefinitions_language.properties files must contain only Latin-1 or Unicode-encoded (\udddd notation) characters. If you created your docCustomDefinitions.properties and docCustomDefinitions_language.properties files in a different format (such as Shift JIS or UTF-8), you must convert each file to ISO-8859-1 before placing it in the /aiw/aiw1/config (UNIX-based operating systems) or C:\aiw\aiw1\config (Windows) directory. Although you can convert the files using whatever method you choose, this section describes one possible method: using the native2ascii utility.

The native2ascii utility converts text to Unicode Latin-1. It is shipped with RICOH ProcessDirector.

• On Linux, the native2ascii utility is at /opt/infoprint/ippd/jre/bin.
• On Windows, the native2ascii.exe utility is at C:\Program Files\Ricoh\ProcessDirector\jre\bin.

The utility is also provided with the Java Development Kit, which you can download from this site:

http://www.oracle.com/technetwork/java/javase/downloads

Instructions for using the utility (for Java 6) are here:

http://download.oracle.com/javase/6/docs/technotes/tools/#intl

For example, to convert a UTF-8 file named docCustomDefinitions-UTF8.properties, you can use this command:

native2ascii -encoding UTF-8 docCustomDefinitions-UTF8.properties > docCustomDefinitions.properties