From: Alejandro Colomar <alx@kernel.org>
To: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml: unwanted line break after bullet (.IP)
Date: Mon, 16 Oct 2023 19:28:40 +0200 [thread overview]
Message-ID: <ZS1yyDgLlsfW0j-J@debian> (raw)
In-Reply-To: <ZS1uhPglIoQJivIP@debian>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On Mon, Oct 16, 2023 at 07:10:22PM +0200, Alejandro Colomar wrote:
>
> But the mandoc(1) manual page says that if no CSS file is specified, it
> should embed a style sheet in the HTML, which seems to contradict the
> resulting HTML:
>
> ```html
> <!DOCTYPE html>
> <html>
> <head>
> <meta charset="utf-8"/>
> <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
> <link rel="stylesheet" href="mandoc.css" type="text/css" media="all"/>
> <title>TEST(1)</title>
> </head>
> ```
My bad here; I was testing both my command and your command, and
accidentally mixed the resulting files. I've re-tested, and if I don't
specify -Ostyle=mandoc.css, it embeds CSS. However, that CSS seems to
be defective, as it seems to produce the same results on firefox.
Here you can inspect the page with embedded CSS:
<https://www.alejandro-colomar.es/man/man0/test-20231016-02.0.html>
>
> mandoc(1):
> HTML Output
> ...
>
> The file /usr/share/misc/mandoc.css documents style‐sheet
> classes available for customising output. If a style‐sheet is
> not specified with -O style, -T html defaults to simple output
> (via an embedded style‐sheet) readable in any graphical or
> text‐based web browser.
>
>
> Is this a mandoc(1) bug? Or a packaging bug?
--
<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:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:17 Alejandro Colomar
2023-10-16 14:52 ` Ingo Schwarze
2023-10-16 15:20 ` Jan Stary
2023-10-16 15:43 ` Ingo Schwarze
2023-10-16 16:03 ` Ingo Schwarze
2023-10-16 17:10 ` Alejandro Colomar
2023-10-16 17:16 ` Alejandro Colomar
2023-10-16 17:28 ` Alejandro Colomar [this message]
2023-10-17 19:02 ` Ingo Schwarze
2023-10-17 21:39 ` Alejandro Colomar
2023-10-18 0:04 ` Ingo Schwarze
2023-10-18 11:32 ` Alejandro Colomar
2023-10-18 14:48 ` Ingo Schwarze
2023-10-18 14:56 ` Alejandro Colomar
2023-10-18 16:20 ` Ingo Schwarze
2023-10-18 18:52 ` Alejandro Colomar
2023-10-19 11:59 ` Ingo Schwarze
2023-10-19 12:48 ` 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=ZS1yyDgLlsfW0j-J@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).