pilm
28th March 2005 14:07 UTC
Error while applying NLF font/RTL
Hi,
I've recently upgraded from NSIS 2.0 to 2.06. I've a script with multiple languages and some Language Strings. Now, when I try to compile a script with RTL/Unicode languages (SimChinese, Japanese, etc), compilation fails after "Generating language table" with this message :
Error while applying NLF font/RTL: ReadVarLenArr - Unicode conversion failed.
NSIS compiler from 2.01 to 2.05 just crash at this point. The MUI MultipleLanguage.nsi script doesn't compile too.
I've searched trough the forum and didn't find any answer... Thanks for your help.
kichik
29th March 2005 18:23 UTC
Are you compiling on Windows or POSIX? Can you include a minimal script reproducing this behavior?
pilm
29th March 2005 19:46 UTC
I'm compiling under Windows XP.
I use, for example :
"MUI.nsh"
>!insertmacro MUI_LANGUAGE "French"
>!insertmacro MUI_LANGUAGE "SimpChinese"
>LangString Name_Section1 ${LANG_FRENCH} "bla bla french"
>LangString Name_Section1 ${LANG_SIMPCHINESE} "bla bla english"
>Function .onInit
!insertmacro MUI_LANGDLL_DISPLAY
FunctionEnd
>
This script used to work nicely with NSIS 2.0, and doesn't now. However it works if I comment the "!insertmacro MUI_LANGUAGE "SimpChinese"" line...
kichik
29th March 2005 20:01 UTC
Aside from the missing OutFile and section, the script works fine for me. Have you changed something in SimpChinese.nlf or SimpChinese.nsh? Can you attach them?
pilm
30th March 2005 17:32 UTC
I changed nothing in theses files, here they are.
kichik
31st March 2005 18:39 UTC
Those files are indeed the same as in the original package.
Can you please try that script on a clean installation of NSIS?
Pilm
1st April 2005 13:13 UTC
I use already a clean install of NSIS.
But maybe the problem comes from my system : I've installed Windows XP without Asians and RTL languages. I suppose it has an inpact only on executed RTL programs, and not on compilation, but who knows... I've just installed the missing asian and RTL fonts, and have still the same bug.
I going to reinstall a full-language Windows, and I'll tell you if the bug is still there after that.