From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Maus Subject: Re: [bug] org-link-escape and (wrong-type-argument stringp nil) Date: Wed, 22 Sep 2010 09:19:15 +0200 Message-ID: <87sk128cuk.wl%dmaus@ictsoc.de> References: <87tylkwpq0.fsf@mundaneum.com> <87mxrc1bwj.wl%dmaus@ictsoc.de> <87sk14rz3t.fsf@gmx.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/mixed; boundary="===============1450276476==" Return-path: Received: from [140.186.70.92] (port=43101 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OyJbx-0001Ln-UY for emacs-orgmode@gnu.org; Wed, 22 Sep 2010 03:19:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OyJbw-0007qV-G6 for emacs-orgmode@gnu.org; Wed, 22 Sep 2010 03:19:25 -0400 Received: from mysql1.xlhost.de ([213.202.242.106]:42105) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OyJbw-0007pf-BW for emacs-orgmode@gnu.org; Wed, 22 Sep 2010 03:19:24 -0400 In-Reply-To: <87sk14rz3t.fsf@gmx.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastian Rose Cc: David Maus , emacs-orgmode@gnu.org, =?UTF-8?B?U8OpYmFzdGllbg==?= Vauban --===============1450276476== Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Wed_Sep_22_09:19:14_2010-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit --pgp-sign-Multipart_Wed_Sep_22_09:19:14_2010-1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sebastian Rose wrote: >Is there a reason for this distinction between multibyte and unibyte? >I favour the "shotgun-approach" if not. It's bullet-proof. >The JavaScript function `encodeURIComponent()' encodes the German Umlaut >`=C3=BC' as `%C3%B6' regardless of the sources encoding actually. That's = why >I wrote the two functions `org-protocol-unhex-string' and >`org-protocol-unhex-compound' (s. org-protocol.el). Ah, yes. From my understandig of the RFC %C3%BC is a valid representation of the "=C3=BC" character. =20 I do not yet fully understand how to unescape such a representation. E.g. Is %C3%BC a hexencoded multibyte char or a succession of two singlebyte chars? >I'll have to take a look at that RFC you mentioned :) Me too :D Best, -- David --=20 OpenPGP... 0x99ADB83B5A4478E6 Jabber.... dmjena@jabber.org Email..... dmaus@ictsoc.de --pgp-sign-Multipart_Wed_Sep_22_09:19:14_2010-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iF4EABEIAAYFAkyZrfIACgkQma24O1pEeOZrWgD/RIjpQ5WV41KUFW6Z+v9Cmn7w WxHQPP/lEWB1OP1G1WkA/jLmu6IUe8pbzIWuDPOJNIyPmMO1Q/s4Ix4hyT7TALUj =bBec -----END PGP SIGNATURE----- --pgp-sign-Multipart_Wed_Sep_22_09:19:14_2010-1-- --===============1450276476== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1450276476==--