Re: decode-char & utf-8-fragment-on-decoding

[Dave Love]

Kenichi Handa <handa@etl.go.jp> writes:

> Thank you.  It seems to be the right fix.  I'll install it
> soon.   Dave, do you see any problem with that?

Yes, I think it's wrong.  I think the only bug is that the doc string
of `utf-8-fragment-on-decoding' is missing the normal `setting it
directly does not take effect' text for a Custom option with a setter.
It has no effect on how decoding is done, and `decode-char' was meant
to be consistent with how utf-8 decoding actually works.

The translation table is always used -- CCL has no way to access Lisp
variables anyway.  It only matters how it's populated (empty by
default).