MobileRead Forums - View Single Post

3rd · 11-22-2010, 07:14 AM

curstpriest,

In the file you've menshioned (word.tar) is folder named "zh_CN.utf8". There are LC_* files. The script use command "localdef" to define locales first and only then copies that folder into /usr/lib/locale/. So spacial LC_* files are prepeared only for zh_CN. I know too little about meaning of LC_* files, but maybe LC_CTYPE and LC_COLLATE files have effect on charsets.

I was unable to make usbnet connection with my Kindle running Duokan. But I think that I can set locales in install/update scripts without connecting to Kindle directly, what bothers me is that folder with LC_* files.

Eventually problem could lie not in locales but somewhere in Duokan software alone.

=========

FethryDuck,

Translating menus is good idea, but it is hard to make translations with invisible chars ;-)

11-22-2010, 07:14 AM	#294
3rd Member Posts: 10 Karma: 10 Join Date: Nov 2010 Device: KDXG	curstpriest, In the file you've menshioned (word.tar) is folder named "zh_CN.utf8". There are LC_* files. The script use command "localdef" to define locales first and only then copies that folder into /usr/lib/locale/. So spacial LC_* files are prepeared only for zh_CN. I know too little about meaning of LC_* files, but maybe LC_CTYPE and LC_COLLATE files have effect on charsets. I was unable to make usbnet connection with my Kindle running Duokan. But I think that I can set locales in install/update scripts without connecting to Kindle directly, what bothers me is that folder with LC_* files. Eventually problem could lie not in locales but somewhere in Duokan software alone. ========= FethryDuck, Translating menus is good idea, but it is hard to make translations with invisible chars ;-)