emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Yury Bulka <yurkobb@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode <emacs-orgmode@gnu.org>,
	Mark Edgington <edgimar@gmail.com>
Subject: Re: Orgmode fails to export specific web-links as latex/pdf
Date: Tue, 16 Jul 2013 22:15:17 +0200	[thread overview]
Message-ID: <87r4eyjm7e.fsf@gmail.com> (raw)
In-Reply-To: <CADqBZocj3Et=8Tke5ogk1bvTPYTxbXHTj1vzgf_nad-aZJu=WQ@mail.gmail.com> (Yury Bulka's message of "Tue, 16 Jul 2013 21:44:00 +0300")

Yury Bulka <yurkobb@gmail.com> 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:Бузок.ogg]]
>
> Turns into:
> \href{https://commons.wikimedia.org/wiki/File:Бузок.ogg}{\url{https://commons.wikimedia.org/wiki/File:Бузок.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,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-07-16 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  2:16 Orgmode fails to export specific web-links as latex/pdf Mark Edgington
2013-07-09 11:14 ` Bastien
2013-07-09 13:48   ` Nicolas Goaziou
2013-07-09 14:55     ` Bastien
2013-07-10 12:35       ` Nicolas Goaziou
2013-07-10 12:36         ` Bastien
2013-07-16 18:37           ` Yury Bulka
2013-07-16 18:44             ` Yury Bulka
2013-07-16 20:15               ` Nicolas Goaziou [this message]
2013-07-16 19:25             ` Nicolas Goaziou
2013-07-24 18:18           ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4eyjm7e.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@gnu.org \
    --cc=edgimar@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yurkobb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).