Re: Mule-UCS 0.84 (KOUGETSUDAI) release.

[Dave Love <d.love@xxxxxxxx>]

Tatsuya Kinoshita <tats@xxxxxxxxxx> writes:

> (But I avoided the `lao' feature because it doesn't work on my
> system.  I put comment marks, ";;;xxx".)

How does it fail?

Some more comments:

I don't know whether Kawabata-san is reading this, but he said there
were a number of problems with the jisx0213 translations and sent a
detailed analysis of some other proposed translation tables.  I guess
I could pass that on if anyone is interested.  I think Handa-san
didn't have time to check it.

I noted this in the code for the composition feature I added to Emacs
21 utf-8.el.  I'd be interested if anyone could tell me what the
problem is.

  ;; Fixme: Takahashi-san implies it may not work this easily.  I
  ;; asked why but didn't get a reply. -- fx

If the package is being updated, I think it should use the Emacs 21
technique for preserving untranslatable sequences as `raw bytes'
rather than losing data.  (See utf-8.el, preferably the version from
Emacs CVS).  I don't know if that can be made to work in Emacs 20, but
there are good reasons for updating to Emacs 21 anyhow.

The changes in utf.el (utf-8-ccl-decode) from Debian should be
credited to Toby Speight <streapadair@xxxxxxx>.  It's unfortunate that
Debian changelogs don't record the authors of such patches.

I think the instructions in README.Unicode for selecting fonts are
inaccurate -- x-charset-registry isn't used in Emacs 21.