unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Fwd: Problem with non-bmp unicode
Date: Sun, 12 Nov 2006 11:32:58 +0900	[thread overview]
Message-ID: <E1Gj59W-0003x7-00@etlken> (raw)
In-Reply-To: <200611101127.47456.jerome@marant.org> (message from Jérôme	Marant on Fri, 10 Nov 2006 11:27:47 +0100)

In article <200611101127.47456.jerome@marant.org>, Jérôme Marant <jerome@marant.org> writes:

> Do you have any clue about this?

Sorry for the late reponse on this thread.

> Subject: Problem with non-bmp unicode
> Date: mercredi 08 novembre 2006 09:26
[...]
> An UTF-8 file (attached) with these three characters:
> U+0022 U+00010380 U+0022
> shows with "emacs -nw":
> "\360\220\216\200"
> which is not usable at all. The file displays correctly if I cat it.

> I tried a bunch of other characters outside the BMP, all of which
> fail in the same way. Characters in the BMP work nicely.

Emacs 22 still doesn't support Unicode characters over BMP.
If you really need to handle them, please use the CVS branch
emacs-unicode-2.

> Apparently, emacs 22 shows a question mark instead of "\360\220\216\200"
> but trying to delete the question mark character with backspace turn it into
> "\360\220\216".

This is written in the comment of utf-8.el.

;; We compose the untranslatable sequences into a single character,
;; and move point to the next character.
;; This is infelicitous for editing, because there's currently no
;; mechanism for treating compositions as atomic, but is OK for
;; display.  They are composed to U+FFFD with help-echo which
;; indicates the unicodes they represent.  This function GCs too much.

I tried to fix this editting problem by using
modification-hooks text property, but couldn't accomplish a
good result.

---
Kenichi Handa
handa@m17n.org

       reply	other threads:[~2006-11-12  2:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611101127.47456.jerome@marant.org>
2006-11-12  2:32 ` Kenichi Handa [this message]
2006-11-18 13:22   ` Fwd: Problem with non-bmp unicode Jérôme Marant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Gj59W-0003x7-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).