discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Nicolas Joly <njoly@pasteur.fr>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv, Nicolas Joly <njoly@pasteur.fr>
Subject: Re: Small rendering difference between nroff and mandoc
Date: Sat, 13 Oct 2012 00:41:46 +0200	[thread overview]
Message-ID: <20121012224146.GA21963@lynche.sis.pasteur.fr> (raw)
In-Reply-To: <20121012164637.GA7552@iris.usta.de>

On Fri, Oct 12, 2012 at 06:46:37PM +0200, Ingo Schwarze wrote:
> 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!

Yep. I find that way a few strange/bad/... constructs that render
differently with both formatters.

> > 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.

Otherwise it would have already been fixed ;)

[...]
> In OpenBSD base, i see one single instance of this issue,
> in open(2).

Actually i do see about 150 man pages in the NetBSD base system
(e.g. in /usr/share/man) that exhibit a similar behaviour ...

> 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

Thanks.

-- 
Nicolas Joly

Biology IT Center
Institut Pasteur, Paris.
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2012-10-12 22:40 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 [this message]
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=20121012224146.GA21963@lynche.sis.pasteur.fr \
    --to=njoly@pasteur.fr \
    --cc=discuss@mdocml.bsd.lv \
    --cc=schwarze@usta.de \
    /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).