August 2006 - 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

XIM and SCIM problems on SuSE 10.1
by Ulrike Schmidt 08 Sep '06

08 Sep '06

Hi, I installed SuSE 10.1 and when I start Xemacs I am experiencing the same problems as this poster who got the advice to ask at SuSE: http://www.archivesat.com/XEmacs_Beta_Testers/thread796578.htm > (1) (xintl/error) Can't initialize XIM: XCreateIC failed I also installed scim, but it exits abnormally: > uli@toshi:~> scim > Smart Common Input Method 1.4.4 > > Launching a SCIM process with x11... > Loading socket Config module ... > Creating backend ... > Loading x11 FrontEnd module ... > SCIM has exited abnormally. Any ideas how this can be solved or examined further? Uli

3 11

scim-tomoe: can't input recognized characters! (KDE)
by Philip Amadeo Saeli 01 Sep '06

01 Sep '06

Hi, I'm running stock SL-10.1 patched with all relevant security and recommended patches. The default locale is en_US.UTF-8. I started a konsole in the zh_TW.UTF-8 locale so I could input some Chinese characters. When I attempted to use the "Handwriting recognition" feature of scim (scim-tomoe) to input a charater for which I did not know the reading, I was not able to get the character from the Handwriting pad into the target application (KDE konsole). Clicking on the character did nothing, nor was there anything else I could find to input the character (i.e., there was no right-click menu, it was not copied into the clipboard, etc). Another issue: I was able to close the tomoe window by clicking the tomoe icon on the scim toolbar. However, I've been unable to open it back up again since the scim toolbar disappears whenever the mouse cursor leaves the Chinese konsole. I was able to close the tomoe window because the scim toolbar became visible and remained so after clicking on the selected character in the tomoe window. Also, selecting "Handwriting recognition" in the skim menu did not open the tomoe window once it had been hidden via the scim toolbar. I started the Chinese console thusly: (LC_CTYPE=zh_TW.UTF-8 XMODIFIERS=@im=SCIM konsole) & So, my main questions are: 1. How to get recognized characters from the tomoe window into the application? 2. How to click something on the scim toolbar when it disappears whenever I leave the application window from which it had been started? BTW, I found a web page which had a little info on it (http://www.h4.dion.ne.jp/~apricots/scim-anthy/howto.html) but I could find no other relevant documentation on this topic. Any help would be appreciated! Phil -- Philip Amadeo Saeli SUSE Linux 10.1 psaeli(a)zorodyne.com

2 4

cjk-enabling fop
by PILCH Hartmut 15 Aug '06

15 Aug '06

Hello Mike and everybody, I've been using fop http://xml.apache.org/fop to generate pdf documents from the intermediary xml format fo generated by xml on SuSE Linux 10.1. Unfortunately the fop version installed on SuSE 10.1 fails to render all characters except those in a very limited set, containing not much more than ASCII. Those outside this set are displayed as "#" Looking at the documentation - FOP FAQ: Some characters are ... displayed as "#" http://xmlgraphics.apache.org/fop/faq.html#pdf-characters - FOP Fonts http://xmlgraphics.apache.org/fop/0.20.5/fonts.html This uses a tool called TTFRead which requires some Java libraries. Lacking experience in Java, I haven't checked yet whether these are available on SuSE 10.1 or must be installed manually. In file:///usr/share/doc/packages/fop/examples/fo/advanced/cid-fonts.pdf there is an example from the FOP documentation that claims to show embedded Japanese CID-keyed fonts. However, these are displayed only by acroread, not by xpdf (which otherwise display CJK fonts perfectly on SuSE 10.1). Also, both xpdf and acroread issue warnings that the file is "damaged". Xpdf also says that it is "attempting to reconstruct xref table". Before diving deeply into this and attempting to configure a working unicode-based docbook->fo->pdf production system, I wanted to ask whether anyone has any experience with this or perhaps even some working package for the next SuSE release. -- Hartmut Pilch http://a2e.de/phm

1 0