From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Noah Slater <nslater@tumbolia.org>, emacs-orgmode@gnu.org
Subject: Re: Radio targets with mixed capitalisation do not work in HTML export
Date: Mon, 17 Mar 2014 12:29:25 +0100 [thread overview]
Message-ID: <87d2hlhxm2.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87eh21qgmh.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 17 Mar 2014 11:11:34 +0100")
Hi Nicolas,
thanks for looking into this.
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Actually, even though it works if you test it on cases like:
>
> <<<Foo>>> foo
>
> it isn't right on more complex cases:
>
> <<<with \alpha>>> with \alpha
True.
It is not right on simpler example too, with just spaces:
========================================================================
<<<Hello World>>>
Let's say hello world to test.
========================================================================
It produces
========================================================================
<p>
<a id="Hello-World">Hello World</a>
</p>
<p>
Let's say <a href="#Hello World">hello-world</a> to test.
</p>
========================================================================
> As you can see, the logic is right in ox-latex.el, ox-html.el and
> ox-beamer.el.
I don't get the logic: the output text has two parts: the target of
the link, the description of the link. It the example above, the
Target is "Hello World", and should be rewritten "Hello-World" to
escape spaces. The description is "hello world" and should not be
rewritten, it must appears the same way to the user.
> Anyway, I think the solution is to slightly change the parser to enforce
> case-insensitivity.
I thought about this, but it does not solve the problem of displaying
the target instead of the link description.
> Some additional properties need to be added in order
> to preserve original contents of both radio links and radio targets.
>
> I pushed such a change. Is it working as expected?
Not for me: when "a word" is linked to a radio target, I expect to see
"a word" in the output, linked to a #a-word id. When "another word"
is linked to "Another Word", I expect to see "another word" in the
output, linking to an anchor #Another-Word.
If we do this, I don't see the need to enforce case sensitivity.
--
Bastien
next prev parent reply other threads:[~2014-03-17 11:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 17:24 Radio targets with mixed capitalisation do not work in HTML export Noah Slater
2014-03-17 2:02 ` Bastien
2014-03-17 10:11 ` Nicolas Goaziou
2014-03-17 11:29 ` Bastien [this message]
2014-03-17 12:04 ` Bastien
2014-03-17 14:27 ` Nicolas Goaziou
2014-03-17 15:50 ` Bastien
2014-03-20 21:58 ` Bastien
2014-03-21 14:25 ` Nicolas Goaziou
2014-03-21 14:30 ` Bastien
2014-03-21 17:25 ` Nicolas Goaziou
2014-03-21 17:28 ` Bastien
2014-03-21 18:47 ` Noah Slater
2014-03-21 21:38 ` Bastien
2014-03-23 17:13 ` Nicolas Goaziou
2014-03-23 17:26 ` Bastien
2014-03-24 10:24 ` Nicolas Goaziou
2014-03-24 14:11 ` Bastien
2014-03-25 9:24 ` Nicolas Goaziou
2014-03-25 11:07 ` Bastien
2014-03-24 13:23 ` Nicolas Goaziou
2014-03-17 12:38 ` Nicolas Goaziou
2014-03-17 12:59 ` Bastien
2014-03-17 13:11 ` Nicolas Goaziou
2014-03-17 14:18 ` 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=87d2hlhxm2.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=nslater@tumbolia.org \
/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).