--- Yannick LE NY wrote:
> LeeE a écrit :
> > There is also a lot of data in the tree that is only generated once
> > FG is running, so you won't find everything in those two files.
> >
> Crazy (all the internal properties in memory, all the modifications are
> not stored)
Most of the internal properties are floating point numbers, integers etc, so
really won't benefit from translation. Translating the actual property paths
isn't worthwhile as they are not end-user-visible (most of the time).
> Then there is no solution to translate the text strings that are defined
> in the flightgear "internal properties"
> I can not translate the "Basic keys" windows and the "Common aircraft
> key" window and the tutorial window ?
I think you will have to create this as a "diff" against the current files.
> I think it's times for flightgear developpers to add full I18N support
> with UTF-8 in the next flightgear release.
I think full I18N support is going to be very difficult to attain.
I'm not sure how easy it will be to add UTF-8 support - I don't know if our
graphics libraries support rendering it, for example.
Of course, the only real way to find out is to try it! You are volunteering? You
will find the source code on the web-site.
-Stuart
___________________________________________________________
Support the World Aids Awareness campaign this month with Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
