From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: double space after `.' issue
Date: Thu, 23 Sep 2010 18:13:39 +0059 [thread overview]
Message-ID: <20100923171403.GM13645@bramka.kerhand.co.uk> (raw)
hi. source from disklabel(8):
The disk label contains information about disk characteristics
.Pq size, type, etc.
and the partition layout, stored on the disk itself.
groff:
The disk label contains information about disk characteristics
(size, type, etc.) and the partition layout, stored on the disk
itself.
mandoc:
The disk label contains information about disk characteristics
(size, type, etc.) and the partition layout, stored on the disk
itself.
i.e. mandoc produces a double space before "and".
groff and mandoc are handling that .Pq line differently. is this on a
TODO list, or do i need to change the source?
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2010-09-23 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 17:14 Jason McIntyre [this message]
2010-09-23 19:51 ` 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=20100923171403.GM13645@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@mdocml.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).