Hi folks, thank you for your answers.... (ok, thanks Mike ;-) Could anyone explain me WHY I have to save my file in EUC-JP encoding although the preamble of the CJK-environment says \begin{CJK}{JIS}{komi} ?? ***** I would like to write \begin{CJK}{EUC}{komi} or something like that. I don't understand the whole stuff by encoding.... ;-( For Mike.... On Wed, 12 Feb 2003, Mike FABIAN wrote:
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? Yes, I do. GNU Emacs...
Does the Japanese in the hello page look correct to you in GNU Emacs? Yes, it does. All fonts are installed correctly..
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
Nice hint...
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 ...) I know that SKK is included in XEmacs. But my XEmacs doesn't start: ludger@garfunkel:~/tex/japanese/examples> xemacs Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-gnu-unifont-medium-r-normal--16-160-75-75-p-80-iso10646-1,-*-*-medium-r-normal--16-*-*-*-c-*-*-*" to type FontSet Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset
Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes@xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/X11R6/bin/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: # bind (frame-being-created) make-frame(nil #<x-device on "localhost:10.0" 0x2672>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â" ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Speicherzugriffsfehler ludger@garfunkel:~/tex/japanese/examples> So I tried it with GNU Emacs....
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. Ok, I don't want to learn a new input method. But are there any short and readable introduction to use Canna. Also I want to have an input method that doesn't use any server. Like SKK where the dict is read in in a buffer....
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: Ok, I did it and it worked... But why?? (see my question above...)
/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.
Ok, but why? In my opinion it should be \begin{CJK}{EUC}{komi}!!!!! ***** Why this confusion?
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. You are right.
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 As I wrote I don't use the GNU Emacs provided by SuSE 8.1. So I cant refer to that....
The XEmacs package on SuSE Linux 8.1 already includes Mule-UCS, but see above. My XEmacs doesn't start....
Thank you, Mike for your answers... Best regards, Ludger