From: Kenichi Handa <handa@m17n.org>
Cc: davidsmith@acm.org, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, ttn@gnu.org, jasonr@gnu.org,
mituharu@math.s.chiba-u.ac.jp
Subject: Re: [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec]
Date: Wed, 09 Aug 2006 12:48:16 +0900 [thread overview]
Message-ID: <E1GAf3I-0001FU-00@etlken> (raw)
In-Reply-To: <85k65sxzcq.fsf@lola.goethe.zz> (message from David Kastrup on Tue, 01 Aug 2006 17:14:13 +0200)
In article <85k65sxzcq.fsf@lola.goethe.zz>, David Kastrup <dak@gnu.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> (if (or (multibyte-string-p string)
>>> (not unibyte-as-is-p))
>>> (encode-coding-string string 'utf-8 t)
>>
>> Encoding a unibyte string doesn't make any sense (IMHO it should
>> signal an error, and indeed in my locally hacked Emacs it does ;-).
> It sounds to me like this would be a sensible setting, and we should
> have it before entering pretest: we would like to catch the cases
> where this happens.
This situation has been there for long (since Emacs 20). I
don't want to touch this part before the release. Emacs 23
is the good chance to clean this matter.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-08-09 3:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 13:14 [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec] Richard Stallman
2006-07-30 20:24 ` Thien-Thi Nguyen
2006-07-31 0:59 ` YAMAMOTO Mitsuharu
2006-07-31 10:13 ` Thien-Thi Nguyen
2006-07-31 10:46 ` Jason Rumney
2006-07-31 16:08 ` Stefan Monnier
2006-07-31 16:35 ` David Smith
2006-07-31 20:49 ` Thien-Thi Nguyen
2006-08-01 3:55 ` YAMAMOTO Mitsuharu
2006-08-01 4:20 ` Stefan Monnier
2006-08-01 4:34 ` YAMAMOTO Mitsuharu
2006-08-01 6:50 ` Stefan Monnier
2006-08-01 7:14 ` Kenichi Handa
2006-08-01 14:32 ` Stefan Monnier
2006-08-01 8:42 ` Jason Rumney
2006-08-01 14:47 ` Thien-Thi Nguyen
2006-08-01 15:10 ` Stefan Monnier
2006-08-01 15:14 ` David Kastrup
2006-08-01 15:54 ` Stefan Monnier
2006-08-01 16:07 ` David Kastrup
2006-08-09 3:48 ` Kenichi Handa [this message]
2006-08-02 2:06 ` YAMAMOTO Mitsuharu
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=E1GAf3I-0001FU-00@etlken \
--to=handa@m17n.org \
--cc=davidsmith@acm.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=monnier@iro.umontreal.ca \
--cc=ttn@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).