Translating JAMS
Line 3: | Line 3: | ||
where key is some string identifier and value a term in a certain language. An example would be: | where key is some string identifier and value a term in a certain language. An example would be: | ||
ExplorerDisabled=JAMS Explorer is diabled in this version! | ExplorerDisabled=JAMS Explorer is diabled in this version! | ||
− | The interfaces are translated by replacing the right part with the translated terms. In order to preserve a proper generation of combined terms, leading and trailing whitespace characters must be kept. | + | The interfaces are translated by replacing the right part with the translated terms. In order to preserve a proper generation of combined terms, leading and trailing whitespace characters must be kept. The results must be stored in a file following the naming convention |
+ | <name>_<language code><country code>.properties | ||
First of all, make sure you have the JDK java development package installed. The files that I am referring to are part of the new JAMS version which has a new package structure. Please install the current version of JAMS that is available at http://jams.uni-jena.de. Afterwards, you can edit the language files by following the these steps: | First of all, make sure you have the JDK java development package installed. The files that I am referring to are part of the new JAMS version which has a new package structure. Please install the current version of JAMS that is available at http://jams.uni-jena.de. Afterwards, you can edit the language files by following the these steps: | ||
Line 10: | Line 11: | ||
* change into the directory containing the JAMS *.jar files (<code>cd c:\program files\jams\lib</code>) | * change into the directory containing the JAMS *.jar files (<code>cd c:\program files\jams\lib</code>) | ||
* extract the JAMS language file by running | * extract the JAMS language file by running | ||
− | <code>jar -xf jams-main.jar resources/ | + | <code>jar -xf jams-main.jar resources/JAMSBundle.properties</code> |
− | * edit the file resources\ | + | * edit the file resources\JAMSBundle.properties as you like, save it and rename it to resources\JAMSBundle_??.properties, where ?? stands for |
* write the modified file back to the archive by running | * write the modified file back to the archive by running | ||
<code>jar -uf jams-main.jar resources/JAMSBundle_pt.properties</code> | <code>jar -uf jams-main.jar resources/JAMSBundle_pt.properties</code> |
Revision as of 19:35, 22 October 2009
You can translate the JAMS graphical user interfaces by editing language files. Those files contain lines of the format
<key>=<value>
where key is some string identifier and value a term in a certain language. An example would be:
ExplorerDisabled=JAMS Explorer is diabled in this version!
The interfaces are translated by replacing the right part with the translated terms. In order to preserve a proper generation of combined terms, leading and trailing whitespace characters must be kept. The results must be stored in a file following the naming convention
<name>_<language code><country code>.properties
First of all, make sure you have the JDK java development package installed. The files that I am referring to are part of the new JAMS version which has a new package structure. Please install the current version of JAMS that is available at http://jams.uni-jena.de. Afterwards, you can edit the language files by following the these steps:
- open a DOS command prompt
- change into the directory containing the JAMS *.jar files (
cd c:\program files\jams\lib
) - extract the JAMS language file by running
jar -xf jams-main.jar resources/JAMSBundle.properties
- edit the file resources\JAMSBundle.properties as you like, save it and rename it to resources\JAMSBundle_??.properties, where ?? stands for
- write the modified file back to the archive by running
jar -uf jams-main.jar resources/JAMSBundle_pt.properties
- delete the extracted files by running
rmdir /s/q resources
- extract the JUICE language file by running the command
jar -xf jams-ui.jar resources/JUICEBundle_pt.properties
- edit the file resources\JUICEBundle_pt.properties as you like
- write the modified file back to the archive by running
jar -uf jams-ui.jar resources/JUICEBundle_pt.properties
- delete the extracted files by running
rmdir /s/q resources