580
edits
Aircraft-set.xml: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 67: | Line 67: | ||
{{note|Most of these tags are optional.}} | {{note|Most of these tags are optional.}} | ||
{{note|FGMeta | {{note|FGMeta contains a Python script <code>fgmeta/catalog/check_aircraft.py</code> which can validate -set.xml files and report potential problems}} | ||
<syntaxhighlight lang="xml"> | <syntaxhighlight lang="xml"> | ||
| Line 81: | Line 81: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The name that will be shown in the aircraft selection dialog of [[FGRun]] and other GUIs. It's called 'description' but consider it the human-readable name for the aircraft. It's the primary thing users will see of your aircraft in UIs, so try to make it as informative as possible without being too long. | The name that will be shown in the aircraft selection dialog of [[FGRun]] and other GUIs. It's called '''description''' but consider it the human-readable name for the aircraft. It's the primary thing users will see of your aircraft in UIs, so try to make it as informative as possible without being too long. Many authors include the manufacturer in the name, but this is not always necessary: e.e there's no need to call an aircraft 'Mikoyan-Gurevich MiG 27 ML (Flogger)'. In this case 'MiG 27ML' or 'Mikoyan MiG-27ML' is likely fine. Nickname such as the NATO reporting name here are good to include in the longer description (see next next section) since this is also searchable in the UI. | ||
<syntaxhighlight lang="xml"> | <syntaxhighlight lang="xml"> | ||