To collect translated files efficiently and let users easily translate our programs, we created a GitHub Repository, where translators can discuss translations and upload completed translations.

Find all our programs’ language files in the Repository. If your language is already there, you can help us proofread it. If not, please help us translate it. You can translate the language file directly or use our translation tool (coming soon) available here.

Use this form to register as a translator. Registration is not required, but it would be nice to keep track of how many volunteer translators we have and their skills. Anonymous translators are also welcome. Now, before you can start translating, there are a some recommended tools you must know about. You can read more about or download them below.

Required Tools

• Notepad3 to translate a language file directly .
• GitHub Desktop to clone or commit new translations.

Clone or Download the ‘Translate’ Repository

Before you start, please read, how to clone or download a repository. Alternatively you can download the program you want to translate. However, we recommend using the Translate repository for easy submission.

Getting Started with Language Files

Now, you need to find the en.ini language file. This will be the file you need to translate. For example; to translate Complete Internet Repair, locate the en.ini at Language\ComIntRep\en.ini. Before you start translating, please read the Documentation on language file directory structure and naming language files. Open the en.ini file in your favorite text editor (we recommend using Notepad3). Save the langauge file as the country code, followed by .ini. For example; save as ru.ini for a Russian translation. Before you start translating; lets take a look at the language file structure:

Language File Header

At the top of all language files, you will find the header section. Line 2 (do not translate) indicates the type of file. Line 4 is the date, the translation was created, line 5 is the author of the language file (normally you if you are creating the language file). And line 6 is a link to your home page, if you have one. Under the Header section, you will see the Main section. Normally nothing needs to change here. It is used to indicate the Rizonesoft software name and version the language file is for.

Language Section

The Language section is important for the program to detect the language it is loading. Here you will enter, next to Name = , the name of the language and next to Code = the language code (find the correct language code here). The last setting here, indicated the Encoding of the text file. Language files should always be in Unicode; please do not change this. Please do not change anything before the equal sign!

Translations Section

Do not change anything in the Translations section! This section is used by Rizonesoft Translate to know what translation sections to look for in the language file.

Start Translating

 

The sections after the Translations section is where you will start translating. But before you jump into it, read the following guidelines:

Each file contains many strings. Each string has three elements: Name, =, followed by a word or paragraph. (For example, Tip_Title_Donate = Donate to our Cause or Label_Home = Homepage) The first part of the name normally indicates the control you are translating. For example; when it starts with label_ you are translating a label control.

Sections

All strings are categorized in different sections, within [] symbols. For example, [About] or [Custom].

Translatable Text

Translators only need to translate the words to the right of the equal sign (=). No changes should be made to the left of the equal sign (=). For example; Help_Update = Check for &updates Please just translate Check for &updates and do not translate or make any changes to Help_Update =.)

Encoding

All language files should be saved in Unicode format for correct display. To make sure the language file is in Unicode format; open it in Notepad3, click on File, go to Encoding and make sure Unicode is selected.

Variables and Access Keys

Do not remove or translate the & sign in menu items. It is used to underline keyboard shortcuts and access keys. For example; Check for &updates will be displayed as Check for updates.

Do not translate program variable. Program variables are between %{} symbols. For example; %{Program.Name}

Do not translate new line indicators, like \rn, \r and \n

Do not translate or change the variables like %s, %d, %u, %.0n, {0}, %d%%. Any change to them (even adding a space between the variables like changing %s to % s) will cause program malfunction.

Submitting a Translation

Alternatively, you can send the translated language file to translate@rizonecloud.com.