From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from kerhand.co.uk (_smtpd@82-69-137-214.dsl.in-addr.zen.co.uk [82.69.137.214])
	by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id o4PMcwHP005203
	for <discuss@mdocml.bsd.lv>; Tue, 25 May 2010 16:38:59 -0600 (MDT)
Received: from localhost (1000@localhost [IPv6:::1])
	by kerhand.co.uk (OpenSMTPD) with ESMTP id 1274827135.jt7QtS0wUVdiVkKk
	for <discuss@mdocml.bsd.lv>; Tue, 25 May 2010 23:38:31 +0100 (BST)
Date: Tue, 25 May 2010 23:38:31 +0100
From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: .Li hiccup (and \*(Pu issue)
Message-ID: <20100525223855.GJ8074@bramka.kerhand.co.uk>
References: <20100525065543.GB8074@bramka.kerhand.co.uk> <4BFBCEBB.4070205@bsd.lv> <20100525141839.GG8074@bramka.kerhand.co.uk> <4BFC3639.8030409@bsd.lv>
X-Mailinglist: mdocml-discuss
Reply-To: discuss@mdocml.bsd.lv
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BFC3639.8030409@bsd.lv>
User-Agent: Mutt/1.4.2.3i

On Tue, May 25, 2010 at 10:42:33PM +0200, Kristaps Dzonsons wrote:
> 
> I respectively suggest, in this case, that the invocations be fixed.  I 
> think that people have confused `Li' as meaning "what follows is 
> interpreted in literal mode", instead of "is rendered in a fixed font", 
> as this behaviour is only used for `Li' and not for any other macro, to 
> wit (on OpenBSD):
> 
> % egrep 'Li [:.;] ' `cat manuals.txt `
> usr.sbin/bgpd/bgpd.conf.5:.Ar as-number Ns Li : Ns Ar local ,
> usr.sbin/bgpd/bgpd.conf.5:.Ar subtype Ar as-number Ns Li : Ns Ar local
> usr.sbin/bgpd/bgpd.conf.5:.Ar subtype Ar IP Ns Li : Ns Ar local
> usr.sbin/bgpd/bgpd.conf.5:.Ar as-number Ns Li : Ns Ar local
> usr.sbin/bgpd/bgpd.conf.5:.Ar as-number Ns Li : Ns Ar local ,
> usr.sbin/bgpd/bgpd.conf.5:.Ar subtype Ar as-number Ns Li : Ns Ar local
> usr.sbin/bgpd/bgpd.conf.5:.Ar subtype Ar IP Ns Li : Ns Ar local
> usr.sbin/bgpd/bgpd.conf.5:.Ar as-number Ns Li : Ns Ar local .
> usr.sbin/bgpd/bgpd.conf.5:.Ar IP Ns Li : Ns Ar local .
> bin/expr/expr.1:.It Ar expr1 Li : Ar expr2
> usr.bin/login/login.1:.Li : Ns Va style
> usr.bin/login/login.1:.Ar user Ns Li : Ns Va style ) .
> 
> Except for expr.1, these are actually trying to fix groff's behaviour of 
> the extra space!  So expr.1 is the only one that actually depends on 
> this crappy behaviour.
> 

so i will change expr.1, if ingo agrees.

> >oh, and while looking at this, i see another issue - we now have no
> >\*(Pu sequence for characters considered punctuation. at least
> >mdoc.samples.7 uses this (probably nothing else). new groff does not
> >recognise it, and its current equivalent man page, groff_mdoc.7 simply
> >lists the punctuation characters. i'm guessing you won;t see a need to
> >add the sequence, so should i just adjust our page?
> 
> We can temporarily define a chars.in for \*(Pu, but only mdoc.samples.7 
> in NetBSD and OpenBSD use this (NB, I don't know where FreeBSD's 
> mdoc.samples.7 is to look at it, but a grep over all the source can't 
> find the invocation).
> 
> Once our mdoc.7 replaces mdoc.samples.7, this won't be an issue.  I 
> suggest having a downstream chars.in patch for it, as I don't want to 
> put it in upstream and have people assume that it exists.  Then once 
> mdoc.7 takes over mdoc.samples.7, it can be removed.
> 
> Thoughts?
> 

i will change mdoc.samples.7 too, if ingo agrees.

jmc
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv