From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: David Smith <davidsmith@acm.org>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Jason Rumney <jasonr@gnu.org>
Subject: Re: [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec]
Date: Wed, 02 Aug 2006 11:06:27 +0900 [thread overview]
Message-ID: <wlk65rzyak.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <jkvepcwm1g.fsf@glug.org>
>>>>> On 01 Aug 2006 10:47:07 -0400, Thien-Thi Nguyen <ttn@gnu.org> said:
> conversion to utf-8 is per the RFC, which seems to be the primary
> context for this function; avoiding that conversion means
> noncompliance w/ the RFC.
Do you mean RFC 3986 by "the RFC"? IIUC, it refers to UTF-8 in the
following 3 parts:
* 2.5 Identifying Data, 3rd paragraph
How to interpret a unreserved character as an octet. (It also
refers to other superset of the US-ASCII character encoding).
* 2.5 Identifying Data, last paragraph
Encoding of a URI component that represents *textual data*
consisting of characters from UCS for *a new URI scheme*.
* 3.2.2 Host
Encoding of a registered name that represents a host.
So, I don't think that avoiding UTF-8 conversion for non-textual data
or for a URI scheme that has existed as of RFC 3986 deviates from the
RFC.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
prev parent reply other threads:[~2006-08-02 2:06 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
2006-08-02 2:06 ` YAMAMOTO Mitsuharu [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wlk65rzyak.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=davidsmith@acm.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.