Installer in Simplified Chinese

John_Sum · 14th November 2007, 10:50

This may be a naive question as I do not have a great deal of experience with NSIS.

I am trying to build an installer in Simplified Chinese. I can do this and the Chinese displays correctly in the installer dialogue, when run on Chinese Windows, except for one place which is the initial language selection combo. If I put German in, it say Deutsch, French is shown as Francais etc. but Simplified Chinese is shown as Chinese(Simplified), i.e. in English, and it is not shown in Chinese script.

I have tried compiling in English Windows and Chinese Windows all to no avail.

When compiling, I get a warning which refers to:

LangString "DESC_SecInstall" is not set in language table of language SimpChinese

but I can no reference to this.

I am using the modern UI and pretty much copying the multilingual example.

I would appreciate anyone's help. Thanx

kichik · 14th November 2007, 18:25

That happens because the standard of using the English name for the language selection is not enforced in the language files.

The LangString warning is generated because you haven't defined a Chinese text for the DESC_SecInstall LangString.

John_Sum · 15th November 2007, 08:48

Thanks for your reply.

So - are you saying that with Simplified Chinese, the standard of using English is applied. If so, do you know how to stop that happening so I can display a Chinese string?

Secondly, I have no idea where to define DESC_SecInstall. Is this the string that is the Chinese text for Simplified Chinese? The inclusion of German gives a similar error message, so I suspect that this is not particularly relevant.

kichik · 15th November 2007, 16:58

Those strings come from the language file. Edit Contrib\Language files\SimpChinese.nsh. You can also hack it a bit by redefining LANGFILE_SIMPCHINESE_NAME to the string you want.

John_Sum · 16th November 2007, 12:03

Thanks again for the reply and for your help.

I have resolved the problem now, by editing the .nsh file. Has to be done on a Chinese Windows system though - could not get it accepted on a language-packed English system.

jimpark · 21st November 2007, 15:57

John, I had the same problem but if you don't care about Windows 9x, then you can use the Unicode version of NSIS. Check out www.scratchpaper.com for the binaries and source. You can also look at the "Unicode" thread in this forum for more information.

John_Sum · 21st November 2007, 17:20

Thanx.

I'll look into that.

John_Sum · 21st November 2007, 17:39

Great stuff. The unicode version has completely solved my problem.

Many, many thanks!

14th November 2007, 10:50	#1
John_Sum Junior Member Join Date: Nov 2007 Posts: 10	Installer in Simplified Chinese This may be a naive question as I do not have a great deal of experience with NSIS. I am trying to build an installer in Simplified Chinese. I can do this and the Chinese displays correctly in the installer dialogue, when run on Chinese Windows, except for one place which is the initial language selection combo. If I put German in, it say Deutsch, French is shown as Francais etc. but Simplified Chinese is shown as Chinese(Simplified), i.e. in English, and it is not shown in Chinese script. I have tried compiling in English Windows and Chinese Windows all to no avail. When compiling, I get a warning which refers to: LangString "DESC_SecInstall" is not set in language table of language SimpChinese but I can no reference to this. I am using the modern UI and pretty much copying the multilingual example. I would appreciate anyone's help. Thanx

14th November 2007, 18:25	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	That happens because the standard of using the English name for the language selection is not enforced in the language files. The LangString warning is generated because you haven't defined a Chinese text for the DESC_SecInstall LangString. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

15th November 2007, 16:58	#4
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Those strings come from the language file. Edit Contrib\Language files\SimpChinese.nsh. You can also hack it a bit by redefining LANGFILE_SIMPCHINESE_NAME to the string you want. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

21st November 2007, 15:57	#6
jimpark Senior Member Join Date: Sep 2007 Posts: 204	John, I had the same problem but if you don't care about Windows 9x, then you can use the Unicode version of NSIS. Check out www.scratchpaper.com for the binaries and source. You can also look at the "Unicode" thread in this forum for more information. Unicode NSIS advocate -- http://www.scratchpaper.com for latest build and source. Last edited by jimpark; 21st November 2007 at 17:02.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

15th November 2007, 08:48	#3
John_Sum Junior Member Join Date: Nov 2007 Posts: 10	Thanks for your reply. So - are you saying that with Simplified Chinese, the standard of using English is applied. If so, do you know how to stop that happening so I can display a Chinese string? Secondly, I have no idea where to define DESC_SecInstall. Is this the string that is the Chinese text for Simplified Chinese? The inclusion of German gives a similar error message, so I suspect that this is not particularly relevant.

16th November 2007, 12:03	#5
John_Sum Junior Member Join Date: Nov 2007 Posts: 10	Thanks again for the reply and for your help. I have resolved the problem now, by editing the .nsh file. Has to be done on a Chinese Windows system though - could not get it accepted on a language-packed English system.

21st November 2007, 17:20	#7
John_Sum Junior Member Join Date: Nov 2007 Posts: 10	Thanx. I'll look into that.

21st November 2007, 17:39	#8
John_Sum Junior Member Join Date: Nov 2007 Posts: 10	Great stuff. The unicode version has completely solved my problem. Many, many thanks!