From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, 1726@emacsbugs.donarmstrong.com,
rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: 23.0.60; end-of-sentence and non-breaking space
Date: Mon, 05 Jan 2009 15:37:55 +0900 [thread overview]
Message-ID: <E1LJj63-0001fC-5N@etlken.m17n.org> (raw)
In-Reply-To: <utz8gmj9t.fsf@gnu.org> (message from Eli Zaretskii on Sat, 03 Jan 2009 18:44:30 +0200)
In article <utz8gmj9t.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > From: Richard M Stallman <rms@gnu.org>
> > Date: Sat, 03 Jan 2009 10:21:58 -0500
> > Cc: cyd@stupidchicken.com, 1726@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
> >
> > IIUC if you want the character with code #xa0, then using \u00a0 would
> > seem like the most unambiguous option (I notice that "\ua0" gives
> > a weird error "Non-hex digit used for Unicode escape").
> >
> > I expected \xa0 to give me that character. It still seems strange
> > that it would do anything else.
> We need some way of inserting raw 8-bit bytes, because otherwise code
> that encodes and decodes text in Lisp will not work. For inserting
> characters, we have the \u alternative; but I don't think there's
> alternative for raw bytes except insert \xNN.
I modified read_escape to treat "\xXX" as a raw-byte code
but treat "\xXXX.." as a character code U+XXX... As far as
I remember, this is to keep backward compatibility.
And, we have the alternative for raw bytes. That is to use
octal form, something like "\240".
---
Kenichi Handa
handa@m17n.org
prev parent reply other threads:[~2009-01-05 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 3:47 23.0.60; end-of-sentence and non-breaking space Chong Yidong
2009-01-02 1:25 ` Richard M Stallman
2009-01-02 2:38 ` bug#1727: " Drew Adams
2009-01-02 4:11 ` Stefan Monnier
2009-01-02 17:13 ` Richard M Stallman
2009-01-03 3:06 ` Stefan Monnier
2009-01-03 9:54 ` Eli Zaretskii
2009-01-03 15:21 ` Richard M Stallman
2009-01-03 16:44 ` Eli Zaretskii
2009-01-04 2:16 ` Richard M Stallman
2009-01-04 4:18 ` Eli Zaretskii
2009-01-04 21:42 ` Richard M Stallman
2009-01-04 4:29 ` bug#1726: " Jason Rumney
2009-01-04 16:45 ` Eli Zaretskii
2009-01-05 7:11 ` Kenichi Handa
2009-01-06 0:01 ` bug#1726: " Richard M Stallman
2009-01-06 4:08 ` Eli Zaretskii
2009-01-05 6:37 ` Kenichi Handa [this message]
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=E1LJj63-0001fC-5N@etlken.m17n.org \
--to=handa@m17n.org \
--cc=1726@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).