From: Nicolas Joly <njoly@pasteur.fr>
To: discuss@mdocml.bsd.lv
Cc: Nicolas Joly <njoly@pasteur.fr>
Subject: Re: Small rendering difference between nroff and mandoc
Date: Sat, 17 Nov 2012 11:49:54 +0100 [thread overview]
Message-ID: <20121117104954.GA23280@lynche.sis.pasteur.fr> (raw)
In-Reply-To: <20121116185704.GB18695@iris.usta.de>
On Fri, Nov 16, 2012 at 07:57:04PM +0100, Ingo Schwarze wrote:
Hello Ingo,
> 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. 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.
>
> As far as i could reproduce, two particular macros were affected,
> namely .In and .Ap. I just fixed those two in both OpenBSD and bsd.lv.
>
> Should you find more, it would be kind if you could speak up again!
Thanks for the fix. I applied it to my local version and checked all
pages again ... A few differences remain with Cd, Fc, Fd, It(?) and
Lb mdoc macros. Seems that some man macros show a similar behaviour,
but i'll check that part later.
Here follow the corresponding pages and constructs :
/usr/share/man/man2/intro.2
.Bl -hang -width Ds
.It Er 0 Em "Error 0" .
Not used.
/usr/share/man/man2/i386_get_ldt.2
.Fd \*[Lt]i386/segments.h\*[Gt] .
These structures are defined by the architecture
/usr/share/man/man3/math.3
.Lb libm .
Declarations for these functions may be obtained from the include file
/usr/share/man/man3/mq.3
.Lb librt .
The process scheduling interface described in
/usr/share/man/man4/pim.4
The PIM-SM protocol is specified in RFC 2362 (to be replaced by
.%T draft-ietf-pim-sm-v2-new-* ) .
The PIM-DM protocol is specified in
/usr/share/man/man7/module.7
.Cd options INSECURE .
Refer to
/usr/share/man/man8/acorn32/nbfs.8
follow RISC OS conventions,as described in the various RISC OS
.%T User Guides .
The underlying FileCore instance used by
/usr/share/man/man9/errno.9
.Bl -hang -width Ds
.It Er \-2 EJUSTRETURN Em "Modify regs, just return" .
No more work is required and the function should just return.
/usr/share/man/man9/in_getifa.9
.Cd options IPSELSRC .
.Cd options IPSELSRC
lets the operator set the policy for choosing the source address
/usr/share/man/man9/percpu.9
the CPU-local storage held by
.Fa pc ,
run
.Fo "(*cb)"
.Fa "p"
.Fa "arg"
.Fa "ci"
.Fc .
Call this in thread context.
Thanks.
--
Nicolas Joly
Biology IT Center
Institut Pasteur, Paris.
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2012-11-17 10:49 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
2012-10-12 22:41 ` Nicolas Joly
2012-11-16 18:57 ` Ingo Schwarze
2012-11-17 10:49 ` Nicolas Joly [this message]
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=20121117104954.GA23280@lynche.sis.pasteur.fr \
--to=njoly@pasteur.fr \
--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).