actually, it shouldn't be too difficult to also make the tutorials translatable using the same technique. After all, the tutorial system is also just a PropertyList XML file and some Nasal code. So the same technique could definitely be used here - just by using io.read_properties() and overwriting the translated strings.
@flightflan: Tell us what tutorial you'd like to translate, so that we can have a look and work out if/how the tutorial system would need to be modified to support translations, it's not like this would be a huge change or very difficult ... certainly not if you are satisfied with having it 80-90% translated.
EDIT:
Looking at the c172p tutorials:
http://gitorious.org/fg/fgdata/blobs/ma ... tartup.xmlIt would already be a good start to translate all the message tags, e.g.:
- Code: Select all
<message>Welcome to Livermore Municipal Airport. In this lesson we'll go through the pre-startup checks and start the aircraft.</message>
To do this, you really only need to provide another XML file and add the corresponding nodes (copy/paste), e.g.:
- Code: Select all
<PropertyList>
<step n="0">
<message>Welcome to Livermore Municipal Airport. In this lesson we'll go through the pre-startup checks and start the aircraft.</message>
</step>
<step>
<message>Before we start up, we need to brief what we'll do in case of an engine fire on startup. As
this isn't our aircraft, and we're fully insured, we'll simply open the door and run away.</message>
</step>
<step>
<message>Next, we check our seatbelts, and seat adjustments. Cessnas can get worn seat rails that
sometimes cause the seat to slip backwards, often just as you take off, so make sure it is secure.</message>
</step>
</PropertyList>
Next, edit the file and translate everything to Spanish/Portugese.
And then, just include it after the original file - so that it overwrites the English messages, that's it.
To support this automatically, the tutorial.nas script would need to be slightly modified:
http://wiki.flightgear.org/Tutorials