From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: eww doesn't decode %AA%BB%CC URL names Date: Fri, 25 Dec 2015 09:17:11 +0200 Message-ID: <83d1tvm1zc.fsf@gnu.org> References: <83r3n0llkt.fsf@gnu.org> <87vb7nsq1g.fsf@gnus.org> <83ziwzmzyp.fsf@gnu.org> <8760znslig.fsf@gnus.org> <83twn7myin.fsf@gnu.org> <87bn9fr59a.fsf@gnus.org> <87vb7npogq.fsf@gnus.org> <87k2o3pnhz.fsf@gnus.org> <83h9j7mu13.fsf@gnu.org> <87fuyrpmw9.fsf@gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1451028129 19855 80.91.229.3 (25 Dec 2015 07:22:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Dec 2015 07:22:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 25 08:21:55 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aCMhG-0008TR-Uc for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 08:21:55 +0100 Original-Received: from localhost ([::1]:34536 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCMcM-0004AJ-V0 for ged-emacs-devel@m.gmane.org; Fri, 25 Dec 2015 02:16:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCMc6-00049W-3V for emacs-devel@gnu.org; Fri, 25 Dec 2015 02:16:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aCMc1-0000C0-S7 for emacs-devel@gnu.org; Fri, 25 Dec 2015 02:16:34 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCMc1-0000Bv-Oo; Fri, 25 Dec 2015 02:16:29 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3476 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aCMc1-0002MX-4E; Fri, 25 Dec 2015 02:16:29 -0500 In-reply-to: <87fuyrpmw9.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 24 Dec 2015 22:17:10 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196815 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Thu, 24 Dec 2015 22:17:10 +0100 > > Eli Zaretskii writes: > > > If you want to check that STRING can be encoded in CODING, do this: > > > > (member CODING (find-coding-systems-string STRING)) > > > > and see if the result is non-nil. > > Hm: > > (find-coding-systems-string "a") > => (undecided) This is normal for pure ASCII. If the return value is just that, then CODING, any CODING, can do the job. > (find-coding-systems-string "§³§Ö§â§Õ§è§Ö") > => (chinese-iso-8bit japanese-shift-jis iso-2022-jp utf-8 korean-iso-8bit euc-jis-2004 japanese-iso-8bit iso-2022-jp-2004 cp855 windows-1251 koi8-t koi8-u cp866 koi8-u cyrillic-koi8 cyrillic-iso-8bit chinese-gb18030 chinese-gbk chinese-big5-hkscs chinese-hz utf-7 iso-2022-kr iso-2022-jp-2 iso-2022-cn-ext iso-2022-cn utf-16 utf-16be-with-signature utf-16le-with-signature utf-16be utf-16le compound-text-with-extensions compound-text iso-2022-7bit utf-8-auto utf-8-with-signature emacs-mule raw-text iso-2022-8bit-ss2 iso-2022-7bit-lock eucjp-ms korean-cp949 japanese-shift-jis-2004 japanese-iso-7bit-1978-irv japanese-cp932 pt154 mik cp1125 cyrillic-alternativnyj utf-7-imap utf-8-emacs prefer-utf-8 no-conversion ctext-no-compositions iso-2022-7bit-lock-ss2 iso-2022-7bit-ss2) > > Wowza. Yeah. > Ok, I think I should now be able to create the function in question. > Thanks for all the help. :-) You are welcome.