Even more strange, while '%3f' reveals the error, '%3F' does not. I guess the ``org-link-unescape`` function has some serious problems with the handling of '?': when using '%3F' in an HTTP URL, it is unescaped when exported to HTML, resulting most of the time in invalid URLs, since the '?' character separates the path from query arguments.
For instance, in "http://x.org/what%3F"; the '%3F' should be left as is instead of being exported as "http://x.org/what?";. In "http://x.org/query?foo=bar";, the '?' should also be left as is. Here it's better to trust the user and leave URLs untouched than trying to be too smart. Cheers, :: Ivan Vilata i Balaguer -- http://ivan.lovesgazpacho.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
