Hi All,

I am looking out for non localized gui parts. There are some. Is there
any decision made up to which extent we intend to localize for a first
flash?
I would identify several levels of diving into this:

GUI wise:
1. Usually accessed areas while doing a Sunday afternoon thermal flight.
2. The config area.
3. More specific modules like waypoint editor and competitive modules.

Code structure wise:
1. Simply change _T() to what is appropriate -> N_() or _() ...
2. Medium sophisticated string operations, to enable loc.
3. Change in gui code structure, because of wf->FindByName(...) et. al.

Text semantic wise:
Looking out for some translation I come to the point where at some place
the English phrases do not hit the point. That impression comes up when
looking into the modules functionality, the manual, and maybe the
manuals of the specific supported sensor hardware. 
A change at this point could easy the translation, or even solve
conflicts of changed functionality, outdated manual etc.

Anybody with an opinion to that?

Helmut

-- 
Helmut Rohs
d: 0761 4512359
p: 0761 5564244


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

Reply via email to