matt weagle
13th May 2001 21:53 UTC

I read a while back a thread about localized versions of NSIS and/or porting the strings to an RC file. Has there been any additional work on this front or would anyone be interested in starting it up? Thanks.

SENCO
14th May 2001 07:59 UTC

I have it translated into spanish
Hey,

I have translated the EXE Header of NSIS in order to use with my spanish language pack (www.winamp.es.org).

It was a very hard task, because I had to read all the code and then translate it. I thought on put it on a .rc file but I believe that it would make bigger the header. The solution I have thought is put them on a .h file using the #DEFINE instruction. The compiled code it would be the same, but it's easier to translate.

Thank you,

alfrenovsky
14th May 2001 12:42 UTC

I needed a spanish version, so I searched for any " and changed the content.

with defines I´ll be more easier. Now we mut translate every new version. I thinks that defines must include syntax.

In spanish case the "$s setup" can´t be translated just changing the word "setup" it must be "instalador %s" or something like that. So i propose that the includes includes all the sentence instead just words.

I can do it, but I don´t know how the other developers will synchronize the versions.

-
Alfrenovsky

matt weagle
14th May 2001 19:48 UTC

I've been looking at the source and am trying to come up with a good way to handle this. I'd rather not have to build EXEs for each language, but agree that RC files might introduce additional overhead. What about defining the strings in a "String Configuration Header" part of the NSI file itself? We set up "string IDs" which can be set just like OutFile or SilentInstall. If a given string exists in the NSI file, it supercedes whatever's coded in the EXE file. Does anyone see problems with this approach? Or should I ask instead, how many problems do people see with this approach ;-) ? Thanks again.