From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?SmFuIELDtmNrZXI=?= Subject: Re: org-protocol: non-ASCII characters Date: Sat, 06 Feb 2010 14:50:26 +0100 Message-ID: <4B6D73A2.8000403@jboecker.de> References: <86tyu2d5xw.fsf@mn.cs.uvic.ca> <4B693FBD.9010608@jboecker.de> <86d40k9702.fsf_-_@mn.cs.uvic.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------020200060600020301090003" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ndl4T-0001iJ-0i for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 08:51:37 -0500 Received: from [199.232.76.173] (port=38120 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ndl4S-0001hD-CL for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 08:51:36 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Ndl4R-00032l-C9 for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 08:51:36 -0500 Received: from mail7.worldserver.net ([217.13.200.27]:45490) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ndl4Q-00031v-OE for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 08:51:35 -0500 In-Reply-To: <86d40k9702.fsf_-_@mn.cs.uvic.ca> 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: dmg@uvic.ca Cc: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --------------020200060600020301090003 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > I have been looking around and I am not sure how to solve this > problem. Withing Evince and Xournal I am encoding any non alphanum (as > defined by the C macro) each byte that is contained in the filename > individually. > > Does anybody know which are the characters above 0 (zero) that need to > be encoded for a safe org link? AFAIK, your current approach is correct. I think I figured it out for evince: the file name you get from evince is already URI-encoded. The attached patch fixes the problem for me, but I do not know if it is the right thing to do. I assume that the forward slashes in the file name still have to be encoded so that org-protocol is not confused; the patch disables URI-encoding for percent signs, so that already URI-encoded characters pass through unharmed. - Jan --------------020200060600020301090003 Content-Type: text/plain; name="qnd-fix.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="qnd-fix.patch" ZGlmZiAtLWdpdCBhL2xpYnZpZXcvZXYtdmlldy5jIGIvbGlidmlldy9ldi12aWV3LmMKaW5k ZXggYzgxNDVmZi4uYzU3NTgzMSAxMDA2NDQKLS0tIGEvbGlidmlldy9ldi12aWV3LmMKKysr IGIvbGlidmlldy9ldi12aWV3LmMKQEAgLTU3NTIsNyArNTc1Miw3IEBAIGV2X3ZpZXdfcHJl dmlvdXNfcGFnZSAoRXZWaWV3ICp2aWV3KQogCQkKIHN0YXRpYyBnaW50IGlzX3VuY2hhbmdl ZF91cmlfY2hhcihjaGFyIGMpCiB7Ci0gIHJldHVybiBpc2FsbnVtKGMpOworCXJldHVybiAo KGMgPT0gJyUnKSB8fCBpc2FsbnVtKGMpKTsKIH0KIAogc3RhdGljIHZvaWQgZW5jb2RlX3Vy aShnY2hhciAqZW5jb2RlZF91cmksIGdpbnQgYnVmc2l6ZSwgY29uc3QgZ2NoYXIgKnVyaSkK --------------020200060600020301090003 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 --------------020200060600020301090003--