From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: tbl in -Thtml doesn't respect current font? Regression against 1.14.5
Date: Wed, 26 Oct 2022 18:16:58 +0200 [thread overview]
Message-ID: <20221026161658.u56cfcmkilztiwpi@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Given:
-- >8 --
a
.ft B
b
.TS
l.
c
.TE
d
.ft R
e
-- >8 --
mandoc (1.14.5-1 and current CVS) produces correct output
(ae in R, bcd in B) in -Tutf8/-Tps.
1.14.5-1 -Thtml yields:
-- >8 --
<div class="manual-text">a <b>b</b>
<table class="tbl">
<tr>
<td><b>c</b></td>
</tr>
</table>
<b>d</b> e</div>
-- >8 --
Which is correct.
CVS yields:
-- >8 --
<main class="manual-text">
a <b>b</b>
<table class="tbl">
<tr>
<td>c</td>
</tr>
</table>
<b>d</b> e
</main>
-- >8 --
Which isn't.
This is an obvious regression against 1.14.5-1.
наб
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-10-26 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221026161658.u56cfcmkilztiwpi@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=discuss@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).