unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: "José A. Romero L." <escherdragon@gmail.com>
Cc: 6252@debbugs.gnu.org
Subject: bug#6252: Emacs does not implement URL (aka "percent") decoding	correctly.
Date: Mon, 24 May 2010 12:33:46 +0900	[thread overview]
Message-ID: <wly6fa2cth.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <AANLkTilLXmD0oCE1in39yqnuAEq6PkvJmyC1a_0eToab@mail.gmail.com>

>>>>> On Sun, 23 May 2010 01:46:54 +0200, José A. Romero L. <escherdragon@gmail.com> said:

> Seems that RFC 3986 has not been implemented correctly in
> Emacs. IMHO that is an important hole you have found there. The
> standard requires that all unreserved characters be encoded/decoded
> as UTF8 bytes.

If you are referring to the following part of RFC 3986, it doesn't say
anything about existing URI schemes (as opposed to "a new URI
scheme"), those defining a component that does NOT represent textual
data, or even for textual data, those NOT consisting of characters
from the Universal Character Sets.

  When a new URI scheme defines a component that represents textual
  data consisting of characters from the Universal Character Set
  [UCS], the data should first be encoded as octets according to the
  UTF-8 character encoding [STD63]; then only those octets that do not
  correspond to characters in the unreserved set should be percent-
  encoded.

(See also http://lists.gnu.org/archive/html/emacs-devel/2006-08/msg00065.html)

Though returning a multibyte string decoded as UTF-8 would be useful
for many cases, I think some "unhex"ing function should also provide a
functionality to return a unibyte string.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp





  reply	other threads:[~2010-05-24  3:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 23:46 bug#6252: Emacs does not implement URL (aka "percent") decoding correctly José A. Romero L.
2010-05-24  3:33 ` YAMAMOTO Mitsuharu [this message]
     [not found]   ` <AANLkTilUODUArElMVd6FzgL08u1TmCVw2kar1Gf9z1Z9@mail.gmail.com>
2010-05-25  8:56     ` bug#6252: Fwd: " José A. Romero L.
2011-09-21 20:17 ` Lars Magne Ingebrigtsen
     [not found]   ` <CAJ_WfoU_JAjf-cTruu3fL1OO5fSMRHsjmnB=-aUK6h6RM7e8AA@mail.gmail.com>
2011-09-22  7:38     ` Lars Magne Ingebrigtsen
     [not found]       ` <CAJ_WfoV04Bis9msxHYLdu5VTONZ7hO_LsKy097MqfnmLf4kfjQ@mail.gmail.com>
2011-09-23  8:34         ` Lars Magne Ingebrigtsen
2011-09-23 11:12           ` José A. Romero L.
2011-09-25 22:16             ` Lars Magne Ingebrigtsen
2011-09-25 22:25               ` José A. Romero L.
2012-04-10  2:14               ` Lars Magne Ingebrigtsen

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=wly6fa2cth.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=6252@debbugs.gnu.org \
    --cc=escherdragon@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 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).