From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Orgmode fails to export specific web-links as latex/pdf Date: Tue, 16 Jul 2013 22:15:17 +0200 Message-ID: <87r4eyjm7e.fsf@gmail.com> References: <87y59gt27c.fsf@bzg.ath.cx> <877ggzn8tq.fsf@gmail.com> <87a9lvpytg.fsf@bzg.ath.cx> <87obaaa8z2.fsf@gmail.com> <87d2qqwq01.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UzBeM-0007zM-Lh for emacs-orgmode@gnu.org; Tue, 16 Jul 2013 16:15:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UzBeL-0001Pm-G6 for emacs-orgmode@gnu.org; Tue, 16 Jul 2013 16:15:06 -0400 In-Reply-To: (Yury Bulka's message of "Tue, 16 Jul 2013 21:44:00 +0300") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Yury Bulka Cc: Bastien , emacs-orgmode , Mark Edgington Yury Bulka writes: > One more thing, related to unicode inside the href of the link: > > [[https://commons.wikimedia.org/wiki/File:%D0%91%D1%83%D0%B7%D0%BE%D0%BA.= ogg][https://commons.wikimedia.org/wiki/File:=D0=91=D1=83=D0=B7=D0=BE=D0=BA= .ogg]] > > Turns into: > \href{https://commons.wikimedia.org/wiki/File:=D0=91=D1=83=D0=B7=D0=BE=D0= =BA.ogg}{\url{https://commons.wikimedia.org/wiki/File:=D0=91=D1=83=D0=B7=D0= =BE=D0=BA.ogg}} > > I.e. for some reason the href gets url-decoded. Such links don't work > in evince. Indeed, links are url-decoded when parsed (see line 3139 in org-element.el). I think the reasoning behind it is that url should then be encoded again to make sure every url is correctly encoded. One possibility is to use (org-link-escape (org-link-unescape raw-link)), that is every parsed link will be url-encoded. Another one is to leave links as-is, but back-end developers will have to deal with that. I lean towards the former. Funnily, this only applied to bracket links (i.e., [[link][desc]]), plain links are not url-decoded (or encoded) at all. This isn't consistent and also needs to be fixed. Any opinion? Regards, --=20 Nicolas Goaziou