The site Gaijin.at is funded by advertising.
By allowing advertising on the domain Gaijin.at you are helping to continue to offer free programs, scripts and online tools.
By translating one of the applications or scripts in an other language, you can support the dissemination and consequently the development of the applications and scripts published by Gaijin.at.
This page describes how to translate applications or scripts by creating your own language files.
Creating a new language file
Submit your language file
Open the subfolder named "Language" or "Languages" in the application folder. In this subfolder is at least one file named "English.lng" (or "english.lng" for PHP scripts), which is the language file for English. This file is maintained by the software author and is always up-to-date.
Language files are always plain-text files that can be edited with a text editor like Windows Notepad or PlainEdit.NET. Do not use Microsoft Word, WordPad or any other similar RTF editor.
Some applications needs UTF-8 encoded language files and other needs unencoded ANSI files. Please see the application overview below for more details.
Language files for PHP scripts must have the same character set and encoding as the script itself. In some scripts the encoding can be configured, so you should see at the script configuration and/or HTML header before translating a script. If you use UTF-8 as encoding the file must not have a BOM (Byte Order Mask).
The best way to start a translation is to make a copy of the file "English.lng" and rename it to your language, e.g. "Polish.lng" or "Portuguese.lng". So you can easily translate from English to your language.
If you have a text editor that supports syntax highlighting, switch on the highlighter for INI files. This should be a help while editing the language file.
Each entry in the language file must by written in one line. Do not use line breaks in the translated text. To insert a line break, there are some placeholders, described below.
Each entry starts with an identifier, like "Lang|Language" or "Lang.Language", followed by an equal sign. Do not change the identifier in any kind. After that, the translated text follows immediately. Lines beginning with a diamond sign ("#") are comments. It is unnecessary to translate these lines. There are sometimes version numbers in comments that mark lines added or changed in the specified version.
Some application supports different character sets (for ANSI). If so, you will find an entry called "Font|Charset" or similar. The possible values for the character set are listed below this entry in the English language file.
In ANSI files or PHP scripts there are usually the following placeholders:
In UTF-8 encoded language files there are usually the following placeholders available:
In this list you can see what file encoding which applications needs and if a BOM (Byte Order Mask) is required for the encoded file.
|Opened Ports Viewer||UTF-8||Yes|
If you have translated an application or a script, please send the language file per e-mail to me.
It is not required to include a language flag icon. The icon is added by me bofore I publish the language file on the product page.
For further questions you can contact me per e-mail.