476
edits
Command line options: Difference between revisions
Jump to navigation
Jump to search
→General Options: Update documentation of --language
(→General Options: Update documentation of --language) |
|||
| Line 88: | Line 88: | ||
<code>--language=code</code> | <code>--language=code</code> | ||
::Select the language for this session. Available codes: <tt>ca</tt>, <tt>de</tt>, <tt>en</tt>, <tt>es</tt>, <tt>fr</tt>, <tt>it</tt>, <tt>nl</tt>, <tt>pl</tt>, <tt>pt</tt>, <tt>ru</tt>, <tt>tr</tt>, <tt> | ::Select the language for this session. Available codes: <tt>ca</tt>, <tt>de</tt>, <tt>en</tt>, <tt>es</tt>, <tt>fr</tt>, <tt>it</tt>, <tt>ka</tt>, <tt>nl</tt>, <tt>pl</tt>, <tt>pt</tt>, <tt>ru</tt>, <tt>sk</tt>, <tt>tr</tt>, <tt>zh_CN</tt>. | ||
:: In FlightGear 2024.2, <code>--language=default</code> is also supported and selects the ''default translation'', also known as “engineering English”. This “translation” contains exactly the English strings that translators translate; these have only one form for both singular and plural, contrary to the English translation loaded by <code>--language=en</code> which, starting from FlightGear 2024.2, can show different forms depending on a “cardinal number” (this applies to those strings that have been declared with <code>has-plural=true</code> in the default translation, i.e. in one of the XML files from <tt>[[$FG_ROOT]]/Translations/default</tt>). | |||
:: In FlightGear 2024.2, in case the locale specified with <code>--language</code> or via user locale settings doesn't match any of the locales defined in <tt>[[$FG_ROOT]]/Translations/locale.xml</tt>, the effect is the same as with <code>--language=en</code>, i.e. proper English with singular and plural forms that may differ. | |||
<code>--launcher[={true|false|1|0|yes|no}]</code><br/> | <code>--launcher[={true|false|1|0|yes|no}]</code><br/> | ||