emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 15:18:33 +0100	[thread overview]
Message-ID: <87r460ewna.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8738ihq8ar.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 17	Mar 2014 14:11:24 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> I see the capitalization problem, but I still don't understand why you
> think target and description are inverted.

Well, they are.

Okay, again:

========================================================================
<<<Hello World>>>

hello world
========================================================================

The target of the second "hello world" is "Hello World" (capitalized).

The description of the second hello world is "hello world" (lower case.)

With the latest maint, the second "hello world" is translated as

<a href="#hello-world">Hello World</a>

whereas it should be

<a href="#Hello-World">hello world</a>
          ^     ^      ^     ^
        [target]       [description]

>    <a href="#xxx">yyy</a>
>
> targets
>
>    <a id="xxx">zzz</a>
>
> In the current state (ignoring the description part), you have:
>
>   <a href="#hello-world">...</a>
>
> and
>
>   <a id="hello-world">...</a>
>
> What do you think is wrong here?

If the radio link is "Hello World", the target should be #Hello-World.

We can decide to lower case all targets, but it is not necessary with
the fix I propose.

-- 
 Bastien

      reply	other threads:[~2014-03-17 14:18 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
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 [this message]

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=87r460ewna.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).