From: Nandakumar Chandrasekhar <navanitachora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Validating Pandoc generated HTML 5
Date: Wed, 15 Nov 2023 07:18:33 -0800 (PST) [thread overview]
Message-ID: <f5859ff8-3e37-4794-9c85-ef6456cd73c1n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1747 bytes --]
Dear Folks,
I have the following question in regard to the HTML 5 generated by Pandoc.
Is Pandoc generating HTML 5 using the XHTML standard?
When validating the generated HTML through the W3C validator I see the
following information notices about void elements:
Trailing slash on void elements has no effect
<https://github.com/validator/validator/wiki/Markup-%C2%BB-Void-elements#trailing-slashes-in-void-element-start-tags-do-not-mark-the-start-tags-as-self-closing>
and interacts badly with unquoted attribute values
<https://github.com/validator/validator/wiki/Markup-%C2%BB-Void-elements#trailing-slashes-directly-preceded-by-unquoted-attribute-values>
.
Since this is just informational I am not too worried about the trailing
slash being placed at the end of elements although it does not seem to be
part of the HTML 5 standard.
However, when I am faced with an error like below I would like to fix it:
Error: Bad value doc-endnotes for attribute role on element aside
<https://html.spec.whatwg.org/multipage/#the-aside-element>.
</figure>↩<aside id="footnotes" class="footnotes footnotes-end-of-document"↩
role="doc-endnotes">↩<hr />
I would like to know the community's verdict on this and how I may remove
these messages while validating if at all possible. Many thanks
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f5859ff8-3e37-4794-9c85-ef6456cd73c1n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4901 bytes --]
next reply other threads:[~2023-11-15 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 15:18 Nandakumar Chandrasekhar [this message]
[not found] ` <f5859ff8-3e37-4794-9c85-ef6456cd73c1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-15 17:21 ` John MacFarlane
2023-11-15 17:45 ` Nandakumar Chandrasekhar
[not found] ` <CAMhuDe8L9CLLXQVU=c3ZfmpyLe+k4h2E9zjNAk8MGHwXT84N2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-16 2:42 ` Nandakumar Chandrasekhar
[not found] ` <07c5c0cd-f115-476c-bd17-c1c31470602an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-17 15:33 ` Nandakumar Chandrasekhar
[not found] ` <08116215-7638-4f79-9261-2574aa1422e7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-04 16:56 ` John MacFarlane
[not found] ` <1EF73A39-A2CD-49D0-9F14-3EDDB1E85A23-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-12-04 17:09 ` John MacFarlane
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5859ff8-3e37-4794-9c85-ef6456cd73c1n@googlegroups.com \
--to=navanitachora-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).