In our Swedish example, the line
There is a localization/caption editor available for download from:
The LANG= attribute for the HTML tag will follow the language for the captions being used. If the language has a default character flow of right to left, then a DIR=RTL attribute tag will be added to the HTML tag.
The width of the menu pads are controlled by the constants in the captions.properties file. The constants names all start with MPW. For example, mpwHelp controls the width of the Help menu pad.
If your language uses characters that are not in the ISO-8859-1 character set, then you will have to create an intermediate file and use the Java SDK native2ascii conversion program. For example, you are translating Polish for which the native character set is ISO-8859-2. Copy captions.properties to a file named "polish" and perform your edits. The editor that you use will have to save the characters in the character set for your language. Next, run the command:
native2ascii -encoding UTF-8 polish captions_pl.properties
In the example above, the translated file is saved by the editor in UTF-8 format. If you use a different file encoding, replace UTF-8 with the encoding you saved the file in.
When you are running Connect Daily, a missing caption will generate a Java Exception. You can check to make sure that you have all required captions. This is particularly important if you have self-translated caption files and you are upgrading to a newer version of Connect Daily. To use the bundleChecker run the following command:
java -classpath <path to cdaily.jar> \
The bundleChecker program will list any missing captions on the screen.
The master captions.properties file contains notes on the usage and substitution parameters of the strings. If you are unsure of the parameters or how a caption may be used, check the master captions file.