NSIS Ansi+Unicode hybrid
I have been playing with the idea of having both A and U NSIS installed in the same directory (Sharing examples,includes etc)
Currently, only simple scripts work. It does this by using hacked versions of makensis that look for their stubs and plugins in separate sub directories. The main makensis.exe has been replaced by a small loader that tries to figure out if the .nsi has a BOM (It also supports /ANSI or /UNICODE as the first parameter on the command line)
Grab the experimental installer if you want to play with it (Do NOT overwrite you normal NSIS install, you also probably want to uncheck startmenu and shell integration during install)
Current issues include:
- ReserveFile calls fail for plugins
- Only ANSI language files are installed and I'm not sure if the unicode compiler is able to pull out the codepage from the .nlf and do proper conversion to unicode, it seems to prefer a BOM (So unicode is pretty much broken when it comes to languages that are not ASCII)
If the official distribution is ever going to support this, we would need two new defines that MUI and other things can use: NSIS_PLUGINSDIR and NSIS_LANGDIR (Defines would be set by the compiler at runtime) (It would be possible for my loader to set these, but there is no support anywhere for them so I would have to patch MUI also, might do that in the future if there is any demand for it)
NB: This configuration is in no way supported by anyone and should only be used to play around and experiment ;)