Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions

Jump to navigation Jump to search
Line 1,385: Line 1,385:
=== Supporting Translations ===
=== Supporting Translations ===
{{Stub}}
{{Stub}}
$FG_ROOT/Translations contains references that are looked up by the menubar - so the menubar merely contains property references, not the strings - the translated strings are then looked up using those properties - e.g. see $FG_ROOT/Translations/en/menu.xml (?)
Next, check preferences.xml for the <intl> tag that includes Translations/locale.xml
At that point, you should understand how the existing scheme works, and how you can use the same mechanism to also localie Canvas dialogs accordingly, even without hard-coding any language into the code.
<ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=292526#p292526
  |title  =  <nowiki> Re: User language </nowiki>
  |author =  <nowiki> Hooray </nowiki>
  |date  =  Aug 14th, 2016
  |added  =  Aug 14th, 2016
  |script_version = 0.40
  }}</ref>
there should be some kind of /sim/intl and /locale tree somewhere in the global tree, have you checked if that's the case or not?
there should be some kind of /sim/intl and /locale tree somewhere in the global tree, have you checked if that's the case or not?


Navigation menu