Gnus development mailing list
 help / color / mirror / Atom feed
From: SL Baur <steve@xemacs.org>
Cc: xemacs-mule@xemacs.org
Subject: Re: MULE primer
Date: 31 Aug 1998 16:02:33 -0700	[thread overview]
Message-ID: <m2af4klppy.fsf@altair.xemacs.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "31 Aug 1998 22:53:44 +0200"

[cc'ed to xemacs-mule]
Lars Magne Ingebrigtsen <larsi@gnus.org> writes in ding@gnus.org:

> What is *the* way to learn about all this MULE stuff?

For detailed technical documentation about charsets, JIS, etc. there's 
the O'Reilly Blowfish book -- Understanding Japanese Information
Processing.  It makes very dry reading except perhaps for Chapter 5 -- 
"Japanese Input" which does give some clues how to make things work.

Unfortunately, unless you can read Japanese there doesn't appear to be 
any documentation.  I learned how to get around by trying things out
and asking questions.  It also helped that I had to build and install
the required extra packages -- I have Canna, Wnn4.2, Wnn6 (courtesy of 
OMRON), SJ3, and Kinput2 (an XIM server that simultaneously can
connect to all of the above backends) installed on my development
machine.  They all work slightly differently, of course. :-P

English documentation for XEmacs is/was being worked on, but the
person who was doing it got as far as a very close draft then dropped
away :-(.

A cheap pocket tourist's dictionary is good enough to get some examples
to type in.

> I have a distinct feeling I must be misunderstanding something basic
> here.  I mean, here's (日本語) some Japanese text, so I must be
> doing something right, but I still don't understand it.

I'm not sure where to begin.  Assuming some basic knowledge of
Japanese ...

For example, the word 日本語 can be represented three different ways.
日本語 is the Kanji form and what you will see in writing.  It can
represented phonetically in hiragana as にほんご.  That's actually
what I see first entering the word in canna (C-\ japanese-canna).
Hiragana is a phonetic alphabet, so what you see is what you type to
get it, in this case `nihongo'.


  parent reply	other threads:[~1998-08-31 23:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-31 20:53 Lars Magne Ingebrigtsen
1998-08-31 21:14 ` Alan Shutko
1998-08-31 21:38 ` Hrvoje Niksic
1998-08-31 22:20 ` Michael Welsh Duggan
1998-09-01  1:10   ` Alan Shutko
1998-09-01  8:22     ` Lars Magne Ingebrigtsen
1998-09-01 16:13       ` Alan Shutko
1998-09-01  8:20   ` Lars Magne Ingebrigtsen
1998-09-01 13:13     ` Michael Welsh Duggan
1998-09-01 14:33       ` William M. Perry
1998-09-01 15:57       ` Lars Magne Ingebrigtsen
1998-09-01 17:43         ` Hallvard B Furuseth
1998-08-31 23:02 ` SL Baur [this message]
1998-09-01  8:46   ` Stephen J. Turnbull
1998-09-01 15:52 ` font suggestions for GNU Emacs? (was Re: MULE primer) John H Palmieri
1998-09-01 19:29   ` John H Palmieri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2af4klppy.fsf@altair.xemacs.org \
    --to=steve@xemacs.org \
    --cc=xemacs-mule@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).