Skip to main content
K.Daube
Community Expert
Community Expert
December 19, 2022
Answered

What's wrong with my localisation approach?

  • December 19, 2022
  • 1 reply
  • 250 views

Dear experts and gurus,

I have this small test program and run it in ESTK with FrameMaker 14, French version:

 

// ES-localisation.jsx - test the localisation à la ExtendScript
var sDnav_hlpTip7   = { en: "Define the heading levels",
                        de: "Überschriften-Ebenen definieren",
                        fr: "Définir les niveaux des titres"};
wDefine = new Window ("dialog", localize (sDnav_hlpTip7), undefined);
wDefine.preferredSize.width = 200;
wDefine.show();

 

FM is French, as the top menu demonstrates. Nevertheless the dialogue title is English:

I follow the method described in the Javascript Tools Guide under the heading Localizing ExtendScript strings.

→ Have I overseen something?

→ Does the process look for the Windows UI language (which in my case is English), not the FM UI language - which obviously is French?

This topic has been closed for replies.
Correct answer K.Daube

Ha, I got it - the documentation states:

The language is chosen by the application at startup, according to the current locale provided by the operating system.

IMHO this is not what a user in the FM environment expects...

1 reply

K.Daube
Community Expert
K.DaubeCommunity ExpertAuthorCorrect answer
Community Expert
December 19, 2022

Ha, I got it - the documentation states:

The language is chosen by the application at startup, according to the current locale provided by the operating system.

IMHO this is not what a user in the FM environment expects...