December 2003 - openSUSE M17n - openSUSE Mailing Lists

Tamil input method for GTK2 available for SuSE Linux 8.2
by Mike FABIAN 03 Feb '04

03 Feb '04

The Tamil input method modul for GTK2 written by Dinesh Nadarajah which is available from http://groups.yahoo.com/group/tamilinix/files/keyboard/tamil-gtk2im.tar.gz is now also available as an rpm package for SuSE Linux 8.2. You can download the packages from here: ftp://ftp.suse.com/pub/people/mfabian/8.2-i586/tamil-gtk2im-0.20030519-0.i5… ftp://ftp.suse.com/pub/people/mfabian/8.2-src/tamil-gtk2im-0.20030519-0.src… -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

1 1

update: ami-1.2.2 for SuSE Linux 8.2
by Mike FABIAN 22 Jan '04

22 Jan '04

ami-1.2.2 packages for SuSE Linux 8.2 are available here: ftp://ftp.suse.com/pub/people/mfabian/8.2-i586/ami-1.2.2-2.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.2-i586/amidic-1.2.2-2.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.2-i586/amignome-1.2.2-2.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.2-src/ami-1.2.2-2.src.rpm Ami 1.2.2 has better support for UTF-8 than Ami 1.0.11. To be able to to enter Hangul syllables which are included in Unicode but are not included in KS X 1001 repertoire (For example U+AC02. U+AC02 can be typed as the keysequence 'r', 'k', 'R' on a qwerty KBD) you need to run both ami and the XIM client with LC_CTYPE="ko_KR.UTF-8". The ~/.xim file from /etc/skel/.xim as distributed with SuSE Linux 8.2 always starts ami in ko_KR.eucKR locale like this: ko*) # Korean if type -p ami > /dev/null 2>&1 ; then export XMODIFIERS="@im=Ami" case $WINDOWMANAGER in *kde|*windowmaker|*wmaker) LANG=ko_KR LC_ALL=ko_KR ami -wm -wait & ;; *) LANG=ko_KR LC_ALL=ko_KR ami & ;; esac fi ;; To get the improvement when running in ko_KR.UTF-8 locale automatically, the setting of LANG and LC_ALL on the command lines which start ami should be removed, i.e. the above snippet should look like: ko*) # Korean if type -p ami > /dev/null 2>&1 ; then export XMODIFIERS="@im=Ami" case $WINDOWMANAGER in *kde|*windowmaker|*wmaker) ami -wm -wait & ;; *) ami & ;; esac fi ;; You can also use the "xim" file from http://www.suse.de/~mfabian/misc/xim and copy it to ~/.xim in your home directory. -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

1 1

update: yudit 2.7 packages available for SuSE Linux 8.1 and 8.0
by Mike FABIAN 15 Jan '04

15 Jan '04

Updated yudit packages are available for SuSE Linux 8.0: ftp://ftp.suse.com/pub/people/mfabian/8.1-i586/yudit-2.7-0.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.1-src/yudit-2.7-0.src.rpm ftp://ftp.suse.com/pub/people/mfabian/8.0-i386/yudit-2.7-0.i386.rpm ftp://ftp.suse.com/pub/people/mfabian/8.0-src/yudit-2.7-0.src.rpm >From the NEWS file of yudit: NEWS> Changes since version 2.6.4: NEWS> --------------------------- NEWS> NEWS> o Added full Unicode compliant bidirectional text support NEWS> o Added fallback to root xinput style if no suitable style is found NEWS> o Received and added Polish gui translations, Persian.kmap, Sanskrit.kmap NEWS> Inuktitut-ICI.kmap, Inuktitut-KBD.kmap, Chinese-Pinyin.kmap, NEWS> Chinese-WB.kmap, ArmenianEastPhon.kmap NEWS> o Speed Optimizations NEWS> o OpenType GPOS support for composing characters NEWS> o Better TAB control NEWS> NEWS> Other Notes: NEWS> ----------- NEWS> Even if you can not read bidirectional scripts, it will be NEWS> useful to type this in the editor command area: NEWS> NEWS> howto bidi NEWS> NEWS> to get some ideas what bidi is, and how it works in Yudit. NEWS> Even if you can not read RL scripts, RL words will be indicated NEWS> in yellow (the default RL color). >From yudit's home page at http://www.yudit.org: > Yudit is a unicode text editor for the X Window System. She can do > True Type font rendering, printing, transliterated keyboard input and > handwriting recognition with no dependencies on external engines. Her > conversion utilities can convert text between various encodings. > Keyboard input maps can also act like text converters. There is no > need for a pre-installed multi-lingual environment. Menus are > translated into many languages. -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

1 4

file names in russian?
by sden 29 Dec '03

29 Dec '03

Hello everyone, The problem is: I have SuSE Linux 9.0 Professional and Windows 98 (Russian edition) on the same computer. I can mount windows partitions without any problems, but if folder/file name in this partition is in russian I can see only ??????. In /etc/fstab I wrote parameters like iocharset=cp1251 and codepage=866, but nothing have been changed (it works fine in ASP Linux - russian distribution based on Red Hat). I can print text in russian in the editor etc. How can I handle this problem? Thank you for help! -- Best regards, Denys Slipetskyy mailto:sden@land.ru

2 1

Jpilot problems
by Alex Khroustalev 10 Dec '03

10 Dec '03

Hi. I use russian koi8-r encoding in SuSE 9.0. 1) In jpilot (gtk2 app) the cyrillic symbols are displayed incorrectly (seems like utf8 representation of koi8-r). There is the following output when the program starts: ** (jpilot:3837): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() Any ideas?

1 0

[Resend: Bad From: addr] Chinese pinyin phonetics input [OpenOffice]:
by Philip Amadeo Saeli 10 Dec '03

10 Dec '03

[Wups! This is a resend. The previous version of this message was sent from a mailer that was not correctly configured and so put in an erroneous "From: " address. Please use return address in my signature.] What is the standard practice for inputting Chinese pinyin (not bopomofo!) phonetics into a document? I'm writing a document where I'd like to include, for each sentence: 1. Chinese characters 2. pinyin transcription of the Chinese characters 3. English translation I am having little problem with the Chinese character input. The problem is including the tone marks required by the pinyin transcription. I've tried wierd latin vowels, but have not been able to find a complete set necessary. I've been using "Insert -> Special Character" in OpenOffice. Also, wheneven I set the XMODIFIERS to other than "@im=local", the compose key stops working, so I am forced to use cut-n-paste to input any non-English chars. How can I get the compose key to work together with a Chinese input method? I'm running SuSE Linux 8.2, KDE 3.1.2 from SuSE, OpenOffice.org 1.0.2 and SCIM 0.8.2 from http://ns.turbolinux.com.cn/~suzhe/scim/. I run my basic system in the en_US.UTF-8 locale, changing LC_CTYPE to zh_CN.UTF-8 for my Chinese work. BTW, I also have xcin running for my work with Traditional Chinese characters, though I'm not using it for this project. I start them both up (xcin and SCIM) when starting up the X Window System. Any help would be appreciated. I have a class project due soon and am tearing my hair out trying to figure out how to do this!!! Thanks, Phil -- Philip Amadeo Saeli SuSE Linux 8.2 psaeli(a)zorodyne.com

3 15

Chinese pinyin phonetics input [OpenOffice]
by Philip Amadeo Saeli 07 Dec '03

07 Dec '03

What is the standard practice for inputting Chinese pinyin (not bopomofo!) phonetics into a document? I'm writing a document where I'd like to include, for each sentence: 1. Chinese characters 2. pinyin transcription of the Chinese characters 3. English translation I am having little problem with the Chinese character input. The problem is including the tone marks required by the pinyin transcription. I've tried wierd latin vowels, but have not been able to find a complete set necessary. I've been using "Insert -> Special Character" in OpenOffice. Also, wheneven I set the XMODIFIERS to other than "@im=local", the compose key stops working, so I am forced to use cut-n-paste to input any non-English chars. How can I get the compose key to work together with a Chinese input method? I'm running SuSE Linux 8.2, KDE 3.1.2 from SuSE, OpenOffice.org 1.0.2 and SCIM 0.8.2 from http://ns.turbolinux.com.cn/~suzhe/scim/. I run my basic system in the en_US.UTF-8 locale, changing LC_CTYPE to zh_CN.UTF-8 for my Chinese work. BTW, I also have xcin running for my work with Traditional Chinese characters, though I'm not using it for this project. I start them both up (xcin and SCIM) when starting up the X Window System. Any help would be appreciated. I have a class project due soon and am tearing my hair out trying to figure out how to do this!!! Thanks, Phil -- Philip Amadeo Saeli SuSE Linux 8.2 psaeli(a)zorodyne.com

1 0