Not touching the Polish files since they appear to be up-to-date (the
scripts also produced changes for these files but they don't seem very
meaningful; I can of course send the resulting files to Roman if he
wants to inspect the changes).
This brings a developer comment to the FlightGear-Qt.xlf files that will
hopefully draw the translators' attention on the fact that they should
put the *up-to-date* address of the "getstart" manual in their language
(use correct address + two occurrences of 'en' to change).
Remove no more used `menu/interface-config`.
Add `menu/highlighting`, `menu/vr-options`, `options/system-time`,
`options/gmt`, `options/local-aircraft-time`.
Correct tip text from "Hold [Shift] while looking around to move the
view up, down, left or right" to "Hold Ctrl ...".
Corrections for Polish nonQt translations.
The files
Translations/zh_CN/options.xml
Translations/zh_CN/tips.xml
Translations/zh_CN/menu.xml
Translations/zh_CN/sys.xml
were already removed as part of commit 0c655af7d1 but were recently
readded by mistake (commit 2a30862e31). Remove them again...
(the new translation infrastructure only needs the master translation
defined by Translations/default/*.xml and the language-specific .xlf
files)
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).
The tips are not enabled in Translations/locale.xml yet, because the
font currently used to display them in FlightGear's splash screen
doesn't have the required glyphs (see [1] for more details). Better
display English tips than empty rectangles on the startup screen.
Merging this in disabled state now has a few advantages compared to
waiting for the font problem to be solved:
- avoid that someone ignoring the merge request[1] duplicates the
translation work;
- allow easy updating of these tips;
- make sure they aren't forgotten when FG's localization files are
converted to XLIFF format.
Ship an empty Translations/zh_CN/options.xml, otherwise
'fgfs --language=zh_CN --help --verbose' won't work at all.
[1] https://sourceforge.net/p/flightgear/fgdata/merge-requests/92/
