From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: kadal <kadalcalypse@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: ox-html export bug
Date: Fri, 8 Sep 2017 20:52:10 +0200 [thread overview]
Message-ID: <CAFgFV9NaEs+KQByaJX-TH9V_+XzCZ2t027mnPkKtKGVSy2sesg@mail.gmail.com> (raw)
In-Reply-To: <af67ddcb-0713-0ac0-6449-25e1e39b8ee9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
2017-09-08 19:40 GMT+02:00 kadal <kadalcalypse@gmail.com>:
> On 09/08/2017 10:32 AM, Nicolas Goaziou wrote:
>
>> kadal <kadalcalypse@gmail.com> writes:
>>
>> Seems like the second one should export to either "<h2 id="my-name">"
>>> or "<h2 id="my-name" id="orge4e91c4">".
>>>
>>
>> Is it valid HTML?
>>
>> Regards,
>>
>> This SO thread has confusing answers: https://stackoverflow.com/ques
> tions/192048/can-an-html-element-have-multiple-ids#192066
>
> Looks like the second option will work.
Not valid according to :
https://www.w3.org/TR/html5/syntax.html#attributes-0
"There must never be two or more attributes on the same start tag whose
names are an ASCII case-insensitive match for each other."
> 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.
Regards,
Fabrice
[-- Attachment #2: Type: text/html, Size: 2296 bytes --]
next prev parent reply other threads:[~2017-09-08 18:52 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 [this message]
2017-09-09 22:37 ` 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=CAFgFV9NaEs+KQByaJX-TH9V_+XzCZ2t027mnPkKtKGVSy2sesg@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kadalcalypse@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).