Re: Some mule-unicode-* characters are incorrectly displayed with fontset-mac

[Kenichi Handa]

YAMAMOTO Mitsuharu <address@hidden> writes:
> In Carbon Emacs on Mac OS X, some characters within character sets
> mule-unicode-* are incorrectly displayed as ASCII characters if we use
> a predefined fontset "fontset-mac".  The problem can be reproduced by

>     M-x set-frame-font RET fontset-mac RET
>     M-x list-charset-chars RET mule-unicode-0100-24ff RET

Thank you for the report.

> The problem can be fixed by changing the definition of the fontset in
> lisp/term/mac-win.el in either of the following ways:

> 1. exclude the case that the entry in the char-table has the value
>    `nil'.
[...]
> 2. use the char-table for decoding instead of that for encoding.

I think 2. is a better fix because it's a little bit faster.
I've just installed it.

> As for the fix 1 above, a similar problem can be found in
> `optimize-char-coding-system-table' in lisp/international/mule.el.

Yes.  I've also changed it along your suggestion.

> As far as I know, most of the uses of `char-map-table' essentially
> operate only on entries having non-nil (or non-default?) values.  How
> about adding some option to control the behavior of `char-map-table'
> so that we can reduce the overhead of needless function calls?

Even if we add that option, without modifying the codes that
use char-map-table, there's no effect.  And, if we are going
to modify them, we can modify them as (if val ...).  So, I'm
negative to that change.

---
Ken'ichi HANDA
address@hidden