From: Paul Onyschuk <blink@bojary.koba.pl>
To: discuss@mdocml.bsd.lv
Subject: Inconsistent sentence spacing
Date: Sun, 3 Jul 2011 17:57:40 +0200 [thread overview]
Message-ID: <20110703175740.ad50c2f6.blink@bojary.koba.pl> (raw)
Sub-section "Sentence Spacing" in mdoc(7) is a bit enigmatic for me.
With following example from manual page:
> .Xr mandoc 1 .
> .Fl T Ns Cm ascii .
Output looks like this:
> mandoc(1). -Tascii.
There isn't trailing space at end of the line, so I'm not sure where
double whitespace cames from. Morover changing period to comma will
give only one space:
> .Xr mandoc 1 ,
> .Fl T Ns Cm ascii .
Output:
> mandoc(1), -Tascii.
Shouldn't first example behave same as:
> .Xr mandoc 1 . No Fl T Ns Cm ascii .
which gives also one whitespace?
Same (double whitespace) comes with exclamation and question marks. Is
that intended behavior?
--
Paul Onyschuk <blink@bojary.koba.pl>
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2011-07-03 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 15:57 Paul Onyschuk [this message]
2011-07-03 16:21 ` Ingo Schwarze
2011-07-03 19:50 ` Paul Onyschuk
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=20110703175740.ad50c2f6.blink@bojary.koba.pl \
--to=blink@bojary.koba.pl \
--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).