unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: function to decode url percent encoding
Date: Mon, 24 May 2010 10:55:00 -0700 (PDT)	[thread overview]
Message-ID: <2a743903-c179-4ed5-b0d5-52d3ceb4b37f@a27g2000prj.googlegroups.com> (raw)
In-Reply-To: a98c204f-a7dd-4f9b-b07d-d6a4da1566ba@11g2000prw.googlegroups.com

did some more testing about this.

the issue first of all seems to be that what characters should be
percent encoded.

i did some testing with browsers, IE, Firefox, Safari, Opera, all
behaved a bit differently in what they think should be percent
encoded.

• URL Percent Encoding and Unicode
  http://xahlee.org/js/url_encoding_unicode.html

text version excerpt follows

---------------------
Summary

Here's some summary of the behavior as it appears from above tests:

    * Firefox (v 3.6.3), is the most aggressive in turning characters
in url into the percent encoded form.
    * Google Chrome (4.1.249.1064 (45376)) will change unicode chars
into percent encoded form, but not parenthesis chars.
    * Safari (4.0.5 (531.22.7)) is better, in that it simply show the
characters as is, as much as it can.
    * Opera (v 10.10, build 1893) is the best, it shows unicode and
paren and en-dash as is.
    * IE (8.0.6001.18904), seems to take the approach that it doesn't
do anything to the url. Whatever you pasted in, remain unchanged

--------------

  Xah
∑ http://xahlee.org/

  reply	other threads:[~2010-05-24 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 18:12 function to decode url percent encoding Xah Lee
2010-05-18 18:26 ` Xah Lee
     [not found]   ` <jwvvdakrk9t.fsf-monnier+gnu.emacs.help@gnu.org>
     [not found]     ` <878w7gaox3.fsf@fh-trier.de>
     [not found]       ` <jwvhbm4oufs.fsf-monnier+gnu.emacs.help@gnu.org>
2010-05-24 14:33         ` Xah Lee
2010-05-24 17:55           ` Xah Lee [this message]
2010-05-25  0:26           ` Jason Rumney

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=2a743903-c179-4ed5-b0d5-52d3ceb4b37f@a27g2000prj.googlegroups.com \
    --to=xahlee@gmail.com \
    --cc=help-gnu-emacs@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.
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).