From: Mark Harris <mark.hsj@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: .br vertical spacing in html output
Date: Sat, 1 Dec 2018 13:31:05 -0800 [thread overview]
Message-ID: <fd14efed-283d-3921-1ae9-f0725481725b@gmail.com> (raw)
With -Thtml, with or without -Ostyle=mandoc.css, a roff .br (line break)
directive is producing a large vertical space between lines. This is
unexpected and does not occur with -Tascii/utf8. Here is an example:
--- foo.1 ---
.TH foo 1
.SH OPTIONS
.IP -a
Enable a
.IP -b
Enable b
.IP -c
The following lines are expected to be single-spaced:
Alpha
.br
Beta
.br
Gamma
.br
Delta
The lines are single-spaced as expected with -Tascii, but with -Thtml
there is a large amount of space between the lines.
.IP -d
Enable d
------
The missing vertical space between .IP paragraphs can be ameliorated by
removing the dl styling from the stylesheet, but I don't see an easy way
to address the extra .br spacing with the stylesheet. Is this something
that can be addressed in mandoc?
- Mark
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2018-12-01 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 21:31 Mark Harris [this message]
2018-12-02 17:21 ` Ingo Schwarze
2018-12-03 16:30 ` Ingo Schwarze
2018-12-04 3:38 ` Ingo Schwarze
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=fd14efed-283d-3921-1ae9-f0725481725b@gmail.com \
--to=mark.hsj@gmail.com \
--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).