From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Cc: Nicolas Joly <njoly@pasteur.fr>
Subject: Re: Small rendering difference between nroff and mandoc
Date: Fri, 12 Oct 2012 18:46:37 +0200 [thread overview]
Message-ID: <20121012164637.GA7552@iris.usta.de> (raw)
In-Reply-To: <20121012150036.GA22434@lynche.sis.pasteur.fr>
Salut Nicolas,
Nicolas Joly wrote on Fri, Oct 12, 2012 at 05:00:36PM +0200:
> I recently started checking for differences between nroff and mandoc
> output for the NetBSD manpages.
Nice to hear that, thanks!
> And noticed a small spacing difference
> between the tools. When a sentence ends with a macro followed by a
> punctuation mark mandoc does only output a single space character but
> nroff adds two.
Neither the groff nor the mandoc side is as simple as that.
For partial implicit block macros, mandoc does end-of-sentence (EOS)
spacing already, e.g.
.Pq enclosed .
following
Also, groff only does that when the punctuation mark appears isolated,
not when it appears at the end of a word, e.g.
.\" fstat(1)
.Ux Ns -domain.
A unidirectional
And groff doesn't do that when the isolated mark appears in the
middle of the line.
So, it only affects certain macros, and in a non-trivial way.
In OpenBSD base, i see one single instance of this issue,
in open(2).
In any case, this is rather rare and of relatively little impact,
compared to other remaining EOS issues. Still, it ought to be
fixed eventually. For now, i'm adding this to
http://mdocml.bsd.lv/cgi-bin/cvsweb/TODO?cvsroot=mdocml
- Trailing isolated dots lack EOS for some macros.
This cannot use mandoc_eos() because groff only does EOS
for isolated dots at least in some of these cases.
Affected macros included those using in_line_eoln().
Make sure to fix open(2)
without breaking fstat(1), ksh(1), tzset(3) and UKC(8).
reported by Nicolas Joly Fri, 12 Oct 2012 17:00:36 +0200
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2012-10-12 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:00 Nicolas Joly
2012-10-12 16:46 ` Ingo Schwarze [this message]
2012-10-12 22:41 ` Nicolas Joly
2012-11-16 18:57 ` Ingo Schwarze
2012-11-17 10:49 ` Nicolas Joly
2012-11-18 0:07 ` Ingo Schwarze
2012-11-19 13:31 ` Nicolas Joly
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=20121012164637.GA7552@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=njoly@pasteur.fr \
/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).