[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Orgmode] Re: org-protocol: non-ASCII characters
From: |
Jan Böcker |
Subject: |
[Orgmode] Re: org-protocol: non-ASCII characters |
Date: |
Sat, 06 Feb 2010 14:50:26 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100120 Shredder/3.0.1 |
> 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
qnd-fix.patch
Description: Text document
- Re: [Orgmode] org-remember support in xournal, Jan Böcker, 2010/02/03
- Re: [Orgmode] org-remember support in xournal, dmg, 2010/02/03
- [Orgmode] org-protocol: non-ASCII characters, D M German, 2010/02/04
- [Orgmode] Re: org-protocol: non-ASCII characters,
Jan Böcker <=
- Re: [Orgmode] Re: org-protocol: non-ASCII characters, Jan Böcker, 2010/02/06
- Re: [Orgmode] Re: org-protocol: non-ASCII characters, Sebastian Rose, 2010/02/08
- Re: [Orgmode] Re: org-protocol: non-ASCII characters, dmg, 2010/02/12
- Re: [Orgmode] Re: org-protocol: non-ASCII characters, Jan Böcker, 2010/02/13
- Re: [Orgmode] Re: org-protocol: non-ASCII characters, Sebastian Rose, 2010/02/15