Skip to content
⌘ NSIS Forum Archive

NSIS v2.30 MUI_PAGE_WELCOME is blank in SimpChinese language?

11 posts

adylee#

NSIS v2.30 MUI_PAGE_WELCOME is blank in SimpChinese language?

NSIS v2.30 MUI_PAGE_WELCOME is blank in SimpChinese language,when i change English language it's okay!
Why?
kichik#
Works fine for me. I can't actually read anything, but the page is definitly not empty. Can you attach the simplest script reproducing this issue?
adylee#
now i list the screenshots in my pc.

NSIS v2.29 in Chinese


NSIS v2.29 in English


NSIS v2.30 in Chinese


NSIS v2.30 in English[IMG]


now you see the blank in SimpChinese version.Why?
kichik#
As I said, it works fine for me. I need a script that reproduces this issue so I can see the problem for myself and try to fix it.
adylee#
this is the content of nsi script file in my project.

; example1.nsi
;
; This script is perhaps one of the simplest NSIs you can make. All of the
; optional settings are left to their default settings. The installer simply
; prompts the user asking them where to install, and drops a copy of example1.nsi
; there.

;--------------------------------

!include "MUI.nsh"
!insertmacro MUI_PAGE_WELCOME
!insertmacro MUI_LANGUAGE "SimpChinese"

; The name of the installer
Name "Example1"

; The file to write
OutFile "example1.exe"

; The default installation directory
InstallDir $PROGRAMFILES\Example1

;--------------------------------

; Pages

Page directory
Page instfiles

;--------------------------------

; The stuff to install
Section "" ;No components page, name is not important

; Set output path to the installation directory.
SetOutPath $INSTDIR

; Put file there
File example1.nsi

SectionEnd ; end the section
kichik#
I still get a welcome page with some text with this script. Have you tried reinstalling NSIS? Maybe some files have been deleted? Doesn't the compiler warn of missing strings for this script?
kichik#
Well, you're not the only one:



It probably has to do something with your codepage. I'll have a look when I get the time. If you want a quick solution, you should probably starting looking at encoding issues yourself or use 2.28.
crony682#
Hmm... In my case, the same symptom has occured(Korean Language).
I solved this problem using
!include "MUI2.nsh"
rather than
!include "MUI.nsh".
kichik#
I've finally tracked down the issue. It's caused by Io2Nsis and Nsis2Io which don't work that well with MBCS. I've modified them a bit for the next version and it should work.

Using MUI2 is a good workaround as it doesn't use InstallOptions and therefore has no need for Nsis2Io and Io2Nsis.