From: Mohamed Akram <mohd.akram@outlook.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: "discuss@mandoc.bsd.lv" <discuss@mandoc.bsd.lv>
Subject: Re: mandoc inserts extraneous <br> tags inside <pre>
Date: Sun, 26 Jun 2022 16:41:18 +0000 [thread overview]
Message-ID: <2A10D5C8-D412-4875-9D64-AD888DE22ACB@outlook.com> (raw)
In-Reply-To: <YrhAKP9m38G2u8lO@asta-kit.de>
Hi Ingo,
Thanks for your response. I did skim the TODO but I think I wasn’t sure if that was the same bug. I’ll keep an eye out for a new release.
Mohamed
> On Jun 26, 2022, at 3:16 PM, Ingo Schwarze <schwarze@usta.de> wrote:
>
> Hello Mohamed,
>
> Mohamed Akram wrote on Sat, Jun 25, 2022 at 04:28:18PM +0000:
>
>> Thanks for this great and useful tool.
>
> You are welcome.
>
>> I did notice a bug however in mandoc when using HTML output.
>> It seems to insert <br> tags inside <pre> sections, which causes
>> there to be double newlines since <pre> already preserves newlines.
>> You can see it in this example which has many code samples in it:
>>
>> curl https://raw.githubusercontent.com/apple-oss-distributions/tcl/tcl-134.121.2/tcl_ext/expect/expect/expect.man | mandoc -T html >example.html
>
> I believe that is the following bug already listed in the mandoc TODO file:
>
> - HTML formatting of .nf should avoid <br/>
> and not close and re-open <pre> on .P
> my mail to ports@ 27 Jun 2021 16:09:20 +0200
> loc ** exist ** algo * size * imp **
>
> I'm expanding the entry a bit to read:
>
> - HTML formatting of .nf should avoid <br/>,
> even when input lines start with whitespace,
> and not close and re-open <pre> on .P
> my mail to ports@ 27 Jun 2021 16:09:20 +0200
> reported again by Mohamed Akram 25 Jun 2022 16:28:18 +0000
> loc ** exist ** algo * size * imp **
>
> This is one among the bugs likely to get addressed during the next round
> of less-important bug fixes. It is less important in so far as a few
> bugs that can crash mandoc are still open. There is no specific time
> frame, but a delay of a few more months is likely.
>
> Thanks for reporting!
>
> Yours,
> Ingo
next prev parent reply other threads:[~2022-06-26 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 16:28 Mohamed Akram
2022-06-26 11:16 ` Ingo Schwarze
2022-06-26 16:41 ` Mohamed Akram [this message]
2022-06-26 17:02 ` Ingo Schwarze
2022-06-26 17:29 ` Mohamed Akram
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=2A10D5C8-D412-4875-9D64-AD888DE22ACB@outlook.com \
--to=mohd.akram@outlook.com \
--cc=discuss@mandoc.bsd.lv \
--cc=schwarze@usta.de \
/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).