emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: kadal <kadalcalypse@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: ox-html export bug
Date: Sun, 10 Sep 2017 00:37:43 +0200	[thread overview]
Message-ID: <87h8wb33d4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFgFV9NaEs+KQByaJX-TH9V_+XzCZ2t027mnPkKtKGVSy2sesg@mail.gmail.com> (Fabrice Popineau's message of "Fri, 8 Sep 2017 20:52:10 +0200")

Hello,

Fabrice Popineau <fabrice.popineau@gmail.com> writes:

> 2017-09-08 19:40 GMT+02:00 kadal <kadalcalypse@gmail.com>:
>
>> That said, the first option is better because if I'm setting a CUSTOM_ID,
>> that's what should be used for internal links...
>>
>>
> I agree with that. Ideally, if you set a CUSTOM_ID, then it should replace
> the default org generated id.

Using raw CUSTOM_ID value in exported documents is an issue because it
requires the user to know, ahead of time, what are the allowed
characters in the output format. As an example, I would consider it to
be a bug if Org refused to export my document to pdf because I had
chosen "100%" as a custom ID somewhere in the document.

However, HTML is a bit special in this case, because users expect to see
custom ID in the address bar of their browser.

Hopefully this is now fixed.

Thank you.


Regards,

-- 
Nicolas Goaziou                                                0x80A93738

      reply	other threads:[~2017-09-09 22:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 17:02 ox-html export bug kadal
2017-09-07 17:32 ` Nicolas Goaziou
2017-09-07 18:04   ` kadal
2017-09-08  8:55     ` Rasmus
2017-09-08 10:19       ` Nicolas Goaziou
2017-09-08 17:18         ` kadal
2017-09-08 17:32           ` Nicolas Goaziou
2017-09-08 17:40             ` kadal
2017-09-08 18:52               ` Fabrice Popineau
2017-09-09 22:37                 ` Nicolas Goaziou [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=87h8wb33d4.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    --cc=kadalcalypse@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).