I'm done with the first stage of the Unicode port.
As you might have seen, it was not just a dumb merge from Jim Park sources..
I made a lot of improvements and fixes over Jim Park version.
Anyway, the current state is that you can compile NSIS sources either as
ANSI, or as Unicode using *scons dist UNICODE=yes
*Stubs & plugins will be compiled as Unicode as well.
As for the scripts, the Unicode version should be completely compatible
with Jim Park's version.
The next stages are :
* Make the Unicode version of MakeNsis able to generate both ANSI &
o So we don't have to release two variant of NSIS and we can
have everybody use only the Unicode version once and for all
* Provide a Plugin API transparently compatible with both ANSI &
o So plugin developers can choose to compile their plugins as
ANSI and/or Unicode, and the plugin layer automatically
converts if there is an ANSI/Unicode mismatch between the
installer and the plugin
I will detail these stages in the following 2 mails... (so don't start
the debate yet)