Re: More Cyrillic vs UTF-8

[Simon Josefsson <jas@extundo.com>]

Richard Stallman <rms@gnu.org> writes:

>     Could we add that information to the PROBLEMS file?
>
>     --- PROBLEMS.~1.147.~	Tue Feb  4 16:44:10 2003
>     +++ PROBLEMS	Sat Apr 26 02:26:21 2003
>     @@ -27,6 +27,11 @@
>      mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
>      mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
>
>     +* Some Unicode characters are not supported.
>     +
>     +Emacs currently only supports the parts of the BMP whose codepoints
>     +are in the ranges 0000-33ff and e000-ffff.
>     +
>
> Mentioning this in PROBLEMS seems like a good idea to me, but a useful
> entry needs to be stated in terms of what behavior the user sees.
> This text doesn't explain the practical consequences; a user would say
> "so what does that mean for me?"

Is this better?  This was the behaviour I got when trying to save the
data; I had specified that the coding system for saving should be
utf-8 but when I tried to save the buffer Emacs was unable to encode
the characters and suggested shift_jis (etc) instead.

--- PROBLEMS.~1.147.~	Tue Feb  4 16:44:10 2003
+++ PROBLEMS	Sat Apr 26 16:13:07 2003
@@ -27,6 +27,13 @@
 mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
 mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
 
+* Encoding some characters as Unicode is rejected by Emacs.
+
+Emacs currently only supports the parts of the BMP whose codepoints
+are in the ranges 0000-33ff and e000-ffff.  If you try to save a file
+containing characters with code points outside this range, Emacs will
+suggest other compatible coding systems.
+
 * Problems with file dialogs in Emacs built with Open Motif.
 
 When Emacs 21 is built with Open Motif 2.1, it can happen that the