From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: .Li hiccup (and \*(Pu issue)
Date: Tue, 25 May 2010 23:38:31 +0100 [thread overview]
Message-ID: <20100525223855.GJ8074@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4BFC3639.8030409@bsd.lv>
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
next prev parent reply other threads:[~2010-05-25 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100525065543.GB8074@bramka.kerhand.co.uk>
[not found] ` <4BFBCEBB.4070205@bsd.lv>
[not found] ` <20100525141839.GG8074@bramka.kerhand.co.uk>
2010-05-25 20:42 ` Kristaps Dzonsons
2010-05-25 22:38 ` Jason McIntyre [this message]
2010-05-25 23:28 ` Ingo Schwarze
2010-05-26 0:49 ` Kristaps Dzonsons
2010-05-26 6:56 ` Jason McIntyre
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=20100525223855.GJ8074@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--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).