All language files are in ASCII text, and can be modified with any good text editor. All you need to do is change the translations from the default values into the values which you choose. Here is an example
%s has %d post office messages Translation of: %s has %d post office messages %s password wrong or not a valid user Translation of: %s password wrong or not a valid user
Instruction | File After Modification | |
Translate all translation lines you wish the product to use. | %s has %d post office messages Translation of: %s hat %d Postmeldungen %s password wrong or not a valid user Translation of: %s password wrong or not a valid user | |
Remove the old 'Translation of:' phrases. | %s has %d post office messages %s hat %d Postmeldungen %s password wrong or not a valid user Translation of: %s password wrong or not a valid user | |
Comment out any translations you do not want the product to perform. | %s has %d post office messages %s hat %d Postmeldungen # %s password wrong or not a valid user # Translation of: %s password wrong or not a valid user |
NOTE CAREFULLY:
- Never remove any variables (e.g. %s, %d) from a translation, nor change the order in which they appear. This would cause incorrect display of messages, and instability of the product.
- A language file need not specify all phrases generated by the product. If you don't wish a certain phrase to be translated, simply comment it out or delete it.
- Never change the original phrase line of any pair, only the translation line. For example, in the default language file, you would only change lines like:Translation of: %s has %d post office messages
How Do I Use Language Translation With DLIST?
When creating your lists.dat file, simply add a language_file setting to each list you want translated. This setting specifies the location of the language file to use for that list. For example:
list newproducts
title Discussion of new products
language_file german.dat
The language file to use: dlist_lang.dat