From: Ingo Schwarze <schwarze@usta.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP
Date: Mon, 16 Oct 2023 18:28:05 +0200 [thread overview]
Message-ID: <ZS1klbvLf5Sc1oeF@asta-kit.de> (raw)
In-Reply-To: <ZS0fTrkKhpYLf0R7@debian>
Hi Alejandro,
Alejandro Colomar wrote on Mon, Oct 16, 2023 at 01:32:30PM +0200:
> groff -man -Thtml seems to never produce a blank line before a TP.
What do you mean by "blank line"?
I'm not aware that any such concept is defined in HTML,
at least not outside the "pre" element (and possibly a few
elements similar to "pre").
> mandoc -man -Thtml produces one in some cases, and I can't see a
> pattern.
>
> I found this bug while reading feature_test_macros(7) in the Debian
> online manpages:
> <https://manpages.debian.org/bullseye/manpages/ftm.7.en.html>
>
> To reproduce this bug, run the following in the Linux man-pages repo:
>
> 1999 groff -man -T html man7/feature_test_macros.7 > ftm.g.html
> 2000 open ftm.g.html
> 2001 mandoc -man -T html man7/feature_test_macros.7 > ftm.m.html
> 2002 open ftm.m.html
You can see that particular page rendered here:
https://man.bsd.lv/Test/ftm.7
It is a long page, and i have been unable to figure out what exactly
you are talking about.
Please point me to the precise position in the file where vertical
spacing before a .TP macro feels lacking or execessive to you,
for example by giving the exact text following that .TP macro,
and ideally also provide an example of where you feel vertical
spacing is about right.
Also note that comparing to groff -T html output is completely
useless because groff -T html output is of utterly atrocious
quality, violating the HTML standard in almost every way imaginable.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2023-10-16 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:32 Alejandro Colomar
2023-10-16 16:28 ` Ingo Schwarze [this message]
2023-10-16 17:22 ` Alejandro Colomar
2023-10-19 14:45 ` Ingo Schwarze
2023-10-19 15:10 ` Ingo Schwarze
2023-10-19 15:17 ` Alejandro Colomar
2023-10-19 16:19 ` Ingo Schwarze
2023-10-19 21:32 ` Alejandro Colomar
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=ZS1klbvLf5Sc1oeF@asta-kit.de \
--to=schwarze@usta.de \
--cc=alx@kernel.org \
--cc=tech@mandoc.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).