unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, yuri.v.khan@gmail.com
Subject: Re: eww doesn't decode %AA%BB%CC URL names
Date: Thu, 24 Dec 2015 20:55:13 +0100	[thread overview]
Message-ID: <87bn9fr59a.fsf@gnus.org> (raw)
In-Reply-To: <83twn7myin.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Dec 2015 21:34:24 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> That's basically just (car (decode-coding-string ...))
>
> I believe you meant detect-coding-string.

Yup.  :-)

>> though, since it'll return utf-8 first if that's a possible charset,
>> won't it?
>
> You cannot rely on it returning UTF-8, that depends on coding
> priorities (that are subject to customizations) and other things.
>
> I think you should use UTF-8 literally as the first choice.

Right.  How do I check whether the bytes are a valid utf-8 sequence,
though?  I thought I remembered something called
`valid-something-something-p', but I can't find it now...

> Yes, they use these in preference to everything else, something like
> this:
>
>   (let ((coding (or coding-system-for-read
>                     document-encoding
> 		    locale-coding-system
>                     ...)))
>       (decode-coding-string ... coding))

Okidoke.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2015-12-24 19:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 14:26 eww doesn't decode %AA%BB%CC URL names Eli Zaretskii
2015-12-24 17:40 ` Lars Ingebrigtsen
2015-12-24 18:07   ` Yuri Khan
2015-12-24 19:03     ` Eli Zaretskii
2015-12-24 19:18       ` Lars Ingebrigtsen
2015-12-24 19:34         ` Eli Zaretskii
2015-12-24 19:55           ` Lars Ingebrigtsen [this message]
2015-12-24 20:40             ` Eli Zaretskii
2015-12-24 20:49               ` Lars Ingebrigtsen
2015-12-24 20:43             ` Lars Ingebrigtsen
2015-12-24 21:00               ` Eli Zaretskii
2015-12-24 21:04               ` Lars Ingebrigtsen
2015-12-24 21:11                 ` Eli Zaretskii
2015-12-24 21:16                   ` Eli Zaretskii
2015-12-24 21:17                   ` Lars Ingebrigtsen
2015-12-24 21:28                     ` Lars Ingebrigtsen
2015-12-25  7:24                       ` Eli Zaretskii
2015-12-25  7:32                         ` Lars Ingebrigtsen
2015-12-25  7:17                     ` Eli Zaretskii

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=87bn9fr59a.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@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).