fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Translations/de/FlightGear-nonQt.xlf

1495 lines
83 KiB
Text
Raw Normal View History

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-02 20:24:17 +00:00
<?xml version='1.0' encoding='UTF-8'?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2.xsd">
<file datatype="plaintext" original="" source-language="en-US" target-language="de" xml:space="preserve">
<body>
<group resname="menu" restype="x-trolltech-linguist-context">
<trans-unit approved="no" id="menu/adjust-hud:0" translate="yes">
<source>Adjust HUD Properties</source>
<target>HUD Optionen</target>
</trans-unit>
<trans-unit approved="no" id="menu/adjust-lod:0" translate="yes">
<source>Adjust LOD Ranges</source>
<target>Szeneriekomplexität</target>
</trans-unit>
<trans-unit approved="no" id="menu/ai:0" translate="yes">
<source>AI</source>
<target>KI</target>
</trans-unit>
<trans-unit approved="no" id="menu/aircraft-center:0" translate="yes">
<source>Aircraft Center (Experimental)</source>
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 00:09:50 +00:00
<target>Flugzeug-Hangar (experimentell)</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/aircraft-checklists:0" translate="yes">
<source>Aircraft Checklists</source>
<target>Flugzeug Checklisten</target>
</trans-unit>
<trans-unit approved="no" id="menu/aircraft-keys:0" translate="yes">
<source>Aircraft Help</source>
<target>Flugzeug Hilfe</target>
</trans-unit>
<trans-unit approved="no" id="menu/atc-in-range:0" translate="yes">
<source>ATC Services in Range</source>
<target>ATC Stationen in der Nähe</target>
</trans-unit>
<trans-unit approved="no" id="menu/autopilot:0" translate="yes">
<source>Autopilot</source>
<target>Autopilot</target>
</trans-unit>
<trans-unit approved="no" id="menu/autopilot-settings:0" translate="yes">
<source>Autopilot Settings</source>
<target>Autopilot einstellen</target>
</trans-unit>
<trans-unit approved="no" id="menu/autostart:0" translate="yes">
<source>Autostart</source>
<target>Autostart</target>
</trans-unit>
<trans-unit approved="no" id="menu/basic-keys:0" translate="yes">
<source>Basic Simulator Keys</source>
<target>Tastenbelegung (allgemein)</target>
</trans-unit>
<trans-unit approved="no" id="menu/carrier:0" translate="yes">
<source>Carrier Controls</source>
<target>Flugzeugträger</target>
</trans-unit>
<trans-unit approved="no" id="menu/cockpit-view-options:0" translate="yes">
<source>Cockpit View Options</source>
<target>Cockpitoptionen</target>
</trans-unit>
<trans-unit approved="no" id="menu/common-keys:0" translate="yes">
<source>Common Aircraft Keys</source>
<target>Tastenbelegung (Flugzeugsteuerung)</target>
</trans-unit>
<trans-unit approved="no" id="menu/configure-dev-extension:0" translate="yes">
<source>Configure Development Extensions</source>
<target />
</trans-unit>
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 09:04:56 +00:00
<trans-unit approved="no" id="menu/cycle-gui:0" translate="yes">
Translations: fix some typos and casing inconsistencies.
2018-10-11 08:24:12 +00:00
<source>Cycle GUI Style</source>
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 09:04:56 +00:00
<target />
</trans-unit>
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-02 20:24:17 +00:00
<trans-unit approved="no" id="menu/debug:0" translate="yes">
<source>Debug</source>
<target>Entwickler</target>
</trans-unit>
<trans-unit approved="no" id="menu/development-keys:0" translate="yes">
<source>Development Keys</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/display-marker:0" translate="yes">
<source>Display Tutorial Marker</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/doc-browser:0" translate="yes">
<source>Documentation Browser</source>
<target>Erweiterte Dokumentation</target>
</trans-unit>
<trans-unit approved="no" id="menu/dump-scene-graph:0" translate="yes">
<source>Dump Scene Graph</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/environment:0" translate="yes">
<source>Environment</source>
<target>Umgebung</target>
</trans-unit>
<trans-unit approved="no" id="menu/environment-settings:0" translate="yes">
<source>Environment Settings</source>
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 00:09:50 +00:00
<target>Umgebungseinstellungen</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/equipment:0" translate="yes">
<source>Equipment</source>
<target>Ausrüstung</target>
</trans-unit>
<trans-unit approved="no" id="menu/exit:0" translate="yes">
<source>Quit</source>
<target>Beenden</target>
</trans-unit>
<trans-unit approved="no" id="menu/failure-submenu:0" translate="yes">
<source>--- Failures ---</source>
<target>--- Fehler ---</target>
</trans-unit>
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 09:04:56 +00:00
<trans-unit approved="no" id="menu/fg1000:0" translate="no">
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 00:09:50 +00:00
<source>FG1000 MFD</source>
<target />
</trans-unit>
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 09:04:56 +00:00
<trans-unit approved="no" id="menu/fg1000-mfd:0" translate="yes">
<source>FG1000 MFD</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/fg1000-pfd:0" translate="yes">
<source>FG1000 PFD</source>
<target />
</trans-unit>
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-02 20:24:17 +00:00
<trans-unit approved="no" id="menu/fgcom-settings:0" translate="yes">
<source>FGCom Settings</source>
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 00:09:50 +00:00
<target>FGCom Konfiguration</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/file:0" translate="yes">
<source>File</source>
<target>Datei</target>
</trans-unit>
<trans-unit approved="no" id="menu/fuel-and-payload:0" translate="yes">
<source>Fuel and Payload</source>
<target>Treibstoff und Ladung</target>
</trans-unit>
<trans-unit approved="no" id="menu/global-weather:0" translate="yes">
<source>Weather</source>
<target>Wetter</target>
</trans-unit>
<trans-unit approved="no" id="menu/goto-airport:0" translate="yes">
<source>Select Airport</source>
<target>Flughafenauswahl</target>
</trans-unit>
<trans-unit approved="no" id="menu/gps:0" translate="yes">
<source>GPS Settings</source>
<target>GPS Konfiguration</target>
</trans-unit>
<trans-unit approved="no" id="menu/help:0" translate="yes">
<source>Help</source>
<target>Hilfe</target>
</trans-unit>
<trans-unit approved="no" id="menu/help-browser:0" translate="yes">
<source>Help (opens in browser)</source>
<target>Hilfe (im Browser)</target>
</trans-unit>
<trans-unit approved="no" id="menu/immatriculation:0" translate="yes">
<source>Immatriculation</source>
<target>Luftfahrzeugkennzeichen</target>
</trans-unit>
<trans-unit approved="no" id="menu/input-config:0" translate="yes">
<source>Mouse Configuration</source>
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 00:09:50 +00:00
<target>Maus-Konfiguration</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/instrument-failures:0" translate="yes">
<source>Instrument Failures</source>
<target>Instrumentenfehler</target>
</trans-unit>
<trans-unit approved="no" id="menu/instrument-settings:0" translate="yes">
<source>Instrument Settings</source>
<target>Instrumente</target>
</trans-unit>
<trans-unit approved="no" id="menu/interface-config:0" translate="yes">
Translations: fix some typos and casing inconsistencies.
2018-10-11 08:24:12 +00:00
<source>User-interface Options</source>
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-02 20:24:17 +00:00
<target />
</trans-unit>
<trans-unit approved="no" id="menu/jetway:0" translate="yes">
<source>Jetway Settings</source>
<target>Jetway</target>
</trans-unit>
<trans-unit approved="no" id="menu/joystick-config:0" translate="yes">
<source>Joystick Configuration</source>
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 00:09:50 +00:00
<target>Joystick-Konfiguration</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/joystick-info:0" translate="yes">
<source>Joystick Information</source>
<target>Joystick Informationen</target>
</trans-unit>
<trans-unit approved="no" id="menu/lag-adjust:0" translate="yes">
<source>Lag Settings</source>
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 00:09:50 +00:00
<target>MP Verzögerung</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/load-tape:0" translate="yes">
<source>Load Flight Recorder Tape</source>
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 00:09:50 +00:00
<target>Flugaufzeichnung laden</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/local_weather:0" translate="yes">
<source>Local Weather (Test)</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/location:0" translate="yes">
<source>Location</source>
<target>Ort</target>
</trans-unit>
<trans-unit approved="no" id="menu/logging:0" translate="yes">
<source>Logging</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/map:0" translate="yes">
<source>Map</source>
<target>Karte</target>
</trans-unit>
<trans-unit approved="no" id="menu/map-browser:0" translate="yes">
<source>Map (opens in browser)</source>
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 00:09:50 +00:00
<target>Karte (im Browser)</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/map-canvas:0" translate="yes">
<source>Map (Canvas)</source>
<target>Karte (Canvas)</target>
</trans-unit>
<trans-unit approved="no" id="menu/menu-about:0" translate="yes">
<source>About</source>
<target>Über FlightGear</target>
</trans-unit>
<trans-unit approved="no" id="menu/mp-carrier:0" translate="yes">
<source>MPCarrier Selection</source>
<target>Auswahl MP Flugzeugträger</target>
</trans-unit>
<trans-unit approved="no" id="menu/mp-chat:0" translate="yes">
<source>Chat Dialog</source>
<target>MP Chat</target>
</trans-unit>
<trans-unit approved="no" id="menu/mp-chat-menu:0" translate="yes">
<source>Chat Menu</source>
<target>MP Chat Menü</target>
</trans-unit>
<trans-unit approved="no" id="menu/mp-list:0" translate="yes">
<source>Pilot List</source>
<target>Pilotenliste</target>
</trans-unit>
<trans-unit approved="no" id="menu/mp-settings:0" translate="yes">
<source>Multiplayer Settings</source>
<target>Multiplayer Konfiguration</target>
</trans-unit>
<trans-unit approved="no" id="menu/multiplayer:0" translate="yes">
<source>Multiplayer</source>
<target>Multiplayer</target>
</trans-unit>
<trans-unit approved="no" id="menu/nasal-console:0" translate="yes">
<source>Nasal Console</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/nasal-repl-interpreter:0" translate="yes">
<source>Nasal REPL Interpreter</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/next-waypoint:0" translate="yes">
<source>Next Waypoint</source>
<target>Nächster Wegepunkt</target>
</trans-unit>
<trans-unit approved="no" id="menu/performance-monitor:0" translate="yes">
<source>Monitor System Performance</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/pilot-offset:0" translate="yes">
<source>Adjust View Position</source>
<target>Betrachtungspunkt</target>
</trans-unit>
<trans-unit approved="no" id="menu/position-in-air:0" translate="yes">
<source>Position Aircraft In Air</source>
<target>Flugzeug positionieren (in der Luft)</target>
</trans-unit>
<trans-unit approved="no" id="menu/previous-waypoint:0" translate="yes">
<source>Previous Waypoint</source>
<target>Vorheriger Wegepunkt</target>
</trans-unit>
<trans-unit approved="no" id="menu/print-rendering-statistics:0" translate="yes">
<source>Print Rendering Statistics</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/print-scene-info:0" translate="yes">
<source>Print Visible Scene Info</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/property-browser:0" translate="yes">
<source>Browse Internal Properties</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/pushback:0" translate="yes">
<source>Pushback</source>
<target>Flugzeugschlepper</target>
</trans-unit>
<trans-unit approved="no" id="menu/radio:0" translate="yes">
<source>Radio Settings</source>
<target>Funkfrequenzen</target>
</trans-unit>
<trans-unit approved="no" id="menu/random-attitude:0" translate="yes">
<source>Random Attitude</source>
<target>Zufällige Fluglage</target>
</trans-unit>
<trans-unit approved="no" id="menu/random-failures:0" translate="yes">
<source>Random Failures</source>
<target>Zufällige Fehler</target>
</trans-unit>
<trans-unit approved="no" id="menu/reload-autopilot:0" translate="yes">
<source>Reload Autopilot</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-gui:0" translate="yes">
<source>Reload GUI</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-hud:0" translate="yes">
<source>Reload HUD</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-input:0" translate="yes">
<source>Reload Input</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-materials:0" translate="yes">
<source>Reload Materials</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-model:0" translate="yes">
<source>Reload Aircraft Model</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-network:0" translate="yes">
<source>Reload Network</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-panel:0" translate="yes">
<source>Reload Panel</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/reload-scenery:0" translate="yes">
<source>Reload Scenery</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/rembrandt-buffers-choice:0" translate="yes">
<source>Select Rendering Buffers</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/rendering-buffers:0" translate="yes">
<source>Hide/Show Rendering Buffers</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/rendering-options:0" translate="yes">
<source>Rendering Options</source>
<target>Grafikoptionen</target>
</trans-unit>
<trans-unit approved="no" id="menu/replay:0" translate="yes">
<source>Instant Replay</source>
<target>Sofortwiederholung</target>
</trans-unit>
<trans-unit approved="no" id="menu/reset:0" translate="yes">
<source>Reset</source>
<target>Flug zurücksetzen</target>
</trans-unit>
<trans-unit approved="no" id="menu/route-manager:0" translate="yes">
<source>Route Manager</source>
<target>Routenplaner</target>
</trans-unit>
<trans-unit approved="no" id="menu/save-tape:0" translate="yes">
<source>Save Flight Recorder Tape</source>
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 00:09:50 +00:00
<target>Flugaufzeichnung speichern</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/scenario:0" translate="yes">
<source>Traffic and Scenario Settings</source>
<target>Flugverkehr und Szenarien</target>
</trans-unit>
<trans-unit approved="no" id="menu/select-livery:0" translate="yes">
Translations: fix some typos and casing inconsistencies.
2018-10-11 08:24:12 +00:00
<source>Select Livery</source>
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-02 20:24:17 +00:00
<target>Lackierung auswählen</target>
</trans-unit>
<trans-unit approved="no" id="menu/show-hide-yokes:0" translate="yes">
<source>Show/hide yokes</source>
<target>Steuerhorn aus-/einblenden</target>
</trans-unit>
<trans-unit approved="no" id="menu/snap-shot:0" translate="yes">
<source>Screenshot</source>
<target>Bildschirmfoto</target>
</trans-unit>
<trans-unit approved="no" id="menu/snap-shot-dir:0" translate="yes">
<source>Screenshot Directory</source>
<target>Fotoverzeichnis festlegen</target>
</trans-unit>
<trans-unit approved="no" id="menu/sound-config:0" translate="yes">
<source>Sound Configuration</source>
<target>Sound-Konfiguration</target>
</trans-unit>
<trans-unit approved="no" id="menu/statistics-display:0" translate="yes">
<source>Cycle On-Screen Statistics</source>
<target />
</trans-unit>
<trans-unit approved="no" id="menu/stereoscopic-options:0" translate="yes">
<source>Stereoscopic View Options</source>
<target>Stereoskopie (3D Anzeige)</target>
</trans-unit>
<trans-unit approved="no" id="menu/stopwatch:0" translate="yes">
<source>Stopwatch</source>
<target>Stoppuhr</target>
</trans-unit>
Sync translations
2019-12-24 22:12:28 +00:00
<trans-unit approved="no" id="menu/swift_connection:0" translate="yes">
<source>swift Connection</source>
<target />
</trans-unit>
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-02 20:24:17 +00:00
<trans-unit approved="no" id="menu/system-failures:0" translate="yes">
<source>System Failures</source>
<target>Systemfehler</target>
</trans-unit>
<trans-unit approved="no" id="menu/tanker:0" translate="yes">
<source>Tanker Controls</source>
<target>Tanker</target>
</trans-unit>
<trans-unit approved="no" id="menu/terrasync:0" translate="yes">
<source>Scenery Download</source>
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 00:09:50 +00:00
<target>Herunterladen der Szenerie</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/tiller-steering:0" translate="yes">
<source>Tiller Steering</source>
<target>Bugradsteuerung</target>
</trans-unit>
<trans-unit approved="no" id="menu/time-settings:0" translate="yes">
<source>Time Settings</source>
<target>Zeit</target>
</trans-unit>
<trans-unit approved="no" id="menu/toggle-fullscreen:0" translate="yes">
<source>Toggle Fullscreen</source>
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 00:09:50 +00:00
<target>Vollbild umschalten</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="menu/toggle-glide-slope:0" translate="yes">
<source>Toggle Glide Slope Tunnel</source>
<target>Anzeige des Gleitpfades (an/aus)</target>
</trans-unit>
<trans-unit approved="no" id="menu/tower-position:0" translate="yes">
<source>Tower Position</source>
<target>Towerposition festlegen</target>
</trans-unit>
<trans-unit approved="no" id="menu/tutorial-start:0" translate="yes">
<source>Tutorials</source>
<target>Tutorials</target>
</trans-unit>
<trans-unit approved="no" id="menu/view:0" translate="yes">
<source>View</source>
<target>Ansicht</target>
</trans-unit>
<trans-unit approved="no" id="menu/view-options:0" translate="yes">
<source>View Options</source>
<target>Sichtoptionen</target>
</trans-unit>
<trans-unit approved="no" id="menu/wildfire-settings:0" translate="yes">
<source>Wildfire Settings</source>
<target>Flächenbrand</target>
</trans-unit>
<trans-unit approved="no" id="menu/wingman:0" translate="yes">
<source>Wingman Controls</source>
<target>Wingman</target>
</trans-unit>
<trans-unit approved="no" id="menu/write-video-config:0" translate="yes">
<source>Save Video Configuration</source>
<target />
</trans-unit>
</group>
<group resname="options" restype="x-trolltech-linguist-context">
<trans-unit approved="no" id="options/AV400-desc:0" translate="yes">
<source>Emit the Garmin AV400 protocol required to drive a Garmin 196/296 series GPS</source>
<target>Das Garmin AV400 Protokoll aktivieren, um ein Garmin 196/296 anzusteuern</target>
</trans-unit>
<trans-unit approved="no" id="options/AV400Sim-desc:0" translate="yes">
<source>Emit the set of AV400 strings required to drive a Garmin 400-series GPS from FlightGear</source>
<target>Die Daten des AV400 Protokolls verwenden um ein Garmin 400-Series GPS durch FlightGear zu steuern</target>
</trans-unit>
<trans-unit approved="no" id="options/adf1-desc:0" translate="yes">
<source>Set the ADF1 radio frequency, optionally preceded by a card rotation.</source>
<target>Die Frequenz des ADF1 angeben, optional mit vorangestellter Kompassabweichung</target>
</trans-unit>
<trans-unit approved="no" id="options/adf2-desc:0" translate="yes">
<source>Set the ADF2 radio frequency, optionally preceded by a card rotation.</source>
<target>Die Frequenz des ADF2 angeben, optional mit vorangestellter Kompassabweichung</target>
</trans-unit>
<trans-unit approved="no" id="options/aero-desc:0" translate="yes">
<source>Select aircraft aerodynamics model to load</source>
<target>Wähle das zu ladende Aerodynamik-Modell des Flugzeugs</target>
</trans-unit>
<trans-unit approved="no" id="options/ai-scenario:0" translate="yes">
<source>Add and enable a new scenario. Multiple options are allowed.</source>
<target>Ein KI-Szenario hinzufügen und aktivieren (kann mehrfach angegeben werden)</target>
</trans-unit>
<trans-unit approved="no" id="options/aircraft-desc:0" translate="yes">
<source>Select an aircraft profile as defined by a top level &lt;name&gt;-set.xml</source>
<target>Auswahl eines Flugzeugs (wählt ein &lt;name&gt;-set.xml Profil aus)</target>
</trans-unit>
<trans-unit approved="no" id="options/aircraft-dir-desc:0" translate="yes">
<source>Specify the exact directory to use for the aircraft (normally not required, but may be useful). Interpreted relatively to the current directory. Causes the &lt;path-cache&gt; from autosave_X_Y.xml, as well as --fg-aircraft and the FG_AIRCRAFT environment variable to be bypassed.</source>
<target>Flugzeug-Verzeichnis relativ zum Pfad zu fgfs.exe</target>
</trans-unit>
<trans-unit approved="no" id="options/aircraft-model-options:0" translate="yes">
<source>Aircraft model directory (UIUC FDM ONLY)</source>
<target>Pfad zur FDM-Datei (NUR FÜR FLUGZEUGE MIT UIUC-FDM)</target>
</trans-unit>
<trans-unit approved="no" id="options/aircraft-options:0" translate="yes">
<source>Aircraft</source>
<target>Flugzeug Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/airport-desc:0" translate="yes">
<source>Specify starting position relative to an airport</source>
<target>Auswahl des Flughafens (bzw. relative Position zu diesem)</target>
</trans-unit>
<trans-unit approved="no" id="options/altitude-desc:0" translate="yes">
<source>Starting altitude</source>
<target>Start in dieser Flughöhe über MSL</target>
</trans-unit>
<trans-unit approved="no" id="options/arm-desc:0" translate="yes">
<source>Specify a multiplier for the aspect ratio.</source>
<target>Einen Multiplikator für das Seitenverhältnis angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/atcsim-desc:0" translate="yes">
<source>Open connection using the ATC sim protocol (atc610x)</source>
<target>Eine Verbindung öffnen unter Verwendung des ATC Sim-Protokolls (atc610x)</target>
</trans-unit>
<trans-unit approved="no" id="options/atlas-desc:0" translate="yes">
<source>Open connection using the Atlas protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des Atlas-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/audio-options:0" translate="yes">
<source>Audio Options</source>
<target>Audio Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/avionics-options:0" translate="yes">
<source>Avionics Options</source>
<target>Avionik-Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/bpp-desc:0" translate="yes">
<source>Specify the bits per pixel</source>
<target>Bits pro Pixel angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/browser-app-desc:0" translate="yes">
<source>Specify path to your web browser</source>
<target>Pfad zu Deinem Internet-Browser angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/callsign-desc:0" translate="yes">
<source>assign a unique name to a player</source>
<target>Dem Spieler einen spezifischen Namen zuweisen</target>
</trans-unit>
<trans-unit approved="no" id="options/carrier-desc:0" translate="yes">
<source>Specify starting position on an AI carrier</source>
<target>Auswahl einer Startposition auf einem Flugzeugträger</target>
</trans-unit>
<trans-unit approved="no" id="options/ceiling-desc:0" translate="yes">
<source>Create an overcast ceiling, optionally with a specific thickness (defaults to 2000 ft).</source>
<target>Einen Wolkendecke erstellen, optional mit einer bestimmten Dicke (Standard ist 2000 ft)</target>
</trans-unit>
<trans-unit approved="no" id="options/com1-desc:0" translate="yes">
<source>Set the COM1 radio frequency</source>
<target>Die Frequenz des COM1-Funkgeräts angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/com2-desc:0" translate="yes">
<source>Set the COM2 radio frequency</source>
<target>Die Frequenz des COM2-Funkgeräts angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/config-desc:0" translate="yes">
<source>Load additional properties from path</source>
<target>Pfad zu einer zusätzlichen Konfigurationsdatei mit benutzerdefinierten Einstellungen</target>
</trans-unit>
<trans-unit approved="no" id="options/console-desc:0" translate="yes">
<source>Display console (Windows specific)</source>
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 00:09:50 +00:00
<target>Konsole anzeigen (nur für Windows)</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/debugging-options:0" translate="yes">
<source>Debugging Options</source>
<target>Entwickleroptionen</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-ai-models-desc:0" translate="yes">
<source>Deprecated option (disable internal AI subsystem)</source>
<target>Veraltete Option (internes KI-Subsystem deaktivieren)</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-ai-traffic-desc:0" translate="yes">
<source>Disable artificial traffic.</source>
<target>KI-Verkehr deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-anti-alias-hud-desc:0" translate="yes">
<source>Disable anti-aliased HUD</source>
<target>HUD mit Kantenglättung deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-auto-coordination-desc:0" translate="yes">
<source>Disable auto coordination</source>
<target>Auto-Koordination von Quer- und Seitenruder deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-clock-freeze-desc:0" translate="yes">
<source>Clock advances normally</source>
<target>Uhrzeit vergeht normal</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-clouds-desc:0" translate="yes">
<source>Disable 2D (flat) cloud layers</source>
<target>Platte 2D-Wolken deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-clouds3d-desc:0" translate="yes">
<source>Disable 3D (volumetric) cloud layers</source>
<target>Volumetrische 3D-Wolken deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-distance-attenuation:0" translate="yes">
<source>Disable runway light distance attenuation</source>
<target>Abschwächung der Startbahnbeleuchtung bei größeren Entfernungen deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-enhanced-lighting:0" translate="yes">
<source>Disable enhanced runway lighting</source>
<target>Detailliete Startbahnbeleuchtung deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-fgcom-desc:0" translate="yes">
<source>Disable FGCom built-in</source>
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 00:09:50 +00:00
<target>FGCom Sprachkommunikation deaktivieren</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/disable-freeze-desc:0" translate="yes">
<source>Start in a running state</source>
<target>Nicht pausiert starten</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-fuel-freeze-desc:0" translate="yes">
<source>Fuel is consumed normally</source>
<target>Treibstoff wird normal verbraucht</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-fullscreen-desc:0" translate="yes">
<source>Disable fullscreen mode</source>
<target>Kein Vollbild</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-horizon-effect:0" translate="yes">
<source>Disable celestial body growth illusion near the horizon</source>
<target>Die Illusion einer vergrößerten Erscheinung von Himmelskörpern nahe dem Horizont deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-hud-3d-desc:0" translate="yes">
<source>Disable 3D HUD</source>
<target>3D-HUD deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-hud-desc:0" translate="yes">
<source>Disable Heads Up Display (HUD)</source>
<target>Head-Up-Display (HUD) deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-mouse-pointer-desc:0" translate="yes">
<source>Disable extra mouse pointer</source>
<target>Zusätzlichen Mauszeiger deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-panel-desc:0" translate="yes">
<source>Disable instrument panel</source>
<target>Instrumentenbrett deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-random-buildings-desc:0" translate="yes">
<source>Exclude random buildings objects</source>
<target>Zufällige Gebäude ausblenden</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-random-objects-desc:0" translate="yes">
<source>Exclude random scenery objects</source>
<target>Zufällige Objekte ausblenden</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-random-vegetation-desc:0" translate="yes">
<source>Exclude random vegetation objects</source>
<target>Vegeation ausblenden</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-real-weather-fetch-desc:0" translate="yes">
<source>Disable METAR based real weather fetching</source>
<target>METAR-basierten Download von realem Wetter deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-rembrandt-desc:0" translate="yes">
<source>Disable Rembrandt rendering</source>
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 00:09:50 +00:00
<target>Rembrandt Rendering-Engine deaktivieren</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/disable-save-on-exit:0" translate="yes">
<source>Don't save preferences upon program exit</source>
<target>Einstellungen beim Beenden nicht speichern</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-sound-desc:0" translate="yes">
<source>Disable sound effects</source>
<target>Sound deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-specular-highlight:0" translate="yes">
<source>Disable specular reflections on textured objects</source>
<target>Spiegelnde Reflektionen antexturierten Objekten deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-splash-screen-desc:0" translate="yes">
<source>Disable splash screen</source>
<target>Startbildschirm deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-terrasync-desc:0" translate="yes">
<source>Disable automatic scenery downloads/updates</source>
<target>Automatischen Download/Update von Szenerie deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-textures-desc:0" translate="yes">
<source>Disable textures</source>
<target>Texturen deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/disable-wireframe-desc:0" translate="yes">
<source>Disable wireframe drawing mode</source>
<target>Drahtgitterdarstellung deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/dme-desc:0" translate="yes">
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 09:04:56 +00:00
<source>Slave the DME to one of the NAV radios, or set its internal frequency.</source>
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-02 20:24:17 +00:00
<target>Das DME an eines der NAV-Funnkgeräte koppeln, oder eine interne Frequenz angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/download-dir-desc:0" translate="yes">
<source>Base directory to use for aircraft and scenery downloads (the TerraSync scenery directory may be specifically set with --terrasync-dir)</source>
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 00:09:50 +00:00
<target>Verzeichnis für heruntergeladene Flugzeuge und Szenerie</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/enable-ai-models-desc:0" translate="yes">
<source>Enable AI subsystem (required for multi-player, AI traffic and many other animations)</source>
<target>KI-Subsystem aktivieren (erforderlich für Multiplayer, KI-Verkehr und viele andere Animationen</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-ai-traffic-desc:0" translate="yes">
<source>Enable artificial traffic.</source>
<target>KI-Verkehr aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-anti-alias-hud-desc:0" translate="yes">
<source>Enable anti-aliased HUD</source>
<target>HUD mit Kantenglättung aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-auto-coordination-desc:0" translate="yes">
<source>Enable auto coordination</source>
<target>Auto-Koordination von Quer- und Seitenruder aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-clock-freeze-desc:0" translate="yes">
<source>Do not advance clock</source>
<target>Uhrzeit eingefroren (Zeit steht still)</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-clouds-desc:0" translate="yes">
<source>Enable 2D (flat) cloud layers</source>
<target>Platte 2D-Wolken aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-clouds3d-desc:0" translate="yes">
<source>Enable 3D (volumetric) cloud layers</source>
<target>Volumetrische 3D-Wolken aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-distance-attenuation:0" translate="yes">
<source>Enable runway light distance attenuation</source>
<target>Abschwächung der Startbahnbeleuchtung bei größeren Entfernungen aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-enhanced-lighting:0" translate="yes">
<source>Enable enhanced runway lighting</source>
<target>Detailliete Startbahnbeleuchtung aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-fgcom-desc:0" translate="yes">
<source>Enable FGCom built-in</source>
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 00:09:50 +00:00
<target>FGCom Sprachkommunikation aktivieren</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/enable-freeze-desc:0" translate="yes">
<source>Start in a frozen state</source>
<target>Pausiert starten</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-fuel-freeze-desc:0" translate="yes">
<source>Fuel tank quantity forced to remain constant</source>
<target>Kein Treibstoff wird verbraucht</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-fullscreen-desc:0" translate="yes">
<source>Enable fullscreen mode</source>
<target>Vollbild</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-horizon-effect:0" translate="yes">
<source>Enable celestial body growth illusion near the horizon</source>
<target>Die Illusion einer vergrößerten Erscheinung von Himmelskörpern nahe dem Horizont aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-hud-3d-desc:0" translate="yes">
<source>Enable 3D HUD</source>
<target>3D-HUD aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-hud-desc:0" translate="yes">
<source>Enable Heads Up Display (HUD)</source>
<target>Head-Up-Display (HUD) aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-mouse-pointer-desc:0" translate="yes">
<source>Enable extra mouse pointer</source>
<target>Zusätzlichen Mauszeiger aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-mouse-pointer-desc:1" translate="yes">
<source>(i.e. for full screen Voodoo based cards)</source>
<target>z.B. für Vollbild-Voodoo-Karten</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-panel-desc:0" translate="yes">
<source>Enable instrument panel</source>
<target>Instrumentenbrett aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-random-buildings-desc:0" translate="yes">
<source>Include random buildings objects</source>
<target>Zufällige Gebäude anzeigen</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-random-objects-desc:0" translate="yes">
<source>Include random scenery objects</source>
<target>Zufällige Objekte darstellen</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-random-vegetation-desc:0" translate="yes">
<source>Include random vegetation objects</source>
<target>Vegetation anzeigen</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-real-weather-fetch-desc:0" translate="yes">
<source>Enable METAR based real weather fetching (this requires an open internet connection)</source>
<target>METAR-basierten Download von realem Wetter aktivieren (setzt eine fuktionierende Internetverbindung voraus)</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-rembrandt-desc:0" translate="yes">
<source>Enable Rembrandt rendering</source>
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 00:09:50 +00:00
<target>Rembrandt Rendering-Engine aktivieren</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/enable-save-on-exit:0" translate="yes">
<source>Allow saving preferences at program exit</source>
<target>Einstellungen beim Beenden speichern</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-sound-desc:0" translate="yes">
<source>Enable sound effects</source>
<target>Sound aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-specular-highlight:0" translate="yes">
<source>Enable specular reflections on textured objects</source>
<target>Spiegelnde Reflektionen antexturierten Objekten aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-splash-screen-desc:0" translate="yes">
<source>Enable splash screen</source>
<target>Startbildschirm aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-terrasync-desc:0" translate="yes">
<source>Enable automatic scenery downloads/updates</source>
<target>Automatischen Download/Update von Szenerie aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-textures-desc:0" translate="yes">
<source>Enable textures</source>
<target>Texturen aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/enable-wireframe-desc:0" translate="yes">
<source>Enable wireframe drawing mode</source>
<target>Drahtgitterdarstellung aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/environment-options:0" translate="yes">
<source>Environment Options</source>
<target>Umgebungs-Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/failure-desc:0" translate="yes">
<source>Fail the pitot, static, vacuum, or electrical system (repeat the option for multiple system failures).</source>
<target>Das Pitotsystem, Vakuumsystem, das statische oder elektrische System ausfallen lassen (Mehrfachnennung für mehrere Systemausfälle möglich)</target>
</trans-unit>
<trans-unit approved="no" id="options/fdm-desc:0" translate="yes">
<source>Select the core flight dynamics model</source>
<target>Wähle das grundlegende Flugdynamikmodell aus</target>
</trans-unit>
<trans-unit approved="no" id="options/fdm-desc:1" translate="yes">
<source>Can be one of jsb, larcsim, yasim, magic, balloon, ada, external, or null</source>
<target>Entweder jsb, larcsim, yasim, magic, balloon, ada, external, oder null</target>
</trans-unit>
<trans-unit approved="no" id="options/fdm-options:0" translate="yes">
<source>Flight Model</source>
<target>Optionen für die Flugphysik</target>
</trans-unit>
<trans-unit approved="no" id="options/features-options:0" translate="yes">
<source>Features</source>
<target>Features</target>
</trans-unit>
<trans-unit approved="no" id="options/fg-aircraft-desc:0" translate="yes">
<source>Specify additional aircraft directory path(s) (alternatively, you can use --aircraft-dir to target a specific aircraft in a given directory)</source>
<target>Konfiguriert Verzeichnisse mit zusätzlichen Flugzeugen</target>
</trans-unit>
<trans-unit approved="no" id="options/fg-root-desc:0" translate="yes">
<source>Specify the root data path</source>
<target>Konfiguration des FlightGear Datenverzeichnisses</target>
</trans-unit>
<trans-unit approved="no" id="options/fg-scenery-desc:0" translate="yes">
<source>Specify the scenery path(s);</source>
<target>Konfiguriert den Pfad zu den Szeneriedaten;</target>
</trans-unit>
<trans-unit approved="no" id="options/fg-scenery-desc:1" translate="yes">
<source>Defaults to $FG_ROOT/Scenery</source>
<target>Voreinstellung ist $FG_ROOT/Scenery</target>
</trans-unit>
<trans-unit approved="no" id="options/fgviewer-desc:0" translate="yes">
<source>Use a model viewer rather than load the entire simulator;</source>
<target>Den Model-Viewer verwenden, anstatt den gesamten Simulator zu laden</target>
</trans-unit>
<trans-unit approved="no" id="options/fix-desc:0" translate="yes">
<source>Specify starting position relative to a fix</source>
<target>Startposition relativ zu einem Fix angeben</target>
</trans-unit>
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 00:09:50 +00:00
<trans-unit approved="no" id="options/flarm-desc:0" translate="yes">
<source>Open connection using the Flarm protocol, which includes NMEA/GPS and traffic reporting messages</source>
<target>Eine Verbindung öffnen unter Verwendung des Flarm Protokolls, welches NMEA/GPS und Verkehrsinformationen überträgt</target>
</trans-unit>
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-02 20:24:17 +00:00
<trans-unit approved="no" id="options/flight-plan-desc:0" translate="yes">
<source>Read all waypoints from a file</source>
<target>Alle Wegpunkte von der angegebenen Datei einlesen</target>
</trans-unit>
<trans-unit approved="no" id="options/fog-disable-desc:0" translate="yes">
<source>Disable fog/haze</source>
<target>Nebel/Dunst deaktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/fog-fastest-desc:0" translate="yes">
<source>Enable fastest fog/haze</source>
<target>Schnellere Darstellung von Nebel/Dunst</target>
</trans-unit>
<trans-unit approved="no" id="options/fog-nicest-desc:0" translate="yes">
<source>Enable nicest fog/haze</source>
<target>Schönere Darstellung von Nebel/Dunst</target>
</trans-unit>
<trans-unit approved="no" id="options/fov-desc:0" translate="yes">
<source>Specify field of view angle</source>
<target>Das Sichtfeld in Grad angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/fpe-desc:0" translate="yes">
<source>Abort on encountering a floating point exception;</source>
<target>Abbruch bei Auftreten einer Floating Point Exception</target>
</trans-unit>
<trans-unit approved="no" id="options/garmin-desc:0" translate="yes">
<source>Open connection using the Garmin GPS protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des Garmin GPS-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/general-options:0" translate="yes">
<source>General Options</source>
<target>Generelle Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/generic-desc:0" translate="yes">
<source>Open connection using a predefined communication interface and a preselected communication protocol</source>
<target>Eine Verbindung öffnen unter Verwendung eines vorgegebenen Kommunukationsinterfaces und eines vorausgewählten Kommunikationsprotokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/geometry-desc:0" translate="yes">
<source>Specify window geometry (640x480, etc)</source>
<target>Fensterabmessungen angeben (z.B. 800x600, 1280x720, etc.)</target>
</trans-unit>
<trans-unit approved="no" id="options/glideslope-desc:0" translate="yes">
<source>Specify flight path angle (can be positive)</source>
<target>Den Winkel des Flugvektors angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/heading-desc:0" translate="yes">
<source>Specify heading (yaw) angle (Psi)</source>
<target>Den Steuerkurs angeben (griech. Psi)</target>
</trans-unit>
<trans-unit approved="no" id="options/help-desc:0" translate="yes">
<source>Show the most relevant command line options</source>
<target>Die wichtigsten Kommandozeilenoptionen zeigen.</target>
</trans-unit>
<trans-unit approved="no" id="options/httpd-desc:0" translate="yes">
<source>Enable http server on the specified address. Specify the port or address:port to bind to.</source>
<target>Einen HTTP-Server am angegebenen Port aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/hud-culled-desc:0" translate="yes">
<source>Hud displays percentage of triangles culled</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/hud-options:0" translate="yes">
<source>Hud Options</source>
<target>HUD-Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/hud-tris-desc:0" translate="yes">
<source>Hud displays number of triangles rendered</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/in-air-desc:0" translate="yes">
<source>Start in air (implied when using --altitude)</source>
<target>In der Luft starten (implieziert bei Verwendung von --altitude)</target>
</trans-unit>
<trans-unit approved="no" id="options/io-options:0" translate="yes">
<source>IO Options</source>
<target>I/O-Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/joyclient-desc:0" translate="yes">
<source>Open connection to an Agwagon joystick</source>
<target>Eine Verbindung zu einem Agwagon-Joystick öffnen</target>
</trans-unit>
<trans-unit approved="no" id="options/jpg-httpd-desc:0" translate="yes">
<source>Enable screen shot http server on the specified port (replaced by --httpd)</source>
<target>Screenshot-HTTP-Server am angegeben Port aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/jsclient-desc:0" translate="yes">
<source>Open connection to a remote joystick</source>
<target>Eine Verbindung zu einem Remote-Joystick öffnen</target>
</trans-unit>
<trans-unit approved="no" id="options/json-report-desc:0" translate="yes">
<source>Print a report in JSON format on the standard output, giving information such as the FlightGear version, $FG_ROOT, $FG_HOME, aircraft and scenery paths, etc.</source>
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 00:09:50 +00:00
<target>Einen Report im JSON-Format ausgeben. Enthält Details über die FlightGear Version und Einstellungen.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="options/language-desc:0" translate="yes">
<source>Select the language for this session</source>
<target>Auswahl der Sprache</target>
</trans-unit>
<trans-unit approved="no" id="options/lat-desc:0" translate="yes">
<source>Starting latitude (south = -)</source>
<target>Start bei Breitengrad (Süden = -)</target>
</trans-unit>
<trans-unit approved="no" id="options/livery-desc:0" translate="yes">
<source>Select aircraft livery</source>
<target>Lackierung des Flugzeugs auswählen</target>
</trans-unit>
<trans-unit approved="no" id="options/log-class-desc:0" translate="yes">
<source>Specify which logging class(es) to use</source>
<target>Die zu verwendende(n) Log-Klasse(n) angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/log-dir-desc:0" translate="yes">
<source>Log to directory DIR. The special value 'desktop' causes logging to the desktop (OS-dependent location). This option may be given several times, using a different value each time. Inside the specified directory, the written log file is named FlightGear_YYYY-MM-DD_&lt;num&gt;.log, where &lt;num&gt; takes the values 0, 1, 2, etc.</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/log-level-desc:0" translate="yes">
<source>Specify which logging level to use</source>
<target>Das zu verwendende Log-Level angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/lon-desc:0" translate="yes">
<source>Starting longitude (west = -)</source>
<target>Start bei Längengrad (Westen = -)</target>
</trans-unit>
<trans-unit approved="no" id="options/mach-desc:0" translate="yes">
<source>Specify initial mach number</source>
<target>Anfängliche Mach-Zahl angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/materials-file-desc:0" translate="yes">
<source>Specify the materials file used to render the scenery (default: Materials/regions/materials.xml)</source>
<target>Die Materials-Datei angeben, die zur Darstellung der Szenerie verwendet wird (Standard: materials.xml)</target>
</trans-unit>
<trans-unit approved="no" id="options/max-fps-desc:0" translate="yes">
<source>Maximum frame rate in Hz.</source>
<target>Die maximale Framerate in Hz</target>
</trans-unit>
<trans-unit approved="no" id="options/metar-desc:0" translate="yes">
<source>Pass a METAR string to set up static weather (this implies --disable-real-weather-fetch)</source>
<target>Einen METAR eingeben, um statisches Wetter einzustellen</target>
</trans-unit>
<trans-unit approved="no" id="options/min-aircraft-status:0" translate="yes">
<source>Allows you to define a minimum status level (=development status) for all listed aircraft</source>
<target>Schränkt die Anzeige auf Flugzeuge mit diesem minimalem Status ein</target>
</trans-unit>
<trans-unit approved="no" id="options/model-hz-desc:0" translate="yes">
<source>Run the FDM this rate (iterations per second)</source>
<target>Lasse das FDM mit dieser Frequenz laufen (Wiederholungen pro Sekunde)</target>
</trans-unit>
<trans-unit approved="no" id="options/multiplay-desc:0" translate="yes">
<source>Specify multipilot communication settings</source>
<target>Multiplayer-Einstellungen angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/multiplayer-options:0" translate="yes">
<source>MultiPlayer Options</source>
<target>Multiplayer-Optionen</target>
</trans-unit>
<trans-unit approved="no" id="options/native-ctrls-desc:0" translate="yes">
<source>Open connection using the FG Native Controls protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des FG Native Controls-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/native-desc:0" translate="yes">
<source>Open connection using the FG Native protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des FG Native-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/native-fdm-desc:0" translate="yes">
<source>Open connection using the FG Native FDM protocol</source>
<target>Eine Verbindung öffnen unter Verwendungdes FG Native FDM-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/native-gui-desc:0" translate="yes">
<source>Open connection using the FG Native GUI protocol</source>
<target>Eine Verbindung öffnen unter Verwendun gdes FG Native GUI-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/nav1-desc:0" translate="yes">
<source>Set the NAV1 radio frequency, optionally preceded by a radial.</source>
<target>Die Frequenz des NAV1-Funkgeräts angeben, obtional mit vorangestelltem Radial</target>
</trans-unit>
<trans-unit approved="no" id="options/nav2-desc:0" translate="yes">
<source>Set the NAV2 radio frequency, optionally preceded by a radial.</source>
<target>Die Frequenz des NAV2-Funkgeräts angeben, obtional mit vorangestelltem Radial</target>
</trans-unit>
<trans-unit approved="no" id="options/ndb-desc:0" translate="yes">
<source>Specify starting position relative to an NDB</source>
<target>Startposition relativ zu einem NDB angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/ndb-freq-desc:0" translate="yes">
<source>Specify the frequency of the NDB. Use with --ndb=ID</source>
<target>Die Frequenz des NDB angeben. Verwendung zusamen mit --ndb=ID</target>
</trans-unit>
<trans-unit approved="no" id="options/network-options:0" translate="yes">
<source>Network Options</source>
<target>Netzwerk</target>
</trans-unit>
<trans-unit approved="no" id="options/nmea-desc:0" translate="yes">
<source>Open connection using the NMEA protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des NMEA-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/notrim-desc:0" translate="yes">
<source>Do NOT attempt to trim the model</source>
<target>Das Flugzeug NICHT trimmen</target>
</trans-unit>
<trans-unit approved="no" id="options/notrim-desc:1" translate="yes">
<source>(only with fdm=jsbsim)</source>
<target>(nur mit --fdm=jsbsim)</target>
</trans-unit>
<trans-unit approved="no" id="options/offset-azimuth-desc:0" translate="yes">
<source>Specify heading to reference point</source>
<target>Kurs relativ zum Referenzpunkt</target>
</trans-unit>
<trans-unit approved="no" id="options/offset-distance-desc:0" translate="yes">
<source>Specify distance to reference point (statute miles)</source>
<target>Distanz zum Referenzpunkt angeben (Statute Miles)</target>
</trans-unit>
<trans-unit approved="no" id="options/on-ground-desc:0" translate="yes">
<source>Start at ground level (default)</source>
<target>Auf dem Boden starten (Standard)</target>
</trans-unit>
<trans-unit approved="no" id="options/opengc-desc:0" translate="yes">
<source>Open connection using the OpenGC protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des OpenGC-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/parking-id-desc:0" translate="yes">
<source>Specify parking position at an airport (must also specify an airport)</source>
<target>Auswahl einer Parkposition am ausgewählten Flughafen</target>
</trans-unit>
<trans-unit approved="no" id="options/parkpos-desc:0" translate="yes">
<source>Specify which starting position on an AI carrier (must also specify a carrier)</source>
<target>Eine Parkposition auf dem angegebenen Flugzeugträger wählen</target>
</trans-unit>
<trans-unit approved="no" id="options/pitch-desc:0" translate="yes">
<source>Specify pitch angle (Theta)</source>
<target>Die Längsneigung angeben (griech. Theta)</target>
</trans-unit>
<trans-unit approved="no" id="options/position-options:0" translate="yes">
<source>Initial Position and Orientation</source>
<target>Position und Orientierung</target>
</trans-unit>
<trans-unit approved="no" id="options/prop-desc:0" translate="yes">
<source>Set property &lt;name&gt; to &lt;value&gt;. &lt;type&gt; can be one of string, double, float, long, int, or bool.</source>
<target>Der Property &lt;name&gt; den Wert &lt;value&gt; zuweisen. &lt;name&gt; kann string, double, float, long, int, oder bool sein.</target>
</trans-unit>
<trans-unit approved="no" id="options/props-desc:0" translate="yes">
<source>Open connection using the interactive property manager</source>
<target>Eine Verbindung öffnen unter Verwendung des interaktiven Property-Managers</target>
</trans-unit>
<trans-unit approved="no" id="options/proxy-desc:0" translate="yes">
<source>Specify which proxy server (and port) to use. The username and password are optional and should be MD5 encoded already. This option is only useful when used in conjunction with the real-weather-fetch option.</source>
<target>Den zu verwendenden Proxy-Server (und Port) angeben. Nutzername und Passwort sind frei wählbar und sollten bereits MD5-codiert sein. Nur sinnvoll in Verbindung mit der Option "--real-weather-fetch"</target>
</trans-unit>
<trans-unit approved="no" id="options/pve-desc:0" translate="yes">
<source>Open connection using the PVE protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des PVE-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/random-objects-desc:0" translate="yes">
<source>(buildings, etc.)</source>
<target>(Gebäude, etc.)</target>
</trans-unit>
<trans-unit approved="no" id="options/random-wind-desc:0" translate="yes">
<source>Set up random wind direction and speed</source>
<target>Zufällige Windrichtung und -geschwindigkeit</target>
</trans-unit>
<trans-unit approved="no" id="options/ray-desc:0" translate="yes">
<source>Open connection using the Ray Woodworth motion chair protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des Ray Woodworth Motion Chair-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/rendering-options:0" translate="yes">
<source>Rendering Options</source>
<target>Grafikoptionen</target>
</trans-unit>
<trans-unit approved="no" id="options/restore-defaults-desc:0" translate="yes">
<source>Reset all user settings to their defaults (rendering options etc)</source>
<target>Alle Optionen auf Standard zurücksetzen (Grafik, etc.)</target>
</trans-unit>
<trans-unit approved="no" id="options/roc-desc:0" translate="yes">
<source>Specify initial climb rate (can be negative)</source>
<target>Die Anfängliche Steig-/Sinkrate angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/roll-desc:0" translate="yes">
<source>Specify roll angle (Phi)</source>
<target>Den Querneigung angeben (griech. Phi)</target>
</trans-unit>
<trans-unit approved="no" id="options/route-options:0" translate="yes">
<source>Route/Way Point Options</source>
<target>Route/Wegpunkt</target>
</trans-unit>
<trans-unit approved="no" id="options/rul-desc:0" translate="yes">
<source>Open connection using the RUL protocol</source>
<target>Eine Verbindung öffnen unter Verwendung des RUL-Protokolls</target>
</trans-unit>
<trans-unit approved="no" id="options/runway-no-desc:0" translate="yes">
<source>Specify starting runway (must also specify an airport)</source>
<target>Auswahl einer Startbahn am ausgewählten Flughafen</target>
</trans-unit>
<trans-unit approved="no" id="options/season-desc:0" translate="yes">
<source>Specify the startup season</source>
<target>Eine Jahreszeit angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/shading-flat-desc:0" translate="yes">
<source>Enable flat shading</source>
<target>Harte Schattierung</target>
</trans-unit>
<trans-unit approved="no" id="options/shading-smooth-desc:0" translate="yes">
<source>Enable smooth shading</source>
<target>Weiche Schattierung</target>
</trans-unit>
<trans-unit approved="no" id="options/show-aircraft-desc:0" translate="yes">
<source>Print a list of the currently available aircraft types</source>
<target>Zeigt eine Liste der verfügbaren Flugzeugtypen</target>
</trans-unit>
<trans-unit approved="no" id="options/show-sound-devices-desc:0" translate="yes">
<source>Show a list of available audio device</source>
<target>Eine Liste der verfügbaren Audiogeräte anzeigen</target>
</trans-unit>
<trans-unit approved="no" id="options/situation-options:0" translate="yes">
<source>Situation Options</source>
<target>Situationsoptionen</target>
</trans-unit>
<trans-unit approved="no" id="options/sound-device-desc:0" translate="yes">
<source>Explicitly specify the audio device to use</source>
<target>Das zu verewendende Audiogerät explizit angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/speed-desc:0" translate="yes">
<source>Run the FDM 'n' times faster than real time</source>
<target>Lasse das FDM mit dem n-fachen der realen Zeit laufen</target>
</trans-unit>
<trans-unit approved="no" id="options/start-date-desc:0" translate="yes">
<source>Specify a starting date/time with respect to</source>
<target>Eine Startzeitangeben relativ zu</target>
</trans-unit>
<trans-unit approved="no" id="options/telnet-desc:0" translate="yes">
<source>Enable telnet server on the specified port</source>
<target>Telnet-Server am angegebenen Port aktivieren</target>
</trans-unit>
<trans-unit approved="no" id="options/terrasync-dir-desc:0" translate="yes">
<source>Set target directory for scenery downloads</source>
<target>Zielverzeichnis für Szenerie-Downloads</target>
</trans-unit>
<trans-unit approved="no" id="options/texture-filtering-desc:0" translate="yes">
<source>Anisotropic Texture Filtering: values should be 1 (default),2,4,8 or 16</source>
<target>Anisotropische Texturfilterung: Wert sollte 1 (Standard), 2, 4, 8, oder 16 sein</target>
</trans-unit>
<trans-unit approved="no" id="options/time-match-local-desc:0" translate="yes">
<source>Synchronize time with local real-world time</source>
<target>Mit Ortszeit synchronisieren</target>
</trans-unit>
<trans-unit approved="no" id="options/time-match-real-desc:0" translate="yes">
<source>Synchronize time with real-world time</source>
<target>Mit Realzeit (UTC) synchronisieren</target>
</trans-unit>
<trans-unit approved="no" id="options/time-offset-desc:0" translate="yes">
<source>Add this time offset</source>
<target>Zeitverschiebung angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/time-options:0" translate="yes">
<source>Time Options</source>
<target>Zeitoptionen</target>
</trans-unit>
<trans-unit approved="no" id="options/timeofday-desc:0" translate="yes">
<source>Specify a time of day</source>
<target>Eine Tageszeit angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/trace-read-desc:0" translate="yes">
<source>Trace the reads for a property;</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/trace-write-desc:0" translate="yes">
<source>Trace the writes for a property;</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/trim-desc:0" translate="yes">
<source>Trim the model</source>
<target>Das Flugzeug trimmen</target>
</trans-unit>
<trans-unit approved="no" id="options/trim-desc:1" translate="yes">
<source>(only with fdm=jsbsim)</source>
<target>(nur mit --fdm=jsbsim)</target>
</trans-unit>
<trans-unit approved="no" id="options/turbulence-desc:0" translate="yes">
<source>Specify turbulence from 0.0 (calm) to 1.0 (severe)</source>
<target>Angabe der Stärke der Turbulenz von 0.0 (gar keine) bis 1.0 (sehr stark)</target>
</trans-unit>
<trans-unit approved="no" id="options/uBody-desc:0" translate="yes">
<source>Specify velocity along the body X axis</source>
<target>Geschwindigkeit entlang der X-Achse des Flugzeugs angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/units-feet-desc:0" translate="yes">
<source>Use feet for distances</source>
<target>Fuß für Entfernungen verwenden</target>
</trans-unit>
<trans-unit approved="no" id="options/units-meters-desc:0" translate="yes">
<source>Use meters for distances</source>
<target>Meter für Entfernungen verwenden</target>
</trans-unit>
<trans-unit approved="no" id="options/usage:0" translate="yes">
<source>Usage: fgfs [ option ... ]</source>
<target>Aufruf: fgfs [ Optionen ... ]</target>
</trans-unit>
<trans-unit approved="no" id="options/vBody-desc:0" translate="yes">
<source>Specify velocity along the body Y axis</source>
<target>Geschwindigkeit entlang der Y-Achse des Flugzeugs angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vDown-desc:0" translate="yes">
<source>Specify velocity along a vertical axis</source>
<target>Geschwindigkeit entlang der Hochachse angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vEast-desc:0" translate="yes">
<source>Specify velocity along a West-East axis</source>
<target>Geschwindigkeit in Ost-West-Richtung angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vNorth-desc:0" translate="yes">
<source>Specify velocity along a South-North axis</source>
<target>Geschwindigkeit in Nord-Süd-Richtung angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vc-desc:0" translate="yes">
<source>Specify initial airspeed</source>
<target>Anfangsgeschwindigkeit angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vehicle-desc:0" translate="yes">
<source>Select an vehicle profile as defined by a top level &lt;name&gt;-set.xml</source>
<target />
</trans-unit>
<trans-unit approved="no" id="options/verbose-desc:0" translate="yes">
<source>Show all command line options when combined with --help or -h</source>
<target>Zeigt die vollständige Lister aller Kommandozeilenoptionen (mit --help oder -h kombinieren)</target>
</trans-unit>
<trans-unit approved="no" id="options/verbose-help:0" translate="yes">
<source>For a complete list of options use --help --verbose</source>
<target>Anzeigen der vollständige Liste aller Optionen mit --help --verbose</target>
</trans-unit>
<trans-unit approved="no" id="options/version-desc:0" translate="yes">
<source>Display the current FlightGear version</source>
<target>Zeigt die aktuelle FlightGear Version</target>
</trans-unit>
<trans-unit approved="no" id="options/view-offset-desc:0" translate="yes">
<source>Specify the default forward view direction as an offset from straight ahead. Allowable values are LEFT, RIGHT, CENTER, or a specific number in degrees</source>
<target>Die stadardmäßige Nach-Vorne-Blickrichtung angeben als Abweichung von geradeaus. Erlaubte Werte sind LEFT, RECHTS, CENTER, oder eine spezifische Angabe in Grad</target>
</trans-unit>
<trans-unit approved="no" id="options/visibility-desc:0" translate="yes">
<source>Specify initial visibility</source>
<target>Die anfängliche Sichtweite in Metern angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/visibility-miles-desc:0" translate="yes">
<source>Specify initial visibility in miles</source>
<target>Die anfängliche Sichtweite in Meilen angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vor-desc:0" translate="yes">
<source>Specify starting position relative to a VOR</source>
<target>Startposition relativ zu einem VOR angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/vor-freq-desc:0" translate="yes">
<source>Specify the frequency of the VOR. Use with --vor=ID</source>
<target>Die Frequenz des VOR angeben. Verwendung zusamen mit --vor=ID</target>
</trans-unit>
<trans-unit approved="no" id="options/wBody-desc:0" translate="yes">
<source>Specify velocity along the body Z axis</source>
<target>Geschwindigkeit entlang der Z-Achse des Flugzeugs angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/wind-desc:0" translate="yes">
<source>Specify wind coming from DIR (degrees) at SPEED (knots)</source>
<target>Windrichtung und -geschwindigkeit in Grad und Knoten angeben</target>
</trans-unit>
<trans-unit approved="no" id="options/wp-desc:0" translate="yes">
<source>Specify a waypoint for the GC autopilot;</source>
<target>Wegpunkt für den Autopiloten angeben</target>
</trans-unit>
</group>
<group resname="sys" restype="x-trolltech-linguist-context">
<trans-unit approved="no" id="sys/binding-subsystems:0" translate="yes">
<source>binding subsystems</source>
<target>Binde Subsysteme</target>
</trans-unit>
<trans-unit approved="no" id="sys/creating-subsystems:0" translate="yes">
<source>creating subsystems</source>
<target>Erzeuge Subsysteme</target>
</trans-unit>
<trans-unit approved="no" id="sys/downloading-scenery:0" translate="yes">
<source>downloading scenery</source>
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 00:09:50 +00:00
<target>Herunterladen der Szenerie</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/finalize-position:0" translate="yes">
<source>finalizing position</source>
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 00:09:50 +00:00
<target>Vorbereiten der Ausgansposition</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/finishing-subsystems:0" translate="yes">
<source>finalizing subsystems</source>
<target>Finalisiere Subsysteme</target>
</trans-unit>
<trans-unit approved="no" id="sys/init:0" translate="yes">
<source>initializing</source>
<target>Initialisiere</target>
</trans-unit>
<trans-unit approved="no" id="sys/init-graphics:0" translate="yes">
<source>initializing graphics engine</source>
<target>Initialisiere Grafik</target>
</trans-unit>
<trans-unit approved="no" id="sys/init-scenery:0" translate="yes">
<source>initializing scenery</source>
<target>Initialisiere Szenerie</target>
</trans-unit>
<trans-unit approved="no" id="sys/init-subsystems:0" translate="yes">
<source>initializing subsystems</source>
<target>Initialisiere Subsysteme</target>
</trans-unit>
<trans-unit approved="no" id="sys/loading-aircraft:0" translate="yes">
<source>loading aircraft</source>
<target>Lade Flugzeug</target>
</trans-unit>
<trans-unit approved="no" id="sys/loading-aircraft-list:0" translate="yes">
<source>loading aircraft list</source>
<target>Lade Flugzeugliste</target>
</trans-unit>
<trans-unit approved="no" id="sys/loading-nav-dat:0" translate="yes">
<source>loading navigation data</source>
<target>Lade Navigationsdaten</target>
</trans-unit>
<trans-unit approved="no" id="sys/loading-scenery:0" translate="yes">
<source>loading scenery</source>
<target>Lade Szenerie</target>
</trans-unit>
<trans-unit approved="no" id="sys/navdata-fixes:0" translate="yes">
<source>loading fixes</source>
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 00:09:50 +00:00
<target>Lade Navigationsdaten</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/navdata-loading-airports:0" translate="yes">
<source>loading airport data</source>
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 00:09:50 +00:00
<target>Lade Flughäfen</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/navdata-navaids:0" translate="yes">
<source>loading navigation aid data</source>
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 00:09:50 +00:00
<target>Lade Navigationsdaten</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/navdata-pois:0" translate="yes">
<source>loading points of interest</source>
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 00:09:50 +00:00
<target>Lade Navigationsdaten</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/navdata-reading-apt-dat-files:0" translate="yes">
<source>reading airport data</source>
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 00:09:50 +00:00
<target>Lese Flughäfen</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="sys/unstable-warning:0" translate="yes">
<source>Unstable nightly build - some features may be under active development</source>
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 00:09:50 +00:00
<target>Entwicklerversion: kann instabile/unfertige Features enthalten!</target>
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-02 20:24:17 +00:00
</trans-unit>
</group>
<group resname="tips" restype="x-trolltech-linguist-context">
<trans-unit approved="no" id="tips/tip:0" translate="yes">
<source>Drag while holding the right mouse button to look around</source>
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 00:09:50 +00:00
<target>Zum Steuern der Blickrichtung die Maus bei gedrückter rechter Taste bewegen!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:1" translate="yes">
<source>Hold [Shift] while looking around to move the view up, down, left or right</source>
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 00:09:50 +00:00
<target>Halte beim Ändern der Blickrichtung [Shift] gedrückt, um den Blick nach oben/unten/links/rechts zu bewegen.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:2" translate="yes">
<source>Press a/A to adjust the simulation speed</source>
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 00:09:50 +00:00
<target>Tasten a/A drücken, um die Simulationsgeschwindigkeit anzupassen.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:3" translate="yes">
<source>Press x/X to zoom in and out</source>
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 00:09:50 +00:00
<target>Drücke x/X um rein oder raus zu zoomen</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:4" translate="yes">
<source>Find frequencies of nearby ATC services from the Radios dialog</source>
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 00:09:50 +00:00
<target>Die Frequenzen der umliegenden ATC Stationen können über den Radio-Dialog gefunden werden.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:5" translate="yes">
<source>Press v to change your viewpoint, Ctrl-V to return to the cockpit</source>
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 00:09:50 +00:00
<target>Drücke v, um die Perspektive zu wechseln. Strg-V kehrt ins Cockpit zurück.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:6" translate="yes">
<source>Press F3 to take a screenshot</source>
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 00:09:50 +00:00
<target>Drücke F3, um ein Bildschirmfoto zu erstellen.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:7" translate="yes">
<source>Join the FlightGear community at http://forum.flightgear.org</source>
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 00:09:50 +00:00
<target>Trete der FlightGear Community bei: http://forum.flightgear.org</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:8" translate="yes">
<source>Press h to bring up a Heads Up Display</source>
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 00:09:50 +00:00
<target>Drücke h, um das Heads-Up-Display zu aktivieren.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:9" translate="yes">
<source>Show or hide the menu bar by pressing F10</source>
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 00:09:50 +00:00
<target>Drücke F10, um die Menüzeile ein-/auszublenden.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:10" translate="yes">
<source>Frame-rate too low? - try disabling AI traffic</source>
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 00:09:50 +00:00
<target>Ruckelt die Simulation? Versuche z.B. den KI Verkehr abzuschalten.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:11" translate="yes">
<source>Select Environment → Weather to fly in different weather</source>
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 00:09:50 +00:00
<target>Wähle Umgebung → Wetter, um in verschiedenen Wetterlagen zu fliegen.</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:12" translate="yes">
<source>Press F12 to change the radio frequencies easily</source>
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 00:09:50 +00:00
<target>Drücke F12, um die Funk-Frequenzen einzustellen!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:13" translate="yes">
<source>Look around by holding down the right mouse button and moving the mouse</source>
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 00:09:50 +00:00
<target>Zum Steuern der Blickrichtung die Maus bei gedrückter rechter Taste bewegen!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:14" translate="yes">
<source>Select Multiplayer → Multiplayer Settings to join the shared flight environment</source>
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 00:09:50 +00:00
<target>Wähle Multiplayer → Multiplayer Konfiguration um gemeinsam mit anderen Piloten zu fliegen!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:15" translate="yes">
<source>Can't get the engine started? - see Help → Aircraft Checklists</source>
Updated German translation
2017-12-31 14:18:15 +00:00
<target>Probleme den Motor zu starten? Siehe Hilfe → Aircraft Checklists</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:16" translate="yes">
<source>Drag while holding the middle and right mouse buttons to move the viewpoint</source>
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 00:09:50 +00:00
<target>Zum Steuern des Standpunkts die Maus bei gedrückter mittlerer und rechter Taste bewegen!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:17" translate="yes">
<source>Press / to explore the internals of the simulator</source>
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 00:09:50 +00:00
<target>Drücke "/", um Internas des Simulators zu erkunden!</target>
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-02 20:24:17 +00:00
</trans-unit>
<trans-unit approved="no" id="tips/tip:18" translate="yes">
<source>Press Tab to move the viewpoint with your mouse and use the scroll wheel to zoom</source>
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 00:09:50 +00:00
<target>Drücke TAB, um den Standpunkt mit der Maus zu bewegen und mit dem Scroll-Rad zu zoomen!</target>
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-02 20:24:17 +00:00
</trans-unit>
</group>
</body>
</file>
Sync translations
2019-12-24 22:12:28 +00:00
</xliff>
Copy permalink