From: Alejandro Colomar <alx@kernel.org>
To: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP
Date: Mon, 16 Oct 2023 19:22:11 +0200 [thread overview]
Message-ID: <ZS1xRG55oh25kZGf@debian> (raw)
In-Reply-To: <ZS1klbvLf5Sc1oeF@asta-kit.de>
[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]
Hi Ingo,
On Mon, Oct 16, 2023 at 06:28:05PM +0200, Ingo Schwarze wrote:
> 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"?
What my eyes experience as a relatively large inter-paragraph space.
> 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
I don't see the bug there. I'm going to guess it's just another case of
a missing CSS file.
>
> 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,
In the Debian bullseye page, check the inter-paragraph space before the
tag _LARGEFILE64_SOURCE (I see a long vertical space) and the tag
_LARGEFILE_SOURCE.
> for example by giving the exact text following that .TP macro,
The lines after the tags say
"Expose definitions for the alternative API specified by the LFS"
and
"This macro was historically used to expose certain functions"
respectively.
> and ideally also provide an example of where you feel vertical
> spacing is about right.
The page you posted in <man.bsd.lv> seems right to me.
>
> 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.
:)
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-16 17:22 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
2023-10-16 17:22 ` Alejandro Colomar [this message]
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=ZS1xRG55oh25kZGf@debian \
--to=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).