October 2005 - openSUSE M17n - openSUSE Mailing Lists

No compose characters possible with asian language setting
by akimbo337＠gmx.de 16 Nov '09

16 Nov '09

Hello! I'm currently using SuSE 9.0 pro for both german and japanese input. This works fine so far, by setting the variables LC_CTYPE to ja_JP.UTF-8 and LANG to de_DE.UTF-8, but nevertheless I experienced a problem: With the LC_CTYPE set to japanese and an input method running (currently kinput2), I cannot type european language compose characters any more - at least the ones I used to produce with two sequent keystrokes ( ´ and e for é for example). The rest of my (german) keyboard layout works all fine, and with LC_CTYPE set to german, é's, à's, ô's, etc pose no problem, but then, of course, I cannot input japanese... This problem seems also to be existent for other language settings that use an input method, I tried it out with a friend who uses chinese input (also on SuSE 9.0 pro). We (my friend and I) are currently writing an article about asian language input with StarOffice/OOo, so we would really appreciate any help or hint concerning this problem. Thanks. Marcel Boeing

5 6

jfbterm related issue (CJK not showing)
by ahmad hassan 29 Oct '05

29 Oct '05

Hi, I am trying to have CJK support in a mini linux distro i made which contains linux kernel (2.6.11 with FB support) + busybox(ash shell available) + file system + an ncurses application. I would like to add a CJK terminal emulator which is small and has good support for CJK and i would like to build it statically(no so's to be used) I have done googling and i have come to conclustion that jfbterm is a good terminal emulator but how do i compile this statically because when i install it on my SUSE linux(its available as rpm in it), it has 4-5 dependencies. Also compiling it with source gives issues with the make process and it doesn't compile correctly. Also if i am succesfull in compiling it successfully what else do i require to put on the mini linux distro of mine and how i put it. I have tried jfbterm on SUSE LINUX 9.1 but it doesn't show correctly even the README file mentioned there with the less command. http://www.suse.de/~mfabian/suse-cjk/jfbterm.html I have set the environment variable FRAMEBUFFER to /dev/fb1 also. If i change the locale to EUC then it displays the japanese characters right on the console(konsole, xterm) without even running jfbterm. Any help would be greatly appreciated in this matter. Thank you. _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

Changing hot keys for SCIM
by Christopher Fynn 20 Oct '05

20 Oct '05

How do I change the Hot-Keys for SCIM? The standard Bhutanese (dz_BT) keyboard uses shift-spacebar to insert a space character and plain (un-shifted) spacebar to insert character 0F0B (which is used like an inter word space in Dzongkha). However sometimes Dzongkha users need to insert a space with shift-spacebar but if SCIM is running it grabs that key combination. - Chris

2 1

ghostscript and LyX-CJK
by hisha 19 Oct '05

19 Oct '05

Dear list, I just installed SUSE9.3, japanese version, in Unicode. Basically everything works, except two snags: 1) lyx-cjk-1.3.5-3 does not allow for kanji input in the main window. I tried this after starting kinput2 -canna& LANG=ja_JP LC_XMODIFIERS="@im=kinput2" lyx-cjk I can see japanese text, e.g. the splash.lyx file. I can input Japanese if I open the "find" dialog, or in the lower bar, the minibuffer, and even copy and paste the result into the main window, but NOT enter Japanese directly. This worked still fine with SUSE 9.1. 2) Next, ghostview. I took an example file, like http://www.suse.de/~mfabian/suse-cjk/vertical-orizontal-test.ps I verified that I can open this in my old SUSE8.2 and see all characters correctly. Next, I open it with gs as normal user in 9.3, from bash. The result are Mojibake and the messages: --- gs vertical-horizontal-test.ps ESP Ghostscript 8.15 (2004-09-22) Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Scanning /usr/X11R6/lib/X11/fonts/ for fonts... 12 files, 12 scanned, 0 new fonts. Scanning /usr/share/fonts/ for fonts... 2 files, 2 scanned, 0 new fonts. Can't find (or can't open) font file /home/hisha/Resource/Font/Ryumin-Light-UniJIS-UTF8-V. Can't find (or can't open) font file Ryumin-Light-UniJIS-UTF8-V. Querying operating system for font files... Didn't find this font on the system! Substituting font Courier for Ryumin-Light-UniJIS-UTF8-V. Loading NimbusMonL-Regu font from /usr/share/ghostscript/fonts/n022003l.pfb... 2395532 1032646 1474788 180942 1 done. Can't find (or can't open) font file /home/hisha/Resource/Font/Ryumin-Light-UniJIS-UTF8-H. Can't find (or can't open) font file Ryumin-Light-UniJIS-UTF8-H. Didn't find this font on the system! Substituting font Courier for Ryumin-Light-UniJIS-UTF8-H. >>showpage, press <return> to continue<< --- Then I switched to root (su -) and there I CAN open the file, without a hitch. The messages are in this case --- ESP Ghostscript 8.15 (2004-09-22) Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Scanning /usr/X11R6/lib/X11/fonts/ for fonts... 12 files, 12 scanned, 0 new fonts. Scanning /usr/share/fonts/ for fonts... 2 files, 2 scanned, 0 new fonts. Loading a TT font from /usr/X11R6/lib/X11/fonts/truetype/ipam.ttf to emulate a CID font Ryumin-Light ... Done. >>showpage, press <return> to continue<< --- These two things happend just afer I installed the system, so I did not change the standard configuration. Now, because I did not find any hint in the suse-cjk guide, does anybody have an idea of what might be going wrong? Hisha __________________________________ Save the earth http://pr.mail.yahoo.co.jp/ondanka/

2 10

Fwd: culmus font package available for SuSE Linux 10.0
by h.w.meester＠umail.leidenuniv.nl 05 Oct '05

05 Oct '05

(I subscribed again, and this mail originally sent by Mike to me I now send to the list. My old e-mail address will no longer be in use.) Van: Mike FABIAN [mailto:mfabian@suse.de] Verzonden: wo 5-10-2005 13:56 Aan: hermanmeester CC: Onderwerp: Re: culmus font package available for SuSE Linux 10.0 > Answering yor question: I'm missing, or haven't found yet, a way to > type Greek accents (most important, the aspiration sign) and the > "iota-subscriptum" beneath the Greek omega and �ta. I think Greek > might need a feature similar to M17N-t-latn-pre, for example. I > guess Linux users from Greece may already use this. (In fact, I'm > only processing some crazy apocalyptic Greek writings from 200 BCE, > when they didn't even invent those accents yet. But some academics > are so perfectionistic, they criticised my unaccented typing.) Please have a look at the file /usr/share/m17n/el-kbd.mim I guess it is very easy to add the things you want to that file. I this file you find a table like this (shortened): (map (map ("q" ?\;) ("w" ??) [...] ("N" ??) ("M" ??) (";a" ??) (";e" ??) [...] (":;y" ??))) This means if you type a 'q' you will get a ';' inserted (the '\' is needed as a quoting character because ';' would otherwise start a comment in lisp). If you type 'w' a '?' will be inserted. Typing sequences of more than one character are also possible, i.e. if you type ';a' a '?' will be inserted, if you type ':;y' a '?' will be inserted. This table can be easily extended to support additional key-sequences. If you think you have suggestions how to extend that table which are of general interest, please edit this file an send a diff to the developer of m17n-lib (this is Kenichi Handa <handa(a)m17n.org>, there is also a mailing list, see http://www.m17n.org/m17n-lib/) If you want some input key-sequences which are very personal and maybe only interesting for you, you can easily create your own input method. Create a directory ~/.m17n copy a m17n input method file which is already a bit similar to what you want into that directory: cp /usr/share/m17n/el-kbd.mim ~/.m17n/herman.mim Edit this file, change title (title "?") -> (title "herman") edit the table as you like. Create a file called "mdb.dir" in the ~/.m17n directory. Put the following line into that file: (input-method t herman "herman.mim") This file is an index of input methods in the directory ~/.m17n. For each input method you add you need such a line. Now add export M17NDIR=$HOME/.m17n to your ~/.profile or ~/.bashrc. This variable tells the m17n library to look for additional input methods in ~/.m17n. Now restart your X session. Activate SCIM and your new input method called "herman" should show up under "other" in the SCIM input method menu. > As for Hebrew, I would love SCIM to enable vocals typing below, > inside and above the Hebrew characters, but this may well be > something I have to produce myself, because even the Israeli's I > asked didn't know this for OpenSource yet. I've been taking a look > at this with a university teacher in Leiden, who designed his own > fonts occasionally. I'll first need some time to convert him to > Linux, however ;) With the above explanation, maybe you can add this feature to the m17n-lib yourself and send the result to the Mr. Kenichi Handa or the m17n-lib mailing list. > By the way Mike, I met a student of Japanese in Leiden, he was > interested in Linux, but he said he could type anything he needed in > Japanese using MSWindows, and didn't want to "change a winning > team". Is there anything about SCIM or UIM or other methods in the > field of Japanese typing that beats the Windows input method? (to > "draw him over the line"?) I guess there must be, but I don't know > any Japanese, nor did I use Windows for a few years. The Japanese input method in windows is quite intelligent. The Japanese input methods available as free software on Linux are currently less intelligent, i.e. the user has to think more while typing and do more manual corrections. Japanese input is usually done by typing the phonetics in Latin alphabet. The input method converts this to Japanese characters. The main problem is, the this conversion is *not* unique. This is very different from something like M17N-t-latn-pre where '"u' is always converted to '�'. In Japanese, there are almost always many possibilities how to convert. Intelligent input methods manage to choose the right conversion from the context most of the time. Less intelligent input methods often get it wrong when converting and the user has to correct manually. For me this is not a big problem, the free input method I am currently using for Japanese (scim-anthy) gets it right maybe 95% of the time if I hit the conversion key at the right moments. One has to get a feeling where in a sentence it is good to hit the conversion key. If one has developed this feeling for an input method like scim-anthy, it also works quite well. But windows users are not used to that. They often type very long sentences without pausing and then hit the conversion key and expect that everything is converted correctly. Even with the best intelligent input methods this doesn't always work. But the commercial input methods can handle this typing style much better than the free input methods. Commercial input methods are available for Linux as well but have to be bought separately. And they are quite expensive. With the Japanese version of SuSE Linux 9.1, the commercial input method "ATOK X" was bundled. With the Japanese version of SuSE Linux 9.2 and 9.3, the commercial input method "Wnn 7" was bundled. For SuSE Linux 10.0, Novell Japan did choose not to bundle any commercial input method any more to cut costs. I.e. if a user wants to use "ATOK X" or "Wnn" on SuSE Linux 10.0, he has to by it directly from the vendors. I think that scim-anthy is really usable, it works reasonably well if the user knows the best places where to hit the conversion key. But as this is different from Windows, the user has to get used to that. > I do know that the SCIM menu, for KDE, looks a lot better than the > MSWind. input method, which looks as if it was created in the '80s. Mike, thanks a lot, that is very helpful, I'll get to work immediately! Regards, Herman -- Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian

1 0