10 commits

Author	SHA1	Message	Date
James Hogan	ba9465972b	Add enable-vr and disable-vr options ... Add command line options for enabling and disabling VR. These are placed at the end of the features section for want of a better place.	2021-08-23 16:12:16 +01:00
Julian Smith	8c7390495b	Added help text for new --load-tape=<url> support.	2021-02-18 21:09:15 +00:00
Julian Smith	6db71f789c	Added -h help text for --composite-viewer option.	2020-11-22 08:22:44 +00:00
Julian Smith	87d406dc6e	Clarified documentation for the --load-tape option.	2020-10-31 23:42:03 +00:00
Julian Smith	a17bbe1fb1	Added help item about --load-tape arg.	2020-06-06 09:56:30 +01:00
Julian Smith	16d5f53900	Include info on --launcher option in --help output.	2020-05-01 20:11:03 +01:00
Stuart Buchanan	7eb7bd8576	Help text for --carrier-abeam option.	2020-04-05 23:22:31 +01:00
Florent Rougon	853a28b319	Fixes in the default translation ... - Add <cycle-gui> in Translations/default/menu.xml - Fix for <dme-desc> in default/options.xml, which mentioned the ADF instead of the DME. Thanks to Michael Danilov for these fixes.	2018-10-12 10:56:08 +02:00
ThorstenB	63f8cf4554	Add description for new protocol parameter.	2017-11-26 21:15:46 +01:00
Florent Rougon	2f420d4c5c	Translations: rename Translations/en to Translations/default ... This is mainly to make it clear that the "translation" in (after this commit) Translations/default, a priori corresponding to en_US, has a special status: it acts as the source describing the set of translatable strings, each with its id (an XML tag name) and numeric index (a PropertyList index, often 0 but not always). In the upcoming i18n infrastructure, the files in Translations/default will be used to: - detect all translatable strings (~ string extraction); - detect obsolete translated strings (those in XLIFF files but not in Translations/default anymore); This will allow a script to update the XLIFF files containing real translations, i.e., update the source strings and possibly remove obsolete entries. So, the files in Translations/default have a special "master" status in this process, and are technically quite different from those in Translations/de, Translations/es, Translations/fr, etc. The latter XML files (those not in Translations/default) will be replaced with their XLIFF equivalent, by the way (conversion script already working). See discussion at <https://sourceforge.net/p/flightgear/mailman/message/35910579/>.	2017-07-13 16:06:53 +02:00

Renamed from Translations/en/options.xml (Browse further)