Adding and Editing Schema Translations

To edit English schema names, open the emxFrameworkStringResource.properties file in any text editor. All properties files are located in Apps/Framework/VERSION/UserInterface.

Or:

To revise text for any non-English language:

1. Open the emxFrameworkStringResource_LANG.properties file using Microsoft Word.

   Word will prompt you to choose the file encoding necessary to load the file.

2. Click OK to accept the default.

Add string IDs for new schema and edit the IDs for renamed schema as needed. Follow the formats described in About Internationalizing.

If you are working with an English file, save the file normally.

Or:

If you are working with a non-English file:

1. Save the file as encoded text.
2. Click Yes to save it in text format, and then choose the same encoding that was used to load the file, which should be the default.
3. Click OK.
4. Convert the file to ASCII by running the following command:

   native2ascii -encoding CODE INPUTFILE OUTPUTFILE 
   

   CODE is the language encoding (shown in the files header).

   INPUTFILE is the name of the file you edited.

   OUTPUTFILE is the name of the file to be created. The output file will be in Unicode, which means it will contain letters followed by escape characters in place of the native characters.

   For example:

   native2ascii -encoding JIS 
   emxFrameworkStringResource_ja_Native.properties
   emxFrameworkStringResource_ja.properties 
   

Save the file in the Apps/Framework/VERSION/UserInterface and make a backup copy of the property files.

If you are running a J2EE implementation, remember to run the warutil and deploy the archive file.

Restart the application server.

Always make backups of string resources files that you configure. When you install a new version of the ENOVIA Business Process Services or applications, the string resources files will be overwritten with updated files.