February 2003 - openSUSE M17n - openSUSE Mailing Lists

CJK-LaTeX using a CJK-environment in \part{}
by Ludger Sicking 15 Feb '03

15 Feb '03

Hi folks, again some questions....? (Why do we live? What are we? Where do we go?.....) I want to use a CJK-environment in a \part{} command, so I wrote: \part{Beweistheorie \`a la Gentzen, % \begin{CJK*}[dnp]{JIS}{min}% <some kanji>\ (Takeuti) und <some kanji>\ (Arai) % \end{CJK*} % --- Die Theorie $\Tpa$% } After saving at is euc-jp I latexed the file and the output was [52] ! Use of \@part doesn't match its definition. <argument> \def \reserved@a { \def \@currenvir {CJK*}\edef \@currenvline {\on... l.6092 } ? Any ideas?? When I wrote \begin{CJK*}[dnp]{JIS}{min} \part{Beweistheorie \`a la Gentzen, ...} \end{CJK*} the problem is that the kanjis don't arise in the table of contents. Have I to use an extra package? Does CJK provide such tricky movements of arguments or should I have to edit the <filename>.toc by myself?? Thank you for your help. Best regards, Ludger

4 10

Qustion on settings
by ugroh＠t-online.de 15 Feb '03

15 Feb '03

Mike, in one of your answers to the "Encoding" problem of Ludger you wrote: " .... I run my computers in ja_JP.UTF-8 locale, it nice to be able to view Files containing Japanese and German Umlauts simply with less in a terminal like mlterm or xiterm and have everything display correctly. ... " Can you tell me where to set this? It would help me too, e.g. writing mails to Japan would make live easier. Thanks -- Mit freundlichen Gruessen / Best regards Ulrich Groh 碁朗潤利

2 1

Internatinal Language Support of SuSE (Pathetic)
by ghugh Song 15 Feb '03

15 Feb '03

Hi, It is my impression that just a few people are interested in internationalization of Linux such as Mike Fabian and Jeongshik Shin. One evidence is that every SuSE distribution has had the file /usr/X11R6/lib/X11/locale/ko/Compose. It should be removed. Otherwise ami (the Korean language input method ) gives no effect. Yet, on every version of SuSE, I had to hand-remove this file. Even funny is that inside this file, there is a warning message against tampering. What is going on? I considered the above instance as the pathetic reality of the internationalization effort which is going on inside SuSE. Frustration does not stop here. I will mention just two very frustrating cases: ****Printing ******** I have wished printing Korean characters directly without doing special from mozilla for a very very looooong time. It never happened in all the SuSE distributions up to 8.1. There were promises. Well, they were promises only. All those howto file made by local gurus turned out to be not woking due to distribution changes. They are pretty much focused on RedHat distributions. ****Evolution********* A nice software called Evolutin by Ximian is suppoesed to work with Asian languages (such as Korean in my case.) However, when I grab the executable (Evolution-1.2.2) and try to run it. Something funny is going on. I can type in Korean characters and they show up nicely as I type Korean characters That means the fonts are there and are working properly. However, as soon as I type <space>, the well-viewed Korean characters suddenly change into an <underscoe>, and nothing shows up. The Evolution-1.0.2 provided by SUSE 8.1 does not have this problem. However, such an old version does not support evolution-pilot program which is the whole point of using evolution. +++++++++++++++++++++++++++++++++++++++++++++++++++++ Admittedly, everything is not controlled by SuSE. I can see that gtk-2.2 or something must have a bug. Now, it is by now evident that many things do not work as they supposed to. However not many people really are concerned with it. Only Mike and Jeongshik Shin. All the rest do not seem to care. They might try it, however after finding that it does not work for them, they give up on Linux and continue using Microsoft Windows. That is the pattern I have been finding all years. It did not change. Regards to all. -- ghugh Song <ghugh(a)bellini.mit.edu> MIT PS: Did I mention that I still will appreciate any solutions to the two above-mentioned problems? Please help.

3 16

Re: [m17n] Japanese, CJK and LaTeX
by Mike FABIAN 14 Feb '03

14 Feb '03

Ludger Sicking <ludgerp(a)uni-muenster.de> さんは書きました: > I mention it's "only" an encoding problem. > I want to use the "Wadalab-test.tex"-file as a base. > So I opened it in my emacs. My emacs couldnt't fontify the kanjis > well. In spite of kanjis "he" displayed: > > [... mojibake ...] That's EUC-JP encoded Japanese. Although your e-mail header doesn't say so. I wonder why your Emacs doesn't display it correctly. Both GNU Emacs and XEmacs display Wadalab-test.tex correctly for me by default. You use GNU Emacs, do you? Does the Japanese in the hello page look correct to you in GNU Emacs? Try M-x view-hello-file If that doesn't look right, you probably lack the most basic Japanese fonts. Is xfntjp.rpm installed? You can switch fontsets in Emacs with "Shift+Left-mouse-button", then select "Fontset" and select one of the offered fontsets. the "standard: 16-dot medium" fontset should always work, even if your only Japanese fonts are those already included in the xf86.rpm. What the locale you are using? You can force to load a file in a specific encoding, e.g. EUC-JP with the following key combination: C-x RET c euc-jp RET C-x C-f Wadalab-test.tex RET > I input my kanji by SKK. (I didn't find an SKK package on SuSE 8.1, so I > installed it by the SKK web page.... Is there such a package provided by > SuSE???) SKK is included in the XEmacs packages for SuSE Linux. I didn't yet make a SKK package to use with GNU Emacs for SuSE Linux (You are the first one who asks ...) Personally I use XEmacs with the native Canna interface to input Japanese, for GNU Emacs there is the tamago.rpm package which offers a nice, direct interface to Canna. I think using Canna is easier than SKK, but the choice of the input method really is a personal preference. > And I saved the file in ISO-2022-JP-2. Don't do that. Save it as euc-jp. If you want to use the Wadalab PostScript fonts, you *must* save it as EUC-JP. In the Wadalab-test.tex file you have for example: \begin{CJK*}[dnp]{JIS}{min} And the documentation /usr/share/doc/packages/cjk-latex/doc/CJK.doc clearly says: CJK.doc> \begin{CJK*}[<fontencoding>]{<encoding>}{<family>} CJK.doc> ... CJK.doc> \end{CJK*} CJK.doc> CJK.doc> are defined. The parameters have the following meaning: CJK.doc> CJK.doc> <encoding> These character sets resp. encodings are currently CJK.doc> implemented in CJK.enc: CJK.doc> CJK.doc> [...] CJK.doc> JIS (For Japanese. CJK.doc> Character set: JIS X 0208:1997. CJK.doc> Encoding: EUC.) You see, you *must* use EUC-JP encoding, if you use the {JIS} parameter in the \begin{CJK*} command. > I processed it with latex (and sjislatex) Forget sjislatex unless you use SJIS. > but there was the following message: > the latex command: > ! Text line contains an invalid character. > l.20 light: {\fontseries{l}\selectfont ^^[ > $BC]Fb^^[(B}\ normal: > ^^[$BC]Fb^^[... [...] > So there is a problem with the encoding.... Yes. You get funny error messages like that when you don't use the correct encoding. Use EUC-JP together with \begin{CJK*}[dnp]{JIS}{min} and all is well. > > BTW: the latex command on the example files worked well. The output was fine > and I can see the kanjis. But I don't want to present a "hello world" as my > titlepage for my diploma thesis... ;-) > > I didnt find an encoding like UTF8 for my emacs... (ok, it's my fault. it's > of course not the emacs given by SuSE 8.1... it has that encoding > possibility....) If you use the GNU emacs on SuSE 8.1, it already has the coding system utf-8, but only for a very limited subset of Unicode. This does not cover Japanese. To be able to use Japanese as well in UTF-8, you need to install the Mule-UCS.rpm package, which is an extension for GNU Emacs for better Unicode coverage. The XEmacs package on SuSE Linux 8.1 already includes Mule-UCS, but you may need to activate it in your XEmacs profile (which is ~/.xemacs/init.el). Add the following line: (if (locate-library "un-define") (require 'un-define)) If you use the default ~/.xemacs/init.el file as distributed with SuSE Linux 8.1, you already have that. -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

3 6

CJK Filenames and Linux File System
by Jethro Cramp 14 Feb '03

14 Feb '03

I'm about to setup a samba filesever using SuSE 8.1 and reiserfs for one of my offices in China. The clients will be mainly Simplified Chinese Windows 2000. Are there any gotchas that I should look out for with respect to filenames in Chinese? Thanks in advance, Jethro Cramp -------------------------------------------------------

2 1

Re: [m17n] CJK Filenames and Linux File System
by Jethro Cramp 14 Feb '03

14 Feb '03

> > Are there any gotchas that I should look out for with respect to > > filenames in > > Chinese? > > http://www.suse.de/~mfabian/suse-cjk/mounting-vfat.html > > Largely works for me as a Chinese user. Thanks, I see the solution you are suggesting is not to use reiserfs but instead use vfat partitions. Anyway on comments on using reiserfs or ext3? Thanks in advance, Jethro

1 0

Setting up CJK Latex for UTF8
by bruce_np 13 Feb '03

13 Feb '03

Hello m17n, I have the CJK package installed, and it works fine with emacs. But now I wanted to use the UTF8 encoding, because it is more readable then the files emacs produce. But I cant get it running. I tried all the UTF8 examples from CJK and always the same result: font T1/song/m/n/10/cyberb00 at 12.0pts (or any other font) not loadable: Metric tfm file not found I worked with kile as latex editor (dont think that is the problem ;) Any suggestions how I can fix this? -- Best regards, bruce_np mailto:bruce_np@sbox.tugraz.at

2 2

Japanese, CJK and LaTeX
by Ludger Sicking 12 Feb '03

12 Feb '03

Hi folks, I tried to tex some Kanjis, but now I want to get help. My system is SuSE 8.1. I installed all CJK and LaTeX stuff. I think I only have to do "RTFM", but I did it!! How can I test my installation. I didn't find a LaTeX-Kanji-Test-List. I know that there is a lot of documentation, but you can believe me I tried some things. I'm confused about the encoding and such things. When I have to use sjislatex when the normal latex command?? In what encoding should I encode my text? Sjift-Ji, Euc-JP, ISO-2022-JP, emacs-mule ??? Could someone send me a little test file that should work on my PC?? This would be a big help. Of course I want to use outline fonts (TrueType or Postscript). When the example file could contain such commands for these fonts... (I think I have to use the [dnp] option... but what encoding and what fontname have I to use then...?) Special thanks for any answer. Best regards, Ludger

2 1

Entering Japanese input into browsers
by Joe Tomcat 12 Feb '03

12 Feb '03

Hello international Suse users. I am currently trying to test some web sites in Japanese. I need to be able to input Japanese text into fill-in forms. I am using Suse 8.1, US edition. I am having a terrible time finding the software I need to accept the input, and then activating that software to accept input. On my other machine, running Redhat 8.0, with kinput2 and cannad already installed and running, there seems to be no way to tell it to actually use kinput2. There must be some kind of keystroke combination that will do this, right? But it is not documented anywhere. Also, I have heard of something called kterm which is like an xterm but can display Japanese chars, but this seems very hard to find anywhere. Any suggestions would be welcome. Thanks!

2 1

Ami: Korean input server patched for UTF-8
by Mike FABIAN 05 Feb '03

05 Feb '03

Here are new packages for SuSE Linux 8.1 for the Korean input method Ami: ------------------------------------------------------------------- Mon Feb 3 17:28:57 CET 2003 - mfabian(a)suse.de - add utf-8 patch by Jungshik Shin <jshin(a)mailaps.org> (see also http://mail.nl.linux.org/linux-utf8/2002-04/msg00147.html) (includes patch for multiline string issue) This patch makes it possible 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). ------------------------------------------------------------------- ftp://ftp.suse.com/pub/people/mfabian/8.1-i586/ami-1.0.11-62.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.1-i586/amidic-1.0.11-62.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.1-i586/amignome-1.0.11-62.i586.rpm ftp://ftp.suse.com/pub/people/mfabian/8.1-src/ami-1.0.11-62.src.rpm To test these, start Ami in ko_KR.UTF-8 locale: LC_ALL=ko_KR.UTF-8 ami export XMODIFIERS="@im=Ami" and then start an application which supports XIM (e.g. mlterm or xiterm) using Ami: XMODIFIERS="@im=Ami" LC_ALL=ko_KR.UTF-8 mlterm Only if *both* ami *and* the client (e.g. mlterm) are running in ko_KR.UTF-8 locale, you can enter the additional characters like e.g. U+AC02. If either ami or the client are running in ko_KR (= ko_KR.eucKR) locale, you can only enter characters from the KS X 1001 repertoire. Of course it was already possible on SuSE Linux 8.1 to start clients in ko_KR.UTF-8 locale, contact the ami which was started in ko_KR locale and input Korean into the client, but in this case you were also limited to characters from the KS X 1001 repertoire. The ami from the package included in SuSE Linux 8.1 cannot run in ko_KR.UTF-8 locale, this just doesn't work, it was necessary to start it in ko_KR locale. Therefore you need the updated package if you want to input Korean characters outside of the KS X 1001 repertoire. Thanks to Jungshik Shin <jshin(a)mailaps.org> for the patch. It would be nice if somebody could test the updated packages and give me feedback, if nobody complains I would like to include the above updated packages in SuSE Linux 8.2. -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

1 0