580
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{Translation notice}} | {{Translation notice}} | ||
FlightGear supports localization, that is, showing the user interface in the user's native language rather than in English | FlightGear supports localization, that is, showing the user interface in the user's native language rather than in English. | ||
This page will help you translate FlightGear to a new language or improve the existing translations. | This page will help you translate FlightGear to a new language or improve the existing translations. | ||
Line 7: | Line 7: | ||
== What can be translated == | == What can be translated == | ||
The following parts of the simulator can be translated: | The following parts of the simulator can be translated: | ||
* the menus, splash screens, startup tips and the text shown when the <code>--help</code> command-line option is used (FlightGear 2.7.0 and later) | * the menus, splash screens, startup tips and the text shown when the <code>--help</code> command-line option is used (FlightGear 2.7.0 and later) | ||
* the shortcut file on Linux systems (FlightGear 2017.1 and later) | * the shortcut file on Linux systems (FlightGear 2017.1 and later) | ||
* the man pages (FlightGear 2017.3 and later). | * the man pages (FlightGear 2017.3 and later) | ||
* the built-in launcher (FlightGear 2018.3 and later) | |||
== How to translate | == How to translate == | ||
# Determine the two letter ISO 639-1 language code for the language you want to translate FlightGear to. A list can be found on the [https://www.loc.gov/standards/iso639-2/php/code_list.php Library of Congress Web site]. | # Determine the two letter ISO 639-1 language code for the language you want to translate FlightGear to. A list can be found on the [https://www.loc.gov/standards/iso639-2/php/code_list.php Library of Congress Web site]. | ||
# Check whether your language already has a subdirectory below [{{fgdata url|path=Translations}} the Translations directory]. If it does not, | # Check whether your language already has a subdirectory below [{{fgdata url|path=Translations}} the Translations directory]. If it does not, ask on the development mailing for the empty translation files to be created for you. (It's better to do this than copying an existing translation, because of data that will be accidentally included otherwise) | ||
# Open the | # Open the .XLF files in the subdirectory of your language and translate the English strings in them. You can edit the .XLF files in a text editor (such as Notepad++ or GEdit) but you can also use translation tools such as Qt Linguist or any XLIFF editor. | ||
# Start FlightGear to test your translation. By default, the simulator will select the locale of your operating system as the language to use; you can explicitly select a language using the command-line option <code>--language=<i>language code</i></code>. | # Start FlightGear to test your translation. By default, the simulator will select the locale of your operating system as the language to use; you can explicitly select a language using the command-line option <code>--language=<i>language code</i></code>. | ||
edits