November 2001 - openSUSE M17n - openSUSE Mailing Lists

CJK-support (manual)
by ugroh＠t-online.de 30 Nov '01

30 Nov '01

I am working my way true the "CJK Support in Suse Linux" Manual. I have installed the japanese fonts (checked by the 2.1.1 example). Now I started the section 3 Input. If I do the examples 3.1.3.1 and 3.1.3.1.1 (with gvim) it doesn't work as described: - Shift-Space don't work - I have japanese items but I cannot enter japanese text Are their more descriptions available how to set up the environment? Also if I start with the example 3.1.3.1. a strange message "warning yubin7 ... " pops up. ??? Thanks for any comment. -- --------------------------------------------------- Mit freundlichen Gruessen / Best regards Ulrich Groh ----------------------------------------------------

2 3

Ghostscript and CJK
by khchan2＠study.csis.hku.hk 27 Nov '01

27 Nov '01

:SuSE 7.2, GNU Ghostscript 5.50: Last night I tried to use KDE to print a Chinese document typed in kword to PDF. Later on I checked the PDF and only the first line was correctly displayed, other lines became all garbage. I got the same result if I print it directly from the printer. I am wondering if this is a problem of kword, the CJK support of gs or even the Chinese font (Arphic) used.

2 2

Re: [m17n] SLES 7 DBCS support
by Alan Darlington 26 Nov '01

26 Nov '01

In response to Diane Brent, Mike Fabian writes: >> For SLES 7, are there or will there be other languages supported besides >> English and German. DBCS languages inparticular? > From a technical point of view, it is no problem at all for us > to add support for Japanese and basic support for Korean and Chinese > as well. Everything necessary is available already in SuSE Linux 7.2. This is true for the IA32 platform. What should be used to complete the Far Eastern environments on other platforms where there is no 7.2 release, such as IA32, PPC32 and /390? Alan Darlington Java Globalization Project Manager IBM Centre for Java Technology IBM UK Laboratories, Hursley MP 154 Phone +44 (0)1962 818308 Internal 7-248308 alan_darlington(a)uk.ibm.com

2 1

Japanese console fonts
by ピアスエリオ 26 Nov '01

26 Nov '01

Hello all, I have a question about Japanese support in the virtual terminals. I'm not sure why but the following console font is loading automatically each time on start up: '161.cp.gz'. It appears to be an arabic font which doesn't help me because my virtual console is set to Japanese (LANG=ja_JP) and all I get is illegible characters when it should be Japanese. Upon looking at the directory where this font resides, I find the directory (/usr/lib/kbd/consolefonts) is loaded with console fonts. Any way of finding out which one is a Japanese font? Thanks for reading this, Eric __________________________________________________ Do You Yahoo!? Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/

2 1

Re: [m17n] Anyone has experience in such combination: KDE2.2.1+SuSE7.2+xcin
by khchan2＠study.csis.hku.hk 22 Nov '01

22 Nov '01

Thank you Dr. Fabian for your reply. I can now have Chinese websites displayed correctly in Konqueror, but I still have some other Chinese problems unresolved. > > When your X11 session starts xcin should start automatically as > well > and you should see a small, blue window with title 'xcin > 2.5.2.3'. Do > you see this window? > I saw the window. At first I couldn't get it changed to have Chinese input method using Ctrl-Space, but after I specified zh_TW instead of zh_TW.Big5 in ./.xinitrc, xcin works now. I have upgraded to 2.5.2.3 today. However, I find that I cannot logout KDE properly everytime, probably because of xcin. On choosing "logout" the whole KDE freezes and I have to use Ctrl-alt-bksp to get out. > > and changed the country settings in KDE to tw; zh_TW.Big5; Big5 > charset. > > What I get is all garbage (looks like a Chinese webpage > displayed using > > Western codepage), I still get garbage in KDE menus and many KDE applications. But I can see Chinese correctly in Konqueror now. I don't know why, but if I use a font size too small, the garbage appears again. In the user account I am testing chinese I don't use anti-aliasing, because the installed fonts are not true type fonts and they don't appear in my primary account that has anti-aliasing enabled. Chinese characters in KDE applications still show up as ??? or rectangular squares or garbage. For example, in licq the Chinese nicknames are displayed as squares while kword displays the chinese words as ???. Switching to chinese fonts simply doesn't help. Although I still have some problems, at least this is a good beginning. Thank you very much again for your information. That's very useful. If other Chinese problems can as well be solved my SuSE experience would then be perfect.

4 12

Using WenLin2 with WINE
by David Fong 22 Nov '01

22 Nov '01

Dear all, Some readers of this list might like to know that WenLin2 (v 2.5) and WenLin2 demo (http://www.wenlin.com) can work under Wine, but either you need to use an old version of Wine (like Codeweavers 20010305) or you need to patch the current source-code of Wine and re-compile Wine yourself. WenLin2 allows you to 'draw' Chinese characters with your mouse into its text-editor, and then output Big5/GB/Unicode files (alternatively, you can type in Pinyin). The primary purpose of WenLin, however, is as a learning tool. The patch is not yet implemented into Wine mainstream. The 'raw' patch file is below (as discussed on comp.emulators.ms-windows.wine), but it won't work with latest public release of Wine (20011108). However, if you know a little about programming, you can follow the patch instructions yourself. (Basically, a MsgWaitForMultipleObjects command needs to be inserted). Cheerio, David. --- input.c.orig Tue Nov 13 21:30:59 2001 +++ input.c Fri Nov 16 12:26:10 2001 @@ -598,7 +598,9 @@ */ WORD WINAPI GetAsyncKeyState(INT nKey) { - WORD retval = ((AsyncKeyStateTable[nKey] & 0x80) ? 0x0001 : 0) + WORD retval; + MsgWaitForMultipleObjects( 0, NULL, FALSE, 0, QS_ALLINPUT ); + retval = ((AsyncKeyStateTable[nKey] & 0x80) ? 0x0001 : 0) | ((InputKeyStateTable[nKey] & 0x80) ? 0x8000 : 0); AsyncKeyStateTable[nKey] = 0; TRACE_(key)("(%x) -> %x\n", nKey, retval); -- Dr.David.Fong(a)medical.net.au - Ivanhoe, 3079, Australia http://www.users.bigpond.com/vkelim/ SuSE Linux

1 0

Problems compiling libtabe (xcin)
by Heinz-Josef Claes 21 Nov '01

21 Nov '01

Hi, I'm trying to compile xcin under SuSE 7.2 (with 7.3 compiling also does not work) libtabe-0.1.9 xcin-2.5.2.3 When compiling libtabe (after starting ./configure) I get the following error messages: make (cd src; make) make[1]: Entering directory `/home/hjc/a/xcin/libtabe/src' gcc -c -Wall -fsigned-char -O2 -DHAVE_CONFIG_H -o tabe_util.o tabe_util.c gcc -c -Wall -fsigned-char -O2 -DHAVE_CONFIG_H -o tabe_zuyin.o tabe_zuyin.c gcc -c -Wall -fsigned-char -O2 -DHAVE_CONFIG_H -o tabe_yin.o tabe_yin.c gcc -c -Wall -fsigned-char -O2 -DHAVE_CONFIG_H -o tabe_tsi.o tabe_tsi.c gcc -c -Wall -fsigned-char -O2 -DHAVE_CONFIG_H -o tabe_tsidbint.o tabe_tsidbint.c tabe_tsidbint.c: In function `tabeTsiDBOpen': tabe_tsidbint.c:85: warning: implicit declaration of function `db_open' tabe_tsidbint.c: In function `tabeTsiDBRecordNumber': tabe_tsidbint.c:165: structure has no member named `bt_nrecs' tabe_tsidbint.c: In function `tabeTsiDBCursorSet': tabe_tsidbint.c:394: too few arguments to function make[1]: *** [tabe_tsidbint.o] Error 1 make[1]: Leaving directory `/home/hjc/a/xcin/libtabe/src' make: *** [all] Error 2 Does anybody know how to compile it or where to get compiled binaries? best regards, Heinz-Josef Claes

2 1

Problem Resolved
by khchan2＠study.csis.hku.hk 19 Nov '01

19 Nov '01

My earlier problem of character alignment has been resolved by only a click - I disabled Anti-aliasing and all the display problems in Kate and kwrite are resolved. Although Anti-aliasing seems to work on your system, for unknown reasons it doesn't work for me. Perhaps later on I will do more tests and see if there is anything I can come up with. The reason I asked if there are alternate Chinese fonts is that the Arphic fonts installed are very difficult even to identify the characters themselves at small font sizes (around 12). In Windows the default "mingti" font is quite readable at small font sizes, but this is not the case for Arphic. Both Chinese and Latin characters are not that easy to look at. I heard that KDE 3 has better support for i18n and non-Latin characters. Did anyone try the Alpha1 release?

2 1

CJK-latex installation
by ugroh＠t-online.de 19 Nov '01

19 Nov '01

I have installed the cjk-rpm file including the Japanese font files. If I LaTeX all the test-files everything is ok. If I start xdvi on the produced dvi-files strange things happens: mktexpk starts up l ooking for the font (e.g. jsso1210) mktexmf jsso1210 ! I can't find file 'jsso1210' .... a lot of more error messages becuase the font isn't found I went over the doc-files and found the remark, taht one has to patch mktexpk with some script whisch I also found in the system. Q1: Is this really the right way? Q2: How to patch the file ? Thanks. -- Mit freundlichen Gruessen / Best regards Ulrich Groh

2 1

Missing Big5 Font for GNU Emacs
by Friedrich Dimmling 19 Nov '01

19 Nov '01

Im using the GNU Emacs with MULE to write CJK-LaTeX documents on a SuSE 7.3 system. I have installed the Arphic Truetype Fonts and I can successfully display Chinese texts (written on a different system with SuSE 7.2) using Xdvi on the system in question. However in GNU Emacs there are only blank squares where the Chinese characters should be. With GB everything works fine i.e. I can see the characters on the screen. I had the same problem on the SuSE 7.2 system where it was solved by two packages of Chinese Fonts included in the 7.2 distribution but missing in the 7.3 distribution. I could not find the packages on the ftp server too (maybe I just dont know where to look). What is the solution to this problem on 7.3? I'm sticking to the GNU Emacs/MULE system because I had terrible problems in trying to setup xcin (Twice I had to reinstall Linux in the end before I gave up). Unfortunately I cannot spend time on trying at the moment and GNU Emacs/MULE seems to be OK for my work. I hope it's just a small trick to perform. Friedrich

2 1