Skip to content
⌘ NSIS Forum Archive

help with installing when user types cryllic characters

5 posts

darryllrohr#

help with installing when user types cryllic characters

hello,

i am creating a multi language installer and our testers in russia have run into a problem with the installer.

i am using modern UI 2 and when the user is prompted to enter the destination folder for the installation (MUI_PAGE_DIRECTORY) and he enters any cryillic characters, the installer fails to install the software.

how can i force the user to enter non-cryllic characters? or can i force the installer to install with cryillic characters? or is there another way to get around this?

thanks for your help.
Anders#
If this is NSIS 3 then use Unicode, for NSIS 2.4x the characters have to match the active codepage for non-Unicode programs (Regional options in the control panel?).
darryllrohr#
thanks for the reply.

I am using version 2.46. so, in regards to "language for non-unicode programs", if someone in Russia simply changed their system locale to English before running the installer, would this allow the installer to work?


I am willing to use version 3.0a2. if I do upgrade to this version, what does it mean to "use Unicode"? is the entire installer a Unicode installer and by simply building an installer with this version inherently make it a Unicode installer?
will my existing nsi file compile and run properly with the new version?
are there specific settings to make to "use Unicode" with this new version?
what other considerations do I need to think about?

thanks for your help,
JasonFriday13#
Originally Posted by darryllrohr View Post
I am willing to use version 3.0a2. if I do upgrade to this version, what does it mean to "use Unicode"? is the entire installer a Unicode installer and by simply building an installer with this version inherently make it a Unicode installer?
will my existing nsi file compile and run properly with the new version?
are there specific settings to make to "use Unicode" with this new version?
what other considerations do I need to think about?

thanks for your help,
By default 3.0a2 creates ansi installers. You have to use 'Unicode True' in the script to compile a unicode installer. You might have to change a few paths if your script references files in the NSIS directory (I haven't double checked this though). 2.46 is the benchmark release, the 3.0 alphas have fixed lots of bugs and added new features (Unicode and (still testing) 64 bit are the major ones), but it's still a work in progress.