From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: william.xue@gmail.com, emacs-devel@gnu.org
Subject: Re: can not decode 0x93 and 0x94 to correct char
Date: Fri, 28 Sep 2007 10:30:01 +0200 [thread overview]
Message-ID: <utzpf42gm.fsf@gnu.org> (raw)
In-Reply-To: <E1Ib9NQ-00055e-81@etlken.m17n.org> (message from Kenichi Handa on Fri, 28 Sep 2007 15:31:04 +0900)
> From: Kenichi Handa <handa@m17n.org>
> Date: Fri, 28 Sep 2007 15:31:04 +0900
> Cc: emacs-devel@gnu.org
>
> \223 and \224 are code points of cp125X for LEFT DOUBLE
> QUOTATION MARK and RIGHT DOUBLE QUOTATION MARK. Their
> Unicode code points are U+201C and U+201D (note that they
> are not included in ISO-8859-1).
>
> With the trunk Emacs, you must use UTF-8 (or the other
> UTF-based encodings, some of CJK encodings) to handle those
> characters.
Actually, Emacs 22.1 displays these characters just fine if I type
"C-x RET c cp1252 RET C-x C-f char_err_clip.c RET". OTOH, using UTF-8
instead if cp1252 still displays octal escapes, like I'd expect.
AFAIK, in Emacs 22 on Windows, cp1252 and friends map these characters
into Unicode by design, and that is why using cp1252 for visiting this
file does The Right Thing. So I don't think the OP needs to wait for
the inherent Unicode support.
next prev parent reply other threads:[~2007-09-28 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 4:33 can not decode 0x93 and 0x94 to correct char William Xue
2007-09-28 6:31 ` Kenichi Handa
2007-09-28 8:30 ` Eli Zaretskii [this message]
2007-09-28 9:38 ` William Xue
2007-10-01 1:33 ` Kenichi Handa
2007-09-28 13:50 ` Stefan Monnier
2007-09-28 14:45 ` Eli Zaretskii
2007-09-29 8:29 ` William Xue
2007-09-29 13:47 ` Stefan Monnier
2007-09-29 15:30 ` William Xue
-- strict thread matches above, loose matches on Subject: below --
2007-09-28 4:24 William Xue
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=utzpf42gm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=william.xue@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.