what-cursor-position vs. Unicode

what-cursor-position vs. Unicode

[Dan Jacobson]

Today we shall discuss what-cursor-position when given an argument of ^U.
We see that it gives Unicode information:
  character: Z (90, #o132, #x5a, U+005A)
Except when you really need it:
  character: 丹 (107109, #o321145, #x1a265)
It should mention U+4E39.
emacs-version "22.0.50.1"

Re: what-cursor-position vs. Unicode

[Eli Zaretskii]

> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Sat, 03 Jun 2006 10:34:59 +0800
> Cc: handa@etl.go.jp
> 
> It should mention U+4E39.
> emacs-version "22.0.50.1"

It does for me, at least when reading your mail.

Perhaps you should send the original file (as a binary attachment), or
describe how you produced the character, if it wasn't from a file.

Also, please tell when was your Emacs resync'ed with CVS, and please
try looking at the character in "emacs -Q".

Re: what-cursor-position vs. Unicode

[Dan Jacobson]

EZ> It does for me, at least when reading your mail.
Hmmm, me too, but not from a file.
EZ> Also, please tell when was your Emacs resync'ed with CVS
All I know beyond emacs-version "22.0.50.1" is I use Debian
emacs-snapshot 20060518-1.
KH> #x1a265 is a character of chinese-cns11643-1, and the
KH> current Emacs doesn't support Unicode mapping for that
KH> character set.
All I know is me and my Unicode UTF-8 char sitting in the file.
>> Just wondering: Why not?
KH> I myself want to avoid spending a time on what becomes useless in
KH> the future.
I see, there is some funny level of indirection that will be
eliminated in the future. Good.

Re: what-cursor-position vs. Unicode

[Miles Bader]

Dan Jacobson <jidanni@jidanni.org> writes:
> KH> I myself want to avoid spending a time on what becomes useless in
> KH> the future.
>
> I see, there is some funny level of indirection that will be
> eliminated in the future. Good.

In the future (well actually right now, on a CVS branch) Emacs will use
a unicode internal representation, where obviously this sort of thing
will be easier...

-Miles
-- 
"Most attacks seem to take place at night, during a rainstorm, uphill,
 where four map sheets join."   -- Anon. British Officer in WW I

Re: what-cursor-position vs. Unicode

[Kenichi Handa]

In article <87irnjklv0.fsf@jidanni.org>, Dan Jacobson <jidanni@jidanni.org> writes:

> Today we shall discuss what-cursor-position when given an argument of ^U.
> We see that it gives Unicode information:
>   character: Z (90, #o132, #x5a, U+005A)
> Except when you really need it:
>   character: 丹 (107109, #o321145, #x1a265)
> It should mention U+4E39.
> emacs-version "22.0.50.1"

#x1a265 is a character of chinese-cns11643-1, and the
current Emacs doesn't support Unicode mapping for that
character set.

---
Kenichi Handa
handa@m17n.org

Re: what-cursor-position vs. Unicode

[Werner LEMBERG]

> #x1a265 is a character of chinese-cns11643-1, and the
> current Emacs doesn't support Unicode mapping for that
> character set.

Just wondering: Why not?


    Werner

Re: what-cursor-position vs. Unicode

[Kenichi Handa]

In article <20060605.102222.112830788.wl@gnu.org>, Werner LEMBERG <wl@gnu.org> writes:

>> #x1a265 is a character of chinese-cns11643-1, and the
>> current Emacs doesn't support Unicode mapping for that
>> character set.

> Just wondering: Why not?

Because no one has implemented it.  I myself want to avoid
spending a time on what becomes useless in the future.  In
addition, in the current Emacs code, adding something like
lisp/international/subst-cns.el leads to slower startup in
CJK locales, which I want to avoid.

But, if someone implement it and Richard agrees on including
it before the release, please go ahead.

---
Kenichi Handa
handa@m17n.org