This makes the "Rendering options" menu entry consistent with its
siblings in the same menu as well as with the section title with the
same name in Translations/es/options.xml.
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...
The 'enable-skyblend-desc', 'disable-skyblend-desc',
'enable-intro-music-desc', 'disable-intro-music-desc',
'enable-game-mode-desc', 'disable-game-mode-desc' and
'disable-ai-scenarios' translated strings have been removed from
Translations/en/options.xml in commit
4f660c96a5. Remove them from
Translations/nl/options.xml where they are still present.
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/
This translated string has been removed from Translations/en/menu.xml in
commit f3ac93b1ef. Remove its translations
from the other Translations/*/menu.xml files that still have it.
This translated string has been removed from Translations/en/menu.xml in
commit ff87cf4257. Remove its translations
from the other Translations/*/menu.xml files that still have it.
The feature is disabled by default. And when enabled the AI wake interaction is computed for aircraft closer than 5 nautical miles to the user aircraft.
Change to use the ports defined in the property tree when connecting from the dialog.
Ensure properties for ports are set to a valid (non zero, not null) value on dialog initialisation.
Add ability to change receive port from dialog firstly to see what it is and secondly to allow multiple fg sessions
