1 reply to this topic

[pscEx]

Currently there are some discussions about organization, responsibility, project layout. etc.

There is an issue hidden in the background which is much more important.

Sometimes developers do not take care on the localization of their scripts.

Samples:

In ???.au3 there is the line

$SendTo=StringLeft(@DocumentsCommonDir,2) & "\Documents and Settings\Default User\SendTo"

what in my (German) build leads to:
[attachment=608:attachment]

In ???.script there is:

%ProgramExe%=x:\programs\%ProgramFolder%\???.exe

What, if in a different script fom a German programmer is:

%ProgramExe%=x:\Programme\%ProgramFolder%\???.exe

And Nuno writes a script with:

%ProgramExe%=x:\Arquivos dos programas\%ProgramFolder%\???.exe

etc. ...

It is very necessary that scripts are maid in that way that localized names are taken from the install CD.
Please, not from the host because the install CD may have a different language!
Therefore caution with the use of e.g. the WinBuilder's variable %UserProfile%!

If you try the localeFolders script which is in the sandbox, that is a first step to what I recommand here.

I'm going to do some more work on it ad hopefully I'll publish a script / tool which helps developers to write locale-independent scripts.

Peter

[edborg]

When improving localization, please take into account the need of having the possibility to set keyboard, dates, currencies in a language different from that of the building CD (it might be a selected one, or the one of the host), as posted here and in the SetKeyboard thread .
Thanks
edborg
P.S. I'm presently not using localization script for this reason, and I use the SetKeyboard. script instead, which works fine, but doesn't fulfil the date/currency need.

ADDED: The feature has been included in Autolocalize.script as from version 019

Edited by edborg, 21 November 2006 - 08:38 AM.