From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: cyd@stupidchicken.com, 1726@emacsbugs.donarmstrong.com,
emacs-devel@gnu.org
Subject: bug#1726: 23.0.60; end-of-sentence and non-breaking space
Date: Sun, 04 Jan 2009 06:18:22 +0200 [thread overview]
Message-ID: <umye7n1pt.fsf__22725.9281011813$1231044299$gmane$org@gnu.org> (raw)
In-Reply-To: <E1LJIXN-0008Vg-Pe@fencepost.gnu.org>
> From: Richard M Stallman <rms@gnu.org>
> CC: cyd@stupidchicken.com, emacs-devel@gnu.org,
> monnier@iro.umontreal.ca, 1726@emacsbugs.donarmstrong.com
> Date: Sat, 03 Jan 2009 21:16:21 -0500
>
> 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.
>
> Naybe that is a valid reason for the current behavior, but that
> doesn't alter the need for the manual to document the behavior.
That was an attempt at explaining the reasons, not telling they don't
need to be documented.
> Meanwhile, the Chinese and Chinese-derived character codes
> do not follow Unicode. So you can't enter them with \u.
> What is the way to enter them?
The problem at hand exists only for codes that are less than FF hex.
next prev parent reply other threads:[~2009-01-04 4:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvljtupcw3.fsf-monnier+emacsbugreports@gnu.org>
2009-01-02 17:13 ` bug#1726: 23.0.60; end-of-sentence and non-breaking space Richard M Stallman
[not found] ` <E1LInaw-0006om-DT@fencepost.gnu.org>
2009-01-03 3:06 ` Stefan Monnier
[not found] ` <jwv7i5dnlcy.fsf-monnier+emacsbugreports@gnu.org>
2009-01-03 9:54 ` Eli Zaretskii
2009-01-03 15:21 ` Richard M Stallman
[not found] ` <E1LJ8K6-0003dL-UD@fencepost.gnu.org>
2009-01-03 16:44 ` Eli Zaretskii
[not found] ` <utz8gmj9t.fsf@gnu.org>
2009-01-04 2:16 ` Richard M Stallman
[not found] ` <E1LJIXN-0008Vg-Pe@fencepost.gnu.org>
2009-01-04 4:18 ` Eli Zaretskii [this message]
2009-01-04 4:29 ` Jason Rumney
[not found] ` <49603B11.5040101@gnu.org>
2009-01-04 16:45 ` Eli Zaretskii
2009-01-05 7:11 ` Kenichi Handa
2009-01-05 6:37 ` Kenichi Handa
[not found] <E1LJjcR-0001uN-1l@etlken.m17n.org>
2009-01-06 0:01 ` Richard M Stallman
2009-01-06 4:08 ` Eli Zaretskii
[not found] <umye7n1pt.fsf@gnu.org>
2009-01-04 21:42 ` Richard M Stallman
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
2009-01-02 1:25 ` Richard M Stallman
2009-01-02 4:11 ` Stefan Monnier
2009-01-01 3:47 Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2008-12-29 10:23 Richard M Stallman
2011-09-11 18:43 ` Lars Magne Ingebrigtsen
2012-03-27 23:27 ` Glenn Morris
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='umye7n1pt.fsf__22725.9281011813$1231044299$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=1726@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--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).