Menu
▾
▴
Home
How to write a translation for NumeRe
This is a short introduction in writing a translation for NumeRe. All you need is a simple text editor, the basic language files and a bunch of time. If you have open questions, please contact the administrator of this project.
Project Members:
- Adji Arioputro
- Arjun Raveendran
- Ayoub Selmi
- Erik Hänel (admin)
- Fabian Wunder
- Jonas Jansen
- Katharina
- Philipp Doblhofer
- Raphael Zehner
- Rudolf Brausemann
Contents of a translation file
A translation file contains three major parts: comments (indicated by a # at the beginning of a line), identifiers (usually in uppercase letters and at the beginning of a line) and the actual language strings (after the identifiers and a additional =, probably containing some place holders %%1%% or %%COMMON_YES_NO%%). Leading or trailing whitespaces/tabulator characters in the language strings or whitespaces between an identifier and the equal sign will be ignored:
#This is a comment
THIS_IS_AN_IDENTIFIER=This is the actual language string and a %%PLACE_HOLDER%%
- Place holders containing only numbers will be replaced during the execution of NumeRe and with the relevant message part.
- The others will be replaced during language loading (at start up) with the language strings of the referenced identifiers, if they can be found.
NumeRe contains two major language files: <>/lang/main.nlng and <>/lang/error.nlng. The first contains all the language strings for usual interaction, whereas the second contains all error messages. There are three further files prefixed with tmpl_*.nlng. These contain templates for scripts, plugins and files. Note, that the comments in these files will be copied to the generated file.
Writing a translation
Writing a translation is quite easy. All you have to do, is to translate every language string you're finding in the language files to your desired language. Please keep in mind that NumeRe is currently not capable of displaying Unicode, so stick to the standard ASCII alphabet.
The special dollar sign $ represents a line break in the language string. If you want to use the dollar sign as a literal character, you have to escape it with a backslash: \$
You may add your own identifiers, if you like to. But these identifiers can only be used to replace place holders in other language strings during loading time. For example, you could do something like
LANG_STRING=language string
THIS_IS_AN_IDENTIFIER=This is the actual %%LANG_STRING%% and a %%PLACE_HOLDER%%
to obtain the upper example. But, we'd like to beg you that you prefix your own identifier with USER_* that they won't interfere with our standard identifiers.
As an additional hint: always keep an backup of your translation. User files are planned, but not yet implemented. There is a small chance that your translation will be overwritten during an update. If you translate the standard files in <>/lang/*.nlng, then your translation will always get overwritten.
Submitting a translation
The submitting process is not yet defined. As a temporary work-around you may submit your translation via e-mail to the administrator.
