Update them from the latest contents of the
$FG_ROOT/Translations/default/*.xml files (default translation).
This was done with:
fg-update-translation-files \
--transl-dir="/path/to/fgdata/Translations" \
merge-new-master de en_US es fr it nl pl pt zh_CN
The reason French is treated specially is that I completed the
translation up to 100% coverage in Qt Linguist as a test case for the
new translation infrastructure, and have no desire to convert this
translation work to the legacy FlightGear-specific XML format. But of
course, this complete translation is in XLIFF 1.2 format (since it is
saved by Qt Linguist) and thus can't be used by FlightGear yet.
On the other hand, for the other languages, no translator ever modified
the XLIFF files, therefore the best way to proceed for is that people
continue to work with the legacy FlightGear-specific XML format until
the new translation infrastructure is ready (this way, their work is
visible in FlightGear). The Python-based tools in FGMeta allow one to
automatically convert from this legacy format to the XLIFF 1.2 format,
as explained in fgmeta/python3-flightgear/README-l10n.txt. Which is
precisely what this commit does.
These files have been generated from the existing XML files (cf.
fg-convert-translation-files in fgmeta).
Translations/en_US/FlightGear-nonQt.xlf is for a proper English
translation, where for instance "found %n airport(s)" would have two
plural forms, "found %n airport" and "found %n airports" (most
non-plural strings can be taken verbatim from the default translation,
and at this point there is no plural form at all yet).
It's not that leading or trailing whitespace in translated strings is
forbidden *in principle*, but I think it is unwanted in most of these
cases. Remove these spaces that could cause confusion, possibly useless
work for translators and/or ugly displays.
The only cases where the spaces seem to have been intentional are the
trailing ones in menu labels (Translations/*/menu.xml), in order to
obtain right alignment of keyboard shortcuts. However, there is only one
case in English where the spacing looks approximately correct
(File -> Reset). In all other cases, it looks awful. And this poor way
of obtaining right alignment gives bad results in other languages, where
translators use the same number of spaces as in English.
Bottom line: if right alignment of keyboard shortcuts is indeed desired
in the menu labels (I think it is), it should be done in a smarter
way...
Use RIGHTWARDS ARROW for each arrow, surrounded by two NO-BREAK SPACE
characters. This prevents line breaking in the middle or at the edges of
such arrows.
Also explicitly specify the UTF-8 encoding for Translations/en/tips.xml,
even though this is implicit with XML when unspecified.
Also remove <intl include="Translations/locale.xml"/> from
preferences.xml. Something equivalent based on readProperties() is done
in FlightGear (cf. FGLocale::FGLocale() in
flightgear/src/Main/locale.cxx).
Add the translation for the <download-dir-desc> switch and update the one
for the <metar-desc> one.
Also change "tempo" to "orario" in menu.xml to be consistent with the
term choice in options.xml.
Run script to identify missing/obsolete items:
de/options.xml is missing 192 translation(s).
de/menu.xml is missing 20 translation(s).
es/options.xml is missing 12 translation(s).
es/menu.xml is missing 78 translation(s).
fr/options.xml is missing 0 translation(s).
fr/menu.xml is missing 0 translation(s).
it/options.xml is missing 212 translation(s).
it/menu.xml is missing 78 translation(s).
nl/options.xml is missing 54 translation(s).
nl/menu.xml is missing 1 translation(s).
pl/options.xml is missing 81 translation(s).
pl/menu.xml is missing 76 translation(s).
pt/options.xml is missing 212 translation(s).
pt/menu.xml is missing 86 translation(s).
