emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jess Balint <jbalint@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: HTML Export doesn't handle internal link with spaces [8.0.7 (8.0.7-6-g13cb28-elpa @ /home/jbalint/.emacs.d/elpa/org-20130812/)]
Date: Fri, 20 Dec 2013 22:47:52 +0100	[thread overview]
Message-ID: <87sitnjit3.fsf@gmail.com> (raw)
In-Reply-To: <87zjo034l8.wl%jbalint@gmail.com> (Jess Balint's message of "Mon, 16 Dec 2013 14:48:03 -0600")

Hello,

Jess Balint <jbalint@gmail.com> writes:

> I've generated a link to a headline with `org-store-link' and
> `org-insert-link'. It's rendered into the Org file like so:
>
>   [[*Headline%20with%Spaces][Headline with Spaces]]
>

[...]

> The problem is in `org-export-resolve-fuzzy-link' which get's the path
> directly from the link:
>
>   (let* ((raw-path (org-element-property :path link))
>
> But at this point it has "%20" in it which causes a problem when
> splitting it:
>
>      ;; Split PATH at white spaces so matches are space
>      ;; insensitive.
>      (path (org-split-string
>         (if match-title-p (substring raw-path 1) raw-path)))
>

Thank you for the report.

This bug exists because `org-insert-link' blindly url-hexifies links,
but nothing will unhexify it before it reaches an export back-end.

This is difficult to solve, because if you unhexify it, the very same
bug will occur on the other side (i.e. links you paste without using
`org-insert-link', which you don't want to unhexify).

IMO, `org-insert-link' shouldn't hexify links in all situations (if at
all).

Anyway, I can't think of any satisfactory solution at the moment.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-12-20 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 20:48 Bug: HTML Export doesn't handle internal link with spaces [8.0.7 (8.0.7-6-g13cb28-elpa @ /home/jbalint/.emacs.d/elpa/org-20130812/)] Jess Balint
2013-12-20 21:47 ` Nicolas Goaziou [this message]
2014-01-03 14:48   ` Bastien
2014-01-03 15:05     ` Nicolas Goaziou
2014-01-04 14:35       ` Bastien
2014-01-05  0:03         ` Nicolas Goaziou
2014-01-05  6:45           ` Bastien
2014-01-06 11:32             ` Nicolas Goaziou
2014-01-06 16:36               ` Bastien

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=87sitnjit3.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jbalint@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

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).