From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv
Subject: Re: HTML5 redux
Date: Thu, 14 Aug 2014 22:26:45 +0200 [thread overview]
Message-ID: <53ED1B85.6070202@bsd.lv> (raw)
In-Reply-To: <20140814012540.GI26534@iris.usta.de>
> I don't object to that route.
>
> I'd probably not merge to the VERSION_1_12 branch until the release
> is done, and i'd probably merge to OpenBSD after the cleanup is done.
Ingo,
Ok! But as seen below, there's more to do before committing...
>> With this patch, both -Thtml and -Txhtml will produce HTML5. This
>> can be disabled in html.c by replacing the HTML_HTML5 allocation
>> with the respective type. The resulting HTML5 validates just fine,
>> as do the existing modes (if replaced in html.c).
>
> Not for me, there is one regression.
>
> But if you remove the chunk cited below, the regression goes
> away, so i'd say, go ahead - in particular if you plan to do the
> cleanup right afterwards.
This is a bit trickier than appears.
Basically, <p /> doesn't exist in HTML5 because <p> isn't a void
element. However, we can't just remove the auto-close parts of <p>
because then we might have
<p>
Hello
<div>world</div>
</p>
Which is invalid.
http://www.w3.org/TR/html-markup/p.html#p
In short, mdoc(7) and man(7) can have all sorts of nested block scopes,
and so can HTML, but <p> can't contain flow elements.
I think it's best, and cleanest, to just avoid <p> and use <div>, say as
<div class="par">.
I understand we lose whatever semantic-ness may be acquired from <p>,
but I don't think it's much of a loss given that, with a classed <div>,
we'll have *real* semantics (the flow elements will be within the
paragraph).
Naturally, this would work happily with HTML4 just as it would with HTML5.
I'll work on a patch and will submit it soon...
Best,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-14 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 22:23 Kristaps Dzonsons
2014-08-14 1:25 ` Ingo Schwarze
2014-08-14 20:26 ` Kristaps Dzonsons [this message]
2014-08-14 23:50 ` Ingo Schwarze
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=53ED1B85.6070202@bsd.lv \
--to=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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).