Re: [PATCH] Unicode Lisp reader escapes

[Richard Stallman <rms@gnu.org>]

      In addition, the default value of
    utf-translate-cjk-mode t, and to which CJK charsets Han
    characters of Unicode are decoded depends on these:

    (1) current-language-environment

What effect does this have?  (Aside from the choice of coding system,
that is.)

    (4) the contents of the hash table ucs-unicode-to-mule-cjk
    (a user can freely reflect one's preference on how to decode
    Unicode character by modifying this hash table).

Could you tell me some examples for how users are really expected
to use this?

Overall:

With so many different variables that might affect the reading of
these characters, it is just too inconvenient for every file to
specify them all.  So I think we need a new feature to make that easy
to do.

Here's one idea.

Add a new "variable" `buffer-coding' which is analogous to `coding'.
Whereas `coding' specifies the encoding in the file, `buffer-coding'
specifies the in-buffer encoding to produce in the buffer.  Its value
could be a list or plist, which would specify the values of all these
many variables.

What do you think?  If you think this is a good idea, could
you try designing the details?