FlightGear wiki - User contributions [en]

Zh/Route manager

2018-07-02T06:24:05Z

Yfanhan:

{{BeingTranslated}}
{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

一个真实的'''路线管理器'''

==介绍==
(在下面的部分中，我们假设你知道基本的IFR概念，并会使用自动驾驶仪和无线电导航）

路线管理器模拟现实世界中GPS和FMS设备的功能，它在任何飞机中都是可用的。一些驾驶舱仪器可以通过自己的UI访问路线管理器，航线管理器也是飞行计划提供给Flightgear的途径。在未来，这将希望允许更好的ATC和多人互动，因为ATC将能够看到飞行员的飞行计划。

It's important to realize that the route-manager (and GPS) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.
==概念==

==制作路线==

===标准仪表离场和标准仪表进场===

===如何飞进场===

==激活路线==

==飞一个路线==

==对准跑道==

==特性==

==有用的软件==

==相关内容==

Zh/Route manager

2018-07-02T06:23:43Z

Yfanhan:

{{BeingTranslated}}
{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

一个真实的'''路线管理器'''

==介绍==
(在下面的部分中，我们假设你知道基本的IFR概念，并会使用自动驾驶仪和无线电导航）
路线管理器模拟现实世界中GPS和FMS设备的功能，它在任何飞机中都是可用的。一些驾驶舱仪器可以通过自己的UI访问路线管理器，航线管理器也是飞行计划提供给Flightgear的途径。在未来，这将希望允许更好的ATC和多人互动，因为ATC将能够看到飞行员的飞行计划。

It's important to realize that the route-manager (and GPS) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.
==概念==

==制作路线==

===标准仪表离场和标准仪表进场===

===如何飞进场===

==激活路线==

==飞一个路线==

==对准跑道==

==特性==

==有用的软件==

==相关内容==

Zh/Howto:Creating 3D instruments

2018-07-02T05:57:53Z

Yfanhan:

本教程描述了制作在FlightGear中使用的3D仪器的基本过程。现在，我们假设你已经完成了仪器的3D模型。我们将会用FITK 50的ITT测量仪作为例子来教会你如何添加3D仪器模型进入驾驶舱。

=== 你需要什么 ===
* 一个文本编辑器（即使是记事本也可以，但是语法高亮可以帮助你找出错误。如果你在Windows上[http://notepad-plus.sourceforge.net/uk/site.htm Notepad++],看起来很合适。）
* 你的3D模型
* Flightgear
=== Creating the XML file ===
The first step is to create an XML file which will load the 3D model and animate it. There are no hard and fast rules about where these files should live or what they must be called, but we'll follow the fairly standard procedure of calling it itt.xml and placing it in the Models directory.

So, using your favourite text editor, create a file called itt.xml in the Aircraft/fokker50/Models directory (folder).

It should start like this (and please remember that case is ALWAYS important);

<?xml version="1.0"?>
<PropertyList>
</PropertyList>

Everything you will add to this file '''must''' go between the <PropertyList> tags.

Now, our file does nothing useful at this point. First of all, we want to tell FG to load the 3d model of our instrument. Add a section under <PropertyList> like this;

<path>itt.ac</path>

This is obviously the name of the 3d model file we wish to load. The model in question looks like this:

[[File:Fokker51_ITT_screenshot1.jpg]]

=== Adding an animation ===

{{main article | Howto:_Animate_models}}

As you can see, the main item to animate is the temperature needle, and its name is "needle" (you can animate either [[AC3D]] "objects" or complete "groups"). We will want to use a "rotate" animation (for more details on available animation types, see "model-howto.html" which is provided with FG in the Docs directory.)

So, we add an <animation> section to our XML file.

<pre>
<animation>
<type>rotate</type>
<object-name>needle</object-name>
</pre>

Now, we need to specify a property which will determine the amount of rotation required; in other words, the property that provides the ITT value at any one time. To find the name of this property, we need to start FlightGear in the usual manner with the correct aircraft (fokker50 in this case). Once FG has started, open the property browser (file/browse internal properties). You will see the top level of the property tree. Click on "engines" and you will see a list of engines; click on the first one (engine) and you will see a long list of properties and their current values.

[[File:Fokker50_prop_browser_screenshot1.jpg]]

Now, we have a slight problem at this stage; the fokker50 was created before JSBSim could model turboprops, and so the ITT property is not available right now. For the purposes of this tutorial though, we'll just use the exhaust temperature instead; the process is what's important.

So, the next line in our XML file will specify the property to use;

<property>engines/engine/egt_degf</property>

Next we need to specify exactly how much that property moves the needle. There are several ways to do this, but we'll use a simple interpolation table since these are especially useful in more complicated situations. The ITT gauge is marked from 0 degC to 1200 degC; since we're having to use a value that's reported in degF for now, we'll just convert those two values. 0 degC is about 32 degF and 1200 degC is about 2192 degF. Two handy tips here; for Linux/unix users, the "units" program is truly invaluable; for everyone, google has a useful units converter; for example search for "
1200 degrees celsius in fahrenheit"

On to our table then.

<pre>
<interpolation>
<entry><ind>32</ind><dep>0</dep></entry>
<entry><ind>2192</ind><dep>230</dep></entry>
</interpolation>
</pre>

The <ind> entries are the ''ind''ependent variables, or values read from the property tree; the <dep> entries are the ''dep''endent variables, or corresponding degrees the object will be rotated by. In this case I found that number by rotating the needle in AC3D from one end of the scale to the other and reading off the rotation value reported (see screenshot)

[[File:Fokker50_rotation_value.jpg]]

Having configured the type of animation, the controlling property, and specified the effect of that property, we need to describe an axis and centre for the animation.

In this case, the centre is easy, because the needle centre is at the origin of the 3d model. If you wanted the rotation centre to be somewhere else, you could use your modelling app to obtain these values.

<pre>
<center>
<x-m>0</x-m>
<y-m>0</y-m>
<z-m>0</z-m>
</center>
</pre>

The axis is also very simple in this case;

<pre>
<axis>
<x>-1</x>
<y>0</y>
<z>0</z>
</axis>
</pre>

The negative sign on the x axis means that the rotation will be clockwise when viewed from the -x direction (i.e. looking "forwards")

That concludes the rotation animation and so (as always) we need to add a suitable closing tag;

<pre>
</animation>
</pre>

=== Digital display ===
Our itt.xml file, as it stands, should now "work" in flightgear; that is, it will animate the needle object to display exhaust temperature on the first engine, in degC (despite the input property being in degF!)

However, the bottom half of the gauge contains a digital readout of the same information, and we haven't mentioned that yet. In order to only introduce one new aspect at a time, for the moment I am going to ignore the fact that our input property is in degF and simply display it using the digits; there are several ways we could display degC (or indeed any kind of value) instead, but those are probably best left to another tutorial.

Now, in order to give the illusion of a digital display, we are going to use a slightly less obvious technique than the simple rotation used for the needle. Our digits are going to come from this texture, freshly borrowed from another model in FlightGear (remember, this is open source software - don't reinvent the wheel unless it's absolutely necessary!).

[[File:digits.jpg]]

Now, each "digit" in the 3d model is a separate rectangle, and each is mapped to the number zero on that texture. What we are going to do is use a "textranslate" animation to slide the texture along to the relevant number in each case. Here's the code for the first digit;

<pre>

<animation>
<type>textranslate</type>
<object-name>digit1</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.0001</factor>
<step>1000</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

As always, if you need more detailed explanations of any of these animations, remember to RTFM which in this case is the model-howto.html referred to previously.

Each subsequent digit is handled in the same way, though with the object-name, factor and step values modified accordingly.

For example, the next digit along, the "hundreds" digit;

<pre>
<animation>
<type>textranslate</type>
<object-name>digit2</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

And so on, for the remaining two. Now, your itt instrument should display the EGT in degC using the needle, and give a "digital" readout of the same in degF.

=== Level Of Detail ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

To prevent objects like this instrument being drawn when the aircraft is actually too far away for them to be seen anyway we use a Level Of Detail section (a "range" "animation".) Notice the <pre></pre> section; this is a comment, feel free to add them where you need a reminder of what's going on.

<pre>

<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</pre>

Now, if you've managed to stay with us the whole way through, the file should look something like this one, which you can download and compare with. [[Media:itt.xml]] Notice that under each new opening xml tag (such as <animation>) the text is indented one more level. Sensible people(!) use one tab to indent each level, others try to use various numbers of spaces to indent; whatever you use, the single most important thing is to be consistent. Consistent indentation makes the file much easier to read.

=== Including the instrument in an aircraft ===

Now to the exciting bit, actually seeing the fruits of our labour in FlightGear!
Including our itt.xml file in the fokker50 is actually an easy step. The "model" XML file controls the 3d model; this is often called aircraftname-model.xml and nearly always lives in the aircraftname/Models directory. However, FG is very flexible and in this case, the model XML file is fokker50/Models/fokker50.xml . To avoid confusion, it would be preferable for this to be called fokker50-model.xml, and if you're creating one from scratch, please use that convention.

If we open that file in a text editor, it should look quite familiar; you will recognise the way it specifies an ac3d file, and animates the various parts of it. However, we wish to include an instrument, and that is done very simply. Below the <offsets> section, add a section like this;

<pre>

<model>
<path>Aircraft/fokker50/Models/itt.xml</path>
<offsets>
<x-m>-8.9088</x-m>
<y-m>-0.0811</y-m>
<z-m>-1.0722</z-m>
<pitch-deg>-10</pitch-deg>
</offsets>
</model>
</pre>

Those numbers can be easily obtained from your 3d modelling app; just open the aircraft model and place an object in the correct position, then use the distances here. The usual FG model coordinate system is used; x=back, y=right, z=up, from the pilot's perspective; the origin is the one in the 3d model (.ac file). The "pitch" entry is fairly obvious; pitch of zero is a completely vertical instrument, pitch of -90 is one tilted "top edge forwards" to lie flat.

Now, when you start FlightGear, you should see your fully-working instrument in all its glory, situated where it ought to be! If you need to move it later, it's trivial to tweak the numbers above to suit.

[[Category:Aircraft enhancement]]
[[Category:Modeling]]
[[Category:Howto|Creating 3D instruments]]

Howto:Creating 3D instruments

2018-07-02T05:38:54Z

Yfanhan:

This tutorial describes the basic process of '''creating''' a 3D '''instrument''' for use in [[FlightGear]]. For now, we're assuming that you have created the actual 3d model to use and wish to include it in a cockpit and animate it. As an example, we will be animating the ITT gauge for the [[Fokker 50]].

=== What you need ===
You will need:
* a text editor (even notepad will do, but one that does syntax highlighting might help you spot typos more easily; if you're on Windows, [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] looks suitable.)
* your 3d modelling package
* and of course a copy of FlightGear

=== Creating the XML file ===
The first step is to create an XML file which will load the 3D model and animate it. There are no hard and fast rules about where these files should live or what they must be called, but we'll follow the fairly standard procedure of calling it itt.xml and placing it in the Models directory.

So, using your favourite text editor, create a file called itt.xml in the Aircraft/fokker50/Models directory (folder).

It should start like this (and please remember that case is ALWAYS important);

<?xml version="1.0"?>
<PropertyList>
</PropertyList>

Everything you will add to this file '''must''' go between the <PropertyList> tags.

Now, our file does nothing useful at this point. First of all, we want to tell FG to load the 3d model of our instrument. Add a section under <PropertyList> like this;

<path>itt.ac</path>

This is obviously the name of the 3d model file we wish to load. The model in question looks like this:

[[File:Fokker51_ITT_screenshot1.jpg]]

=== Adding an animation ===

{{main article | Howto:_Animate_models}}

As you can see, the main item to animate is the temperature needle, and its name is "needle" (you can animate either [[AC3D]] "objects" or complete "groups"). We will want to use a "rotate" animation (for more details on available animation types, see "model-howto.html" which is provided with FG in the Docs directory.)

So, we add an <animation> section to our XML file.

<pre>
<animation>
<type>rotate</type>
<object-name>needle</object-name>
</pre>

Now, we need to specify a property which will determine the amount of rotation required; in other words, the property that provides the ITT value at any one time. To find the name of this property, we need to start FlightGear in the usual manner with the correct aircraft (fokker50 in this case). Once FG has started, open the property browser (file/browse internal properties). You will see the top level of the property tree. Click on "engines" and you will see a list of engines; click on the first one (engine) and you will see a long list of properties and their current values.

[[File:Fokker50_prop_browser_screenshot1.jpg]]

Now, we have a slight problem at this stage; the fokker50 was created before JSBSim could model turboprops, and so the ITT property is not available right now. For the purposes of this tutorial though, we'll just use the exhaust temperature instead; the process is what's important.

So, the next line in our XML file will specify the property to use;

<property>engines/engine/egt_degf</property>

Next we need to specify exactly how much that property moves the needle. There are several ways to do this, but we'll use a simple interpolation table since these are especially useful in more complicated situations. The ITT gauge is marked from 0 degC to 1200 degC; since we're having to use a value that's reported in degF for now, we'll just convert those two values. 0 degC is about 32 degF and 1200 degC is about 2192 degF. Two handy tips here; for Linux/unix users, the "units" program is truly invaluable; for everyone, google has a useful units converter; for example search for "
1200 degrees celsius in fahrenheit"

On to our table then.

<pre>
<interpolation>
<entry><ind>32</ind><dep>0</dep></entry>
<entry><ind>2192</ind><dep>230</dep></entry>
</interpolation>
</pre>

The <ind> entries are the ''ind''ependent variables, or values read from the property tree; the <dep> entries are the ''dep''endent variables, or corresponding degrees the object will be rotated by. In this case I found that number by rotating the needle in AC3D from one end of the scale to the other and reading off the rotation value reported (see screenshot)

[[File:Fokker50_rotation_value.jpg]]

Having configured the type of animation, the controlling property, and specified the effect of that property, we need to describe an axis and centre for the animation.

In this case, the centre is easy, because the needle centre is at the origin of the 3d model. If you wanted the rotation centre to be somewhere else, you could use your modelling app to obtain these values.

<pre>
<center>
<x-m>0</x-m>
<y-m>0</y-m>
<z-m>0</z-m>
</center>
</pre>

The axis is also very simple in this case;

<pre>
<axis>
<x>-1</x>
<y>0</y>
<z>0</z>
</axis>
</pre>

The negative sign on the x axis means that the rotation will be clockwise when viewed from the -x direction (i.e. looking "forwards")

That concludes the rotation animation and so (as always) we need to add a suitable closing tag;

<pre>
</animation>
</pre>

=== Digital display ===
Our itt.xml file, as it stands, should now "work" in flightgear; that is, it will animate the needle object to display exhaust temperature on the first engine, in degC (despite the input property being in degF!)

However, the bottom half of the gauge contains a digital readout of the same information, and we haven't mentioned that yet. In order to only introduce one new aspect at a time, for the moment I am going to ignore the fact that our input property is in degF and simply display it using the digits; there are several ways we could display degC (or indeed any kind of value) instead, but those are probably best left to another tutorial.

Now, in order to give the illusion of a digital display, we are going to use a slightly less obvious technique than the simple rotation used for the needle. Our digits are going to come from this texture, freshly borrowed from another model in FlightGear (remember, this is open source software - don't reinvent the wheel unless it's absolutely necessary!).

[[File:digits.jpg]]

Now, each "digit" in the 3d model is a separate rectangle, and each is mapped to the number zero on that texture. What we are going to do is use a "textranslate" animation to slide the texture along to the relevant number in each case. Here's the code for the first digit;

<pre>

<animation>
<type>textranslate</type>
<object-name>digit1</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.0001</factor>
<step>1000</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

As always, if you need more detailed explanations of any of these animations, remember to RTFM which in this case is the model-howto.html referred to previously.

Each subsequent digit is handled in the same way, though with the object-name, factor and step values modified accordingly.

For example, the next digit along, the "hundreds" digit;

<pre>
<animation>
<type>textranslate</type>
<object-name>digit2</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

And so on, for the remaining two. Now, your itt instrument should display the EGT in degC using the needle, and give a "digital" readout of the same in degF.

=== Level Of Detail ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

To prevent objects like this instrument being drawn when the aircraft is actually too far away for them to be seen anyway we use a Level Of Detail section (a "range" "animation".) Notice the <pre></pre> section; this is a comment, feel free to add them where you need a reminder of what's going on.

<pre>

<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</pre>

Now, if you've managed to stay with us the whole way through, the file should look something like this one, which you can download and compare with. [[Media:itt.xml]] Notice that under each new opening xml tag (such as <animation>) the text is indented one more level. Sensible people(!) use one tab to indent each level, others try to use various numbers of spaces to indent; whatever you use, the single most important thing is to be consistent. Consistent indentation makes the file much easier to read.

=== Including the instrument in an aircraft ===

Now to the exciting bit, actually seeing the fruits of our labour in FlightGear!
Including our itt.xml file in the fokker50 is actually an easy step. The "model" XML file controls the 3d model; this is often called aircraftname-model.xml and nearly always lives in the aircraftname/Models directory. However, FG is very flexible and in this case, the model XML file is fokker50/Models/fokker50.xml . To avoid confusion, it would be preferable for this to be called fokker50-model.xml, and if you're creating one from scratch, please use that convention.

If we open that file in a text editor, it should look quite familiar; you will recognise the way it specifies an ac3d file, and animates the various parts of it. However, we wish to include an instrument, and that is done very simply. Below the <offsets> section, add a section like this;

<pre>

<model>
<path>Aircraft/fokker50/Models/itt.xml</path>
<offsets>
<x-m>-8.9088</x-m>
<y-m>-0.0811</y-m>
<z-m>-1.0722</z-m>
<pitch-deg>-10</pitch-deg>
</offsets>
</model>
</pre>

Those numbers can be easily obtained from your 3d modelling app; just open the aircraft model and place an object in the correct position, then use the distances here. The usual FG model coordinate system is used; x=back, y=right, z=up, from the pilot's perspective; the origin is the one in the 3d model (.ac file). The "pitch" entry is fairly obvious; pitch of zero is a completely vertical instrument, pitch of -90 is one tilted "top edge forwards" to lie flat.

Now, when you start FlightGear, you should see your fully-working instrument in all its glory, situated where it ought to be! If you need to move it later, it's trivial to tweak the numbers above to suit.

[[Category:Aircraft enhancement]]
[[Category:Modeling]]
[[Category:Howto|Creating 3D instruments]]

[[zh:Howto:Creating_3D_instruments]]

Howto:Creating 3D instruments

2018-07-02T05:38:02Z

Yfanhan:

Zh/Howto:Creating 3D instruments

2018-07-02T05:36:43Z

Yfanhan: Created page with "This tutorial describes the basic process of '''creating''' a 3D '''instrument''' for use in FlightGear. For now, we're assuming that you have created the actual 3d model..."

Zh/Using TerraGear

2018-02-10T14:07:42Z

Yfanhan: Created page with "TerraGear Process Flow Chart TerraGear软件项目用创建flightgear中表示地形和包括机场，城市，森林，河流，..."

[[File:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]]
[[TerraGear]]软件项目用创建flightgear中表示地形和包括机场，城市，森林，河流，田野，道路的地景的文件来支持[[flightgear]]

Using TerraGear

2018-02-10T07:30:13Z

Yfanhan:

{{Out of date}}

[[File:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]]
The [[TerraGear]] software project supports [[FlightGear]] by creating the files used by FlightGear to represent the elevation and texture of the earth, including airports, cities, fields, forests, rivers, roads and so on. The TerraGear software reads data files containing ground elevation, airport locations and layouts, geographical land-cover data, and more, and produces the scenery files used by FlightGear to represent the terrain of the world.

For simplicity and convenience, most FlightGear users simply download the plug-and-play scenery files from the FlightGear scenery server, or use [[TerraSync]] to automatically download scenery as needed. But there is a variety of reasons you might want to use TerraGogrear to produce your own terrain files, rather than downloading the standard FlightGear scenery.

For instance, if you use [[WorldEditor]] to modify/improve information about an [[:Category:Airports|airport]]'s taxiway/apron layout, you might wish to see how that modified airport would look in the scenery before deciding you're happy with the results. Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher-resolution vector data (vmap1, Tiger, osm) to get better roads/streams. For all these reasons, learning how to use TerraGear is a good idea.

== Obtaining TerraGear ==
You can either build TerraGear yourself, or download a pre-compiled binary. The later is the easiest and advised for starters.

* '''Option 1a - Download TerraGear pre-compiled (recommended for beginners) on Windows'''
*# Download the latest TerraGear build from the [http://build.flightgear.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip FlightGear Build Server].
*# Create or choose a directory to hold the TerraGear tools.
*# Unzip the package and move the files from <code>archive/install/msvc100/TerraGear/bin</code> into a sub-directory named <code>Terragear/</code> in the base directory.

* '''Option 1b - Download ppa packages for Ubuntu Linux'''

https://launchpad.net/~saiarcot895/+archive/ubuntu/flightgear-edge/+index?batch=75&memo=75&start=75

* '''Option 2 - Compile TerraGear from source code''' as explained in [[Building TerraGear|this article]].

{{note|1=You might need <code>default_priorities.txt</code> from the {{terragear source|path=src/BuildTiles/Main/default_priorities.txt|text=git repository}} or from the archive downloaded from the build server (in the <code>archive/install/msvc100/TerraGear/share</code> subdirectory). See [http://forum.flightgear.org/viewtopic.php?f=5&p=77950 this forum thread] for details.}}

=== GUI tool ===
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Using TerraGear ==
First, choose the boundaries for the area of scenery you want to build, in terms of latitude and longitude. The smaller the area of scenery you generate, the smaller the amount of data you will need, and the less CPU time it will take. For example, if you are just interested in generating a new airport layout at 12.3W 34.4N, then simply generating the scenery between 12W 34N and 13W 35N would be sufficient.

Write down the bounding box (minimum and maximum longitude and latitude) for the scenery you want to generate. Remember that West and South are negative - in essence 4W 10S would be -4, -10. Try not to get mixed up, otherwise you'll end up generating scenery or airports on the other side of the planet!

You'll be dealing with multiple different types of data in various formats. Create a new directory for your scenery work. Within that directory, create the following sub-directories:

; <code>data/</code>: For raw and pre-processed data (eg elevation files)
; <code>output/</code>: For the scenery files you will create
; <code>work/</code>: For data that has been processed (eg by shape-decode) and is ready to be munged into scenery

=== Obtaining and processing data ===
TerraGear uses three different kinds of information to generate scenery:

# The elevation of the land (provided by SRTM)
# The location and layout of airports (provided by apt.dat or a custom .dat)
# Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0, [[CORINE]] etc. or custom shapefiles)

This article describes how obtain and process each of these types of data in order, and bring it together for use by FlightGear. The order of these steps is important. For example, the airport data step needs the elevation data to determine the elevation of the airports and thus you should start with preparing elevation data.

{{caution|For inclusion in the official FlightGear scenery, all data '''must''' come from [[GNU GPL]] compatible sources!}}

==== Elevation data ====
The best worldwide elevation data currently available is from the Shuttle Radar Topography Mission (SRTM). There are two types of SRTM data:
* Highly accurate 1-arcsecond resolution data, known as SRTM-1, for the USA
* Less accurate 3-arcsecond resolution data, known as SRTM-3, for the rest of the world.
From now on, we'll assume you are using SRTM-3 data. Unless otherwise noted, the process for SRTM-1 is identical.

You can download the appropriate data from http://dds.cr.usgs.gov/srtm/version2_1/. You want all .hgt.zip files covering your region of interest. Depending on the size of your scenery, there may be quite a few. Download them to <code>data/SRTM-1/</code> (or SRTM-3/SRTM-30 depending on the type you downloaded) in your base directory. (Genapts looks for a few known, hardcoded elevation data directories in its working directory. SRTM-30 is one of them and this is the least confusing in that list. Note: W.E.F. 31st July 2010, the genapts tool now also looks for SRTM-1/SRTM-3 directories. If you are using an older version, please supply the directories using --dem-path).

Now we've got the data, we need to convert it into something of use to TerraGear. First, you need to unzip each of the .hgt files. After that, open the commandline (Windows: Start > Run > <code>cmd.exe</code>) and change into the base directory (<code>cd .../.../TerraGear</code>).

{{note|According to [[TerraGear_Documentation]], hgtchop is superseded by gdalchop.}}
{{note|For SRTM-1 data, replace the <code>3</code> by a <code>1</code> in the first argument to hgtchop}}
{{tip|If you want to create a batch-file, replace <code>%f</code> with <code>%%f</code>, see [http://technet.microsoft.com/en-us/library/bb490909.aspx]}}

For Windows:
for %f in (.\data\SRTM-3\*.hgt) do .\Terragear\hgtchop.exe 3 %f .\work\SRTM-3
or
for %f in (.\data\SRTM-3\*.hgt) do .\Terragear\hgtchop.exe 3 .\data\SRTM-3\%f .\work\SRTM-3

For Linux:
for f in ${PWD}/data/SRTM-3/*.hgt; do ./Terragear/hgtchop 3 "${f}" "${PWD}/work/SRTM-3"; done

Now you will get a lot of .arr.gz files in your work/SRTM-3/ directory. We need to convert these to the .fit.gz format. Run the commandline again with

{{note|The space and dot at the and are important!}}

For Windows:
.\Terragear\terrafit.exe work\SRTM-3

For Linux:
./Terragear/terrafit work/SRTM-3

==== Airport data ====
Now we've got elevation data, we can generate our airports. First, create a <code>data/airports/</code> directory and copy in your apt.dat file. This may be direct from your FlightGear data package (though you'll need to unzip it), or it may be one that you've modified with [[WorldEditor]].

The command to create airports is "genapts850". Run it without any arguments to see the various command-line options.

If it is simply run with a specified apt.dat and work directory, it will generate airport layouts for every airport in the file, which can take a long time. Make sure the input is not the apt.dat.gz, but an uncompressed file. Otherwise genapts850 will block and not produce any output.

If you are just creating a single airport and you know the ICAO ID (for example [[San Francisco International Airport|KSFO]], EGPH or EG32), use it as follows from your root scenery directory (in essence the directory above your data, work and output directories). If you use an apt.dat file with one single airport in it you should omit the <code>--airport</code> parameter.

genapts850 --input=data/airports/apt.dat --work=./work --airport=<AIRPORT_ID>

or, if you have elevation data available:

genapts850 --input=data/airports/apt.dat --work=./work --dem-path=SRTM-3

If you are generating a larger set of scenery, then you can specify the minimum and maximum longitude and latitude.

Genapts will create two sub-directories in your work directory:

* <code>AirportArea/</code>
* <code>AirportObj/</code>

These contain the definitions of the airport layout and any objects present (e.g. windsocks and beacons).

==== Landuse data ====
The final piece of data we need to generate is the landuse data. In general, this is taken from the VMAP0 dataset as shapefiles from the scenery database mapserver, but other sources can also be used.

The landuse data can be split into a number of different types:

; Landmass: Separates the land from the sea. It can be used as a mask for all other data. The most commonly used is the VMAP0 Landmass, but GSHHS can also be used. When running tg-construct with <code>--ignore-landmass</code>, all input shapefiles will be taken into consideration, so no landmass mask is required then.
; Land use data: Defines whether a piece of land is forest, urban, sand, lava, glacier etc. These are usually VMAP0 data, defined as polygons.
; Line data: Includes railroads, streams, roads. Typically VMAP0, but also OpenStreetMap for roads.
; Point data: Is currently only used for defining towns.

By far the easiest way to get this data is to download shapefiles from the wonderful [http://mapserver.flightgear.org MapServer]. The MapServer lets you download the shapefiles for any selected scenery area. Click on the "Download Shapefiles" link (or go direct: http://mapserver.flightgear.org/download.psp). Enter in the bounding box of the scenery you want to generate, select the type of shapefile data you want, and click download.

==== Layers ====

; <code>v0</code>: Global coverage, low detail. This is "the last resort", but unfortunately it is the only layer that covers the entire world.
; <code>cs</code>: It is v0 with some contributions someone did in the past. Get this instead of v0.
; <code>v1</code>: Only parts of some countries available, higher detail than v0.
; <code>clc06</code>: European '''only'''. Very high detail, this is the preferred choice for an European country.
; <code>osm</code>: Global coverage, high resolution but very low detail.
: This means: if you are interested in an area out of Europe and forests are defined in OpenStreetMaps for your area, this is going to be the best data source. If forests are not defined, you will get a dull, neverending DEFAULT landclass. OSM provides the best coastline and I encourage you to use this coastline even in Europe. [http://forum.flightgear.org/viewtopic.php?f=5&t=25549&sid=d501cb651ef9e34ca9dc8fae429d51ab&p=234002#p234002]

{{caution|Make sure each shape file is in its own directory whether you download shape files or create your own otherwise the ogrDecode step will fail.}}
Download each shapefile into a seperate (!) <code>data/shapefiles/...</code> directory. So, for v0_landmass, you would end up with <code>data/shapefiles/v0_landmass/v0_landmass.shp</code> etc.

You can load these shapefiles into a GIS editor such as [[QGIS]] or GRASS to view and edit. This is a good idea to verify you have the correct files! Later on, you can experiment with replacing various shapefiles with other versions (GSHHS for coastline, OSM for roads etc.).

The next step is to decode the shape-files into TerraGear format using the '''ogr-decode''' command (renamed to '''poly-decode''' in recent versions of TerraGear).

There are three important command-line arguments for ogr-decode:
* the destination directory for the decoded data
* the location of the shapefile's directory
* the material type

Each shape-file corresponds with one of the material types defined in the materials.xml files. The mapping is pretty obvious. For example, <code>v0_mixedcroppasturecover</code> maps to <code>MixedCropPastureCover</code>. Note that the material types are case-sensitive, so it is a good idea to refer to the <code>[[$FG_ROOT]]/Materials/default/materials.xml</code> file (<code>[[$FG ROOT]]/materials.xml</code> in FlightGear 2.6.0 and older) to hand so you can check. The exception is landmass, which - when used - MUST be mapped onto the type Default.

Additionally, there are a number of optional arguments, to indicate the width of line data (for roads, streams, railways), how large to make point data (for towns) and how long the longest straight line is allowed to be.

For example, to decode the <code>v0_landmass</code> shapefile, you use the following command:

ogr-decode --max-segment 500 --area-type Default work/Default data/shapefiles/v0_landmass

To create streams of width 10 metres

ogr-decode --max-segment 500 --line-width 10 --area-type Stream work/Stream data/shapefiles/v0_stream

To generate some towns about 1km across

ogr-decode --point-width 500 --area-type Town work/Town data/shapefiles/v0_town

Run this command for each shapefile in the set.

== Generating scenery ==
You will now have a work directory, with subdirectories like:
{|
|
: AirportArea
: AirportObj
: Bog
: Default
: DryCropPastureCover
: EvergreenBroadCover
: GrassCover
: IrrCropPastureCover
: Lake
: Marsh
: MixedCropPastureCover
| valign="top" |
: MixedForestCover
: Railroad
: Road
: Sand
: ScrubCover
: Shared
: SRTM-3
: Stream
: Town
: Urban
|}

Now we can actually generate the scenery. This is done by the tg-construct command. Run the command with <code>--help</code> to get usage information.

We need to define:
* The work (<code>--work-dir</code>) and output (<code>--output-dir</code>) directories.
* The center of the scenery we want to generate (<code>--lat</code> and <code>--lon</code>).
* The radius (<code>--xdist</code> and <code>--ydist</code>) from which to generate.
* All the work directories to include in the scenery.

{{note|The output directory must point to a <code>Terrain/</code> directory, else recent FlightGear versions will be unable to load the terrain.}}

For example:
{{Pre2|<nowiki>tg-construct --work-dir=./work --output-dir=./output/Terrain --min-lon=55 --max-lon=57 --min-lat=60 --max-lat=62 AirportArea SRTM-3 AirportObj Default Stream Bog IrrCropPastureCover Town Lake Urban Railroad DryCropPastureCover Road EvergreenBroadCover Marsh Sand MixedCropPastureCover ScrubCover GrassCover MixedForestCover</nowiki> }}

When this finishes, the output directory will contain a scenery sub-tree. Point to it by setting either [[$FG_SCENERY]] or by using the <code>--fg-scenery</code> command-line option to fgfs, and give your new scenery a try!

== Troubleshooting ==
Below is a list of common problems and solutions. If in doubt - Google it. Many problems (particularly when compiling TerraGear) have been hit before:

* Crashes in genapts. Sometimes genapts will crash when dealing with a particular airport. In that case, try running it again with the <code>--start-id</code> argument to start at the airport it failed on, and the <code>--nudge</code> argument which tries to nudge the calculations in the right direction.
* tg-construct killed. The tg-construct process may kill itself if it is using too many system resources. Increasing the values for <code>setrlimit</code> in <code>src/BuildTiles/Main/main.cxx</code> is the best solution.
* tg-construct silently stops immediately without an error and nothing goes to the "output" directory: make sure that lon/lat values correspond to tiles boundaries. See [[Tile Index Scheme]]
* Airports appear in the bottom of holes, or there are spaces between the airports and the scenery. This typically happens when genapts is unable to find the correct elevation data, or the elevation data changed between running genapts and shape-decode. Try generating a single airport in your scenery area using genapts, and look at the output. In particular, make sure there is a work/SRTM-3 directory.
* Only the airports appear in the scenery. There are three typical causes for this:
** You didn't download the correct shapefiles for the area.
** You haven't run shape-decode on the <code>v0_landmass</code> shapefile as Default
** You didn't include the correct directories in tg-construct.
* Generate scenery includes data removed from the shapefiles. If you are editing shapefiles, you need to delete the appropriate work subdirectory before running shape-decode. Otherwise your changes will be in addition to those already present.
* All the scenery is flat and at sea-level. Typically this is because you didn't include any elevation data in your tg-construct command. Make sure there's a STRM-3 directory included in the command-line.
* All terrain copies the material of a certain shapefile. You have probably forgotten to put each of the downloaded shapefiles in a seperate directory inside the Data/shapefiles directory.
* genapts850 never passes the stage "Adding airport <ICAO> to parse list": did you unzip <code>apt.dat.gz</code>?

== General comments from forum discussion ==
{{cquote|f-ojac, you are right, the parameters used in scenery 2.0 were "-e 5 -x 20000" according to the wiki. I don't know why I had the impression these parameters were not public. In any case, it does not matter because using the same parameters will create closer results, but they are not guaranteed to be the same.

The parameters used to create scenery 2,0 seem to be:

-m ??: the minimum number of vertices in a tile. In FG, any number bellow 100 (and probably, any number below 1000) will do. I don't think there is any surface on the world perfectly flat for several kilometers. The default value is 50 and I'm sure is ok for any normal use.
-e 5: the max allowed error for elevation, in meters. That is: if terrafit calculates a simplification of the terrain where all points are at most this distance from the real elevation, no more vertices are created. The default value is 40 meters: a point may have an elevation error up to 40m (~100ft) High values for this parameter create less detailed mountains and smaller (in disk size) and more efficient (in FPS) terrain.
-x 20000: the max number of vertices in a tile. If this number of vertices is reached, terrafit stop regardless the max error of the vertices. The default value is 1000

Keep in mind you can set values that do not make sense:

* "-e 1 -x 100" does not make sense because it is going to be impossible to calculate errors less than 1 meters using only 100 vertices. The max number of vertices will be reached always and the max error will be probably ignored.
* "-e 300 -x 20000" does not make sense, tiles are going to use for sure much less vertices than 20,000 because you are allowing huge elevation errors.

If you want an efficient scenery (less vertices), use the default values "-e 40 -x 1000". If you want more accurate elevation at the cost of disk space and FPS, use values similar to scenery 2.0 ("-e 5 -x 20000") Anything in the middle will produce performance and disk use in the middle.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=5&t=24681#p225363
|title=Re: Terrasync Help (surprinsingly!) :)
|author=ludomotico |date= Mon Nov 24, 2014 4:28 am}}</ref>|ludomotico}}

<references/>

== Related content ==
* [[Howto:Create custom terrain]], editing/making terrain data.
* [[TerraGear CORINE]], building terrain from CORINE data.
* [[TerraGear Documentation]], using TerraGear details.

{{Terra}}

[[Category:Scenery enhancement|TerraGear, Using]]

[[fr:Utiliser TerraGear]]
[[zh:Using TerraGear]]

Portal:Developer

2018-01-25T14:44:46Z

Yfanhan:

{{Main page/Header
|title=Welcome to the developer portal
|introduction=Please visit [http://forum.flightgear.org our forum] if you cannot find what you're looking for.
|rightbox=

|rightcolumn1= </div>
[[FlightGear and Git|Development repository status]] 
<center style="padding-top:.9em;">{{GitStatus}}</center>

|rightcolumn2= </div>
Getting started 

[[How the FlightGear project works]] 
[[Howto: Understand the FlightGear development process|The development process]] · [[Release plan]] 
[[Building FlightGear]] · [[FlightGear and Git|Git]] · [[FlightGear Build Server|Build server]] 
[[Property tree]] · [[File formats]] · [[Tools of the Trade]]

|rightcolumn3= </div>
General 

[[Long Term Goals|Long term goals]] · [[:Category:Popular Community Requests|Popular Ideas]] · [[Google Summer of Code]] 
[[Project Infrastructure Enhancements|Project infrastructure enhancements]] 
[[Improving Glider Realism|Improving glider realism]] / [[Improving Helicopter Realism|helicopter realism]] 
[[Howto:Set up a multiplayer server|Setting up a multiplayer server]] · [[FlightGear Expo Checklist|Expo checklist]]

|rightcolumn4= [[File:Portal aircraft.png|40px]]</div>
[[Portal:Developer/Aircraft|Aircraft]] 

[[Howto:Troubleshooting Aircraft Performance Issues]]·
[[Howto: Make an aircraft|Making an aircraft]] · [[Flight Dynamics Model|Flight dynamics model]] 
[[Howto: 3D Aircraft Models|3D aircraft models]] · [[Howto: Edit a livery|Liveries]] · [[:Category:Aircraft Resources|Resources]] 
[[Soaring instrumentation sdk]] · [[Creating instruments for FG|Creating instruments]] · [[System dependent instruments|System dependent instruments]] 
[[Howto: Design an autopilot|Designing an autopilot]]

|rightcolumn5= [[File:Nuvola apps kaboodle.png|40px]] </div>
Animations 

[[Howto: Animate models|Animate models]] · [[Howto: Illuminate faces|Illuminate objects]] 
[[Howto: Animate gear scissors|Gear scissors]] · [[Tracking animation]] 
[[Howto: Make a clickable panel|Clickable panels]] · [[Knob / slider animation]]

|rightcolumn6= [[File:Portal developer.png|40px]] </div>
Core 

[[:Category:FlightGear Core developers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] 
[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Nasal/CppBind|Adding scripting bindings]] 
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]] 
[[Built-in Profiler]] · [[Howto:Extend Nasal]] · [[Howto:Using Ada in FlightGear]] (updated!) 
[[Howto:Use Property Tree Objects]] · [[Code cleanup]] 
[[FlightGear-Points of Interest]] · [[Request for comments]] 
[[OpenSceneGraph]] · [[Rendering system improvements]]

|rightcolumn7= [[File:Portal scenery.png|40px]] </div>
[[Portal:Developer/Scenery|Scenery]] 

[[Procedural Texturing]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]] 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]] 
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]] 
[[Interactive traffic]]

|rightcolumn8= [[File:Nasallogo3.png|40px]] </div>
[[Nasal|Scripting]] 

[[Nasal FAQ|Frequently asked questions]] · [[Howto:Write simple scripts in Nasal|Writing simple scripts]] 
[[Nasal for C++ programmers]] · [[Nasal Variables|Variables and their types]] 
[[Nasal Conditionals|Conditionals]] · [[Nasal Loops|Loops]] · [[Nasal Operators|Operators]] · [[Nasal Console|In-sim console]]

|rightcolumn9= [[File:Animation Icon.png|40px]] </div>
Effects and shaders 

[[Shaders]] · [[Project Rembrandt]] 
[[Howto:Shader Programming in FlightGear|Shader programming in FlightGear]] 
[[Shader Coding - Best Practices|Best Practices]] · [[GLSL Shader Programming Resources|GLSL resources]]


|sections=

{{Main page/Leftbox|title=Put a piece of yourself into FlightGear!
|contents=In FlightGear, "development" is [[Howto:Understand the FlightGear development process|anything that improves the project]]. So, it's not just code-related [[Howto:Start core development|core development]]. There's also [[Portal:Developer/Scenery|scenery development]], [[Portal:Developer/Aircraft|aircraft development]] and all the stuff you can see in the column here on the left. If you want an extended overview, check out the [[Volunteer]] page.

Actually that's not all you can contribute. There's also documentation, with the [[FlightGear Manual]]... and this wiki of course! To contribute to the wiki, head off to the [[Portal:Wiki|Wiki Portal]]. There's a lot to do there too.

If you want to get in touch with other developers, register an account at the [http://forum.flightgear.org/viewforum.php?f=18 forum], and for core development subscribe to the [[mailing list]] too and consider visiting the {{tickets|issue tracker}}.

Remember: we might call it volunteering, but what should drive you is [[How the FlightGear project works|the fun of doing something]].
}}

{{Main page/Leftbox|title=For core developers
|contents=Visit [[:Category:Core development projects]] to see a list of currently ongoing projects!
See [[:Category:Developer Plans]] to see a list of developer plans for the upcoming release.
See [[request for comments]] for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress (admittedly a little outdated meanwhile).

'''Help needed:'''

Creating an integrated [[Canvas]] based GUI launcher/package manager {{Issue|1295}}:

{{cquote|For aircraft, the system supports aircraft dirs, there is the package manager code which works but is currently unused, which can download and extract zipped aircraft. This needs a GUI but thanks to the new reset architecture we can finally build this GUI inside FG - i.e an ‘aircraft chooser’ UI - however I am find building such a UI rather outside my comfort zone. If anyone would like to help in this area, let me know.<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32239376/
|title=size of flightgear-data
|author=James Turner |date= 2014-04-17 18:23:24}}</ref>|James Turner}}

The [[YASim]] FDM is looking for a new maintainer:

{{cquote|There are some pending merge requests[http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/533DBD01.9040802%40sol2500.net/#msg32183541] to add some YASim features, but we have an issue that since none of the current C++ developers own, or are experts in YASim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.

Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)

So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too,
if people are new to C++), and providing we have some assurance that a representative sample of YASim aircraft are unchanged or improved by the patch.
Suggestions for that means in practice, are most welcome!

Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}

{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my latencies here are measured in weeks.Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}

<references/>

}}

{{Main page/Leftbox|title=Coding Help Needed! (Updated 11/2013)
|contents=
* {{Pending}} [[World Scenery 3.0 roadmap]]
* {{Pending}} [[Reset & re-init]] and [[Fixing Presets]]
* {{Pending}} [[USB HID Support]] - mapping USB/HID devices onto the property tree
* {{Pending}} [[Project Rembrandt#TODO List|Project Rembrandt (Todo List)]] (Shadows/Deferred Rendering: OpenGL/OSG, C++)
* {{Pending}} [[Canvas Development]] - discusses possible future Canvas additions
* {{Pending}} [[Canvas Properties#Planned Features|Canvas Project (Planned Features)]] (fully scriptable 2D rendering API)
* {{Pending}} [[Canvas Widgets#Missing_.2F_Todo|Canvas Widgets (Missing Features)]] (Canvas GUI layer for scriptable widgets)
* {{Pending}} [[Howto:Use Property Tree Objects|Depreciate tied properties and use PropertyObjects instead]]
* {{Pending}} [[A_local_weather_system#Feature_requests_on_the_C.2B.2B_side|Local weather system Improvements]] (Requested C++ Changes)
* {{Pending}} [[Subsystem-level Memory Tracking for FlightGear]]
* {{Pending}} [[How the Nasal GC works|Fixing the Garbage Collector]] (the GC in [[Nasal]] needs to be improved)
* {{Pending}} [[CompositeViewer Support|Switching to osgViewer::CompositeViewer]] (multiple scenery cameras and moving maps)
* {{Pending}} [[Performance Database via FDM]] - implementing VNAV support for FlightGear aircraft
* {{Pending}} [[TerraGear scenery build server]]


}}

{{Main page/Leftbox|title=Wanted: interview candidates
|contents=Every month we try to include an interview with a contributor in the [[FlightGear Newsletter]]. Anyone contributing to FlightGear, in whatever way, is welcome to answer a few questions and write his/her own interview.

More info at [[FlightGear Newsletter: Interview]].
}}
}}

[[Category:Portals]]

[[ca:Portal:Desenvolupador]]
[[es:Portal:Desarrollo]]
[[fr:Portal:Développeur]]
[[sr:Portal:Razvoj]]
[[zh:Portal:Developer]]

Zh/Help:Tutorial

2018-01-25T08:41:32Z

Yfanhan: Created page with "寻求FlightGear飞行模拟器的支持，看用户门户或浏览故障类别。这里有一些帮助页面，在编辑wiki时可能有用。他们中的大多数都是关..."

寻求FlightGear飞行模拟器的支持，看用户门户或浏览故障类别。

这里有一些帮助页面，在编辑wiki时可能有用。他们中的大多数都是关于MediaWiki软件本身的使用的技术。为了更流畅的介绍，请先看前三个。

==阅读==
*[[Help:Main navigation elements]]

==编辑==

==高级编辑==

==技术问题与请求==
有请求或与维基/服务器技术问题，在Gmail接触hellosimon。

Zh/Route manager

2018-01-25T07:32:20Z

Yfanhan: Created page with "{{BeingTranslated}} {{forum|46|Autopilot & Route Manager}} {{Autoflight Navigation}} 一个真实的'''路线管理器''' ==介绍== ==概念== ==制作路线== ===标..."

{{BeingTranslated}}
{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

一个真实的'''路线管理器'''

==介绍==

==概念==

==制作路线==

===标准仪表离场和标准仪表进场===

===如何飞进场===

==激活路线==

==飞一个路线==

==对准跑道==

==特性==

==有用的软件==

==相关内容==

Route manager

2018-01-25T07:31:49Z

Yfanhan:

{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

A real '''route-manager''' page!

[[File:Routemanager.jpg|thumb|270px|The route manager dialog.]]

== Introduction ==
(in the following sections, familiarity with basic [[IFR]] concepts, [[Autopilot]] usage and [[radio navigation]] is assumed)

The route-manager models part of the functionality found in real-world [[GPS]] and FMS devices, but is usable in any aircraft. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better [[ATC]] and multi-player interactions, since [[ATC]] logic or controllers will be able to observe the filed plan associated with a pilot.

It's important to realize that the route-manager (and [[GPS]]) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.

== Concepts ==
The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints. All information is currently optional, which is highly unrealistic, but convenient.

Route manager waypoints are entered as a [[navaid]] ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. Each waypoint may also have an [[altitude]] associated with it, for vertical navigation modes (VNAV). In the future, other data, especially speed restrictions, may also be associated with waypoints.

The route-manager maintains a ''current waypoint'', which is shown in route-manager dialog, the GPS dialog (in LEG mode), on the default HUD, and potentially in cockpit displays in the aircraft. Normally, the route-manager moves automatically to the next waypoint after passing the current point (this is known as 'sequencing'), but if necessary the active waypoint can be manually adjusted.

An important piece of terminology is a ''leg'', which is a section of route between two waypoints. Many real-world devices deal in legs primarily, since each leg corresponds to a desired track, a distance and possibly an altitude to climb / descend. In the FlightGear route manager, the ''active leg'' is from the previous waypoint to the current waypoint - i.e the current waypoint is where you're heading to at the moment.

== Defining a Route ==
The simplest way to define a route is to add waypoints one at a time by identifier. Since navaid identifiers are not unique, the route-manager uses your departure airport or the previously defined waypoint to locate the identifier search. In practice, navaids with conflicting names are located far enough apart that this works automatically in practice.

From Flightgear 2016.2.0 onwards, it is also possible to add a list of waypoints using the route manager dialog. These should be separated by spaces, e.g. "TLA DCS HON WCO BNN" and the result is the same as typing individually and pressing the add button for each.

Until departure and arrival procedures are supported, you can often define them yourself, by creating offset waypoints, as shown in the examples below.

Routes can be loaded and saved to and from a simple XML format, so you may prefer to create the routes in a text editor, and load them instead of entering them by hand. You can also use a 3rd party flight-planning tool to create the route, export the route in GPX format and load the file with the route manager (requires FlightGear >= 2.99 and the file must have the suffix ".gpx"). Contact the developer list if you are interested on working on support for further file formats.

In the future, auto-routing using airways or VOR-VOR routing will also be added.

Example waypoint definitions:

;KJFK
: airport identifier
;UW
: navaid identifier ([[NDB]], [[VOR]] or a fix/interaction)
;TLA/210/35
: offset from a [[navaid]] - in this example, the 210-degree magnetic radial from TLA VOR, 35 nautical miles out
;WOBAD@18000
: WOBAD fix, at eighteen thousand feet altitude
;SPL/050/12.3@2000
: 12.3 nautical miles from SPL VOR on the 050 magnetic radial, at two thousand feet
;-20,55
: virtual point at W020N55, eg. when flying North Atlantic Tracks

See also [[#Useful Software]]

=== SIDs and STARs ===
As of FlightGear 2.4.0, the route manager has basic [[SID]]/[[STAR]] support. The route files are not free; access for a single {{wikipedia|AIRAC}} cycle and subscriptions can be bought at [http://www.navigraph.com/ Navigraph].

# Download the Level-D formatted files from the [http://www.navigraph.com/FmsDataPricing.aspx Navigraph manual install page]; log in and pay for the access when prompted. '''Save the .exe file somewhere safe (in case you need to reinstall the route files in the future): Navigraph won't provide you with another copy when the next data update comes out.'''
# Run the executable file. When prompted, choose to extract the data files in a directory on your Desktop (or in another easily accessible place).
# Open that directory, you will find many XML files named <tt>ICAO.procedures.xml</tt> (where <tt>ICAO</tt> is the ICAO code of the airport the XML file refers to): move each of them to [[$FG_SCENERY]]/Airports/<tt>I</tt>/<tt>C</tt>/<tt>A</tt>/<tt>ICAO</tt>.procedures.xml (replace <tt>I</tt>, <tt>C</tt>, <tt>A</tt> and <tt>ICAO</tt> with the corresponding letters of the ICAO code). (Example: put <tt>EDDF.procedures.xml</tt> in [[$FG_SCENERY]]/Airports/E/D/D/EDDF.procedures.xml</tt>).

The third point can be automated to install many procedure files at once:

* If you have Ruby installed on your computer, you can use [http://files.goneabitbursar.com/fg/install-navdat.rb this renaming script].
* Another possibility, using [https://www.python.org/ Python] 3, is this [http://people.via.ecp.fr/~flo/python_dumping_ground/short_scripts/extract-navdata.py extract-navdata.py script], which can install the files from a directory or directly from a tarball. Run <tt>extract-navdata.py --help</tt> or <tt>python3 extract-navdata.py --help</tt> for instructions. You may need to use <tt>py -3</tt> instead of <tt>python3</tt> on Windows, cf. [https://docs.python.org/3/using/windows.html Using Python on Windows].
* You could also use a small bash-script to do the work for you. Bash is a shell, native on Linux, also exists on Macs. Copy the following code into a new file, name it "convert.sh". Put it into the lowest directory, where all the xml-files are stored. (.../Level-D Simulations/navdata/)
:<syntaxhighlight lang="bash" enclose="div">#!/bin/bash

for file in *.xml
do
FILENAME=$( echo $file | sed s/.xml// )
DIR=$( echo "$FILENAME" | sed s/[A-Z0-9]\$// )
ONE=$( echo "$DIR" | sed s/[A-Z0-9]\$// | sed s/[A-Z0-9]\$// )
TWO=$( echo "$DIR" | sed s/[A-Z0-9]// | sed s/[A-Z0-9]\$// )
THREE=$( echo "$DIR" | sed s/[A-Z0-9]// | sed s/[A-Z0-9]// )
#echo "$file => $DIR => $ONE / $TWO / $THREE / $file"
mkdir -pv "../Airports/$ONE/$TWO/$THREE"
cp -v $file "../Airports/$ONE/$TWO/$THREE/$FILENAME.procedures.xml"
done
</syntaxhighlight>
:# Now it's time to fire up a terminal and navigate to the files: <code>cd /path/to/Level-D Simulations/navdata</code>
:# To make the script executable type: <code>chmod +x convert.sh</code>
:# Now you're ready to run the script! <code>./convert.sh</code>
:When the script is done, you will find a new folder on your hard-disk: "/path/to/LevelD/Airports" which contains the files in our "I/C/A/ICAO.procedures.xml fashion". You can now copy this Airports-folder into a new scenery-folder and add it to your scenery-list.

Next time you start FlightGear, you can load the routes through the route manager interface.

=== Flying Approaches ===
The route manager can also be used to fly from airport to airport without using navaids or waypoints. The following is a step-by-step tutorial on how to plan a flight from KSFO-KLAX without using navaids or waypoints.

In the route manager, you will see two rows at the top: departure and arrival. They are almost the same, except departure has SID and the arrival airport has STAR (see below, SID/STAR).

1. In the departure airport row, fill in the ICAO of the airport you are departing from (KSFO) as well as the runway you are taking off from. (10R) If you are not familiar with the airport, choose your departure runway carefully, as your taxi time will depend on the distance of this runway. The SID dropdown can remain as it is.

2. In the arrival airport row, fill in the ICAO of the airport you are arriving at (KLAX) as well as the runway you will be landing on. (06L) Again, if you are not familiar with this airport, choose your arrival runway carefully, as this may significantly extend flight time. Next, select "Default" in the approach dropdown box. STAR can remain as it is.

3. There should now be a list of waypoints below the information fields. The first waypoint (outside of the airport) is a ways from the departure airport (in this example, 283.9 NM). However, the waypoints following that continue the approach, so they are only a few nautical miles away from the previous. The list should be populated with at least 4 waypoints, excluding the airports. When this is true, proceed to the next step.

4. There is a row of buttons at the bottom of the route manager. Press the button that says "Activate". This will enable the route that you have created (in this case, KSFO-KLAX). However, we don't want to fly to the airport we're already at. We want to fly to the first waypoint, which should be APP-4. To do this, click on APP-4 and click the "Jump To" button at the bottom. APP-4 should now be highlighted in orange. This means that autopilot is ready to fly to that waypoint.

5. Once you get above 500ft, after takeoff, enable autopilot. Click LNAV for lateral navigation to that first waypoint. Your plane will make a slight turn (in this case) towards Los Angeles. Altitude works separately, so you will have to set your own altitude and vertical speed. (If pressing the LNAV button only produces this error: "Captain, we forgot to program or activate the route manager!", you forgot to click the activate button! Repeat step 4 and 5, then proceed to step 6. You should pause the simulation while doing this.)

6. Your planes will make all the turns for you to get on approach. Remember that you, the pilot, are responsible for altitude, which deserves a whole different tutorial in itself.

== Activating a Route ==
Activating a route performs certain checks, and creates start and end waypoints based on the selected departure and arrival info. For the moment, that consists of adding the departure runway as waypoint zero, but in the future (when departure procedures are supported) this will create the appropriate procedure waypoints.

This will also be the hook point for calculating cruise information, such as top-of-climb and top-of-descent points in the future.

Other devices (especially a GPS/FMS) may trigger other changes based on activating a route, such as sequencing the first leg of the route, resetting internal counters / timers, and so on.

== Flying a Route ==

When a route is activated, the GPS system enters 'leg' mode, and will automatically sequence waypoints as they are overflown. Note that all aircraft can use the default route-manager and GPS functions, even aircraft that would never (historically) has such systems. This is a convenience to casual users, testing, and so on.

In particular, the GPS drives some properties of the generic autopilot, so 'true heading hold' mode can be used to fly the route manager route (or any other GPS course).

The default [[HUD]] (activated by pressing 'h') shows information about the active waypoint and leg, in the top-left corner. Notably, it includes the identifier, time and distance to the current waypoint, the magnetic bearing to the waypoint, and the current ground track, and finally the deviation (in nautical miles) from the leg course.

In aircraft with realistic navigation systems, or customised autopilots, the default behaviours above may not work; hopefully the aircraft author has provided alternative methods, such as panel instruments, to control the interaction with that aircraft's autopilot and panel.

=== Lining up with Runways ===
The route-manager only provides guidance to a particular location - to arrive on a particular heading, such as lined up with a runway or [[ILS]] localizer, it is necessary to use multiple waypoints. Virtually all ILS approaches define multiple [[fixes]] that can be used for this purpose, usually including altitude restrictions. For example, for the [http://flightaware.com/resources/airport/KPHX/IAP/ILS+OR+LOC+RWY+08 KPHX 08 approach], waypoints ALLIS, SARTE, HIKID, ILIKE, JAMIL and WAZUP are defined, extending 20nm from the threshold. Typically you enter the initial approach fix (IAF), ALLIS in this example, and as many of the intermediate waypoints as necessary, depending on required descent profile. It is helpful to include the glidepath capture waypoint (WAZUP), to provide an easy altitude reference and cross-check that your ILS receiver is working.

== Properties ==
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available.

== Useful Software ==
To easily create entries for route manager the application;
*[http://rubyforge.org/projects/fgmap Flightgear Mapping] is useful. With just a few clicks you can add navaids displayed on the map and as well a route you have defined there via waypoints. Navaids can be inserted into the list at any point, not just at the end.
*[http://sourceforge.net/projects/fgflightplanner/ Kelpie Flight Planner] appears to be a very thorough route planning tool that works on Windows, Linux and other operating systems.

== Related content ==
* For additional route managr system details, see [[Route manager internals]].
* [[Howto: Create a flightplan]]
* [[Radio beacons]]
* [[Radio navigation]]

[[Category:Autoflight| ]]
[[Category:FlightGear feature]]
[[Category:Menubar]]

[[es:Gestor de rutas]]
[[zh:Route_manager]]

Route manager

2018-01-25T07:30:03Z

Yfanhan:

Fr/Aide:Traduire

2018-01-25T05:19:30Z

Yfanhan:

Depuis septembre 2009, le [[Main Page|Wiki FlightGear]] permet l'utilisation de plusieurs langues. Dorénavant, chaque article peut être traduit dans n'importe quelle langue, afin d'en faciliter la compréhension pour les utilisateurs non-anglophones.

=== Nous avons besoin de vous ! ===
Le Wiki contenant déjà {{NUMBEROFARTICLES}} articles (certains plus petits que d'autres), cela représente beaucoup de travail de traduire toutes les pages. Quelques utilisateurs ont commencés à traduire, mais nous avons vraiment besoin d'aide et pour être plus précis : de la vôtre !

Si nous traduisions ne serait-ce qu'un ou deux articles chacun, cela ne prendrait pas "si" longtemps pour avoir au moins les articles les plus importants comme [[Flying the helicopter]], [[FlightGear]], [[Installing Scenery]] et [[New to FlightGear]].

=== Exemples ===
Pour les exemples d'articles déjà traduits allez voir [[Main Page]].

=== Comment commencer à traduire ? ===
Tout d'abord, vous devez trouver un article que vous aimeriez traduire. Ensuite, dans la barre d'adresse de votre navigateur web (Safari, Firefox, Opéra...) ajoutez l'abréviation du langage désiré (allez voir [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php ici] pour la liste) suivie par une barre de fraction (/) avant le titre de l'article anglais et allez sur cette page. Par exemple si je voulais traduire l'article terrasync en français, je visiterais [[fr/TerraSync]]. Comme vous pouvez le voir cette page n'existe pas encore, donc nous sommes sûrs que personne n'a traduit cet article pour le moment.

Maintenant, traduisons cet article. Vous pouvez laisser les liens wiki comme ils sont (ils redirigent vers l'article anglais), à moins que l'article soit traduit dans la langue de votre article. Dans ce cas, vous faites un lien wiki comme ceci : <tt><nowiki>[[:nl:Hoofdpagina]]</nowiki></tt>. [[:nl:Hoofdpagina]] sera montré dans l'article. Il est cependant recommandé d'utiliser<tt><nowiki>[[:nl:Hoofdpagina|Hoofdpagina]]</nowiki></tt>, car il permet de ne pas faire référence au préfixe de la langue ([[:nl:Hoofdpagina|Hoofdpagina]]).

Tout en bas de l'article, vous devez placer les liens de langue, de manière à ce qu'il y ait une sympathique liste de sélection dans le menu. Toutes les traductions de l'article devraient être listées. Par exemple, dans l'article anglais de [[TerraSync]], nous ajoutons: <tt><nowiki>[[nl:TerraSync]]</nowiki></tt>. Sur l'article néerlandais, nous ajoutons <tt><nowiki>[[en:TerraSync]]</nowiki></tt>. La langue dans laquelle l'article a été rédigé peut être laissée de côté. Veuillez laisser les langues en ordre alphabétique, de manière à ce qu'il soit plus facile d'ajouter ou de supprimer des langues.

==== Quels articles ne devraient pas être traduit ====
'''Ne pas''' commencer à traduire des articles qui doivent '''[[:Category:afd|être détruits]]''' ou '''[[:Category:Articles to be merged|améliorés]]'''. Ces articles doivent d'abord être améliorés dans leur langue d'origine.

'''Merci beaucoup pour vos traductions ou pour toute autre contribution que vous auriez réalisé sur le wiki ! Votre dur labeur est très apprécié par tous les utilisateurs de Flightgear !'''

[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[nl:Help:Vertalen]]
[[fr:Help:traduire]]
[[en:Help:translate]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[zh:Help:Translate]]

[[Category:Help|Translate]]

Es/Help:Traducir

2018-01-25T05:18:52Z

Yfanhan:

Desde el pasado mes de Septiembre de 2009, La [[Main Page|FlightGear Wiki]] soporta multiples lenguas. Desde ahora cada uno de los articulos puede ser traducido a otra lengua, incrementando la simpatia para usuarios no nativos del habla inglesa.

=== Te necesitamos! ===
Asi como tenemos {{NUMBEROFARTICLES}} artículos (algunos más pequeños que otros) traducir todas estas páginas resulta un infierno lleno de trabajo. Un grupo reducido de usuarios ha comenzado a traducir, pero definítivamente necesitaremos ayuda, para ser preciso: tu ayuda¡ (al menos) de aquellos que hablen más de una lengua, No me sorprendo de saber que muchos de los usuarios de FG son no nativos de la lengua inglesa.

Si todos traducimos una o dos páginas desde ahora en adelante, no nos llevará mucho tiempo traducir al menos los articulos más importantes (como son [[:es:Volando el helicoptero|Volando el helicoptero]], [[:es:FlightGear|FlightGear]], [[Installing Scenery|Instalar escenarios]] y [[:es:Nuevo en FlightGear|Nuevo en FlightGear]]).

=== Ejemplos ===
Para ejemplos de páginas de artículos ya traducidos (sólo en un par de lenguas), echa un vistazo a la [[Main Page|Página Principal]].

=== ¿Como comienzo a traducir ? ===
Primero necesitas encontrar un artículo que desees traducir. Luego en la barra de Direcciones URL de tu navegador, añade (es/) la abreviatura de la lengua deseada delante del nombre de la página (mira
[http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php aquí] para ver la lista) sobre el titulo del artículo en Inglés y ve a esta página. Por tanto si quiero traducir el artículo TerraSync al español, visitaría la página [[es/TerraSync]]. Como puedes ver esta página no existe todavía, por tanto tendremos la seguridad de que nadie la ha traducido hasta la fecha.

Ahora traducimos el artículo actual. Puedes dejar los enlaces wiki como están (apuntando al articulo en Inglés), a no ser que el artículo al que apunta este traducido al lenguaje de tu artículo. En este caso tienes que hacerle un enlace wiki como este: <tt><nowiki>[[:es:Portada]]</nowiki></tt>. [[:es:Portada]] será mostrado en el articulo. Sin embargo se prefiere usar este <tt><nowiki>[[:es:Portada|Portada]]</nowiki></tt>, asi este eliminará el prefijo de lenguaje ([[:es:Portada|Portada]]).

Al final del todo en la base del artículo tienes que poner los enlaces de Lenguas, así habrá una lista de selección en el menú. Todas las traducciones del articulos se listarán. Por tanto en el artículo Inglés de [[TerraSync]], añadiremos: <tt><nowiki>[[es:TerraSync]]</nowiki></tt>. En el artículo en español, añadimos <tt><nowiki>[[en:TerraSync]]</nowiki></tt>. Asi la lengua en la que está escrito el artículo puede ser omitida. Por favor mantén el orden alfabético de las lenguas, asi será más fácil añadir/quitar lenguas.

Una vez traducido el artículo, necesitas añadir un enlace de lengua en cada una de las traducciones del artículo. Visita el articulo en Inglés para ver en qué lenguas está traducido este.

==== Que artículos no deben ser traducidos ====
'''NO''' empezar a traducir articulos que estén '''[[:Category:afd|considerados para borrarse]]''' o '''[[:Category:Articles to be merged|que deben ser fundidos]]'''. Primero debe ser mejorada las variante en Inglés de estos articulos.

'''Muchas gracias por tus traducciones u otras contribuciones que haces al wiki! Tu duro trabajo es realmente apreciado por todos los usuarios de FG!'''

[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[en:Help:Translate]]
[[pt:Help: Traduzir]]
[[nl:Help:Vertalen]]
[[ru:Справка:Перевод]]
[[fa:راهنمایی:ترجمه]]
[[zh:Help:Translate]]
[[Category:Help|Translate]]

De/Help:Übersetzen

2018-01-25T05:16:45Z

Yfanhan:

Seit September 2009 unterstützt das [[:de:Hauptseite|FlightGear Wiki]] mehrere Sprachen. Seit diesem Zeitpunkt kann ''jeder'' Artikel in ''jede'' Sprache übersetzt werden, was die Benutzerfreundlichkeit für Nicht-Englisch sprechende Benutzer erhöht.

== Wir brauchen DICH! ==
Da wir momentan {{NUMBEROFARTICLES}} Artikel haben (einige kleiner als andere), ist es ein verdammt umfangreiches Stück Arbeit alle Artikel zu übersetzen. Einige Benutzer haben schon damit angefangen, doch wir brauchen noch mehr Hilfe - um genau zu sein: '''Deine''' Hilfe! So gut wie jeder hier im Wiki spricht mehr als nur eine Sprache, also würde es nicht überraschen, wenn die meisten [[:de:FlightGear|FlightGear]] Benutzer Englisch nicht als Muttersprache sprechen.

Wenn wir nur ab und zu mal einen Artikel übersetzen würden, würde es '''sehr''' lange dauern, zumindest die wichtigsten Artikeln (wie [[Flying the helicopter]], [[FlightGear]], [[Installing Scenery]] und/oder [[New to FlightGear]]) zu übersetzen.

=== Beispiele ===
Für Beispiele von Artikeln, die schon (in einige Sprachen) übersetzt wurden, schau auf der [[:de:Hauptseite|Hauptseite]] nach.

== Wie übersetze ich einen Artikel? ==
Bei Artikeln die schon in eine oder mehrere Sprachen übersetzt wurden, findest Du in der Menüleiste auf der linken Seite am Ende einen Hinweis darauf (''in anderen Sprachen''). Dort sind die Sprachen aufgelistet, in denen der Artikel verfügbar ist. Aber '''Achtung''', nicht immer sind diese Hinweise korrekt. Manchmal wird vergessen einen Artikel als übersetzt zu markieren.

Zunächst brauchst Du einen Artikel, den Du übersetzen möchtest (und der natürlich noch nicht übersetzt wurde). Wenn Du den Artikel geöffnet hast, fügst Du in der Adresszeile Deines Browsers die Abkürzung der gewünschten Sprache ([http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php hier] eine Übersicht der verfügbaren Abkürzungen), gefolgt von einem Slash (/) vor dem Titel des englischsprachigen Artikels und öffnest diese Seite.

Beispiel:

''Originalartikel'': <code><nowiki>http://wiki.flightgear.org/index.php/TerraSync</nowiki></code>

''Einzufügen ist'': <code><nowiki>http://wiki.flightgear.org/index.php/</nowiki>'''<nowiki>de/</nowiki>'''<nowiki>TerraSync</nowiki></code>

Wenn diese Seite nicht existiert (das MediaWiki-System wird Dir dies mitteilen), dann kannst Du Dir sicher sein, dass die Seite noch nicht auf Deutsch übersetzt wurde.

== Übersetzen ==
=== Schritt-für-Schritt Anleitung ===
# Gehe auf die englische Version der Seite, die Du übersetzen willst.
# Lies Dir die englische Seite durch und suche nach Fehlern oder möglichen Verbesserungen. Verbessere und aktualisiere dann die englische Seite - wenn Du dir unsicher bist, schreibe deine Ideen auf die Diskussionsseite. (Es gibt zwar keinen Grund dafür, wenn die Übersetzungen besser als die Originalseiten sind, aber es orientieren sich alle restlichen Sprachen an der ''aktuellen'' englischen Seite).
# Prüfe in der Liste '''In other languages''' links, dass der Artikel nicht schon übersetzt wurde (siehe [[#Wie übersetze ich einen Artikel?|oben]]).
# Wenn die Sprache nicht aufgeführt wird, kannst Du mit der Übersetzung beginnen. (Wenn Deine Sprache aufgeführt '''ist''', überprüfe und aktualisiere sie mithilfe der englischen Seite)
# Suche dein Sprachenkürzel ''Language Extension'' '''LE''' aus [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php dieser] Liste oder der [[Main_Page|Hauptseite]]. Für Deutsch lautet es '''"de"'''.
# Rufe die Bearbeitungsfunktion (Edit) der englischen Seite auf.
# Am Seitenende werden die Links zu den Sprachen aufgeführt. Füge dort <tt><nowiki>[[LE:Seitentitel]]</nowiki></tt> hinzu. Setze für ''LE'' dein Sprachenkürzel (de) ein und für ''Seitentitel'' den entgültigen '''übersetzten''' Seitennamen (kann auch Leerzeichen enthalten) ein. Sortiere die Sprachen alphabetisch.
# Wenn Du auf {{Key press| Show preview }} klickst, sollte deine Sprache links erscheinen. Speicher dann die Seite {{Key press| Save page }}.
# Klicke auf den neuen Sprachenlink und erstelle dort eine neue Seite (unter ''create'' oben links).
# Wenn du dir die Seite für eine spätere Übersetzung reserviern willst, füge <tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt> am oberen Ende der Seite ein.
# Kopiere ans untere Ende Deiner Seite <tt><nowiki>[[en:Page title]]</nowiki></tt> und ersetze <tt>Page title</tt> mit dem Originaltitel der englischen Seite (wenn vorhanden mit Leerzeichen; achte auf Groß/Kleinschreibung).
# Wenn der Artikel schon in andere Sprachen übersetzt wurde, kopiere die Liste von der Bearbeitungsseite des englischen Artikels in deinen. Die Sprache in der deine Übersetzung verfasst wird, kann ausgelassen werden. Achte darauf, die Auflistung alphabetisch zu sortieren (en aber immer oben). Dies vereinfacht das Hinzufügen oder Entfernen von Übersetzungen.
# Prüfe mithilfe von {{Key press| Show preview }}, ob die Links funktionieren und speicher die Seite.{{Key press| Save page }}
# Wenn die Seite in [[Translation requests]] gelistet ist, kannst Du die Übersetzung dort angeben
# Nun kannst du mit der Übersetzung des Quelltextes vom englischen Artikel in deine neue Seite beginnen.
# Wenn du fertig bist und es noch andere Übersetzungen gibt, setze <tt><nowiki>[[de:deutscher Seitentitel]]</nowiki></tt> an das Seitenende der anderen Übersetzungen (alphabetisch).
# Schaue auf der englischen Seite links auf Tools>What links here. Suche dort nach Seiten mit deinem Sprachenkürzel. Suche in denen dann den entsprehenden Link zur englischen Seite und ändere ihn auf den Link zur deutschen Version (siehe [[#Wikilinks|unten]])
# Beobachte weiter alle späteren Änderungen der englischen Seite und halte deine Übersetzung so aktuell.

=== Formatierung und spezielle Elemente ===
Bei Deiner Übersetzung wirst Du hin und wieder auf merkwürdige Zeichenketten stoßen. Hier sind einige davon erklärt. Eine vollständige Liste findest du [[Help:Your first article|hier(en)]].

* <tt><nowiki>== text ==</nowiki></tt> ist eine '''Überschrift'''.
* <tt><nowiki>''text''</nowiki></tt> ist eine '''Formatierung'''. Zwei mal bedeutet ''kursiv'', drei mal (<tt><nowiki>'''text'''</nowiki></tt>) '''fett'''.
* <tt><nowiki>* text / # text</nowiki></tt> sind '''Aufzählungen''' mit <nowiki>*</nowiki> Punkt (wie hier) oder <nowiki>#</nowiki> mit Zahlen (wie oben)
* <tt><nowiki>[[Seitenname|text]]</nowiki></tt> ist ein '''Wikilink''' ([[#Wikilinks|siehe unten]]). Vor dem '''{{!}}''' steht der Seitenname, dahinter der Linktext, den du übersetzen kannst.
* <tt><nowiki>[www.google.de Google]</nowiki></tt> ist ein '''Weblink'''. Dieser geht zu [http://www.google.de Google]. Vor dem ersten Leerzeichen steht der Link, dahinter der angezeigte Text, den du übersetzen kannst.
* <tt><nowiki>{{Name|Parameter}}</nowiki></tt> ist ein '''Template'''. Es fügt Teile wie Tabellen, Textfelder, andere Links... hinzu. Eine Übersicht einiger Templates findest du [[:de:Help:Messagebox Vorlagengalerie|hier]]. Generell gilt, was vor dem ersten '''{{!}}''' steht, ist der Templatename, der nicht mit übersetzt werden darf. Hinter dem ersten '''{{!}}''' sind Parameter oder angezeigte Texte, die Du evtl. übersetzen darfst. Zu den meißten Templates gibt es eine Beschreibung, die Du durch die Suchfunktion oder unter <tt><nowiki>wiki.flightgear.org/template:name</nowiki></tt> erreichst. Dort kannst Du sie auch manchmal übersetzen: [[Help:Templates#Translating templates|Anleitung zur Übersetzung von Templates]]

==== Wikilinks ====
Lass die Wikilinks wie sie sind (also auf den englischen Artikel verlinkt) solange der verlinkte Artikel noch nicht in Deine Sprache übersetzt wurde. Ist der Artikel schon übersetzt, dann ändere den Link folgendermaßen ab:

''Originallink:'' <code><nowiki>[[MainPage]]</nowiki></code>

''Nach Übersetzung:'' <code><nowiki>[[:de:Hauptseite]]</nowiki></code>, der Sprachen-Präfix wird mit angezeigt: [[:de:Hauptseite]].

''Besser:'' <code><nowiki>[[:de:Hauptseite|Hauptseite]]</nowiki></code>, der Sprachen-Präfix wird nicht mehr angezeigt: [[:de:Hauptseite|Hauptseite]].

Lass bei den Kategorien am unteren Ende der Seite z.B. <code><nowiki>[[Category:Help|Übersetzen]]</nowiki></code> den ersten Teil so stehen. Der Artikel wird durch sie zugeordnet. Den zweiten Teil darfst Du übersetzen.

== Welche Artikel '''nicht''' übersetzt werden sollten ==
Übersetze '''keine''' Artikel, die für eine [[:Category:afd|Löschung]] oder ein [[:Category:Articles to be merged|Zusammenfügen]] vorgeschlagen sind. Zunächst sollten die englischsprachigen Artikel verbessert/erweitert werden.

'''Danke vielmals für Deine Übersetzung und auch für alle weiteren Beiträge im Wiki. Alle [[:de:Flightgear|Flightgear]] Benutzer werden Deine Arbeit zu schätzen wissen!'''

[[ca:Help:Traduir]]
[[en:Help:Translate]]
[[es:Help:Traducir]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[it:Help:Tradurre]]
[[nl:Help:Vertalen]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[zh:Help:Translate]]

[[Category:Help|Übersetzen]]

Ca/Help:Traduir

2018-01-25T05:16:09Z

Yfanhan:

{{hatnote|Per a la traducció de plantilles, vegeu [[Help:Plantilles#Traducció de plantilles]].}}

Des de setembre de 2009, el [[Ca/Portada|wiki de FlightGear]] és compatible amb diversos idiomes. A partir d'ara, tots els articles es poden traduir a qualsevol idioma, augmentant la facilitat d'ús dels usuaris que no parlen anglès.

===Us necessitem!===
Tenim actualment {{NUMBEROFARTICLES}} articles (alguns són més petits que d'altres), és un gran treball haver de traduir totes les pàgines. Un parell d'usuaris ja van començar a traduir, però definitivament podríem ajudar-nos i, per ser més exactes, necessitem de la vostra ajuda. Gairebé tothom aquí parla més d'un idioma, així que no sorprèn que la majoria dels usuaris de FG siguin parlants d'idiomes no natius d'anglès.

Si tots ens posem a traduir una o dues pàgines de tant en tant, no hauria de portar molt de temps tenir almenys els articles més importants traduïts (com [[Ca/Vol en helicòpter|Vol en helicòpter]], [[Ca/FlightGear|FlightGear]], [[Ca/Instal·lació de l'escenari|Instal·lació de l'escenari]] i [[Ca/Nou a FlightGear|Nou a FlightGear]]).

Vegeu la pàgina de [[Translation requests|peticions de traducció]] per a les traduccions més urgents.

===Exemples===
Per a exemples d'articles ja traduïts (en un parell d'idiomes), feu una ullada a la [[Ca/Portada|Portada]].

=== Com puc començar a traduir? ===
Primer heu de trobar un article que vulgueu traduir. A continuació, a la barra URL del navegador, afegiu l'abreviatura del vostre idioma (vegeu
[https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php aquí] per a una llista) seguit d'una barra inclinada (/) davant del títol de l'article anglès i entreu en aquesta pàgina. Per tant, per exemple si tenim que traduir l'article TerraSync al neerlandès, podríem entrar a la pàgina amb l'enllaç [[nl/TerraSync]]. Com podeu veure, aquesta pàgina encara no existeix, així que estem segurs que ningú l'ha traduït al neerlandès fins ara.

Ara traduïm l'article real. Podeu deixar enllaços wiki tal com estan (assenyalant l'article en anglès), llevat que l'article es tradueixi a l'idioma del vostre article. En aquest cas, feu un enllaç wiki com aquest: <tt><nowiki>[[:nl:Hoofdpagina]]</nowiki></tt>. [[:nl:Hoofdpagina]] es mostrarà a l'article. No obstant això, es prefereix utilitzar <tt><nowiki>[[:nl:Hoofdpagina|Hoofdpagina]]</nowiki></tt>, ja que agafarà el prefix d'idioma ([[:nl:Hoofdpagina|Hoofdpagina]]).

A la part inferior de l'article cal que col·loqueu els enllaços d'idioma, així que hi haurà una bona llista de selecció al menú. Totes les traduccions de l'article s'han d'enumerar. Així que a l'article anglès de [[TerraSync]], afegim: <tt><nowiki>[[nl:TerraSync]]</nowiki></tt>. En l'article neerlandès, afegim <tt><nowiki>[[en:TerraSync]]</nowiki></tt>. Es pot excloure el llenguatge en què s'escriu l'article. Mantingueu les llengües per ordre alfabètic, de manera que serà més fàcil afegir o eliminar idiomes.

Un cop hagueu traduït un article, heu d'afegir un enllaç d'idioma a cada traducció de l'article. Visiteu l'article en anglès per veure en quina llengua s'ha traduït.

==== Guia pas a pas ====
# Cerqueu la versió en anglès de la pàgina que vulgueu traduir.
# Comproveu si accepteu el contingut de la pàgina anglesa, utilitzeu la pàgina de discussió o editeu la pàgina anglesa perquè estigui actualitzada (no hi ha cap motiu perquè una pàgina traduïda no sigui millor com la versió en anglès, però per a la sincronització s'a preferit que la versió en anglès estigui actualitzada primer).
# Mireu a sota, si la pàgina s'ha traduït a altres idiomes, s'enumerarà a continuació '''En altres idiomes'''.
# Si el vostre idioma no apareix, podeu reclamar-lo i començar a traduir. (Si el vostre idioma es troba a la llista, verifiqueu-lo i actualitzeu-lo)
# Descobriu el codi de llengua o Language Extension '''LE''' [https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php d'aquesta] llista.
# Editeu la versió anglesa a la pàgina.
# Afegiu al final de la pàgina <tt><nowiki>[[LE:títol de la pàgina]]</nowiki></tt> on LE és el codi de l'idioma i <tt>títol de la pàgina</tt> és el títol '''correcte''' en la '''vostra llengua'''.
# Deseu la pàgina anglesa i comproveu si troba el vostre idioma.
# Feu clic a l'enllaç d'idioma per editar la pàgina en el vostre idioma.
# Afegiu <tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt> a la part superior de la pàgina.
# Afegiu <tt><nowiki>[[en:títol de la pàgina]]</nowiki></tt> a la part inferior de la vostra pàgina, on <tt>títol de la pàgina</tt> és el títol de la pàgina original en anglès.
# Si la pàgina anglesa ja s'ha traduït a altres idiomes, copieu i enganxeu-los a la pàgina anglesa al final de la vostra pàgina.
# Deseu la vostra pàgina i comproveu si la llengua s'ha vinculat.
# Podeu reclamar la vostra traducció aquí: [[Translation requests]]
# Comenceu a traduir i afegiu el vostre treball a la nova pàgina.
# Col·loqueu l'enllaç a la vostra traducció (<tt><nowiki>[[LE:títol de la pàgina]]</nowiki></tt>) a la part inferior de les pàgines d'altres traduccions.
# Seguiu/Reviseu la pàgina anglesa i actualitzeu la vostra pàgina quan vegeu actualitzacions interessants.

=== Quins articles no s'han de traduir? ===
'''No''' comenceu a traduir articles que són '''[[:Category:afd|considerats per a la seva supressió]]''' o '''[[:Category:Articles to be merged|cal una fusió]]'''. En primer lloc, cal millorar les variants en anglès d'aquests articles.

'''Moltes gràcies per a les vostres traduccions o qualsevol altra contribució que feu al wiki. El vostre treball dur és realment apreciat per tots els usuaris de FG!'''

[[Category:Help|Translate]]

[[de:Help:Übersetzen]]
[[en:Help:Translate]]
[[es:Help:Traducir]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[it:Help:Tradurre]]
[[nl:Help:Vertalen]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[zh:Help:Translate]]
[[th:Help:Translate]]

It/Help:Tradurre

2018-01-25T05:15:34Z

Yfanhan:

Dal Settembre del 2009, la [[Flightgear Wiki]] supporta la possibilità di avere la traduzione di ogni articolo in qualsiasi lingua, permettendo di avere visite dello stesso articolo anche da parte di utenti che non conoscono l'inglese.

===Abbiamo bisogno di TE!===
Da momento che abbiamo {{NUMBEROFARTICLES}} articoli (alcuni più corti di altri), è necessario fare un gran lavoro per tradurli tutti. Un paio di utenti hanno già iniziato a tradurre, ma abbiamo decisamente bisogno di aiuto, e per essere precisi il tuo aiuto! Quasi tutti parlano più di una lingua, quindi non mi sorprendo che la maggior parte degli utenti di Flightgear non siano di madrelingua inglese.

Se noi tutti ci impegnassimo a tradurre solo una o due pagine ogni tanto, non sarebbe necessaria una grande quantità di tempo e avremmo almeno gli articoli più importanti tradotti.

Gli articoli che necessitano di una traduzione urgente si trovano nella pagina [[Translation requests]].

===Esempi===
Per un esempio di pagina che è stata tradotta in più lingue da un'occhiata alla [[Main Page|Pagina Principale]]

===Come posso inizare a tradurre?===
In primo luogo devi trovare l'articolo che vuoi tradurre. Successivamente, nella barra dell'URL del tuo browser, aggiungi l'abbreviazione della tua lingua desiderata (fai riferimento a [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php here] per una lista delle abbreviazioni) e aggiungi uno slash (/) prima del nome dell'articolo scritto in inglese ed entra nella pagina. Detto questo, se volessi tradurre l'articolo che fa riferimento a TerraSync in italiano, dovrei visitare la pagina [[it/TerraSync]]. come puoi vedere, questa pagina non esiste ancora e siamo sicuri che nessuno abbia tradotto questa pagina fin'ora.

Ora traduciamo l'articolo vero e proprio. Puoi lasciare link wiki come sono (indicando l'articolo inglese), a meno che l'articolo è tradotto nella lingua del vostro articolo. In questo caso si fa un collegamento wiki come questo: [[: NL: Hoofdpagina]]. nl: Hoofdpagina verrà mostrato in questo articolo. Si è preferito tuttavia usare [[: NL: Hoofdpagina | Hoofdpagina]], come che sbarazzarsi del prefisso lingua (Hoofdpagina).

In fondo lontano di questo articolo è necessario inserire i link di lingua, quindi ci sarà un elenco di selezione piacevole nel menu. Tutte le traduzioni di questo articolo dovrebbe essere incluso. Così sull'articolo inglese di TerraSync, aggiungiamo: [[nl: TerraSync]]. Sull'articolo olandese, aggiungiamo [[it: TerraSync]]. La lingua che l'articolo è scritto in può essere lasciato fuori. Si prega di tenere le lingue in ordine alfabetico, in modo che sarà più facile per aggiungere / rimuovere le lingue.

Dopo aver tradotto un articolo, è necessario aggiungere un link lingua su ogni traduzione dell'articolo. Visita l'articolo inglese per vedere in quali lingue è stato tradotto.

==== Guida passo per passo ====
# Trovare la versione inglese della pagina che si desidera tradurre.
# Verificare se siete d'accordo con il contenuto della pagina inglese, utilizzare la pagina di discussione o modificare la pagina inglese in modo che sia up-to date (vi è alcun motivo per cui una pagina tradotta non dovrebbe essere meglio come la versione inglese, ma per la sincronizzazione è preferibile che la versione inglese è up-to-date in primo luogo).
# Guardare a sinistra in basso, se la pagina è stata tradotta in altre lingue sarà elencare tali lingue al di sotto '' 'In altre lingue' ''.
# Se la tua lingua non è presente nell'elenco si può pretendere e iniziare a tradurre. (Se la vostra lingua * è * elencato, controllare e aggiornare)
# Scopri il Extension Language '' 'LE' '' della lingua da [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php questo] lista.
# Modificare la versione inglese della pagina.
# Aggiungere al fondo della pagina <tt><nowiki> [[LE: Titolo della pagina]] </nowiki></tt> dove LE è l'estensione di lingua e <tt> Titolo della pagina </tt> è il '' 'corretto' '' titolo '' 'la lingua'''.
# Salvare la pagina inglese e verificare se ora elenca la lingua.
# Fare clic sul collegamento linguaggio per modificare la pagina nella tua lingua.
# Aggiungere <tt><nowiki> {{BeingTranslated}} ~~~~ </nowiki> </tt> nella parte superiore della pagina.
# Invio <tt><nowiki> [[it: Pagina title]] </nowiki> </tt> nella parte inferiore della pagina, dove <tt> Titolo della pagina </tt> è il titolo della pagina originale inglese.
# Se la pagina inglese è già stato tradotto in altre lingue copiare e incollare le lingue dalla pagina inglese al fondo della pagina.
# Salvare la pagina e controllare se il linguaggio collega di lavoro.
# È possibile richiedere il traduzione qui: [[Translation requests]]
# Avviare tradurre e inserire il vostro lavoro nella nuova pagina.
# Posizionare il link per la vostra traduzione (<tt><nowiki> [[LE: Titolo della pagina]] </nowiki> </tt>) in fondo alle pagine di altre traduzioni.
# Seguire / Guarda la pagina inglese e aggiornare la pagina quando si vede aggiornamenti interessanti.

=== Quali articoli non dovrebbero essere tradotti? ===
 '' Non '' iniziare a tradurre articoli che sono '' [[:Category:Afd |considerati in attesa di eliminazione]] '' oppure '' [[:Category:Articles to be merged|articoli che necessitano di essere fusi]]. In quanto le varianti inglesi di tali articoli dovrebbero essere migliorate.

'' 'Grazie mille per le vostre traduzioni o altri contributi apportate alla wiki! Il vostro duro lavoro è molto apprezzato da tutti gli utenti di Flightgear! '' '

[[Category:Help|Translate]]

[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[nl:Help:Vertalen]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[zh:Help:Translate]]

Help:Translate

2018-01-25T05:14:37Z

Yfanhan:

{{hatnote|For translation of templates, see [[Help:Templates#Translating templates]].}}

Since September 2009, the [[Main Page|FlightGear Wiki]] supports multiple languages. From now on every article can be translated into any language, increasing the user friendliness for non-native English speaking users.

===We need '''YOU'''!===
As we have {{NUMBEROFARTICLES}} articles (some are smaller than others,) it is a heck lot of work to translate all the pages. A couple of users already started translating, but we definitely could use some help, and to be precise: your help! (Almost) everyone here speaks more than one language, so I wouldn't be surprised if most of the FG users are non-native English speakers.

If we all just translate one or two pages every now and then, it would not take *that* long to have at least the most important articles (like [[Flying the helicopter]], [[FlightGear]], [[Installing Scenery]] and [[New to FlightGear]]) translated.

Look at [[translation requests]] for the most urgent translations.

===Examples===
For examples of articles already translated (into a couple of languages,) take a look at the [[Main Page]].

=== How do I start translating? ===
First you need to find an article that you'd like to translate. Then, in the URL bar of your browser, add the abbreviation of your desired language (see
[https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php here] for a list) followed by a slash (/) in front of the English article title and go to that page. Thus, if I wanted to translate the TerraSync article into Dutch, I would visit the [[nl/TerraSync]] page. As you can see this page does not exist yet, so we are sure no-one translated it in Dutch so far.

Now we translate the actual article. You can leave wiki links as they are (pointing to the English article,) unless the article is translated into the language of your article. In that case you make a wiki link like this: <tt><nowiki>[[:nl:Hoofdpagina]]</nowiki></tt>. [[:nl:Hoofdpagina]] will be shown in the article. It is prefered however to use <tt><nowiki>[[:nl:Hoofdpagina|Hoofdpagina]]</nowiki></tt>, as that will get rid of the language prefix ([[:nl:Hoofdpagina|Hoofdpagina]]).

At the far bottom of the article you need to place the language links, so there will be a nice selection list in the menu. All translations of the article should be listed. So on the English article of [[TerraSync]], we add: <tt><nowiki>[[nl:TerraSync]]</nowiki></tt>. On the Dutch article, we add <tt><nowiki>[[en:TerraSync]]</nowiki></tt>. The language that the article is written in can be left out. Please keep the languages in alphabetical order, so it will be easier to add/remove languages.

Once you have translated an article, you need to add a language link to it on every translation of the article. Visit the English article to see in which languages it has been translated.

==== Step by step guide ====
# Find the English version of the page you would like to translate.
# Check if you agree with the content of the English page, use the discussion page or edit the English page so that it is up-to date (There is no reason why a translated page should not be better as the English version but for synchronisation it's preferred that the English version is up-to-date first) .
# Look left below, if the page has been translated to other languages it will list those languages below '''In other languages'''.
# If your language is not listed you can claim it and start translating. (If your language *is* listed, check it and update it)
# Find out the Language Extension '''LE''' of your language from [https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php this] list.
# Edit the English version on the page.
# Add to the bottom of the page <tt><nowiki>[[LE:Page title]]</nowiki></tt> where LE is the language extension and <tt>Page title</tt> is the '''correct''' title in '''your language'''.
# Save the English page and check if it now lists your language.
# Click the language link to edit the page in your language.
# Add <tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt> at the top of the page.
# Enter <tt><nowiki>[[en:Page title]]</nowiki></tt> at the bottom of your page, where <tt>Page title</tt> is the title of the original English page.
# If the English page has already been translated to other languages copy and paste those languages from the English page to the bottom of your page.
# Save your page and check if the language links work.
# You can claim your translation here: [[Translation requests]]
# Start translating and place your work into the new page.
# Place the link to your translation (<tt><nowiki>[[LE:Page Title]]</nowiki></tt>) at the bottom of the pages of other translations.
# Follow/Watch the English page and update your page when you see interesting updates.

=== What articles should not be translated? ===
'''Do not''' start translating articles that are '''[[:Category:afd|considered for deletion]]''' or '''[[:Category:Articles to be merged|need merging]]'''. First, the English variants of those articles should be improved.

'''Thanks a lot for your translations or any other contributions you make to the wiki! Your hard work is really appreciated by all FG users!'''

[[Category:Help|Translate]]

[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[it:Help:Tradurre]]
[[nl:Help:Vertalen]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[zh:Help:Translate]]
[[th:Help:Translate]]

Zh/Help:Translate

2018-01-25T05:14:17Z

Yfanhan:

{{hatnote|翻译模板，请参阅[[Help:Templates#Translating templates]]。}}

自2009年9月以来，维基的FlightGear支持多种语言。现在，每一篇文章都可以翻译成任何语言，增加对非母语英语使用者的用户友好性。

===我们需要你！===
现在，我们有2957篇文章，翻译所有的页面是一件很辛苦的工作。有几个用户已经开始翻译，但我们依然需要您的帮助！
这里的每个人都说不止一种语言，所以如果大部分的FG用户都是非英语母语者，我也不会感到惊讶。如果我们只是把一个
或两个页面翻译，每种语言有最重要的页面（如如何飞行直升机，FlightGear，安装风光和FlightGear的新手）的翻译将不会花费太长时间。
查看最迫切的翻译请求。

===实例===
对于已经翻译过的文章，请看主页。

===我怎样开始翻译？===
首先，你需要找到一篇你想翻译的文章。然后，在浏览器的URL栏上英文文章标题前添加一个斜线（/）和你想要的语言的缩写，然后转到那个页面。因此，如果我想把terrasync翻译成荷兰语，我将参观NL / terrasync页。正如你所看到的，这个页面还不存在，所以我们确信至今没有人用荷兰语翻译它。

现在我们翻译实际的文章。您可以为它们wiki保留链接（指向英文文章），除非文章被翻译成您文章的语言。在这种情况下，你做的维基链接是这样的：<tt><nowiki>[[:nl:Hoofdpagina]]</nowiki></tt>。但最好使用<tt><nowiki>[[:nl:Hoofdpagina|Hoofdpagina]]</nowiki></tt>，因为这会摆脱语言的前缀。

在文章的最底层，你需要放置语言链接，这样菜单中就会有一个不错的选择列表。所有文章的翻译都应该列出来。所以在[[terrasync]]的英语文章添加：<tt><nowiki>[[nl:TerraSync]]</nowiki></tt>。在荷兰的文章中，我们添加 <tt><nowiki>[[en:TerraSync]]</nowiki></tt>。这篇文章原来的语言可以被忽略。请按字母顺序排列语言，这样就更容易添加/删除语言。

一旦你翻译了一篇文章，你需要在这篇文章的不同语言版本中添加一个语言链接。浏览英文文章，看看已翻译过的语言。

====具体操作过程====
# 查找您要翻译的网页的英文版本。
# 检查你是否同意英文页的内容，使用讨论页或编辑英文页，以便它是最新的（没有理由解释为什么翻译的页面不应该比英文版本更好，但是为了同步，英文版本最好是最新的）。
# 向左看，如果页面被翻译成其他语言，它将列出这些语言。
# 如果您的语言没有列出，您可以创建它，并开始翻译。（如果您的语言已列出，请检查并更新它）
# 从[https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php 这个列表]中找出语言的扩展名。
# 编辑页面上的英文版本。
# 添加<tt><nowiki>[[LE:Page title]]</nowiki></tt>到页面的底部，LE是语言扩展名，Page title是您语言中正确的标题。
# 保存英语页面并检查它是否列出了你的语言。
# 单击你的语言的链接，编辑页面。
# 在页面的顶部添加<tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt>
# 在页面底部输入<tt><nowiki>[[en:Page title]]</nowiki></tt>，其中<tt>Page title</tt>是原始英文页面的标题。
# 如果英文页面已被翻译成其他语言，请将这些语言从英文页复制并粘贴到页面底部。
# 保存您的页面并检查语言链接是否工作。
# 您可以在这里声明您的翻译：[[Translation requests]]。
# 开始翻译，把你的成果放到新的页面中。
# 在其他翻译页面的底部放置链接(<tt><nowiki>[[LE:Page Title]]</nowiki></tt>)到你的翻译。
# 当你看到有趣的更新时，跟随/观看英语页面并更新你的页面。

===哪些文章不应该翻译？===
'''不要'''开始翻译被认为是'''[[:Category:afd|需要删除]]'''或'''[[:Category:Articles to be merged|需要合并]]'''的文章。首先，应该改进这些文章的英语版本。

'''非常感谢你的翻译或者你对维基的任何贡献！你的辛勤工作将得到所有FG用户的赞赏！'''

[[Category:Help|Translate]]

[[en:Help:Translate]]
[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[it:Help:Tradurre]]
[[nl:Help:Vertalen]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[th:Help:Translate]]

Zh/Help:Translate

2018-01-25T05:13:36Z

Yfanhan:

{{hatnote|翻译模板，请参阅[[Help:Templates#Translating templates]]。}}

自2009年9月以来，维基的FlightGear支持多种语言。现在，每一篇文章都可以翻译成任何语言，增加对非母语英语使用者的用户友好性。

===我们需要你！===
现在，我们有2957篇文章，翻译所有的页面是一件很辛苦的工作。有几个用户已经开始翻译，但我们依然需要您的帮助！
这里的每个人都说不止一种语言，所以如果大部分的FG用户都是非英语母语者，我也不会感到惊讶。如果我们只是把一个
或两个页面翻译，每种语言有最重要的页面（如如何飞行直升机，FlightGear，安装风光和FlightGear的新手）的翻译将不会花费太长时间。
查看最迫切的翻译请求。

===实例===
对于已经翻译过的文章，请看主页。

===我怎样开始翻译？===
首先，你需要找到一篇你想翻译的文章。然后，在浏览器的URL栏上英文文章标题前添加一个斜线（/）和你想要的语言的缩写，然后转到那个页面。因此，如果我想把terrasync翻译成荷兰语，我将参观NL / terrasync页。正如你所看到的，这个页面还不存在，所以我们确信至今没有人用荷兰语翻译它。

现在我们翻译实际的文章。您可以为它们wiki保留链接（指向英文文章），除非文章被翻译成您文章的语言。在这种情况下，你做的维基链接是这样的：<tt><nowiki>[[:nl:Hoofdpagina]]</nowiki></tt>。但最好使用<tt><nowiki>[[:nl:Hoofdpagina|Hoofdpagina]]</nowiki></tt>，因为这会摆脱语言的前缀。

在文章的最底层，你需要放置语言链接，这样菜单中就会有一个不错的选择列表。所有文章的翻译都应该列出来。所以在[[terrasync]]的英语文章添加：<tt><nowiki>[[nl:TerraSync]]</nowiki></tt>。在荷兰的文章中，我们添加 <tt><nowiki>[[en:TerraSync]]</nowiki></tt>。这篇文章原来的语言可以被忽略。请按字母顺序排列语言，这样就更容易添加/删除语言。

一旦你翻译了一篇文章，你需要在这篇文章的不同语言版本中添加一个语言链接。浏览英文文章，看看已翻译过的语言。

====具体操作过程====
# 查找您要翻译的网页的英文版本。
# 检查你是否同意英文页的内容，使用讨论页或编辑英文页，以便它是最新的（没有理由解释为什么翻译的页面不应该比英文版本更好，但是为了同步，英文版本最好是最新的）。
# 向左看，如果页面被翻译成其他语言，它将列出这些语言。
# 如果您的语言没有列出，您可以创建它，并开始翻译。（如果您的语言已列出，请检查并更新它）
# 从[https://phabricator.wikimedia.org/diffusion/MW/browse/master/languages/data/Names.php 这个列表]中找出语言的扩展名。
# 编辑页面上的英文版本。
# 添加<tt><nowiki>[[LE:Page title]]</nowiki></tt>到页面的底部，LE是语言扩展名，Page title是您语言中正确的标题。
# 保存英语页面并检查它是否列出了你的语言。
# 单击你的语言的链接，编辑页面。
# 在页面的顶部添加<tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt>
# 在页面底部输入<tt><nowiki>[[en:Page title]]</nowiki></tt>，其中<tt>Page title</tt>是原始英文页面的标题。
# 如果英文页面已被翻译成其他语言，请将这些语言从英文页复制并粘贴到页面底部。
# 保存您的页面并检查语言链接是否工作。
# 您可以在这里声明您的翻译：[[Translation requests]]。
# 开始翻译，把你的成果放到新的页面中。
# 在其他翻译页面的底部放置链接(<tt><nowiki>[[LE:Page Title]]</nowiki></tt>)到你的翻译。
# 当你看到有趣的更新时，跟随/观看英语页面并更新你的页面。

===哪些文章不应该翻译？===
'''不要'''开始翻译被认为是'''[[:Category:afd|需要删除]]'''或'''[[:Category:Articles to be merged|需要合并]]'''的文章。首先，应该改进这些文章的英语版本。

'''非常感谢你的翻译或者你对维基的任何贡献！你的辛勤工作将得到所有FG用户的赞赏！'''

[[Category:Help|Translate]]

[[en:Help：Translate]]
[[ca:Help:Traduir]]
[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[fa:راهنمایی:ترجمه]]
[[fr:Help:Traduire]]
[[it:Help:Tradurre]]
[[nl:Help:Vertalen]]
[[pt:Help: Traduzir]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]
[[th:Help:Translate]]

Help:Translate

2018-01-25T05:11:02Z

Yfanhan:

Zh/Help:Translate

2018-01-25T03:40:41Z

Yfanhan:

Zh/Help:Translate

2018-01-25T03:24:19Z

Yfanhan:

Zh/Help:Translate

2018-01-25T03:17:24Z

Yfanhan: Created page with "帮助：翻译 (翻译模板，请参阅帮助#翻译模板：模板。) 自2009年9月以来，维基的FlightGear支持多种语言。现在，每一篇文章都可以翻..."

帮助：翻译
(翻译模板，请参阅帮助#翻译模板：模板。)
自2009年9月以来，维基的FlightGear支持多种语言。现在，每一篇文章都可以翻译成任何语言，增加对非母语英语使用者的用户友好性。

内容
1我们需要你！
2例子
3我怎样开始翻译？
3.1具体操作指南
4哪些文章不应该翻译？

我们需要你！
现在，我们有2957篇文章，翻译所有的页面是一件很辛苦的工作。有几个用户已经开始翻译，但我们依然需要您的帮助！
这里的每个人都说不止一种语言，所以如果大部分的FG用户都是非英语母语者，我也不会感到惊讶。如果我们只是把一个
或两个页面翻译，每种语言有最重要的页面（如如何飞行直升机，FlightGear，安装风光和FlightGear的新手）的翻译将不会花费太长时间。
查看最迫切的翻译请求。

实例
对于已经翻译过的文章，请看主页。