From: "Anthony J. Bentley" <firstname.lastname@example.org>
To: Ingo Schwarze <email@example.com>
Subject: Re: HTML5
Date: Sun, 10 Aug 2014 11:38:34 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Hi Ingo and Kristaps,
Ingo Schwarze writes:
> Why not? What downside do you see?
I tried to come up with a technical justification to use HTML4 but
could only come up with aesthetic reasons. And along the way realized
two truths about HTML5 that make me uncomfortable in my decision: first,
that parsing HTML5 really is both simpler and more well-defined (HTML4
still had delusions of SGML-grandeur), and second, that there really is
no sane way to format equations in HTML4; I had not considered the
possibility of eqn at all. So consider my objection to HTML5 output
> > And if we do that, is there any point to switching doctypes?
> Yes, one minor and one major.
> The minor is less doctype/content-type clutter.
> The major is to get MathML for eqn.
> That also explains why i think validating against both 5 and 4.01
> (for non-eqn content) does have some merit. Again, if that is
> possible, but as far as i understand, it is.
I don't think this is possible; the whole reason Kristaps' patch
can unify things is because it uses some XML-like syntax that is valid
in HTML5 and invalid in HTML4. Despite that, per above I have no
objections to doing that at this point.
Anthony J. Bentley
To unsubscribe send an email to email@example.com
prev parent reply other threads:[~2014-08-10 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:33 HTML5 Kristaps Dzonsons
2014-08-10 2:23 ` HTML5 Ingo Schwarze
2014-08-10 11:39 ` HTML5 Kristaps Dzonsons
2014-08-10 16:12 ` HTML5 Ingo Schwarze
2014-08-10 4:33 ` HTML5 Anthony J. Bentley
2014-08-10 15:17 ` HTML5 Ingo Schwarze
2014-08-10 17:38 ` Anthony J. Bentley [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).