[-- Attachment #1: Type: text/plain, Size: 461 bytes --] Hi folks, Thanks for this great and useful tool. 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 [-- Attachment #2: Type: text/html, Size: 1178 bytes --]
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 -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
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
Hi Mohamed, Mohamed Akram wrote on Sun, Jun 26, 2022 at 04:41:18PM +0000: > Thanks for your response. I did skim the TODO but I think I wasn’t > sure if that was the same bug. No problem, duplicate reports also help me prioritize because they tell me that more people feel affected. Then again, that's not a guarantee that time for the fix will be found more quickly. > I’ll keep an eye out for a new release. It is likely that after the bug will be fixed, a few more months may go by until the next release comes. I'm also in the habit of notifiying bug reporters right after fixing their bugs, such that they can pick up and use the patch until the release comes, if they want to, and such that they can test whether the patch really fixes the problem for them. Yours, Ingo -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
> On Jun 26, 2022, at 9:02 PM, Ingo Schwarze <schwarze@usta.de> wrote:
>
> I'm also in the habit of notifiying bug reporters right after fixing
> their bugs, such that they can pick up and use the patch until the
> release comes, if they want to, and such that they can test
> whether the patch really fixes the problem for them.
That’s really awesome. A patch would be sufficient in my case since I’m just running this on my machine. Also, if anyone else comes across this I found a little workaround in the meantime using some sed magic:
mandoc -T html file | sed '/<pre>/,/<\/pre>/{/^<br\/>$/d;}’
Mohamed