[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [BUG] External unicode links without a description in ox-html

From: Nicolas Goaziou
Subject: Re: [O] [BUG] External unicode links without a description in ox-html
Date: Mon, 25 Jul 2016 14:52:59 +0200


Michael Brand <address@hidden> writes:

> There seems to be a related issue with an inconsistency between HTML
> and other export formats in using org-link-unescape for the link
> _destination_ part: With the Org file
> 1) https://duckduckgo.com/?q=Org+mode+%252B+Worg
> 2) https://duckduckgo.com/?q=Org+mode+%2B+Worg
> org-open-at-point on link 1) opens a web browser with the search field
> filled with "Org mode + Worg" as expected by me.

This looks like an error to me. 

If I type https://duckduckgo.com/?q=Org+mode+%252B+Worg in my browser,
I get

  "Org mode %2B Worg"

as the search string. It should be the same when opening the link from
an Org document. These URI are /not/ equivalent.

> The same happens when using link 1) of the HTML export. But when
> exporting to PDF (via LaTeX), ODT or ASCII (browse-url-at-point)
> I have to use link 2) to get the same result. I think one should be
> able to consistently use link 1) for all export formats.

It looks as we're trying to paper over an Org problem here, which is the
redundant link escaping that happens when calling `org-insert-link' (C-c

AFAICT, there are two reasons for Org to escape a link: when the link
contains either "]]" or multiple consecutive spaces. The former
obviously breaks Org link syntax. The latter doesn't survive a call to

Alas, Org handles it the wrong way, by using a mechanism that cannot be
properly undone; you cannot possibly know how many times the desired URI
has been encoded, if at all. Moreover, this mechanism isn't user
friendly, i.e., you cannot reasonably ask a user to encode an URI on the
fly when jolting notes.

I can see two ways out:

1. Do not escape anything. 

   This prevent any link with a description to contain either "]]" or
   multiple spaces, but these requirements are so uncommon we probably
   shouldn't bother.

2. Use a different internal escape mechanism.

   By providing our own simple escape mechanism, e.g., \]\], we can
   solve the issues raised above.

In any case, Org should not create something as


if the real URI is




Nicolas Goaziou

reply via email to

[Prev in Thread] Current Thread [Next in Thread]