David Megginson writes:
> Curtis L. Olson wrote:
>
> > Having given a very tiny bit of thought to 'internationalizing'
> > flightgear I thought perhaps a first start would be to provide
> > translated versions of menu.xml and options.xml
>
> I'm looking forward to the Minnesotan translation. Will it sound like
> Prairie Home Companion, or Fargo?
David,
With the current property system, is it possible to do something like
the following. In preferences.xml have an entry like:
<language>strings-fr.xml</language>
Then in menu.xml use a property value to specify the include file,
something like:
<strings include=/sim/language/>
Then in menu.xml we could reference the strings property names (thus
indirectly referencing the actual text) rather hard coding the text:
<menu>
<submenu>
<name>/strings/file</name>
<option>
<name>/strings/save-flight</name>
<call>saveFlight</call>
</option>
<option>
<name>/strings/load-flight</name>
<call>loadFlight</call>
</option>
<option>
<name>/strings/reset</name>
<call>reInit</call>
</option>
<option>
The strings-fr.xml file would look something like (according
to babelfish):
<file>Dossier</file>
<save-flight>Economiser le vol</save-flight>
<load-flight>Vol de charge</load-flight>
<reset>Remise</reset>
The big thing that would need to be looked at is if we can include
based on the contents of a property name, rather than just include
some hard coded file name.
Regards,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
