Interface Language Support

DmitryBarashev · April 3, 2017, 1:35pm

We use Crowdin web service for translations, so you need to register there and choose Bulgarian translation

You can find the guidelines here:

bardsoftware/ganttproject/blob/wiki/TranslationGuidelines.md

# Translation guidelines #
#### Preamble ####
GanttProject interface is translated to 20+ languages thanks to community efforts. If you volunteer to create a translation to your language, please read the text below.

### Short introduction ###
_If you know how localization works in Java and what resource bundle is, you may skip this section_

Strings which appear in GanttProject interface are stored in .properties files, one file per language. Such files are called _resource bundles_. A .properties file is a text file with key-value pairs. GP code uses keys to fetch values from the file matching the selected interface language.

### How to translate ###
In GanttProject 2.6 release cycle we're using [Crowdin](http://crowdin.net) - a web service for software localization. You don't need any software except a web browser (and probably GanttProject itself)

To edit a translation, you need to create an account on CrowdIn (they also have an option of signing in with Google and Facebook accounts). Then go to GanttProject page: http://crowdin.net/project/ganttproject find your favorite language, click it, choose "Gp 2.6 Brno" in the file list and start translating. You don't need any special permission or access rights, but I will appreciate if you [drop me a note](http://www.ganttproject.biz/about) before you start your work.


CrowdIn shows you a list of keys and their English values, which are grouped by translation state (untranslated go first and are marked with red bullets) and sorted alphabetically by key name inside each group. Your task is basically to scan through a list of untranslated keys and type value for your language in a _TRANSLATION_ box (don't forget to press _COMMIT TRANSLATION_). To do it properly, you need to know the context where a string is used. Very often you may guess the context from the key name (you see the name just above the translation text area), e.g. _baseline.dialog.hide_ means that it is used in a baseline dialog on a button which hides), but sometimes the context is not clear. Don't hesitate to ask about the context in the comments. There are already comments for some keys. Find the context in GanttProject UI and make sure that your translations will fit into the layout and will look consistent with the surrounding elements.

In some values you may find placeholders for parameters (e.g. _File {0} was modified since the last access_). You need to keep all placeholders, as they will be filled with values in the runtime. Don't hesitate to ask if their meaning looks unclear.

### How to test ###

This file has been truncated. show original