[Gpg4win-devel] zh_CN/TW translations for GpgEx, GpgOL and Gpg4win installer
arthur2e5 at aosc.xyz
arthur2e5 at aosc.xyz
Mon Nov 16 19:34:34 CET 2015
Yes, I got it! Since I am on my school laptop with CP437 as default, I used
[NTLEA](https://ntlea.codeplex.com/) to emulate the CP936 codepage. Anyway,
the Chinese (simplified) selection popped up and worked well.
16.11.2015, 04:35, "Andre Heinecke" <aheinecke at intevation.de>:
> Hi,
>
> On Saturday 14 November 2015 01:30:30 Mingye Wang wrote:
>> On my computer (default non-unicode cp = 936 (zh_CN), Windows 10 10240),
>> I didn't even see a popup. Is it remembering my choice somewhere?
>
> Yes, the last selection is stored in the registry:
> HKEY_LOCAL_MACHINE/Software/GNU/GPG4Win Installer Language
>
> Just delete this value and the language popup should show up again.
>
>> Anyway, I can only find some oddity regarding those `SUBLANG_CHINESE`
>> things. In the NSIS source, although Contrib/MakeLangId uses this
>> `correct' (i.e. defined in MSDN) pairs in sub[] and even iterates
>> through it, their
>> [Example/languages.nsi](http://sourceforge.net/p/nsis/code/HEAD/tree/NSIS/tr
>> unk/Examples/languages.nsi) uses `LANG_SIMPCHINESE` and `LANG_TRADCHINESE`.
>> These two strings can be found nowhere else according to my `grep`, but
>> some extra search on the web shows that almost nobody use
>> `${SUBLANG_CHINESE_SIMPLIFIED}`.
>>
>> So here is a possible patch (I am only changing your commit diff found
>> on webgit):
>>
>> diff a/po/nsis-msgfmt.c b/po/nsis-msgfmt.c
>> --- a/po/nsis-msgfmt.c
>> +++ b/po/nsis-msgfmt.c
>> @@ -80,8 +80,8 @@ iso639_to_nsis
>> { "bg", "LANG_BULGARIAN", "Bulgarian" },
>> { "ca", "LANG_CATALAN", "Catalan" },
>> { "zh", "LANG_CHINESE", NULL },
>> - { "zh_CN", "SUBLANG_CHINESE_SIMPLIFIED", "SimpChinese" },
>> - { "zh_TW", "SUBLANG_CHINESE_TRADITIONAL", "TradChinese" },
>> + { "zh_CN", "LANG_SIMPCHINESE", "SimpChinese" },
>> + { "zh_TW", "LANG_TRADCHINESE", "TradChinese" },
>> { "zh_HK", "SUBLANG_CHINESE_HONGKONG", NULL },
>> { "zh_SG", "SUBLANG_CHINESE_SINGAPORE", NULL },
>> { "zh_MO", "SUBLANG_CHINESE_MACAU", NULL },
>>
>> I hope this works. As some kind of precaution, I actually doubt if those
>> `SUBLANGs` will ever work -- they never include them in their examples.
>> (I am too lazy to open up an IDE and look at how the thing works)
>
> Thanks for looking into it. Yes with the SUBLANG_ definitions I got warnings
> during the installer build that the translations are not used.
>
> Based on the same example you've mentioned I changed it:
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=commit;h=770737e288492683588619f762c6974eb76361b3
>
> (This commit is part of the Beta Version I've uploaded)
> The warnings were gone and everything looked ok to me at build time. But I
> still did not have Chinese selectable. Thats why I thought maybe the codepage
> is involved somehow. But I still doubt that.
>
> Regards,
> Andre
>
> --
> Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/
> Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
> Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
More information about the Gpg4win-devel
mailing list