1
0
Fork 0
Commit graph

17 commits

Author SHA1 Message Date
Roman Ludwicki
f2756bff81 i18n: refresh the FlightGear-nonQt.xlf files
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.
2021-10-14 01:14:16 +02:00
Roman Ludwicki
a70e54fe10 i18n: update the Polish translation (the nonQt part) 2021-08-04 19:12:20 +02:00
Florent Rougon
d67feb5ef1 i18n: refresh the FlightGear-nonQt.xlf files
Propagate changes (walker-related, from the previous commit) in the
default translation to all FlightGear-nonQt.xlf files.
2021-08-04 10:20:04 +02:00
Florent Rougon
e634f37c82 i18n: refresh the FlightGear-nonQt.xlf files
Propagate changes in the default translation to all FlightGear-nonQt.xlf
files.
2021-08-04 00:05:34 +02:00
Slawek Mikula
0113e8c4ad Polish translation updates - next branch 2020-12-22 11:07:05 +01:00
Slawek Mikula
7894e36e42 - #2163 - polish translations - update 2020-06-21 13:54:06 +01:00
Florent Rougon
eb6dbb7797 I18N: Resync the Polish FlightGear-nonQt.xlf
Apparently, this file hasn't received the cleaned up source strings for
weather scenarios obtained since FGMeta commit c2a241c35[1]. The file
committed here was produced by simply running
fg-update-translation-files with what we currently have in FGData. I've
ignored changes to the other FlightGear-nonQt.xlf files because they
seem to all boil down to a modification of the order in which XML
attributes are given (what a PITA!).

[1] c2a241c357
2020-06-18 16:28:30 +02:00
Slawek Mikula
f81951b00d - #2163 - polish translations - update 2020-06-18 10:18:31 +01:00
James Turner
2aaf21d4bc Update non-Qt translations (including weather)
Add weather scenarios translations to the XLIFF files
2020-06-17 17:09:43 +01:00
James Turner
0e1da8d1f3 Sync non-Qt translations. 2020-06-15 16:39:39 +01:00
Florent Rougon
4adabbf809 i18n: refresh all FlightGear-nonQt.xlf files
The FlightGear-nonQt.xlf files are now in sync with
fgdata/Translations/default/*.xml.
2020-04-15 15:31:27 +02:00
James Turner
92446c3d39 Sync translations 2019-12-24 22:12:28 +00:00
James Turner
5c4f83b927 Polish translations by Slawek Mikula 2019-12-24 21:59:49 +00:00
Michael Danilov
113b635efa Translations: fix some typos and casing inconsistencies. 2018-10-15 23:25:07 +02:00
Florent Rougon
836eb64df0 Refresh the FlightGear-nonQt.xlf translation 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
2018-10-12 11:04:56 +02:00
Florent Rougon
f6637f495d Update all non-French XLIFF translation files
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.
2018-01-19 01:27:20 +01:00
Florent Rougon
2a9f70eb49 Add XLIFF 1.2 translation files
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).
2017-08-18 13:36:35 +02:00