From: Ingo Schwarze <schwarze@usta.de>
To: Jan Stary <hans@stare.cz>
Cc: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml: unwanted line break after bullet (.IP)
Date: Mon, 16 Oct 2023 17:43:13 +0200 [thread overview]
Message-ID: <ZS1aEeN8FXcEMXiI@asta-kit.de> (raw)
In-Reply-To: <ZS1UswPaKCTw_10G@www.stare.cz>
Hi Jan,
Jan Stary wrote on Mon, Oct 16, 2023 at 05:20:19PM +0200:
> On Oct 16 16:52:14, schwarze@usta.de wrote:
>> as expected, the "final text" follows on the same line.
> For completeness: it doesn't, in lynx.
> But that's on lynx, which seems to make the break after <dt>
Does Lynx provide any support for CSS whatsoever?
The lynx(1) manual page doesn't seem to mention CSS.
Using a web search engine to search the Lynx homepage for "CSS"
brings up a single page,
https://lynx.invisible-island.net/lynx2.8.8/breakout/CHANGES
and the two instances of the string "CSS" on that page give me
the impression that lynx(1) likely does not have any CSS support.
The non-authoritative page
https://shkspr.mobi/blog/2020/12/how-and-why-to-use-lynx-the-faster-web-browser/
explicitly claims that it has no CSS support.
As i said, expecting any particular whitespace formatting when
processing HTML input is completely unreasonable without correctly
working CSS support. The HTML language simply isn't designed for
anything like that.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2023-10-16 15:43 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 [this message]
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
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=ZS1aEeN8FXcEMXiI@asta-kit.de \
--to=schwarze@usta.de \
--cc=hans@stare.cz \
--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).