Unicode strings, such as resource names, are always
converted to ANSI and back to Unicode using the ANSI
codepage. The strings should be stored as Unicode.
I still would like to see my problem fixed. The generated
project.nsh file holds a set of !definesm and I only
experience problems when a value of one of these contain
UTF-8 specific characters (ie. ,,,,).
thomas@paal.net
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, but I still would like to see the problem I'm
experiencing fixed. The project.nsh file is just a set of
!defines, and the problem arise only when I'm using one of
these values and the value contain UTF-8 specific characters.
The characters are then printed wrong (as two characters) in
the GUI.
thomas@paal.net
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Please fix this ASAP! I'm using the maven nsis-plugin, which
generates an UTF-8 encoded project.nsh file...
thomas@paal.net
Logged In: YES
user_id=584402
The resource editor is not used to read script files. Fixing
the lossy conversion will not allow makensis to compile
UTF-8 encoded scripts.
Logged In: NO
I still would like to see my problem fixed. The generated
project.nsh file holds a set of !definesm and I only
experience problems when a value of one of these contain
UTF-8 specific characters (ie. ,,,,).
thomas@paal.net
Logged In: NO
Ok, but I still would like to see the problem I'm
experiencing fixed. The project.nsh file is just a set of
!defines, and the problem arise only when I'm using one of
these values and the value contain UTF-8 specific characters.
The characters are then printed wrong (as two characters) in
the GUI.
thomas@paal.net
Logged In: YES
user_id=584402
Please submit your request as a separate feature request.
Logged In: YES
user_id=604457
NSIS does not yet support Unicode. Script files should not be
saved in UTF-8 format but in ANSI format.