From: "John O'Regan" <john.a.oregan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: using pandoc to validate html
Date: Wed, 19 Jul 2017 12:54:14 +0100 [thread overview]
Message-ID: <CALwjjMia2ujP-5WOYZ0o2J00VAHKuj7+HDewm_A8mcmvbvHOfg@mail.gmail.com> (raw)
Hello All,
I used Pandoc to convert HTML to HTML. It stripped out all comments.
It also fixed badly-nested inline tags.
This made me wonder if Pandoc can tell if HTML input is valid or not,
which would come in very handy for my cmdPost project.
To be clear, I'd like to know if an HTML fragment is valid or not. I
don't care about the corrected HTML. Can Pandoc provide this
information? I'm using Windows 7, btw. I checked the ERRORLEVEL
environment variable, but malformed HTML didn't set the value to 1.
John
next reply other threads:[~2017-07-19 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 11:54 John O'Regan [this message]
[not found] ` <CALwjjMia2ujP-5WOYZ0o2J00VAHKuj7+HDewm_A8mcmvbvHOfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-23 8:01 ` 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=CALwjjMia2ujP-5WOYZ0o2J00VAHKuj7+HDewm_A8mcmvbvHOfg@mail.gmail.com \
--to=john.a.oregan-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).