From MAILER-DAEMON Wed Apr 05 10:18:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cvllg-00010n-LS
	for mharc-groff@gnu.org; Wed, 05 Apr 2017 10:18:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42964)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tkurtbond@gmail.com>) id 1cvlle-0000zi-E9
	for groff@gnu.org; Wed, 05 Apr 2017 10:18:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tkurtbond@gmail.com>) id 1cvllc-00085Y-Kr
	for groff@gnu.org; Wed, 05 Apr 2017 10:18:38 -0400
Received: from mail-lf0-x22a.google.com ([2a00:1450:4010:c07::22a]:36581)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <tkurtbond@gmail.com>) id 1cvllc-000851-Cj
	for groff@gnu.org; Wed, 05 Apr 2017 10:18:36 -0400
Received: by mail-lf0-x22a.google.com with SMTP id x137so9604591lff.3
	for <groff@gnu.org>; Wed, 05 Apr 2017 07:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=0tT5hNpUoBwZr0lBqUsidFamNg7TdBJg0fS0mJrgD+k=;
	b=f8IE3IopiBtmFQsPuCyA31jKQizLa/UQ8y2EEej+lc4p4yPXY3wxFQ5Q7rlSrI4tJq
	Y2WjXOicvIE0GykC3tYHzyoVhS3GGuGv7c8SntUqpF8TiCogSANT+Tv9J3zFf79MM3pw
	6gJ2OETl6Mylp4wnbk785Zc1mQWe8wzcxiL08MxTw0taQmS9FcdoKVhObuNmTYGNBN0E
	cBJQh+grE2WX9Rs9YVSucs44MYRUNCT4LxA9qk4MEBQq3+WFIYoU4d5IJ1Pe38swl5CM
	9W5Uo1OJjFaqzuQxUYG0PrX9hkcFVLDiv/gUfi5x7eyFKW1LFwa8V9TBZc0sw4cd6rKB
	zxbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=0tT5hNpUoBwZr0lBqUsidFamNg7TdBJg0fS0mJrgD+k=;
	b=NlVvSoM725ikqWddT/JA6seqDnx8n3QTMRH6aLcDvCDSbTxpXnqdKj0jnVjQUeC/qW
	FweKZhlTeR5HYmp3Vx6l7Zs99AkgTP8Xlre+Y50rfn59DmGDvIpgKozaw8+BYgqqqOby
	GOfzoThEgM5DO8xseDuITlDCveTjbq17Vu3bw72VMEFW2n+7XOJII1EA9OuX0Gdkue8x
	vWvW3J01ws81IaTEa19F8x3Vk2OFaJUpZFoEtyY6Uv4Y6GcnDEQrYCL5W08wxPqqQFRb
	WrK/ae8NORD224AhjEeQgVMsXV3kSKDASrrkXV0sLOjq7odliPvOP5IWQXt5Ns218suW
	Rt1g==
X-Gm-Message-State: AFeK/H1sEroFyhE4m64SGd3kflA3spqk5WxEUXlT4M3QYdd36IuFva62w7ChUNaAmUZ2NZsnQhXVgqrdOZlsew==
X-Received: by 10.25.125.11 with SMTP id y11mr10155184lfc.101.1491401914678;
	Wed, 05 Apr 2017 07:18:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.205.69 with HTTP; Wed, 5 Apr 2017 07:18:34 -0700 (PDT)
From: "T. Kurt Bond" <tkurtbond@gmail.com>
Date: Wed, 5 Apr 2017 10:18:34 -0400
Message-ID: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
To: groff@gnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1450:4010:c07::22a
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: [Groff] Trying to use tabs and tab stops in groff
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 14:18:39 -0000

Hello,

I'm trying to use tabs and tab stops in groff to so some simple tables, and
can't figure out why it is not working.  Here's the input:

.\" groff -mm tabs.mm | ps2pdf - tabs.pdf
.P
A sentence to start the example.
.\" http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/ch08.htm
.\" output should look something like:
.\"
http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/art/08/08unx25.gif
.nf
.ta 3i 4.5i
Name\tBirthday\tTelephone

John Smith\t1/1/70\t(410) 555-1111
Dave Jones\t2/2/63\t(311) 800-0000
.tc -
Bob Williams\t3/3/56\t(999) 555-2222
.fi
.P
A sentence to end the example.


I get a result with everything smashed together, as if the "\t"s weren't
there at all.

Any idea what I'm doing wrong?

-- 
T. Kurt Bond, tkurtbond@gmail.com

From MAILER-DAEMON Wed Apr 05 10:39:54 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cvm6E-0007br-KQ
	for mharc-groff@gnu.org; Wed, 05 Apr 2017 10:39:54 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48724)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mbianchi@foveal.com>) id 1cvm6D-0007bl-1f
	for groff@gnu.org; Wed, 05 Apr 2017 10:39:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mbianchi@foveal.com>) id 1cvm68-0001ky-5L
	for groff@gnu.org; Wed, 05 Apr 2017 10:39:53 -0400
Received: from relay01.pair.com ([209.68.5.15]:37069)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mbianchi@foveal.com>) id 1cvm68-0001i2-0Z
	for groff@gnu.org; Wed, 05 Apr 2017 10:39:48 -0400
Received: from foveal8 (pool-74-105-229-180.nwrknj.fios.verizon.net
	[74.105.229.180])
	by relay01.pair.com (Postfix) with ESMTP id 0E227D01104
	for <groff@gnu.org>; Wed,  5 Apr 2017 10:39:42 -0400 (EDT)
Received: by foveal8 (Postfix, from userid 617)
	id C988011E0042; Wed,  5 Apr 2017 10:39:41 -0400 (EDT)
Resent-From: Mike Bianchi <mbianchi@foveal5.foveal.com>
Resent-Date: Wed, 5 Apr 2017 10:39:41 -0400
Resent-Message-ID: <20170405143941.GA13584@foveal5.foveal.com>
Resent-To: groff@gnu.org
Date: Wed, 5 Apr 2017 10:37:05 -0400
From: Mike Bianchi <MBianchi@Foveal.com>
To: "T. Kurt Bond" <tkurtbond@gmail.com>
Message-ID: <20170405143705.GA12600@foveal5.foveal.com>
References: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Trying to use tabs and tab stops in groff
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 14:39:54 -0000

I cannot see what you are doing wrong (why the \t is not seen as a tab)
but if you change all your  \t  to actual  tab  characters you get:

	Name                          Birthday       Telephone

	John Smith                    1/1/70         (410) 555=E2=80=901111
	Dave Jones                    2/2/63         (311) 800=E2=80=900000
	Bob Williams=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=
=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=
=E2=80=90=E2=80=90=E2=80=903/3/56=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=
=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90(999) 555=E2=80=902222

									Mike

On Wed, Apr 05, 2017 at 10:18:34AM -0400, T. Kurt Bond wrote:
> Hello,
>=20
> I'm trying to use tabs and tab stops in groff to so some simple tables,=
 and
> can't figure out why it is not working.  Here's the input:
>=20
> .\" groff -mm tabs.mm | ps2pdf - tabs.pdf
> .P
> A sentence to start the example.
> .\" http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/ch08.htm
> .\" output should look something like:
> .\"
> http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/art/08/08unx=
25.gif
> .nf
> .ta 3i 4.5i
> Name\tBirthday\tTelephone
>=20
> John Smith\t1/1/70\t(410) 555-1111
> Dave Jones\t2/2/63\t(311) 800-0000
> .tc -
> Bob Williams\t3/3/56\t(999) 555-2222
> .fi
> .P
> A sentence to end the example.
>=20
>=20
> I get a result with everything smashed together, as if the "\t"s weren'=
t
> there at all.
>=20
> Any idea what I'm doing wrong?
>=20
> --=20
> T. Kurt Bond, tkurtbond@gmail.com

--=20
 Mike Bianchi
 Foveal Systems

 973 822-2085

 MBianchi@Foveal.com
 http://www.AutoAuditorium.com
 http://www.FovealMounts.com


From MAILER-DAEMON Wed Apr 05 14:04:07 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cvpHr-0000pv-Ix
	for mharc-groff@gnu.org; Wed, 05 Apr 2017 14:04:07 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56048)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1cvpHo-0000pl-SU
	for groff@gnu.org; Wed, 05 Apr 2017 14:04:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1cvpHl-0007lg-QW
	for groff@gnu.org; Wed, 05 Apr 2017 14:04:04 -0400
Received: from relay01.pair.com ([209.68.5.15]:48155)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1cvpHl-0007kJ-NJ
	for groff@gnu.org; Wed, 05 Apr 2017 14:04:01 -0400
Received: from orac.inputplus.co.uk (83.199.189.80.dyn.plus.net
	[80.189.199.83])
	by relay01.pair.com (Postfix) with ESMTP id E8557D00A60;
	Wed,  5 Apr 2017 14:03:56 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id E7DC21FE95;
	Wed,  5 Apr 2017 19:03:55 +0100 (BST)
To: "T. Kurt Bond" <tkurtbond@gmail.com>
cc: groff@gnu.org
mail-followup-to: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
References: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
Date: Wed, 05 Apr 2017 19:03:55 +0100
Message-Id: <20170405180355.E7DC21FE95@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Trying to use tabs and tab stops in groff
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 18:04:06 -0000

Hi Kurt,

> I'm trying to use tabs and tab stops in groff to so some simple
> tables, and can't figure out why it is not working.

Mike pointed out you need real ASCII tab characters to have your example
work.  `\t' is used in `copy mode', e.g. when defining a macro, to
create a tab that's interpreted later, e.g. when the macro is invoked.

    $ printf '%s\n' .nf '.de m' 'foo\tbar' 'x\ty\tz\tz\ty' .. .m |
    > nroff | grep .
    foo     bar
    x       y       z       z       y
    $

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Wed Apr 05 14:07:54 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cvpLW-0001s2-SK
	for mharc-groff@gnu.org; Wed, 05 Apr 2017 14:07:54 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57289)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tkurtbond@gmail.com>) id 1cvpLU-0001rp-2l
	for groff@gnu.org; Wed, 05 Apr 2017 14:07:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tkurtbond@gmail.com>) id 1cvpLT-0001Hn-2d
	for groff@gnu.org; Wed, 05 Apr 2017 14:07:52 -0400
Received: from mail-lf0-x232.google.com ([2a00:1450:4010:c07::232]:34585)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <tkurtbond@gmail.com>) id 1cvpLS-0001H2-Qh
	for groff@gnu.org; Wed, 05 Apr 2017 14:07:50 -0400
Received: by mail-lf0-x232.google.com with SMTP id z15so14257532lfd.1
	for <groff@gnu.org>; Wed, 05 Apr 2017 11:07:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=MP+Pk9aRPpDGk9FMuMS3bDQylbUrVqHaZM84eIWPWJw=;
	b=QE8HJxmgpPSDnVapsMxvDTAXk++T5hl3k+C5Jgr50EwOEY3RCi/mkHebnzksG+umJh
	cFiA0ql/hABKPQ8ckoMmUCSJb4/rcnE4BdXPAvQBnzif0RsaSxQmisES2336NbRffSUC
	QFxqDAV3/Dsf7ROKnyqiutCJjUHUQ3h5mhTcVw3bnjFXf8e0gv9uRiuZmJDCsn3IpAMc
	O+rPCLJ+r3VrHDuqej4cr0im/q1lbEeYkeBSulm3OHs5fNKOs482x8cRcUmUYRva1rGo
	NPzzKVG1a+SrMjkYbFBIQkVNitviLLNOcZQGS9JcjI7UVO8u4BHzWutNX6hnqOUUHeiA
	pcyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=MP+Pk9aRPpDGk9FMuMS3bDQylbUrVqHaZM84eIWPWJw=;
	b=h7J8oZmiPy8gsxxmWkrQj9irn4l5MlmEWk5MHtqJ4I7rxSlTnTu1TXAQSVfQECJlUX
	+TPqGRwMERewHCyrxHRsla69jSiQp6SK6gm+iAwyJIvMeHEgAuoIKmWUb6w5OlqYclrT
	NjgO8K1WUUre9M1iRdxRbKKr4GAkyKWxhKiK2pvJd5MKZsKSnr/FNAsEZM/r7fo6NHli
	2hr5V0VaoTPnA1vac/31m2L9dKb5xLXzpxFVXGZpXbb5iOyaNFCAFtVqGPEEgNtFqOk2
	7++cYTDd7QaZMEq7z3x+gYAUj/vJeg79XyymJF1e15eqjiM8+toWOtKc2ShWKKjdtGvq
	+C0Q==
X-Gm-Message-State: AFeK/H3eLlG8Wpn71FSRM9QxL3lpomxd9pqXoOq4mtRuRCGB4uoPEzhYKTvdkbNoLXcwR8HjrHv1qrgWVc2mQQ==
X-Received: by 10.46.1.220 with SMTP id f89mr9371072lji.7.1491415667901; Wed,
	05 Apr 2017 11:07:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.205.69 with HTTP; Wed, 5 Apr 2017 11:07:47 -0700 (PDT)
In-Reply-To: <20170405180355.E7DC21FE95@orac.inputplus.co.uk>
References: <CAN1EhV8TT-2j=_r1e_9g_GPepW+fPktxpjaL0b0H4K_qg4jNTQ@mail.gmail.com>
	<20170405180355.E7DC21FE95@orac.inputplus.co.uk>
From: "T. Kurt Bond" <tkurtbond@gmail.com>
Date: Wed, 5 Apr 2017 14:07:47 -0400
Message-ID: <CAN1EhV8xr2KFwb7V=OO2BvyeQqi6JtHG3gx8=7Zy8dD3NjKHKA@mail.gmail.com>
To: groff@gnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1450:4010:c07::232
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Trying to use tabs and tab stops in groff
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 18:07:53 -0000

Ok, now it makes sense.  Thanks to both of you!

On Wed, Apr 5, 2017 at 2:03 PM, Ralph Corderoy <ralph@inputplus.co.uk>
wrote:

> Hi Kurt,
>
> > I'm trying to use tabs and tab stops in groff to so some simple
> > tables, and can't figure out why it is not working.
>
> Mike pointed out you need real ASCII tab characters to have your example
> work.  `\t' is used in `copy mode', e.g. when defining a macro, to
> create a tab that's interpreted later, e.g. when the macro is invoked.
>
>     $ printf '%s\n' .nf '.de m' 'foo\tbar' 'x\ty\tz\tz\ty' .. .m |
>     > nroff | grep .
>     foo     bar
>     x       y       z       z       y
>     $
>
> --
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy
>



-- 
T. Kurt Bond, tkurtbond@gmail.com and http://unwind-protect.org/~tkb/
<http://unwind-protect.org/%7Etkb/>

From MAILER-DAEMON Wed Apr 05 14:59:19 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cvq9H-00032w-Iv
	for mharc-groff@gnu.org; Wed, 05 Apr 2017 14:59:19 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48334)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1cvq9F-00031m-Fy
	for groff@gnu.org; Wed, 05 Apr 2017 14:59:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1cvq9C-0000Qk-HC
	for groff@gnu.org; Wed, 05 Apr 2017 14:59:17 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:41528)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1cvq9C-0000QO-Bx
	for groff@gnu.org; Wed, 05 Apr 2017 14:59:14 -0400
Received: from tahoe.cs.Dartmouth.EDU (tahoe.cs.dartmouth.edu [129.170.212.20])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v35IxClH015061
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
	for <groff@gnu.org>; Wed, 5 Apr 2017 14:59:12 -0400
Received: from tahoe.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by tahoe.cs.Dartmouth.EDU (8.15.2/8.14.3) with ESMTP id v35IxCi4130453
	for <groff@gnu.org>; Wed, 5 Apr 2017 14:59:12 -0400
Received: (from doug@localhost)
	by tahoe.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v35IxBU8130452
	for groff@gnu.org; Wed, 5 Apr 2017 14:59:11 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704051859.v35IxBU8130452@tahoe.cs.Dartmouth.EDU>
Date: Wed, 05 Apr 2017 14:59:11 -0400
To: groff@gnu.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: Re: [Groff] Trying to use tabs and tab stops in groff
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 18:59:18 -0000

> I cannot see what you are doing wrong (why the \t is not seen as a tab)

>From the troff user's manual: "\t   Non-interpreted horizontal tab"


From MAILER-DAEMON Mon Apr 10 19:05:06 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cxiMs-0006bS-Iy
	for mharc-groff@gnu.org; Mon, 10 Apr 2017 19:05:06 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54348)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bertrand.garrigues@laposte.net>) id 1cxiMq-0006bL-Bt
	for groff@gnu.org; Mon, 10 Apr 2017 19:05:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bertrand.garrigues@laposte.net>) id 1cxiMm-000375-Ga
	for groff@gnu.org; Mon, 10 Apr 2017 19:05:04 -0400
Received: from smtpoutz29.laposte.net ([194.117.213.104]:51358
	helo=smtp.laposte.net)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <bertrand.garrigues@laposte.net>)
	id 1cxiMm-00031u-5A
	for groff@gnu.org; Mon, 10 Apr 2017 19:05:00 -0400
Received: from smtp.laposte.net (localhost [127.0.0.1])
	by lpn-prd-vrout017 (Postfix) with ESMTP id C9553A04AAB
	for <groff@gnu.org>; Tue, 11 Apr 2017 01:04:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=laposte.net; s=mail0;
	t=1491865472; bh=urBtVDnqDHp2hBLa0xtO8zFR1QqeHw3EqAWDT3HTF94=;
	h=From:To:Cc:Subject:References:Date:In-Reply-To;
	b=DKTFJ+T7JtqP3TfME5/vHq2ftlVrpYmiS3hV/SpNSKPO1ZBCx87CnECLcs/wEf/iV
	votn+BR7SCFkmga7Y5cliSlsxhkDi0rHVInTpZ41uA/7ORiYOpEv7TdYS6kurOdCg2
	yTkJzqmSwvT40NWgnGrq0u5ffQdUUYyx+ZUXIWNkGOFAjl9lwyxblXiUM3T0T+Yl6n
	1qMUFb7K4gFroeMgJyErvkZCgmPZgct1ekkcCps7IAI9blxVdEJBmKfMKOnJ6sB8GI
	epJhTy8tSVuYaduLnKn5a15VSf4N703qlCghwDw/iLnveCmRkdZvAzjqbOxeRHFUqc
	bIiWOiIXuQ5YQ==
Received: from smtp.laposte.net (localhost [127.0.0.1])
	by lpn-prd-vrout017 (Postfix) with ESMTP id BCBCDA04ABE
	for <groff@gnu.org>; Tue, 11 Apr 2017 01:04:32 +0200 (CEST)
Received: from lpn-prd-vrin004 (lpn-prd-vrin004.prosodie [10.128.63.5])
	by lpn-prd-vrout017 (Postfix) with ESMTP id AFEE6A04AAB
	for <groff@gnu.org>; Tue, 11 Apr 2017 01:04:32 +0200 (CEST)
Received: from lpn-prd-vrin004 (localhost [127.0.0.1])
	by lpn-prd-vrin004 (Postfix) with ESMTP id 9CB8D711354
	for <groff@gnu.org>; Tue, 11 Apr 2017 01:04:32 +0200 (CEST)
Received: from hsiaomi. (jau72-h04-89-95-237-97.dsl.sta.abo.bbox.fr
	[89.95.237.97])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by lpn-prd-vrin004 (Postfix) with ESMTPSA id 49DE97112FA;
	Tue, 11 Apr 2017 01:04:31 +0200 (CEST)
From: Bertrand Garrigues <bertrand.garrigues@laposte.net>
To: Peter Schaffter <peter@schaffter.ca>
Cc: groff@gnu.org
References: <20170227032334.26858.92818@vcs0.savannah.gnu.org>
	<20170227032335.686FA2600F@vcs0.savannah.gnu.org>
	<877f4bl114.fsf@laposte.net> <20170227231755.GE9845@augustus>
	<87a88z4dk6.fsf@laposte.net> <20170305231835.GA19621@augustus>
	<87fuiqhumd.fsf@laposte.net>
Date: Tue, 11 Apr 2017 01:04:30 +0200
In-Reply-To: <87fuiqhumd.fsf@laposte.net> (Bertrand Garrigues's message of
	"Tue, 07 Mar 2017 00:07:38 +0100")
Message-ID: <87lgr7euf5.fsf@laposte.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-VR-SrcIP: 89.95.237.97
X-VR-FullState: 0
X-VR-Score: -100
X-VR-Cause-1: gggruggvucftvghtrhhoucdtuddrfeeliedrudefgddvtdcutefuodetggdotefrodftvfcurfhrohhf
X-VR-Cause-2: ihhlvgemucfntefrqffuvffgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhs
X-VR-Cause-3: ucdlqddutddtmdenucfjughrpefhvffufhffjgfkfgggtgesthdtredttdertdenucfhrhhomhepuegv
X-VR-Cause-4: rhhtrhgrnhguucfirghrrhhighhuvghsuceosggvrhhtrhgrnhgurdhgrghrrhhighhuvghssehlrghp
X-VR-Cause-5: ohhsthgvrdhnvghtqeenucfkphepkeelrdelhedrvdefjedrleejnecurfgrrhgrmhepmhhouggvpehs
X-VR-Cause-6: mhhtphhouhhtpdhhvghlohephhhsihgrohhmihdrpdhinhgvthepkeelrdelhedrvdefjedrleejpdhm
X-VR-Cause-7: rghilhhfrhhomhepsggvrhhtrhgrnhgurdhgrghrrhhighhuvghssehlrghpohhsthgvrdhnvghtpdhr
X-VR-Cause-8: tghpthhtohepphgvthgvrhesshgthhgrfhhfthgvrhdrtggr
X-VR-AvState: No
X-VR-State: 0
X-VR-State: 0
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 194.117.213.104
Subject: Re: [Groff] [groff] 01/01: Version 2.2 updates.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 23:05:05 -0000

Hi Peter,

On Mon, Mar 06 2017 at 11:07:38 PM, Bertrand Garrigues <bertrand.garrigues@laposte.net> wrote:
> For some reasons on my environment, there are lots of font files
> missing in font/devpdf; particularly there are no font from the N
> family (previously in typesetting.mom you would use another font
> family and thus this problem would be unnoticed).  I'll check what is
> happening on the font generation.

I was a bit busy these last weeks but now I have a bit of time to check
this problem.  On my environment only the fonts that are marked as 'Y'
in font/devpdf/Foundry.in will be generated (in fact, copied from
devps).  Other fonts (for example 'AB') are missing.  As you have a
working environment, could you please help me to understand what is
going on by applying the following patch, rebuilding the devpdf fonts
('make clean' and 'make font/devpdf/build_font_files' is sufficient).
and send me the logs?

Thanks a lot,

Bertrand Garrigues

Here is the patch to apply:

diff --git a/font/devpdf/util/BuildFoundries.pl b/font/devpdf/util/BuildFoundries.pl
index 39f2f0d2..1af85ae0 100644
--- a/font/devpdf/util/BuildFoundries.pl
+++ b/font/devpdf/util/BuildFoundries.pl
@@ -96,10 +96,11 @@ sub LoadFoundry
 
                my $gotf=1;
                my $gropsfnt=LocateFile($devps,$r[0],0);
-
+                print STDERR "[LoadFoundry]:gropsfnt:$gropsfnt\n";
                if ($gropsfnt ne '' and -r "$gropsfnt")
                {
                    my $psfont=UseGropsVersion($gropsfnt);
+                    print STDERR "[LoadFoundry]:psfont:$psfont, font file:$r[5], is base:$r[1]\n";
                    if (!PutDownload($psfont,LocatePF($foundrypath,$r[5]),uc($r[1])))
                    {
                        if (uc($r[1]) ne 'Y')
@@ -210,8 +211,9 @@ sub LocatePF
 {
     my $path=shift;
     my $file=shift;
-
-    return(LocateFile($path,$file,0));
+    my $ret=LocateFile($path,$file,0);
+    print STDERR "[LocatePF]:$ret:\n";
+    return("$ret");
 }
 
 sub LocateFile


From MAILER-DAEMON Tue Apr 11 18:01:32 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cy3qu-0006qI-7n
	for mharc-groff@gnu.org; Tue, 11 Apr 2017 18:01:32 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33855)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bertrand.garrigues@laposte.net>) id 1cy3qs-0006qA-QV
	for groff@gnu.org; Tue, 11 Apr 2017 18:01:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bertrand.garrigues@laposte.net>) id 1cy3qp-0004EX-Qb
	for groff@gnu.org; Tue, 11 Apr 2017 18:01:30 -0400
Received: from smtpoutz299.laposte.net ([178.22.154.199]:34732
	helo=smtpoutz2.laposte.net)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <bertrand.garrigues@laposte.net>)
	id 1cy3qp-0004CT-Gi
	for groff@gnu.org; Tue, 11 Apr 2017 18:01:27 -0400
Received: from smtpoutz2.laposte.net (localhost [127.0.0.1])
	by lpn-prd-vrout011 (Postfix) with ESMTP id 3021452A7EE
	for <groff@gnu.org>; Wed, 12 Apr 2017 00:01:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=laposte.net; s=mail0;
	t=1491948085; bh=T+Xuei+5htpP5HlnhkB/6AT4oUe1CaWjEsQsaSoBkeI=;
	h=From:To:Subject:References:Date:In-Reply-To;
	b=RmahW8fP4DmnRHxbNOMPLGgYgNhP/bG/IL9xDuZ+orjdAjDmei8IWLwzyzDweHysw
	VPiSVYL5ODtszeBRMExBi8NbCrOLREY5C7xBjYlSM2PhIFHLGyNlG6aH2/lYRKTISH
	u0NQtlvP4UeHCbSdImDT2tRGAZGjn7gnRITNBNyHwhvjtUfuaRUEzij7HfELX+ucxo
	VAUMEddA9/3ejiYfAYC9aP6SSw4Ve3fOLFkQvjwkekyYGVh1Ru7PPOZqXhb4zcQu0H
	vyVNirFXCFmcAjey5K4VsPEUaz+DSlEQzQ6iDzi6fwQdf+OZoSN5iGU3TZKS9woJvq
	zL85cdWjvTizA==
Received: from smtpoutz2.laposte.net (localhost [127.0.0.1])
	by lpn-prd-vrout011 (Postfix) with ESMTP id 2254952A86A
	for <groff@gnu.org>; Wed, 12 Apr 2017 00:01:25 +0200 (CEST)
Received: from lpn-prd-vrin003 (lpn-prd-vrin003.laposte [10.128.63.4])
	by lpn-prd-vrout011 (Postfix) with ESMTP id 1DA8452A7EE
	for <groff@gnu.org>; Wed, 12 Apr 2017 00:01:25 +0200 (CEST)
Received: from lpn-prd-vrin003 (localhost [127.0.0.1])
	by lpn-prd-vrin003 (Postfix) with ESMTP id 0CF6548F099
	for <groff@gnu.org>; Wed, 12 Apr 2017 00:01:25 +0200 (CEST)
Received: from hsiaomi. (jau72-h04-89-95-237-97.dsl.sta.abo.bbox.fr
	[89.95.237.97])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by lpn-prd-vrin003 (Postfix) with ESMTPSA id D9E8B48EF9E
	for <groff@gnu.org>; Wed, 12 Apr 2017 00:01:24 +0200 (CEST)
From: Bertrand Garrigues <bertrand.garrigues@laposte.net>
To: groff@gnu.org
References: <20170227032334.26858.92818@vcs0.savannah.gnu.org>
	<20170227032335.686FA2600F@vcs0.savannah.gnu.org>
	<877f4bl114.fsf@laposte.net> <20170227231755.GE9845@augustus>
	<87a88z4dk6.fsf@laposte.net> <20170305231835.GA19621@augustus>
	<87fuiqhumd.fsf@laposte.net> <87lgr7euf5.fsf@laposte.net>
Date: Wed, 12 Apr 2017 00:01:24 +0200
In-Reply-To: <87lgr7euf5.fsf@laposte.net> (Bertrand Garrigues's message of
	"Tue, 11 Apr 2017 01:04:30 +0200")
Message-ID: <87h91umwnf.fsf_-_@laposte.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-VR-SrcIP: 89.95.237.97
X-VR-FullState: 0
X-VR-Score: 0
X-VR-Cause-1: gggruggvucftvghtrhhoucdtuddrfeeliedrudehgddtlecutefuodetggdotefrodftvfcurfhrohhf
X-VR-Cause-2: ihhlvgemucfntefrqffuvffgnecuuegrihhlohhuthemucehtddtnecunecujfgurhephffvufhfffgj
X-VR-Cause-3: kfgfgggtsehttdertddtredtnecuhfhrohhmpeeuvghrthhrrghnugcuifgrrhhrihhguhgvshcuoegs
X-VR-Cause-4: vghrthhrrghnugdrghgrrhhrihhguhgvsheslhgrphhoshhtvgdrnhgvtheqnecukfhppeekledrleeh
X-VR-Cause-5: rddvfeejrdeljeenucfrrghrrghmpehmohguvgepshhmthhpohhuthdphhgvlhhopehhshhirghomhhi
X-VR-Cause-6: rddpihhnvghtpeekledrleehrddvfeejrdeljedpmhgrihhlfhhrohhmpegsvghrthhrrghnugdrghgr
X-VR-Cause-7: rhhrihhguhgvsheslhgrphhoshhtvgdrnhgvthdprhgtphhtthhopehgrhhofhhfsehgnhhurdhorhhg
X-VR-AvState: No
X-VR-State: 0
X-VR-State: 0
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 178.22.154.199
Subject: [Groff] font/devpdf broken with ghostscript 9.21
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 22:01:31 -0000

(renamed the subject, was [groff] 01/01: Version 2.2 updates.)

Hi all,

On Tue, Apr 11 2017 at 01:04:30 AM, Bertrand Garrigues <bertrand.garrigues@laposte.net> wrote:
> On Mon, Mar 06 2017 at 11:07:38 PM, Bertrand Garrigues <bertrand.garrigues@laposte.net> wrote:
>> For some reasons on my environment, there are lots of font files
>> missing in font/devpdf; particularly there are no font from the N
>> family (previously in typesetting.mom you would use another font
>> family and thus this problem would be unnoticed).  I'll check what is
>> happening on the font generation.

I've opened bug #50786 and assigned it to me; this bug is blocking me
for the preparation of the next release.  I think I can fix it quickly
and then resume the release generation.

Thanks again to Peter for helping me on this problem,

Regards,

Bertrand Garrigues


From MAILER-DAEMON Thu Apr 20 18:37:56 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1Ki4-0005ob-8w
	for mharc-groff@gnu.org; Thu, 20 Apr 2017 18:37:56 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48171)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1Ki2-0005oU-1y
	for groff@gnu.org; Thu, 20 Apr 2017 18:37:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1Khy-0004RR-Vm
	for groff@gnu.org; Thu, 20 Apr 2017 18:37:54 -0400
Received: from relay01.pair.com ([209.68.5.15]:36411)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d1Khy-0004Qx-Qq
	for groff@gnu.org; Thu, 20 Apr 2017 18:37:50 -0400
Received: from orac.inputplus.co.uk (unknown [84.93.89.70])
	by relay01.pair.com (Postfix) with ESMTP id 88527D00B3F
	for <groff@gnu.org>; Thu, 20 Apr 2017 18:37:49 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 5B41A1F93A
	for <groff@gnu.org>; Thu, 20 Apr 2017 23:37:48 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Thu, 20 Apr 2017 23:37:48 +0100
Message-Id: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 22:37:55 -0000

Hi,

If a command is called /bin/foo-bar and it processes a file format
foo-xyzzy, then should their man pages use

    foo\-bar
    .IR foo\-bar (1)
    .IR foo\-xyzzy (5)

...and so on?  That's what I thought, `foo-bar' being a hyphen.

Various things around the place collude so both `\-', or the wrong,
hyphen, `-', produce U+002D, e.g.
/usr/share/groff/1.22.3/tmac/an-old.tmac has

    .\" For UTF-8, map some characters conservatively for the sake
    .\" of easy cut and paste.
    .
    .if '\*[.T]'utf8' \{\
    .  rchar \- - ' `
    .
    .  char \- \N'45'
    .  char  - \N'45'
    .  char  ' \N'39'
    .  char  ` \N'96'
    .\}

But for a man page that's cross platform, non-groff, e.g. AIX, and to be
seen in a variety of formats, all groff's `-T's at least, how does one
ensure that U+002D will result so it can be cut and pasted back to the
shell?  Investigation is hamped by some viewers, e.g. PDF, seeming to
translate non-U+002D back to U+002D as a "favour".  :-)  Fine, but one
can't assume the user's PDF viewer will do this.

\N'45' is portable since it's CSTR 54, but it's Nth character of the
current font.  Does that mean I should use this wherever I want to
ensure U+002D appears in the output for pasting?

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Thu Apr 20 20:04:08 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1M3U-0001oF-SH
	for mharc-groff@gnu.org; Thu, 20 Apr 2017 20:04:08 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33503)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1M3T-0001o8-0R
	for groff@gnu.org; Thu, 20 Apr 2017 20:04:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1M3P-0007Ej-0j
	for groff@gnu.org; Thu, 20 Apr 2017 20:04:07 -0400
Received: from magicmail02.frii.com ([216.17.135.171]:58303
	helo=magic02.frii.com) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1M3O-0007EZ-P9
	for groff@gnu.org; Thu, 20 Apr 2017 20:04:02 -0400
Received: (qmail 14891 invoked from network); 21 Apr 2017 00:04:01 -0000
Received: from 184-96-197-252.hlrn.qwest.net (HELO [192.168.0.13])
	(clarke@frii.com@184.96.197.252)
	by 216.17.135.171 with (DHE-RSA-AES128-SHA encrypted) SMTP
	(05853ab0-2626-11e7-ba24-dfe7c4685a1b); Thu, 20 Apr 2017 18:04:01 -0600
To: Ralph Corderoy <ralph@inputplus.co.uk>, groff@gnu.org
References: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
From: Clarke Echols <clarke@verinet.net>
Message-ID: <a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
Date: Thu, 20 Apr 2017 18:04:00 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
X-MagicMail-OS: Inactive
X-MagicMail-UUID: 05853ab0-2626-11e7-ba24-dfe7c4685a1b
X-MagicMail-Authenticated: clarke@frii.com
X-MagicMail-SourceIP: 184.96.197.252
X-MagicMail-RegexMatch: 9
X-MagicMail-EnvelopeFrom: <clarke@verinet.net>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 216.17.135.171
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 00:04:08 -0000

When I was responsible for all of the manpages in HP's HP-UX (Unix) 
reference manual
and online, I always *typeset* with Courier bold, and used the simple 
hyphen character
because it was all monospace.

Courier was standard for all literals in SYNTAX, including command name, 
and options
such as -r, -f, etc.  Only variable arguments such as "filename", 
directory name, etc.
were always in italic.  This convention was also used in the 
DESCRIPTION, EXAMPLES,
and other such sections.

If a minus sign appeared in regular text, I always used \(mi.  The 
top-of-page heading
(such as cp(1) for the copy-file page, was always in bold Roman (I used 
New Century
Schoolbook bold).

I used the .C name for macros, as in .CI, .IC, for command lines in the 
SYNOPSIS.  I
rewrote/edited the AT&T Unix macros to accommodate that for names of 
commands, functions,
punctuation in C-language functions, etc.  I NEVER used bold Roman font 
for literals in
such instances.

Clarke

On 04/20/2017 04:37 PM, Ralph Corderoy wrote:
> Hi,
>
> If a command is called /bin/foo-bar and it processes a file format
> foo-xyzzy, then should their man pages use
>
>      foo\-bar
>      .IR foo\-bar (1)
>      .IR foo\-xyzzy (5)
>
> ...and so on?  That's what I thought, `foo-bar' being a hyphen.
>
> Various things around the place collude so both `\-', or the wrong,
> hyphen, `-', produce U+002D, e.g.
> /usr/share/groff/1.22.3/tmac/an-old.tmac has
>
>      .\" For UTF-8, map some characters conservatively for the sake
>      .\" of easy cut and paste.
>      .
>      .if '\*[.T]'utf8' \{\
>      .  rchar \- - ' `
>      .
>      .  char \- \N'45'
>      .  char  - \N'45'
>      .  char  ' \N'39'
>      .  char  ` \N'96'
>      .\}
>
> But for a man page that's cross platform, non-groff, e.g. AIX, and to be
> seen in a variety of formats, all groff's `-T's at least, how does one
> ensure that U+002D will result so it can be cut and pasted back to the
> shell?  Investigation is hamped by some viewers, e.g. PDF, seeming to
> translate non-U+002D back to U+002D as a "favour".  :-)  Fine, but one
> can't assume the user's PDF viewer will do this.
>
> \N'45' is portable since it's CSTR 54, but it's Nth character of the
> current font.  Does that mean I should use this wherever I want to
> ensure U+002D appears in the output for pasting?
>

-- 
Clarke Echols
Copywriter and Marketing Communications Specialist
Loveland, CO
(970) 667-6736

www.ClarkeEchols.com

Global climate change is real.  It's caused
by the SUN.

Carbon dioxide CANNOT affect climate in the slightest.
Want proof?

Go to https://www.youtube.com/embed/BC1l4geSTP8
for the facts.

"Five percent of the people actually think.
Ten percent think they think.
And the other eighty-five percent
would rather die than think."
    -- Thomas Edison --

"How fortunate for governments
that the people do not think."
    -- Adolf Hitler --

"During the course of administration,
and in order to disturb it, the artillery
of the press has been leveled against us,
charged with whatsoever its licentiousness
could devise or dare.  These abuses of an
institution so important to freedom and
science are deeply to be regretted,
inasmuch as they tend to lessen its
usefulness and to sap its safety."
    -- Thomas Jefferson (1805) --


From MAILER-DAEMON Thu Apr 20 21:00:36 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1Mw8-0000pJ-2m
	for mharc-groff@gnu.org; Thu, 20 Apr 2017 21:00:36 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47235)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d1Mw4-0000o8-NX
	for groff@gnu.org; Thu, 20 Apr 2017 21:00:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d1Mw1-000108-Gk
	for groff@gnu.org; Thu, 20 Apr 2017 21:00:32 -0400
Received: from mail-qt0-x243.google.com ([2607:f8b0:400d:c0d::243]:34655)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d1Mw1-0000zu-Bb
	for groff@gnu.org; Thu, 20 Apr 2017 21:00:29 -0400
Received: by mail-qt0-x243.google.com with SMTP id y33so10036755qta.1
	for <groff@gnu.org>; Thu, 20 Apr 2017 18:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=Mzzc9mPg2VCzrvXVSin7XpQyioNbLyp7PFkp5H2ajjE=;
	b=DDZhkDBM3xE9pmIRtiWdVBD0RAjJguZJ084HstQteqM5Ay8oKebXdNOX2oHaopBw2G
	FZkbRQEdd0T7xF0GgE1U5SMAs/dcU6GK++KrCpOtOpnPfGiv/1vrPKSVCYB8yB7zspH0
	d0/CdlOhVka/BzisvnJl8BXVWv9boUXLhj+eQSXrNZV11CfwKQKk1vFdo5S6NqgzGLDp
	Eu9e1WOxzFW+Rew5Oj1NwsZd4czQ5ujDEA6TelXS7iZJK4fI/StJxoMSzak9oYnjq6Z7
	dmkfpmDMN1JHWvkFEqPR5mj0bthr+jYaTG3i/dilxy9r0RIewdMv0/60TWdiqaDmY8b3
	wC5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=Mzzc9mPg2VCzrvXVSin7XpQyioNbLyp7PFkp5H2ajjE=;
	b=HLw8nTSIkRF2Amd9IRTFvkJnjsMuRdiRQz7Xw/ZLEYG2yAu9TZycvUep+uzyGhUvG4
	TmXYXA1ToxJVCs1P5lL3JMuDxfo4Vdaym9gIxXqr7o7LOuJnUTWrkXKmNYqph6FoSEbn
	DkkcxGOJeZ15m1SOTl66tc/v8pCjTx+MGWDF4knOX1/MpFX9oyEcTpI49IXe7valYh2R
	Vr2J36IWjqt4Nyhg3eH6Q87zntd4/wo6UphAoera17clvx/2DTkkAOqAytXlR+I7N7Wi
	oJXOKF4gGQayf46RuYrO1TPtGPLRTyZF+uQqQXfo+nR9+w3LtmqiGPDk+7OdUHBsGUK1
	P2HQ==
X-Gm-Message-State: AN3rC/63D6ShIT0Xa7y6RWmSCq3SRF6D/pDVH0e7ybbGq1XW+gqtgOC2
	LVAnl6er4h/b7/gVwBiGxw==
X-Received: by 10.200.36.2 with SMTP id c2mr10773472qtc.271.1492736428053;
	Thu, 20 Apr 2017 18:00:28 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	n12sm5342372qkn.29.2017.04.20.18.00.26 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 20 Apr 2017 18:00:26 -0700 (PDT)
Date: Thu, 20 Apr 2017 21:00:23 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170421010021.6hkmd4enb5acwueo@crack.deadbeast.net>
References: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
	<a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="mp5zizsoq7rxkp7p"
Content-Disposition: inline
In-Reply-To: <a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:400d:c0d::243
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 01:00:34 -0000


--mp5zizsoq7rxkp7p
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-20T18:04:00-0600, Clarke Echols wrote:
> When I was responsible for all of the manpages in HP's HP-UX (Unix)
> reference manual and online, I always *typeset* with Courier bold, and
> used the simple hyphen character because it was all monospace.
>=20
> Courier was standard for all literals in SYNTAX, including command
> name, and options such as -r, -f, etc.  Only variable arguments such
> as "filename", directory name, etc.  were always in italic.  This
> convention was also used in the DESCRIPTION, EXAMPLES, and other such
> sections.
>=20
> If a minus sign appeared in regular text, I always used \(mi.
[...]
> I used the .C name for macros, as in .CI, .IC, for command lines in the
> SYNOPSIS.

What was/is the distinction between the "Syntax" and "Synopsis"
headings?  I've only seen the former occasionally, and when I have, it's
been exactly what is elsewhere called a "Synopsis".

Regards,
Branden

--mp5zizsoq7rxkp7p
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlj5WZwACgkQ0Z6cfXEm
bc5JfhAAmMjhY1ieeCmtyjtwwxRIBXLtk1aW+O1VcyiwzTJ5+N6/QjJrdXt9OTjE
Cidu8UvBKZZrO+KiqiJspMecLDIpUWEdTDo5FrZLfrZu4ftt+Ow89Lt/4Q0YlNGf
Pinu/4bf5L5hZcqJShJvOgXUAOej5Xvx4T+QuW5pDrhEQISevUd5QzLg0skbWU/K
SxHoTEVz0jLQ0TjdhL3ccPM7+xj6/vyLoAc66faH03QYV8dAaODVyanklCA/cqHH
R0lCTNT5ivvRAMFnOZGoWhMzNvUFb34dzqPZbKFHa4QveLD+9LPYdfJPjE9lYXHk
4SkkbO67HyfBDrtck2Yc5Ibca7wn1z/9SIXDXKK/umYPFxZ1n+jknjrnTNbNGsim
8l8tn85HEG+suvxPJK4slMDmUXRbv5Ymr0pUDmhRqEGEQXQaHayCyH5vZv6VOAbl
Fxd/L0sQ8N8+DjfDiNPt00dwnnSXjLLP+0CXHwjQ5jU/jjoPcKXkPmiEvm5mGg4U
g2r+4mUN/mBX8VW6f76gFylXDbJBrX2cURtbk2XPD+2X3w6hCugzP+06oa5IpQKh
KFPQ6dygjWfvUOw+daNGxSrVDYw3aR3IgzOxXdngK9/8MvJJKsldce/O7fRGkgoZ
JmbG5Zj2pGBBa+oYfa/J2CBlNccqRJryah1lv/CEdhr1iC3IF18=
=6g1b
-----END PGP SIGNATURE-----

--mp5zizsoq7rxkp7p--


From MAILER-DAEMON Fri Apr 21 01:12:08 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1QrY-0000eg-Jk
	for mharc-groff@gnu.org; Fri, 21 Apr 2017 01:12:08 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43771)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1QrV-0000cs-Lj
	for groff@gnu.org; Fri, 21 Apr 2017 01:12:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1QrS-0008Jn-Df
	for groff@gnu.org; Fri, 21 Apr 2017 01:12:05 -0400
Received: from magicmail03.frii.com ([216.17.135.172]:59317
	helo=magic03.frii.com) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <clarke@verinet.net>) id 1d1QrS-0008H6-5g
	for groff@gnu.org; Fri, 21 Apr 2017 01:12:02 -0400
Received: (qmail 27074 invoked from network); 21 Apr 2017 05:11:59 -0000
Received: from 184-96-197-252.hlrn.qwest.net (HELO [192.168.0.13])
	(clarke@frii.com@184.96.197.252)
	by 216.17.135.172 with (DHE-RSA-AES128-SHA encrypted) SMTP
	(0b4b9e50-2651-11e7-a5c9-835c39c07ee7); Thu, 20 Apr 2017 23:11:59 -0600
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>, groff@gnu.org
References: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
	<a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
	<20170421010021.6hkmd4enb5acwueo@crack.deadbeast.net>
From: Clarke Echols <clarke@verinet.net>
Message-ID: <340d4773-01f3-0420-f8b9-5b8a0222b1b8@verinet.net>
Date: Thu, 20 Apr 2017 23:11:58 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170421010021.6hkmd4enb5acwueo@crack.deadbeast.net>
X-MagicMail-OS: Inactive
X-MagicMail-UUID: 0b4b9e50-2651-11e7-a5c9-835c39c07ee7
X-MagicMail-Authenticated: clarke@frii.com
X-MagicMail-SourceIP: 184.96.197.252
X-MagicMail-RegexMatch: 9
X-MagicMail-EnvelopeFrom: <clarke@verinet.net>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 216.17.135.172
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 05:12:07 -0000

Back in the early 1970s, it was called "syntax" when I was
writing programs in assembler and BASIC.

[My first encounter with AT&T Unix manuals and manpages was in
1985, and SYNOPSIS was a new term for me.  (I was a hardware
engineer in the rest of the 1970s, and writing user manuals
for data communication and hardware support until Unix
invaded my world with Unix field-support manuals in 1984.  Then
I inherited the Unix reference manual (manpages) until the end
of 1985 until I took over the HP-UX Reference from 1989 through
1992 when it was 3000 pages in 3 volumes, and weighed close to
10 pounds (US weight).  We called it "the brick" for obvious
reasons. :-) ]

But it makes a lot of sense, because it is a quick-look at the
keywords, options, and arguments, used in an environment where
you might be looking for information about a command (or "utility"
as AT&T called them), or it could be to guide the use of function
calls in system or library calls.

Thus it is a convenient, quick way to see what to do or how to
structure your code to work in a C or other program.

And in that context, "syntax" tends to look like an inaccurate
term in that broader context.

I had to go through a transition in my thinking as a result, but
after a few months, it seemed perfectly naturally -- especially
after 5 years of working almost exclusively on manpages before I
ended up designing and creating online help for HP-UX system
administration software from 1993 through most of 1999 before I
retired and left the corporate world.

Clarke


On 04/20/2017 07:00 PM, G. Branden Robinson wrote:
> At 2017-04-20T18:04:00-0600, Clarke Echols wrote:
>> When I was responsible for all of the manpages in HP's HP-UX (Unix)
>> reference manual and online, I always *typeset* with Courier bold, and
>> used the simple hyphen character because it was all monospace.
>>
>> Courier was standard for all literals in SYNTAX, including command
>> name, and options such as -r, -f, etc.  Only variable arguments such
>> as "filename", directory name, etc.  were always in italic.  This
>> convention was also used in the DESCRIPTION, EXAMPLES, and other such
>> sections.
>>
>> If a minus sign appeared in regular text, I always used \(mi.
> [...]
>> I used the .C name for macros, as in .CI, .IC, for command lines in the
>> SYNOPSIS.
> What was/is the distinction between the "Syntax" and "Synopsis"
> headings?  I've only seen the former occasionally, and when I have, it's
> been exactly what is elsewhere called a "Synopsis".
>
> Regards,
> Branden

-- 
Clarke Echols
Copywriter and Marketing Communications Specialist
Loveland, CO
(970) 667-6736

www.ClarkeEchols.com

Global climate change is real.  It's caused
by the SUN.

Carbon dioxide CANNOT affect climate in the slightest.
Want proof?

Go to https://www.youtube.com/embed/BC1l4geSTP8
for the facts.

"Five percent of the people actually think.
Ten percent think they think.
And the other eighty-five percent
would rather die than think."
    -- Thomas Edison --

"How fortunate for governments
that the people do not think."
    -- Adolf Hitler --

"During the course of administration,
and in order to disturb it, the artillery
of the press has been leveled against us,
charged with whatsoever its licentiousness
could devise or dare.  These abuses of an
institution so important to freedom and
science are deeply to be regretted,
inasmuch as they tend to lessen its
usefulness and to sap its safety."
    -- Thomas Jefferson (1805) --


From MAILER-DAEMON Fri Apr 21 10:11:33 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1ZHZ-0005Cf-EQ
	for mharc-groff@gnu.org; Fri, 21 Apr 2017 10:11:33 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58556)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1ZHW-0005BU-Cs
	for groff@gnu.org; Fri, 21 Apr 2017 10:11:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1ZHS-0000pp-Tm
	for groff@gnu.org; Fri, 21 Apr 2017 10:11:30 -0400
Received: from relay01.pair.com ([209.68.5.15]:59510)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d1ZHS-0000oC-Nn
	for groff@gnu.org; Fri, 21 Apr 2017 10:11:26 -0400
Received: from orac.inputplus.co.uk (110.81.114.87.dyn.plus.net
	[87.114.81.110])
	by relay01.pair.com (Postfix) with ESMTP id EAAB9D00B20
	for <groff@gnu.org>; Fri, 21 Apr 2017 10:11:21 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id E47DB21568
	for <groff@gnu.org>; Fri, 21 Apr 2017 15:11:20 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
References: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
	<a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
Date: Fri, 21 Apr 2017 15:11:20 +0100
Message-Id: <20170421141120.E47DB21568@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 14:11:32 -0000

Hi,

Clarke wrote:
> used the simple hyphen character because it was all monospace.
...
> If a minus sign appeared in regular text, I always used \(mi.

It was a lot easier then when the was only ASCII `-' and nothing else.
:-)

Here's how R and TR fonts map onto character 45 in groff.

    $ cd /usr/share/groff/1.22.3/font
    $ for f in dev*/?(T)R; do
    >     echo $f
    >     awk '$2 !=3D "\"" {p=3D0} $4 ~ /^(45|0+55|0x0*2[dD])$/ {p=3D1} =
p' $f
    >     echo
    > done
    devascii/R
    \-	24	0	0055
    hy	"
    -	"
    mi	"
    en	"

So -Tascii is simple.

    devdvi/TR
    hy	349526,451470	0	0055
    -	"

So `\-' isn't 45 in -Tdvi.  And TR doesn't mention it or `\(mi'.  (Those
two are always the same AIUI, which makes me wonder about -Tascii
defining both.)

    devhtml/R
    hy	24	0	0x002D
    -	"

    devlatin1/R
    \-	24	0	0055
    mi	"
    -	"
    hy	"
    en	"

-Tlatin1 is like -Tascii.  Correct, since it offer no alternatives.

    devlbp/TR
    -	1110	0	0x2d	 0,45	 # hyphen
    \-	1110	0	0x2d	 0,45	 # hyphen
    hy	1110	0	0x2d	 0,45	 # "
    hy	1880	0	0x2d	 6,0	 # hyphen
    .C1	1110	0	0x2d	 0,45	 # - minus "minus sign from current font"

    devlj4/TR

?

    devpdf/TR
    -	333,257	0	45	hyphen
    hy	"

    devps/TR
    -	333,257	0	45	hyphen
    hy	"

`\-' is 173 in -Tpdf and -Tps;  ISO-8859-1's `soft hyphen'.

    devutf8/R

One must use `\N[45]' for -Tutf8.

    $ groff -Tutf8 <<<'-\-\(mi\(en\N[45]' | uniq | recode ..dump
    UCS2   Mne   Description

    2010   -1    hyphen
    2212   -2    minus sign
    2212   -2    minus sign
    2013   -N    en dash
    002D   -     hyphen-minus
    000A   LF    line feed (lf)
    000A   LF    line feed (lf)
    $

    devX100-12/TR
    \-	5,5	0	055

    devX100/TR
    \-	4,4	0	055

    devX75-12/TR
    \-	4,4	0	055

    devX75/TR
    \-	4,3	0	055

-TdevX* are all the same;  `\-' gives 45, 055 in octal.  Out of
interest, they map `-' and `\(hy' onto 0255, `soft hyphen' in
ISO-8859-1.

I'm no clearer.  Except I'm not sure what I want is possible.  So what's
"best practice" when aiming at groff, non-groff, old systems,
proprietary systems?

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Fri Apr 21 11:26:55 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1aSV-0000Sn-Q5
	for mharc-groff@gnu.org; Fri, 21 Apr 2017 11:26:55 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1aSS-0000S9-Sj
	for groff@gnu.org; Fri, 21 Apr 2017 11:26:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1aSN-0006cX-Si
	for groff@gnu.org; Fri, 21 Apr 2017 11:26:52 -0400
Received: from sdaoden.eu ([217.144.132.164]:38672)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1aSN-0006bZ-M1
	for groff@gnu.org; Fri, 21 Apr 2017 11:26:47 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id CE87216051; Fri, 21 Apr 2017 17:26:45 +0200 (CEST)
Date: Fri, 21 Apr 2017 17:28:55 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170421152855.7OmUj%steffen@sdaoden.eu>
References: <20170420223748.5B41A1F93A@orac.inputplus.co.uk>
	<a5921aa8-b6e5-b85a-689e-27db21dee841@verinet.net>
	<20170421141120.E47DB21568@orac.inputplus.co.uk>
In-Reply-To: <20170421141120.E47DB21568@orac.inputplus.co.uk>
Mail-Followup-To: Ralph Corderoy <ralph@inputplus.co.uk>, groff@gnu.org
User-Agent: s-nail v14.9.0-pre4-11-g745b3025
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 15:26:53 -0000

Ralph Corderoy <ralph@inputplus.co.uk> wrote:
 |Clarke wrote:
 |> used the simple hyphen character because it was all monospace.
 |...
 |> If a minus sign appeared in regular text, I always used \(mi.
 |
 |It was a lot easier then when the was only ASCII `-' and nothing else.
 |:-)
 ..
 |I'm no clearer.  Except I'm not sure what I want is possible.  So what's
 |"best practice" when aiming at groff, non-groff, old systems,
 |proprietary systems?

I use U+002D hyphen-minus.  The minus sign is a mathematical
symbol, i would say.  Hyphen-minus logically combines two words.
But that came naturally, i didn't really think about it.  Maybe
the text-processor should be so smart to realize that the actual
use cases combines words without an intermediate newline, and
should correct the glyph "to look nicer" in that case?

--steffen


From MAILER-DAEMON Fri Apr 21 21:56:32 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1kHn-0003xn-Vu
	for mharc-groff@gnu.org; Fri, 21 Apr 2017 21:56:31 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34497)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d1kHm-0003wU-4y
	for groff@gnu.org; Fri, 21 Apr 2017 21:56:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d1kHj-0003ft-5F
	for groff@gnu.org; Fri, 21 Apr 2017 21:56:30 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:32832)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1d1kHj-0003eO-1D
	for groff@gnu.org; Fri, 21 Apr 2017 21:56:27 -0400
Received: from tahoe.cs.Dartmouth.EDU (tahoe.cs.dartmouth.edu [129.170.212.20])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v3M1uOuQ009397
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
	for <groff@gnu.org>; Fri, 21 Apr 2017 21:56:24 -0400
Received: from tahoe.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by tahoe.cs.Dartmouth.EDU (8.15.2/8.14.3) with ESMTP id v3M1uOeq014002
	for <groff@gnu.org>; Fri, 21 Apr 2017 21:56:24 -0400
Received: (from doug@localhost)
	by tahoe.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v3M1uOcE013999
	for groff@gnu.org; Fri, 21 Apr 2017 21:56:24 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
Date: Fri, 21 Apr 2017 21:56:24 -0400
To: groff@gnu.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 01:56:31 -0000

I think it's pretty hopeless to ask for AI that can tell
whether a pasted symbol is a hyphen or a minus sign.
The answer is likely to depend on whether it is being
pasted into a program or into a document.

Doug


From MAILER-DAEMON Fri Apr 21 22:52:04 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1l9Y-0003X3-Nj
	for mharc-groff@gnu.org; Fri, 21 Apr 2017 22:52:04 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44717)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d1l9X-0003VC-4I
	for groff@gnu.org; Fri, 21 Apr 2017 22:52:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d1l9T-0003Tn-8G
	for groff@gnu.org; Fri, 21 Apr 2017 22:52:03 -0400
Received: from mail-qt0-x235.google.com ([2607:f8b0:400d:c0d::235]:34397)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d1l9T-0003Ta-38
	for groff@gnu.org; Fri, 21 Apr 2017 22:51:59 -0400
Received: by mail-qt0-x235.google.com with SMTP id c45so82266755qtb.1
	for <groff@gnu.org>; Fri, 21 Apr 2017 19:51:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=NgsIxWF6I++3e1ZQUjlA4TFACfa+p9ZFW2EVteia+3g=;
	b=jHaMTq1MnTWKSk78l5BH3WxWtKsgNso5IveXfULcpLLyCobL16xd7FffNIlZuuvNWC
	nCQvPiE2zOF+4VAghfAzdrKsiEWo+eWq4XzB9srTkiVvsQ+zT6flruiQZDVCiuO2vI7y
	oHDHadw3z2O3cOLqyowkWema2aCATxVC3dTPE6fbSd8C0GYHZ1W9HUDGESvD8f9T+sRB
	QSlZaiTkQUNqR6lwzhh6e8hiJcu/vPdg+/ARkR84NiJiqIJR6oiYMaITQOEqGbMwsq5p
	f4kw2t/r3PC71Ps493NNnTx0TkLcjWMg3hm8X37IIX4SMw7zpYt1haGLM9Ja5+XESHCk
	jVfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=NgsIxWF6I++3e1ZQUjlA4TFACfa+p9ZFW2EVteia+3g=;
	b=d9e7o1/0DIrI0mu94xRyHxZxRnqUzqB8KN8HbrGsm5m1w9Gb1gBYmzmz1DACtELF4J
	r5eo+YMdQWBZH52c2XJeQNbsGxdrO5S48GpIFk74hYmENTdsJVL0XkCVuNVMgkE/yy2c
	F6eCmMoS/wfAlNF6GPwuxrl/3w6UIlaSAM/GwYmJzAJXXDUnzUC16lBgyOtGSeeQrpEP
	8GuToUJ77qmGp2PsybgRJcgMn/vPf0MSyYxpqmEZi4ZIDZbKSDGwthJYvVQ306BuwohH
	k3gsi9y20rccsKqDeHak5DQB0717FZM3kUsGGVtMudXEy4JS1KyePwdapSCbleTpEJ3s
	5L1w==
X-Gm-Message-State: AN3rC/68iA3UZHGNtwjGaujA/VjUFanqCyIL7FZSZs4rBD0ZKOCRzSHr
	XXkof9x37mW2K5XDTNM=
X-Received: by 10.237.52.97 with SMTP id w88mr16118410qtd.178.1492829517904;
	Fri, 21 Apr 2017 19:51:57 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id 14sm7746841qtp.29.2017.04.21.19.51.56
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Fri, 21 Apr 2017 19:51:56 -0700 (PDT)
Date: Fri, 21 Apr 2017 22:51:54 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170422025151.usnhi7hargsmb375@crack.deadbeast.net>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="dwpzjkcq2ermcjb4"
Content-Disposition: inline
In-Reply-To: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:400d:c0d::235
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 02:52:04 -0000


--dwpzjkcq2ermcjb4
Content-Type: multipart/mixed; boundary="lu2avhqxorryirzf"
Content-Disposition: inline


--lu2avhqxorryirzf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

At 2017-04-21T21:56:24-0400, Doug McIlroy wrote:
> I think it's pretty hopeless to ask for AI that can tell
> whether a pasted symbol is a hyphen or a minus sign.
> The answer is likely to depend on whether it is being
> pasted into a program or into a document.

Here's my attempt at clarifying the issue.

Regards,
Branden

--lu2avhqxorryirzf
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="groff-minus.patch"
Content-Transfer-Encoding: quoted-printable

diff '--color=3Dalways' -u groff.orig/groff.7 groff/groff.7
=1B[1m--- groff.orig/groff.7	2017-04-21 22:30:26.841049571 -0400
+++ groff/groff.7	2017-04-21 22:48:22.891848022 -0400
=1B[0m=1B[36m@@ -2826,7 +2826,13 @@=1B[0m
 .
 .TP
 .ESC -
=1B[31m-The \- (minus) sign in the current font.=1B[0m
=1B[32m+The \- (minus) sign in the current font,
+except in the
+.B an
+and
+.B andoc
+macro packages used for manual pages, where it stands for the ASCII
+hyphen-minus (0x2D).=1B[0m
 .
 .TP
 .ESC _
=1B[36m@@ -2836,7 +2842,8 @@=1B[0m
 .
 .TP
 .ESC .
=1B[31m-The same as a dot (\[oq].\[cq]).  Necessary in nested macro=1B[0m
=1B[32m+The same as a dot (\[oq].\[cq]).
+Necessary in nested macro=1B[0m
 definitions so that \[oq]\[rs]\[rs]..\[cq] expands to \[oq]..\[cq].
 .
 .TP
diff '--color=3Dalways' -u groff.orig/groff_char.7 groff/groff_char.7
=1B[1m--- groff.orig/groff_char.7	2017-04-21 22:14:32.801694552 -0400
+++ groff/groff_char.7	2017-04-21 22:49:57.282990951 -0400
=1B[0m=1B[36m@@ -269,6 +269,16 @@=1B[0m
 .B -
 the ISO \%latin1 \[oq]Hyphen, Minus Sign\[cq] (code\ 45) prints as a
 hyphen; a minus sign can be obtained with \[oq]\f(CW\e-\fP\[cq].
=1B[32m+.I Exception:
+In the
+.B an
+and
+.B doc
+macro packages used for manual pages, \[oq]\f(CW\e-\fP\[cq] is mapped
+back to code\ 45; a hyphen or dash of the appropriate width can be found
+in the table
+.BR Punctuation ,
+below, and a mathematical minus sign with \[oq]\f(CW\e(mi\fP\[cq].=1B[0m
 .
 .
 .TP

--lu2avhqxorryirzf--

--dwpzjkcq2ermcjb4
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlj6xTwACgkQ0Z6cfXEm
bc6dOg/+OoTQ98KjnY8pDTATIbaMc5KaYFJ7UZYMaO8h+inFGtVtiVQgAYXE0wU8
vm+oy7NVaXPkiAXmQH91zD22E6oDLENmCAmR1nV3usb6EcPzA2Ozb6W350pNowhc
Z3NAU2C3yqM8wSe3uLMVvxD4fU53qScoUnNyCPPSOzfQVhOjs6uG7GDCap2c1+tk
iwuRSqQg84s8uCeOriI2qssdYrr1R/hCc7WUx55rWlpSyzR/hHqYGIaCh1hZpEAs
aizGJspkntTiin6vrbG9F7uaJPwCXhJWk70Mb/tkF3xLnLKKDkMLFTw/pYuhO1dk
6JY5Tcx3mQM2YgGAseYvSJ1EZEmhrqAtBbqI40+PEKDAT7cSQnOZDbtXm03sBTWS
5EnBAWCxbEiPMNTisiBPfpyx5pTwaYmlSPgrtxoEhXVK+9iiOSTxIuM4hehCCbU+
8WC816wKHwQVpg17cJKNxt/N7sWSsIsghrhfbyymCHIpVNGP8DUjPvwqicC4bVtz
pIiICL2UHqlY32EpPiusLyfTcZX4JvMkwhGB/qRc9MOjFJ6qcnJY4UJjeg9yD4Ki
sTft8+tq3Mg2B4bmjLTjBeozrCVFjUenfXfzNFb3jnyqWplHbXOYWY8mFM7Qe0jq
qgZAt6qrQnk9YVRcgOt1DDj3D1VGmvPb6MOau79yhFnefJjl1Yo=
=dtav
-----END PGP SIGNATURE-----

--dwpzjkcq2ermcjb4--


From MAILER-DAEMON Sat Apr 22 07:47:39 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1tVr-0003qi-Ea
	for mharc-groff@gnu.org; Sat, 22 Apr 2017 07:47:39 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59302)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1tVp-0003qX-BX
	for groff@gnu.org; Sat, 22 Apr 2017 07:47:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d1tVm-00029w-8h
	for groff@gnu.org; Sat, 22 Apr 2017 07:47:37 -0400
Received: from relay01.pair.com ([209.68.5.15]:60543)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d1tVm-00029m-3y
	for groff@gnu.org; Sat, 22 Apr 2017 07:47:34 -0400
Received: from orac.inputplus.co.uk (unknown [81.174.188.214])
	by relay01.pair.com (Postfix) with ESMTP id 3C973D00B0B
	for <groff@gnu.org>; Sat, 22 Apr 2017 07:47:31 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 4F5F2214E2
	for <groff@gnu.org>; Sat, 22 Apr 2017 12:47:30 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
Date: Sat, 22 Apr 2017 12:47:30 +0100
Message-Id: <20170422114730.4F5F2214E2@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 11:47:38 -0000

Hi,

Doug wrote:
> I think it's pretty hopeless to ask for AI that can tell
> whether a pasted symbol is a hyphen or a minus sign.
> The answer is likely to depend on whether it is being
> pasted into a program or into a document.

Right.  I'm happy for the typist to put in the effort.  Perhaps I'm
getting too hung up on making the output be pasteable, but it's
annoying, and not obvious to some, why `foo=E2=80=90bar' doesn't run when=
 pasted
from foo-bar(1).

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sat Apr 22 10:15:52 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1vpI-00061m-Gm
	for mharc-groff@gnu.org; Sat, 22 Apr 2017 10:15:52 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51944)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vpG-00060q-B8
	for groff@gnu.org; Sat, 22 Apr 2017 10:15:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vpC-00025e-I2
	for groff@gnu.org; Sat, 22 Apr 2017 10:15:50 -0400
Received: from sdaoden.eu ([217.144.132.164]:38696)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vpC-00025N-9a
	for groff@gnu.org; Sat, 22 Apr 2017 10:15:46 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 87A0816051; Sat, 22 Apr 2017 16:15:44 +0200 (CEST)
Date: Sat, 22 Apr 2017 16:15:48 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170422141548.gzoKG%steffen@sdaoden.eu>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
	<20170422025151.usnhi7hargsmb375@crack.deadbeast.net>
In-Reply-To: <20170422025151.usnhi7hargsmb375@crack.deadbeast.net>
Mail-Followup-To: groff@gnu.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
User-Agent: s-nail v14.9.0-pre4-11-g745b3025
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 14:15:51 -0000

"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
 |At 2017-04-21T21:56:24-0400, Doug McIlroy wrote:
 |> I think it's pretty hopeless to ask for AI that can tell
 |> whether a pasted symbol is a hyphen or a minus sign.
 |> The answer is likely to depend on whether it is being
 |> pasted into a program or into a document.
 |
 |Here's my attempt at clarifying the issue.

I for myself will keep all that in my queue; but i think it will
be better to write something like "unless documented otherwise",
and then add such notes for man(7) and mdoc(7).

--steffen


From MAILER-DAEMON Sat Apr 22 10:19:49 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d1vt6-0006SE-Tv
	for mharc-groff@gnu.org; Sat, 22 Apr 2017 10:19:48 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53010)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vt5-0006S2-I8
	for groff@gnu.org; Sat, 22 Apr 2017 10:19:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vt2-0003Eu-BH
	for groff@gnu.org; Sat, 22 Apr 2017 10:19:47 -0400
Received: from sdaoden.eu ([217.144.132.164]:38698)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d1vt2-0003Em-3k
	for groff@gnu.org; Sat, 22 Apr 2017 10:19:44 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 9E29716051; Sat, 22 Apr 2017 16:19:43 +0200 (CEST)
Date: Sat, 22 Apr 2017 16:19:47 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: groff@gnu.org
Message-ID: <20170422141947.8MonX%steffen@sdaoden.eu>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
In-Reply-To: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
Mail-Followup-To: groff@gnu.org, Doug McIlroy <doug@cs.dartmouth.edu>
User-Agent: s-nail v14.9.0-pre4-11-g745b3025
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 14:19:48 -0000

Doug McIlroy <doug@cs.dartmouth.edu> wrote:
 |I think it's pretty hopeless to ask for AI that can tell
 |whether a pasted symbol is a hyphen or a minus sign.
 |The answer is likely to depend on whether it is being
 |pasted into a program or into a document.

Of course you are right.
Just ignore my rash messages, please.

--steffen


From MAILER-DAEMON Sat Apr 22 15:36:59 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d20q3-0004D8-8c
	for mharc-groff@gnu.org; Sat, 22 Apr 2017 15:36:59 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54347)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d20q0-0004Cw-RV
	for groff@gnu.org; Sat, 22 Apr 2017 15:36:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d20pv-0007T6-VA
	for groff@gnu.org; Sat, 22 Apr 2017 15:36:56 -0400
Received: from mail-qt0-x236.google.com ([2607:f8b0:400d:c0d::236]:35691)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d20pv-0007SP-Q9
	for groff@gnu.org; Sat, 22 Apr 2017 15:36:51 -0400
Received: by mail-qt0-x236.google.com with SMTP id y33so90361635qta.2
	for <groff@gnu.org>; Sat, 22 Apr 2017 12:36:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=Va/oQ5DKwX6Bh1J0BlqzD4RsVVqRaFr/2JXOl2tWCF8=;
	b=N6ON0qBziJ29+Mp6gmYEMzUbuvCN8bpx38eCobS16dsP1kLVFBUKSKJY7FQfhIoMg/
	6RY0qenMUWdNZ4PHsvYbe3sicCpn0r+dVIDpT3HQtkhyLJeFBw6MzztTR3lAayp9EG2W
	osX8RHmrFISCR/j2sp1A5B4U0dSvd4xS4Qgd5VW/RQvJfEXYKs9KbpxFBKb+7pFsTTZQ
	aMhHyjVWxAwScbxCWFVhOpH8lUnWaWcofFI7xWjGUJHJnZXWzTCBF1Q7h2TcGj6rAsTY
	Qkt1bu9JUvfF1z/Ek/2J7Y10EDMbI7bOYirwb7QRghHKAqw5Abrc9Ezou/pyh7tJ/51h
	eQhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=Va/oQ5DKwX6Bh1J0BlqzD4RsVVqRaFr/2JXOl2tWCF8=;
	b=G34tnPG9ilwjUPhwNEqP/8T/FkvWbRaR3R8iVZOZYkC++C4mtnJSh47i6AaZivX7cH
	ZTishU7giRFDsCWOjlFxTk/GA7CZqjuFBU5GRY5GV+2jIG/U6qIZ8cyYh3vlqP3jaeLS
	ajvE00xpJVAEVSJKj/u0GfWVAD8gk4aUYd8ipiOl8UiNm2SkKVS+PHkA1pOlA+T2qwgk
	BVu8o/fY9J9Ia0Kn0zorJjb8EqjaDumUip87FDq/NptK1p8CtLv5rZ1hX2oIB5uhlIpn
	WLvTS1oD0A4rIAGsu5Q3J5EG+Y1kd3jE1M9wyFApEWgpLFf5TXmNQTLPTmEdFG5zTzxo
	8Anw==
X-Gm-Message-State: AN3rC/42Cp5JePU0f9V2x2TUQ7FP928lTK5Lq1pCnlq7klEWlBQNqcYX
	9fpY7p7dANKeljwokuY=
X-Received: by 10.200.57.226 with SMTP id v89mr20727036qte.255.1492889810973; 
	Sat, 22 Apr 2017 12:36:50 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	136sm4959554qke.33.2017.04.22.12.36.49 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 22 Apr 2017 12:36:49 -0700 (PDT)
Date: Sat, 22 Apr 2017 15:36:47 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170422193645.mroruphgf2sc7ujk@crack.deadbeast.net>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
	<20170422025151.usnhi7hargsmb375@crack.deadbeast.net>
	<20170422141548.gzoKG%steffen@sdaoden.eu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="qt3prhwycs3ww3pv"
Content-Disposition: inline
In-Reply-To: <20170422141548.gzoKG%steffen@sdaoden.eu>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:400d:c0d::236
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 19:36:57 -0000


--qt3prhwycs3ww3pv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-22T16:15:48+0200, Steffen Nurpmeso wrote:
> "G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
>  |At 2017-04-21T21:56:24-0400, Doug McIlroy wrote:
>  |> I think it's pretty hopeless to ask for AI that can tell
>  |> whether a pasted symbol is a hyphen or a minus sign.
>  |> The answer is likely to depend on whether it is being
>  |> pasted into a program or into a document.
>  |
>  |Here's my attempt at clarifying the issue.
>=20
> I for myself will keep all that in my queue; but i think it will
> be better to write something like "unless documented otherwise",
> and then add such notes for man(7) and mdoc(7).

Sounds reasonable.  Interested in a revised patch to do just that?  ;-)

Regards,
Branden

--qt3prhwycs3ww3pv
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlj7sLQACgkQ0Z6cfXEm
bc4IfA//bHTiaogl6HOI/HLw5hn/en3pLaNIlgCDx6JLxS4qhC9n0GCaNP6CmpuX
Eb7R3pbuDVPQX0+GPxiNMCJBDtoFfgR03cde2XxPo1YFCHAXBUbIgbzk2oPS6kMF
r2z/eXp1SDrdXZKSeMytiN6TQz7ZF5Ag1/w4aJ83dsLUuaPpj6HcuP2gQfQzQGQ+
IPqoEuFHfYxMGTECWl+AqV2P0u/H4dYGFYcuL5R+cjyoHVs+3ORqalEy2r5baE2C
wLeBJww/x3asFla1M/xCu3zYdQ2ZnBwbs513Co+4n9bJDztSXJovtf+zQXcFD7nI
LqR30aXAV4hkd/TU87rbaBShcJdBLHLvPsg1Z7lmzHoEhr4jcDXOQOMqp1KV08yZ
w2tS+zNqPptwgZR8wuCPR4aCeYDchR6UeZVyfRU3dPUwhDmM8fmIyJppbME3Wttx
0Kpa9RTArU+3Gbyb1Qg7FJQTiNtkShHzQcfvUbF7DXPr0bfTgP5l78+YC9g1Mh60
YHbv9dzPGFSGhTrpBElmU0iTRhbctHOsep5X+YP8jwCWt6Z38yOJUHw9m/+LianS
n1NS4LPj7FwhvLaUR/GRIXHEtR3bfjMdMrDXK2mUV/Rd7DUyK+a6NOW/xaQA5vcT
5fDidj4sMJh1zcHitLF+nxfPnQNW7ufZs0AoEeMM0EDEo41OKsE=
=tzs2
-----END PGP SIGNATURE-----

--qt3prhwycs3ww3pv--


From MAILER-DAEMON Sat Apr 22 17:48:55 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d22tj-0004uc-6O
	for mharc-groff@gnu.org; Sat, 22 Apr 2017 17:48:55 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47061)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d22tf-0004uO-Vu
	for groff@gnu.org; Sat, 22 Apr 2017 17:48:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d22tc-0000pJ-TQ
	for groff@gnu.org; Sat, 22 Apr 2017 17:48:52 -0400
Received: from sdaoden.eu ([217.144.132.164]:38718)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d22tc-0000ow-IR
	for groff@gnu.org; Sat, 22 Apr 2017 17:48:48 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 4F00D16051; Sat, 22 Apr 2017 23:48:46 +0200 (CEST)
Date: Sat, 22 Apr 2017 23:48:45 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: groff@gnu.org
Message-ID: <20170422214845.IX3sI%steffen@sdaoden.eu>
References: <201704220156.v3M1uOcE013999@tahoe.cs.Dartmouth.EDU>
	<20170422025151.usnhi7hargsmb375@crack.deadbeast.net>
	<20170422141548.gzoKG%steffen@sdaoden.eu>
	<20170422193645.mroruphgf2sc7ujk@crack.deadbeast.net>
In-Reply-To: <20170422193645.mroruphgf2sc7ujk@crack.deadbeast.net>
Mail-Followup-To: groff@gnu.org
User-Agent: s-nail v14.9.0-pre4-11-g745b3025
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=-=XKSVrfCgH5VSOzjGIZCokAEtpYLDm5XBF8KC=-="
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 21:48:53 -0000

This is a multi-part message in MIME format.

--=-=XKSVrfCgH5VSOzjGIZCokAEtpYLDm5XBF8KC=-=
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-ID: <20170422214845.e3TfL%steffen@sdaoden.eu>

"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
 |At 2017-04-22T16:15:48+0200, Steffen Nurpmeso wrote:
 |> "G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
 |>|At 2017-04-21T21:56:24-0400, Doug McIlroy wrote:
 |>|> I think it's pretty hopeless to ask for AI that can tell
 |>|> whether a pasted symbol is a hyphen or a minus sign.
 |>|> The answer is likely to depend on whether it is being
 |>|> pasted into a program or into a document.
 |>|
 |>|Here's my attempt at clarifying the issue.
 |> 
 |> I for myself will keep all that in my queue; but i think it will
 |> be better to write something like "unless documented otherwise",
 |> and then add such notes for man(7) and mdoc(7).
 |
 |Sounds reasonable.  Interested in a revised patch to do just that?  ;-)

Maybe so?  But, like its name says...
A nice rest-weekend i wish.

--steffen

--=-=XKSVrfCgH5VSOzjGIZCokAEtpYLDm5XBF8KC=-=
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="stumble-into-town.diff"
Content-ID: <20170422214845.jjiFP%steffen@sdaoden.eu>

diff --git a/man/groff.7.man b/man/groff.7.man
index ed53ca1a..c4e636a1 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -2824,7 +2824,15 @@ Unescaped: left quote, backquote (ASCII 0x60).
 .
 .TP
 .ESC -
-The \- (minus) sign in the current font.
+The mathematical \- (minus) sign in the current font.
+Some macro packages, namely
+.BR groff_man (7)
+and
+.BR groff_mdoc (7) ,
+which support generation of Unix manual pages, map this to
+U+002D hyphen-minus instead.
+(E.g., this usually allows for copy and paste usage of
+manual content.)
 .
 .TP
 .ESC _
diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 1869f951..719b9f1c 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -268,7 +268,10 @@ single quotation mark; the original character can be obtained with
 .TP
 .B -
 the ISO \%latin1 \[oq]Hyphen, Minus Sign\[cq] (code\ 45) prints as a
-hyphen; a minus sign can be obtained with \[oq]\f(CW\e-\fP\[cq].
+hyphen; a mathematical minus sign can be obtained with
+\[oq]\f(CW\e(mi\fP\[cq].
+Explicit symbols can be found in the table
+.BR Punctuation .
 .
 .
 .TP
diff --git a/tmac/groff_man.7.man b/tmac/groff_man.7.man
index f207ef6d..e618f775 100644
--- a/tmac/groff_man.7.man
+++ b/tmac/groff_man.7.man
@@ -1135,6 +1135,14 @@ preprocessor(s).
 .SH "PORTABILITY AND TROFF REQUESTS"
 .\" --------------------------------------------------------------------
 .
+The
+.B man
+macros remap some characters, e.g., the minus sign \-.
+To gain specific punctuation and other symbols it is advisable
+to use explicit requests, see
+.BR groff_char (7)
+for more.
+.
 Since the
 .B man
 macros consist of groups of
diff --git a/tmac/groff_mdoc.7.man b/tmac/groff_mdoc.7.man
index 5968d0b6..36541720 100644
--- a/tmac/groff_mdoc.7.man
+++ b/tmac/groff_mdoc.7.man
@@ -4147,6 +4147,14 @@ A normal user will never need it.
 .
 .Sh "FORMATTING WITH GROFF, TROFF, AND NROFF"
 .
+The
+.Nm
+macros remap some characters, e.g., the minus sign \-.
+To gain specific punctuation and other symbols it is advisable
+to use explicit requests, see
+.Xr groff_char 7
+for more.
+.Pp
 By default, the package inhibits page breaks, headers, and footers if
 displayed with a
 .Tn TTY

--=-=XKSVrfCgH5VSOzjGIZCokAEtpYLDm5XBF8KC=-=--


From MAILER-DAEMON Sun Apr 23 12:10:11 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2K5S-00084g-Va
	for mharc-groff@gnu.org; Sun, 23 Apr 2017 12:10:11 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52506)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d2K5Q-00080G-In
	for groff@gnu.org; Sun, 23 Apr 2017 12:10:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d2K5N-0002qR-EN
	for groff@gnu.org; Sun, 23 Apr 2017 12:10:08 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:58116)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1d2K5N-0002q8-AS
	for groff@gnu.org; Sun, 23 Apr 2017 12:10:05 -0400
Received: from coolidge.cs.Dartmouth.EDU (coolidge.cs.dartmouth.edu
	[129.170.213.217])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v3NGA4Hu019251
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
	for <groff@gnu.org>; Sun, 23 Apr 2017 12:10:04 -0400
Received: from coolidge.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTP id
	v3NGA4UK010075 for <groff@gnu.org>; Sun, 23 Apr 2017 12:10:04 -0400
Received: (from doug@localhost)
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v3NGA36r010074
	for groff@gnu.org; Sun, 23 Apr 2017 12:10:03 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
Date: Sun, 23 Apr 2017 12:10:03 -0400
To: groff@gnu.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Apr 2017 16:10:09 -0000

>> I think it's pretty hopeless to ask for AI that can tell
>> whether a pasted symbol is a hyphen or a minus sign.
>> The answer is likely to depend on whether it is being
>> pasted into a program or into a document.
>
> Right.  I'm happy for the typist to put in the effort.  Perhaps I'm
> getting too hung up on making the output be pasteable, but it's
> annoying, and not obvious to some, why `foo?bar' doesn't run when pasted
> from foo-bar(1).

Interesting difference in habits. I never look at groff-ed man pages on
line--only the default nroff, which is fine for pasting, and more
importantly, examinable with a full-featured editor.

And I don't see how a typist can foresee what I am going to
paste text into any better than AI can.  After all, I write
man pages and other documents *about* programs in volume
comparable to programs themselves.

Doug


From MAILER-DAEMON Mon Apr 24 03:29:22 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2YR0-0005uP-Jc
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 03:29:22 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54124)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2YQx-0005ro-UD
	for groff@gnu.org; Mon, 24 Apr 2017 03:29:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2YQu-0007Jn-0a
	for groff@gnu.org; Mon, 24 Apr 2017 03:29:19 -0400
Received: from mail-yb0-x231.google.com ([2607:f8b0:4002:c09::231]:35741)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2YQt-0007Jf-Rn
	for groff@gnu.org; Mon, 24 Apr 2017 03:29:15 -0400
Received: by mail-yb0-x231.google.com with SMTP id 6so56328689ybq.2
	for <groff@gnu.org>; Mon, 24 Apr 2017 00:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=TYN/HLWVcEKRykR/+9OCl2+p4rgP/Lri71EmHojjBxc=;
	b=XXpSmWQSb+TYjtWmCqrZ58MxEtDpTtNImE0NZb+8gabC7rOG/X/Ra+klGVhuxQmMIo
	g4RuZd25AdTKMgHlhvHyrwqnl1YQO6JpEMKrNmQG7YI8nn2B16gdf30tASJuFlFvIWwZ
	nFXSlqDw9PumIbD7SaRwVBswFJ5D8b7t3dcOxDNJwx45OEuz+vSIxMj5XJIF1X351dff
	4KxOOmLsraaLFVTgr0+axZwykJofw+K/MAS/RI1mKvMrgvEK1gRRAMoHP0PsBUY0TVwA
	H0m7vh5vCmNjDvzp5BKQZvV8wd8rtUtKq5Vg5KGkJFZ5qPFjxwWoIhq1Hccax6W6+UGc
	4ggA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=TYN/HLWVcEKRykR/+9OCl2+p4rgP/Lri71EmHojjBxc=;
	b=BRbnTQH4ycX9ehqONNouJUK4UKqReqiin2wZucopyrOLwj4UKf/we2SpXzd6qhMslP
	Yls7H7WwmmBTPbOyTXJP/oDfSko0wTLgy3uEfo0C7FNnGxzumXphOVswZb53f2ivzcwY
	7iJz96apyaPQoE/m5XHCCQRb2yrkRnUGQNS3UXkqmwMoLzLOgRFplQy99I4HcqcVojtR
	epkKERvpzDw5B8XSF3Wr33i2Fx2lzir5m+qPFOs3qMxbxZUzHL/PhOL05l0/R/uUodrY
	Qj8hoZG4GeggPhZHUJLJic6hxwGqfPvTxQUIlHeg28i4Gfqi6SFpjsDLKbLDlQaHvTQc
	4q7g==
X-Gm-Message-State: AN3rC/71XXXSVcwdDOjVlLZQTmKmEMq3NUnpD7eKNsPDEtOICNSBmBDE
	o+TpRUByHuRHcbLFQI0=
X-Received: by 10.37.91.136 with SMTP id p130mr3662591ybb.2.1493018953373;
	Mon, 24 Apr 2017 00:29:13 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	z17sm6922475ywd.67.2017.04.24.00.29.11 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 00:29:12 -0700 (PDT)
Date: Mon, 24 Apr 2017 03:29:09 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="vtrpf2j5y6xa3mab"
Content-Disposition: inline
In-Reply-To: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::231
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 07:29:21 -0000


--vtrpf2j5y6xa3mab
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

At 2017-04-23T12:10:03-0400, Doug McIlroy wrote:
> Interesting difference in habits. I never look at groff-ed man pages
> on line--only the default nroff, which is fine for pasting, and more
> importantly, examinable with a full-featured editor.

A lot of (GNU/)Linux systems these days are configured with
UTF-8-capable terminal emulators by default, so grotty emits UTF-8
characters.  Even 15-20 years ago, on my Debian systems at least, I was
getting ISO 8859-1 to my consoles and xterms, and those damned hyphens
would show up if the source was wrong.

So the former advantage was lost with the march of post-ASCII progress,
but the latter remains.  In fact, with a font with good glyph coverage
like FreeFont (Mono)[1], every glyph save two in groff_char(7) renders,
and bold and italics look nice.

> And I don't see how a typist can foresee what I am going to paste text
> into any better than AI can.  After all, I write man pages and other
> documents *about* programs in volume comparable to programs
> themselves.

There have been a few attempts at "manlint" programs over the years but
all seem to have died away.  Perhaps the fate of "lint" itself points to
the correct solution; maybe we should be adding coaching diagnostics
into groff (and its macro packages) itself, where they can be enabled
with a flag.

The triple-overloading of codepoint 45 in ASCII as hyphen-minus-dash
sure did impose a technical debt.  :(

Regards,
Branden

--vtrpf2j5y6xa3mab
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlj9qTkACgkQ0Z6cfXEm
bc5isQ/+OEkZb+DPOAEolfEc6mDqykV8f4XCa5OQN/Uhqep9jMTPQ5lePFF4WJiU
hSVpucbOs2p+HpHJ3mVNQpr1lkt9FYZ5lqW1o1Z8V3N+mKAECWuaeEpZ/A3a7isu
jQYUwp+zdhgR7P368mL/wuKQtrS44wuOFe4whp8lm7QGaCopueFSJKiN66gX078c
JqhSZ04S4xauz3uATTxJRm+MpbwIZvxIOp8wXzOVh1ebMG7E5J8Xu6M/GVKoT08i
041XNyQG1UDAszG0MvEBVmUpXRmMdwI4qiXQEJSTh/iVeVzn5MThrla+obcg6bk3
OsYJCfkOy9VIHvzs5XQfO3N2ZcVJE+65Vmjtg87AyiavQp7chXkRmV8boHhjBAH4
MddQhjJ1fsRd4+OAlWeEgxf2UkIKe8TFtde67lOh1KZuOdnHLhqsZk+iW2MDitp1
XD1VTlzz7xAgQki0V7NOoGSPLf3PsEjH7KhPgIlAyiyC6mxU/2He4mySIq1L7lMw
9Q+NsgV7+NzzfL0BWfmilLdBKkU767C6N13L8FAtTj3z4DiOrvoM59SCJEx9SZnZ
uLJMjAm06e4OpWA/gfRwU9+BbeHZXO5NyMkozon3nQbQQpjRocYyzZCjchvsSWJI
zOHnRRLWDQHOw0cm9gzYbh/LkDmTCGjH8cz62nsZvzkcfBn8aII=
=DnVZ
-----END PGP SIGNATURE-----

--vtrpf2j5y6xa3mab--


From MAILER-DAEMON Mon Apr 24 07:16:47 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2bz5-00078C-50
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 07:16:47 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56535)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2bz2-00077d-Cy
	for groff@gnu.org; Mon, 24 Apr 2017 07:16:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2byz-00070M-6w
	for groff@gnu.org; Mon, 24 Apr 2017 07:16:44 -0400
Received: from relay01.pair.com ([209.68.5.15]:37042)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d2byz-000707-2p
	for groff@gnu.org; Mon, 24 Apr 2017 07:16:41 -0400
Received: from orac.inputplus.co.uk (156.187.189.80.dyn.plus.net
	[80.189.187.156])
	by relay01.pair.com (Postfix) with ESMTP id 022C9D00B54
	for <groff@gnu.org>; Mon, 24 Apr 2017 07:16:40 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 097A1201ED
	for <groff@gnu.org>; Mon, 24 Apr 2017 12:16:39 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
Date: Mon, 24 Apr 2017 12:16:39 +0100
Message-Id: <20170424111639.097A1201ED@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 11:16:45 -0000

Hi Branden,

> and those damned hyphens would show up if the source was wrong.

Right, that's the problem.

    $ find /etc/machine-id | nroff | xargs ls
    ls: cannot access '/etc/machine=E2=80=90id': No such file or director=
y
    $=20

Judging by the lack of suggestions, I'm assuming `\-' is the best bet to
get a paste-able ASCII `-'.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Mon Apr 24 07:50:28 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2cVg-0005Ou-Mz
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 07:50:28 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34001)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2cVe-0005Oc-LU
	for groff@gnu.org; Mon, 24 Apr 2017 07:50:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2cVa-0007da-NH
	for groff@gnu.org; Mon, 24 Apr 2017 07:50:26 -0400
Received: from mail-yb0-x243.google.com ([2607:f8b0:4002:c09::243]:32868)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2cVa-0007dT-Ik
	for groff@gnu.org; Mon, 24 Apr 2017 07:50:22 -0400
Received: by mail-yb0-x243.google.com with SMTP id d72so3312673ybh.0
	for <groff@gnu.org>; Mon, 24 Apr 2017 04:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=B2Pqjfxy2t9r/0RSNV4rs0WVhHVj8MO65ZyCJr3Qhw4=;
	b=uxL6L4pIfWXEVk18DNjQ+/TgLekFie3aAx2nQn3FpARvyrN/jtbZ1I9e1se7WlXeet
	8mojWuKSi0ObmaMMwPav8TrEj9GxOvpJFlZueausRdTSm3cNyXLCNDNgzoekQ3cq2zP8
	Q93iPu2VzHDNvw49FAy7MZrmnnsm+hYuXuFw5VChCPvR0ZFsDAAVPRtTdCzgTbpwjIL4
	v/fH1zG/sok/BhIwONVlKiVRVemeS4/NENxouUk2GBhWvScR1EiuKkvmtVv2p1eSOP8V
	4tBJ0lJ540jMCSUd2SFHOHWQQXXXwF9tqwApwEZcdLbm7L069LKAS3zbV0rSpS6noIUi
	d6Tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=B2Pqjfxy2t9r/0RSNV4rs0WVhHVj8MO65ZyCJr3Qhw4=;
	b=YQcvpGiped0xtZveM8B938KBzHoly2YOfHJ/RkOMYVA6741G5CbLW2kqIf2Kr1D9Y1
	NQpwQ0RptnwkM8ZGDYSYoZR5x/06YNOx52cUn2NXlLU29fNVXsBbH8Kq7/DqTPcnfEI8
	LkZ4Y3CN3Ia52jh2hWU1xho5XaZ99h9aiA8oaBLRzNzZ3ClwjY61crk39VoTwwU3POF2
	KHO1SBjYPVkrRH9IqOtE87nKZmAEaqJwSm3g92zj4oYgvsyHqrOS8OpqP22dIBpHRziW
	37BuoUDoID/ieep1xKo3GBk2tprIASkdxB23uvjOEnWyPwR5Itqhv4+JzDxSMnAXZ1Em
	Twag==
X-Gm-Message-State: AN3rC/5GthsjrX7e8hyWRHtZv4rgm/yzDAlgwWDiiC8yPNNeHyJ/9ZQT
	LFC4vMHLWO7TdtmAzWULhQ==
X-Received: by 10.37.75.199 with SMTP id y190mr4227607yba.58.1493034621639;
	Mon, 24 Apr 2017 04:50:21 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	z17sm7077605ywd.67.2017.04.24.04.50.20
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 04:50:20 -0700 (PDT)
Date: Mon, 24 Apr 2017 07:50:18 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424111639.097A1201ED@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::243
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 11:50:27 -0000

At 2017-04-24T12:16:39+0100, Ralph Corderoy wrote:
> Judging by the lack of suggestions, I'm assuming `\-' is the best bet to
> get a paste-able ASCII `-'.

I certainly believe that is the intent of the an and doc macro package
authors.

$ grep -n -3 45 /usr/share/groff/current/tmac/{an,doc}*.tmac
/usr/share/groff/current/tmac/an-old.tmac-678-.if '\*[.T]'utf8' \{\
/usr/share/groff/current/tmac/an-old.tmac-679-.  rchar \- - ' `
/usr/share/groff/current/tmac/an-old.tmac-680-.
/usr/share/groff/current/tmac/an-old.tmac:681:.  char \- \N'45'
/usr/share/groff/current/tmac/an-old.tmac:682:.  char  - \N'45'
/usr/share/groff/current/tmac/an-old.tmac-683-.  char  ' \N'39'
/usr/share/groff/current/tmac/an-old.tmac-684-.  char  ` \N'96'
/usr/share/groff/current/tmac/an-old.tmac-685-.\}
--
/usr/share/groff/current/tmac/doc.tmac-3453-.ec
/usr/share/groff/current/tmac/doc.tmac-3454-.if '\*[.T]'utf8' \{\
/usr/share/groff/current/tmac/doc.tmac-3455-.rchar \- - ' `
/usr/share/groff/current/tmac/doc.tmac:3456:.char \- \N'45'
/usr/share/groff/current/tmac/doc.tmac:3457:.char  - \N'45'
/usr/share/groff/current/tmac/doc.tmac-3458-.char  ' \N'39'
/usr/share/groff/current/tmac/doc.tmac-3459-.char  ` \N'96'
/usr/share/groff/current/tmac/doc.tmac-3460-.\}

Regards,
Branden


From MAILER-DAEMON Mon Apr 24 08:08:33 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2cnB-0002Kj-GR
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 08:08:33 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38644)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2cn5-0002KX-FN
	for groff@gnu.org; Mon, 24 Apr 2017 08:08:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2cmx-0004L9-8L
	for groff@gnu.org; Mon, 24 Apr 2017 08:08:23 -0400
Received: from relay01.pair.com ([209.68.5.15]:38602)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d2cmx-0004Ku-3v
	for groff@gnu.org; Mon, 24 Apr 2017 08:08:19 -0400
Received: from orac.inputplus.co.uk (156.187.189.80.dyn.plus.net
	[80.189.187.156])
	by relay01.pair.com (Postfix) with ESMTP id ED097D00AE9
	for <groff@gnu.org>; Mon, 24 Apr 2017 08:08:17 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 2EF71201ED
	for <groff@gnu.org>; Mon, 24 Apr 2017 13:08:17 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
Date: Mon, 24 Apr 2017 13:08:17 +0100
Message-Id: <20170424120817.2EF71201ED@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 12:08:33 -0000

Hi Branden,

> I certainly believe that is the intent of the an and doc macro package
> authors.
...
> /usr/share/groff/current/tmac/an-old.tmac:681:.  char \- \N'45'
> /usr/share/groff/current/tmac/an-old.tmac:682:.  char  - \N'45'

Yes, but they nobble `-' too, so I could just write a sloppy man page
with `-', never using `\-', and it would paste from the terminal.  But
there's other -T in groff, and other troffs than groff too, with their
own -man.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Mon Apr 24 08:18:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2cwx-0007cF-Uf
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 08:18:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42538)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2cwv-0007Zy-4a
	for groff@gnu.org; Mon, 24 Apr 2017 08:18:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2cwq-0007o4-6L
	for groff@gnu.org; Mon, 24 Apr 2017 08:18:37 -0400
Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]:34881)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2cwq-0007nz-1H
	for groff@gnu.org; Mon, 24 Apr 2017 08:18:32 -0400
Received: by mail-yw0-x242.google.com with SMTP id k11so6623596ywb.2
	for <groff@gnu.org>; Mon, 24 Apr 2017 05:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=0aoMT4GwvuDpMdJM+b+K2Ool/XbklYafDxHfLd91zZw=;
	b=nPKWlmtviCZUV+Fdll0rr+uA63hOI+gktU3407bX+/VxbAR3rAXDZPdoKqEK6UzhlC
	EbtSOphpU4Cfse94VBNQAEGxOLSPaEzfLBHtxNiHt6Nd6CnkDNSMhzODAFJpvw7yhmx2
	y6WUxwItbYEyLy8ghD9Bhynw/33vMSZfnAB+8Z9QV21eLCToYNeIzG/4jvCDRCFLuOP9
	nEKc+eOlWHILO4odk0AiSUqnFi2xBf4dayYKwc8wYsRRfB+Jcn1OLgm5A9QJsVRhLMUG
	lSj9IZ0UKMXrv0wsdUDYf3oNNMGJUKSWumb3hoL7V6UDAf8t3XUebJeIWnm9z2v+/z5Z
	DgPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=0aoMT4GwvuDpMdJM+b+K2Ool/XbklYafDxHfLd91zZw=;
	b=meWStqpwPFY2oZKCqhRJImgBjzix1dsOp6sTR3cO98YvCBAQBP6ku82sCdB1EiFrXB
	Ykb9e618OXJerSDb7BKMhhe8jSohJf6y2Kxh4TkN/nF82ZPAl76p2ZnX3OQjc9rvhDwR
	o5UXZ6PMZfNGElzlo5UBsTGZiqoc0jYrrccICCwlCDqpHpxlfk3qo8oj5UXH/XQ7CIN9
	x9CuNa0My2xXrNFMbsP8oqWLYLnHkmJIXNDLYJjjvcCHDltAAQ06zxWnuzf9XX6wR8v2
	xHDeKvVFPEsVkskAMcBP7hBRW5kC+/3VQog/h/BkfNCqXKG+CXYgbNr8YiVfzVyS0cEY
	/eXw==
X-Gm-Message-State: AN3rC/6TzuXyKZjEhpsiAo7p/YmC7BQ6vBhdjANe8hw3y8ZQgiYzxnsj
	QGF5QU7FuKGuaQ==
X-Received: by 10.129.155.6 with SMTP id s6mr841937ywg.105.1493036311441;
	Mon, 24 Apr 2017 05:18:31 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	d80sm7087811ywh.75.2017.04.24.05.18.30
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 05:18:30 -0700 (PDT)
Date: Mon, 24 Apr 2017 08:18:28 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170424121826.qb734iy72burofyx@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424120817.2EF71201ED@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::242
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 12:18:38 -0000

At 2017-04-24T13:08:17+0100, Ralph Corderoy wrote:
> Hi Branden,
> 
> > I certainly believe that is the intent of the an and doc macro package
> > authors.
> ...
> > /usr/share/groff/current/tmac/an-old.tmac:681:.  char \- \N'45'
> > /usr/share/groff/current/tmac/an-old.tmac:682:.  char  - \N'45'
> 
> Yes, but they nobble `-' too, so I could just write a sloppy man page
> with `-', never using `\-', and it would paste from the terminal.

Yeah--that's a sop to the sloppy, perhaps an ill-advised one.

Debian's groff packages have the following in /etc/groff/man.local:

.  \" Debian: Strictly, "-" is a hyphen while "\-" is a minus sign, and the
.  \" former may not always be rendered in the form expected for things like
.  \" command-line options.  Uncomment this if you want to make sure that
.  \" manual pages you're writing are clear of this problem.
.  \" UNCOMMENTED: branden, 2017-04-08
.  if '\*[.T]'utf8' \
.    char - \[hy]

> But there's other -T in groff,

Right--even groff's macro packages only offer this sop on the UTF-8
device.

> and other troffs than groff too, with their
> own -man.

True, but even Heirloom troff goes to considerable effort to be groff-
compatible.

What would you like to see?

Regards,
Branden


From MAILER-DAEMON Mon Apr 24 10:39:27 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2f9D-0003zL-LE
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 10:39:27 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53437)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2f9A-0003xc-Nf
	for groff@gnu.org; Mon, 24 Apr 2017 10:39:25 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2f98-0005eg-0w
	for groff@gnu.org; Mon, 24 Apr 2017 10:39:24 -0400
Received: from scc-mailout-kit-01.scc.kit.edu ([129.13.231.81]:56859)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d2f97-0005dw-PT
	for groff@gnu.org; Mon, 24 Apr 2017 10:39:21 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d2f92-000254-OH; Mon, 24 Apr 2017 16:39:17 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d2f92-0006nA-0r; Mon, 24 Apr 2017 16:39:16 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d2f91-0007Q7-SZ; Mon, 24 Apr 2017 16:39:15 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 061bd53f;
	Mon, 24 Apr 2017 16:39:15 +0200 (CEST)
Date: Mon, 24 Apr 2017 16:39:15 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170424143915.GA47874@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424121826.qb734iy72burofyx@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 129.13.231.81
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 14:39:26 -0000

Hi,

i think it is clear due to Ralph's extensive analysis that this
whole thing is a mess:  Even looking at groff only, for historical
reasons, the input sequences

  -   \-   \(hy   \(mi   \(en

are handled differently across output devices and across macro sets,
so even using current groff alone, no consistent way exists to get
the equivalent of the Unicode HYPHEN-MINUS character, even though
that is important for manual pages.

Besides, writing manual pages absolutely needs to be simple.  Manual
pages must be written by programmers who may not know typography and
who are not prepared to, and shouldn't be required to, acquire
specialized knowledge just to write the required manuals together
with their code.  So even if we would come up with some elaborate
recommendation about hyphens/dashes/minuses in manual pages, it
would be useless because it wouldn't be followed in practice.

While i consider the above a serious issue, i'm much less worried
about Ralph's concern with old implementations.  Frankly, there are
only three practically relevant roff implementations that are widely
used for manual pages: groff, Heirloom, and mandoc.  The maintainers
are all active on this list and cooperate well.  So we have the
chance to decide something that is simple and implement it everywhere,
even if it diverges somewhat from historical practice.


To understand my following proposal, observe this:

First, in contrast to classical typography, we need four rather
than the usual three output characters (using Unicode names for
clarity without intending to imply that Unicode is used as the
character set by each output device):

 1. U+2010  HYPHEN
 2. U+2013  EN DASH
 3. U+2212  MINUS SIGN
 4. U+002D  HYPHEN-MINUS

The latter doesn't exist in normal typography, but is required for
programming and hence for manual pages.

In cases where you are not concerned about copy and paste but want
a particular typographic representation, no matter whether in a
manual page or in some other document, you can use the escape
sequences

  \(hy   \(mi   \(en

already now.  OUTSIDE manual pages, you can also use - for \(hy
(and you usually will do that) and you can use \- for \(mi (though
i probably wouldn't recommend that; it mostly exists for historical
reasons).

INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
already now because the three main implementations (including groff)
don't do that in the quite important -Tutf8 device.


So here is what i propose.

Let's not change anything (neither code nor recommendations) for
typesetting OUTSIDE manual pages, unless there are bugs in devices.

INSIDE manual pages (both -man and -mdoc), let's change - and \-
to always map to U+002D HYPHEN-MINUS for all devices and let's tell
people to simply use - for HYPHEN-MINUS and stop worrying.  Those
who care and are aware of such subtleties can use \(hy \(mi \(en
in running text in manuals, but 95% of manual page authors probably
won't, and that's not a problem at all.


This proposal has two downsides, but i consider both very minor
compared to the gain, which is having a consistent way to get U+002D
HYPHEN-MINUS in manual pages, and having a very simple rule that
has very good chances to actually be followed in practice and make
all this easily understandable for the future.

First minor downside for manual pages: Hyphens in running
text that are given as - will be rendered as HYPHEN-MINUS for
all devices.  But that's a very minor regression because that's
the case for the most important devices (ascii, utf8, html)
already now.  (Note that i'm not saying that utf8 is more
important than ps/pdf in general - only for manual pages.)

Second minor downside: Hyphen-minus signs in code elements that are
given as - (which we will then encourage!) may render as U+2010
HYPHEN on some legacy systems.  But that's an even smaller issue.
Which legacy systems are there in the first place?  Which of them
support anything except ascii and latin-1?  Who uses them?  Will
the users get upset about seeing hyphens in such cases?  I suspect
the answers are "very few, almost none, almost nobody, no".  And
if they do get upset, it will be easy for them to update their
software to follow groff's lead.


Assuming this is considered the right direction, how would one
best implement, in doc.tmac-u and an-old.tmac, - == \- == U+002D
for all devices?

Yours,
  Ingo


From MAILER-DAEMON Mon Apr 24 11:02:14 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2fVG-0001AF-0x
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 11:02:14 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58975)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2fVA-00017O-K0
	for groff@gnu.org; Mon, 24 Apr 2017 11:02:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2fV4-00058X-U4
	for groff@gnu.org; Mon, 24 Apr 2017 11:02:08 -0400
Received: from mail-yb0-x234.google.com ([2607:f8b0:4002:c09::234]:36647)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2fV4-00058K-Oz
	for groff@gnu.org; Mon, 24 Apr 2017 11:02:02 -0400
Received: by mail-yb0-x234.google.com with SMTP id s22so60838789ybe.3
	for <groff@gnu.org>; Mon, 24 Apr 2017 08:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mime-version:content-disposition
	:user-agent; bh=nlRPkED6HbbpwXdTd8WCAABp+4qJNuWTqvV2hMIs7lI=;
	b=U73CibVwJlUxmqukK8zjTWldtr1txjnj3XhGBpq7QjYJybUDVsaTGrR+rFNxZt5PyX
	PF20MwN/SK5W6X8Ci2geVdg2opq0JFkx2ofdzBcsTYTEejXygueMaleiST+l8vTIjRBR
	VX61bqrF3lwDS3T8j0W6Y3yb9ppK+R+eYz+GKdve9qT2si6Syqt8J4+P/YdJDreEyDeo
	mRNPdELzPuLUBSk9s2+7HVLyegkhjZbEc5Mz3pejG5/RkewjpA6qlYvjd5WIXduegGxd
	3QCZp7wLQSprOzjP7V7g9YVYg4RSthjT8S/REiNhyXsvNEnnCMyAg917GPEa504lEwq+
	FrWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-disposition:user-agent;
	bh=nlRPkED6HbbpwXdTd8WCAABp+4qJNuWTqvV2hMIs7lI=;
	b=RB/ela3NOUFxmn+REFosf/nsgneSlj86GEbzpwO66A4a4aF2bbmUGookfgPKb8pRpq
	O5+rry/G/xdEna1atm2W6ZUpQ+P07wcnlAJAksqHGqD87uiI2LPe/altLYSZyHh7qXIU
	nmNqXs1+VofHoDIgu45ZiLuJZCDMsgQmjBPVrTSJ4veMc/+9B7CtEO0562yUbvIxRWfG
	wCAzdXFtxleq6oep2Woh5fD5gD29mSB+20sjOAYu5Dhva33u1adcfN/vdaZEUSg+0V7F
	+/MRzuME4khdzcsdH6wzVaorRnBY6AiF5CGD8xQTkncNwkg/1RvVpYRtOoh6aWpdWdQS
	p5Jw==
X-Gm-Message-State: AN3rC/5jdgfd+NXkilpHL207VOVHGvxgoJA0mqH2L62RS0Ho+iO5QH2s
	48iCO5rHYmZv2jhk5vw=
X-Received: by 10.37.50.18 with SMTP id y18mr5051287yby.18.1493046121591;
	Mon, 24 Apr 2017 08:02:01 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	q30sm7276804ywa.31.2017.04.24.08.02.00 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 08:02:00 -0700 (PDT)
Date: Mon, 24 Apr 2017 11:01:58 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::234
Subject: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 15:02:12 -0000

Hi folks,

The ksh93 man page has the following in its source:

    .SS Field Splitting.
    After parameter expansion and command substitution,
    the results of substitutions are scanned for the field separator
    characters (those found in
    .SM
    .B IFS\^\c
    )
    and split into distinct fields where such characters are found.

I think the intention here was to get back to the normal-size roman font
after "IFS" without introducing a stretchable space (hence \c) but still
leave some room between the small bold IFS and the closing parenthesis,
hance the hair space \^.

My question is, were the man macros intended to work this way?  Should
we expect ")" to render in a small font, or full-size roman?

I ask because I have a change to the TP macro I'm testing on my system
that would, I think, make font life easier for a lot of man page
writers.  To my shock, the impact of that change was only about 1 dozen
out of the ~6,900 pages on my system, but the above was one of them.
(Most of those 1 dozen were in the man-db and groff packages, too.)

Regards,
Branden


From MAILER-DAEMON Mon Apr 24 11:22:47 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2fp9-0004aj-S0
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 11:22:47 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35931)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2fp7-0004aZ-No
	for groff@gnu.org; Mon, 24 Apr 2017 11:22:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d2fp4-0004S0-Kh
	for groff@gnu.org; Mon, 24 Apr 2017 11:22:45 -0400
Received: from relay01.pair.com ([209.68.5.15]:48417)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d2fp4-0004RY-Fj
	for groff@gnu.org; Mon, 24 Apr 2017 11:22:42 -0400
Received: from orac.inputplus.co.uk (156.187.189.80.dyn.plus.net
	[80.189.187.156])
	by relay01.pair.com (Postfix) with ESMTP id 5E8EDD01089
	for <groff@gnu.org>; Mon, 24 Apr 2017 11:22:38 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 93942201ED
	for <groff@gnu.org>; Mon, 24 Apr 2017 16:22:37 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
Date: Mon, 24 Apr 2017 16:22:37 +0100
Message-Id: <20170424152237.93942201ED@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 15:22:46 -0000

Hi Branden,

>     .SM
>     .B IFS\^\c
>     )
>
> I think the intention here was to get back to the normal-size roman
> font after "IFS" without introducing a stretchable space (hence \c)
> but still leave some room between the small bold IFS and the closing
> parenthesis, hance the hair space \^.

Agreed.

> My question is, were the man macros intended to work this way?  Should
> we expect ")" to render in a small font, or full-size roman?

.SM affect the next input line as it uses an input trap, `.it'.  `\c'
doesn't make an input line continue to the next as far as input traps
are concerned;  groff has .itc for that.  So the .SM is over by the `)'.

groff's Postscript output seems to agree.

    /F0 10 /Times-Roman@0 SF
    /F1 9 /Times-Bold@0 SF
    (IFS) 72 84 moveto show
    F0(\)) .75 0 rmoveto show

I welcome being corrected.  :-)

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Mon Apr 24 11:41:32 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2g7I-0003b6-Dh
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 11:41:32 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42936)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2g7F-0003ZX-Pv
	for groff@gnu.org; Mon, 24 Apr 2017 11:41:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2g7C-0002wl-Mw
	for groff@gnu.org; Mon, 24 Apr 2017 11:41:29 -0400
Received: from mail-yw0-x243.google.com ([2607:f8b0:4002:c05::243]:33426)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2g7C-0002wK-Hu
	for groff@gnu.org; Mon, 24 Apr 2017 11:41:26 -0400
Received: by mail-yw0-x243.google.com with SMTP id 203so14206231ywe.0
	for <groff@gnu.org>; Mon, 24 Apr 2017 08:41:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=pzt99MzRJH3mD6kNWBK7N+9d3DT+aW6qQYa7WzWaYHw=;
	b=Llzr9U/S1js3wsz7DK9SFMsjpdoi97f8nybzOuKSljyvzgIcO2nXgaWj1ndgW7ngSm
	WBmD8hddT6yOL6bXzssrPAwjg9WN7EvYKFAF5ln8amW0wGJ+mEKLCuluUw53Fm0k31a2
	hOEjcfATDZLbKV6F91HdPg2f2jkQCpidkUEBmiavrJvl1elfIFpS+tYfD2xs6EFf9cDG
	ZENWrHbjKzWxhIIjxIGmiE+zel6cpq4R/EDwAHJCCuyaS2URE9Qj6q+sKo9oOZ6EQeOU
	Q8VcEaogD3Sq+5wGFpQFCOH3Ga9zAaTnaipT6EKmFH5Evs6PWkFUsBgwR+0twUsnvAaA
	iZ/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=pzt99MzRJH3mD6kNWBK7N+9d3DT+aW6qQYa7WzWaYHw=;
	b=S0rbyTgGDqZw2KoQ4oFqQ7vqtG7iszKsJCOFWqbiKM0tKMu2aQgd0aaEM++mo++Wpf
	WyCWeSrD52mTGMq/wShHIFTK1gMlT7oUGv1QYeCcCZ0bdDCaDW9aZxhGnG5MGlRfjOd2
	4i4TlZxaGjdEK/4d9a9Kdc144WJ44xmQAcLMdndAXe86hCMx6iN49hEPF9AYechQRl03
	vZB8Vm0yXhV0hZorXCanUsv3Ax6AHs2Kc4IwLKMuPvW6E/A2nd2Y1pxvDFLZH/W07I1R
	50uLIqbG6u/SvOUTHVV6SfJqyDbo0A8q+qpNMos2IoxnYw9sTgEmj8sU3wtXsf01bID1
	WjXA==
X-Gm-Message-State: AN3rC/4WJqwea8enssmpQfXX74P4fE5K5+wg8zo+AgX0YDhFLbeNH1zV
	en+Ngj+eYQ/LsfZiFH+X9A==
X-Received: by 10.129.122.135 with SMTP id v129mr5849437ywc.67.1493048485777; 
	Mon, 24 Apr 2017 08:41:25 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id k1sm935170ywi.34.2017.04.24.08.41.23
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 08:41:24 -0700 (PDT)
Date: Mon, 24 Apr 2017 11:41:22 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424152237.93942201ED@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::243
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 15:41:31 -0000

At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote:
> .SM affect the next input line as it uses an input trap, `.it'.  `\c'
> doesn't make an input line continue to the next as far as input traps
> are concerned;  groff has .itc for that.  So the .SM is over by the `)'.

That's exactly the hack I wanted to make to the TP macro.  I want to
change its .it to an itc, thus:

.de1 TP
.  sp \\n[PD]u
.  if \\n[.$] .nr an-prevailing-indent (n;\\$1)
.  itc 1 an-trap
.  in 0
.  if !\\n[an-div?] \{\
.    ll -\\n[an-margin]u
.    di an-div
.  \}
.  nr an-div? 1
..

My objective is to enable us to migrate from ugly markup like this,
which is frequently seen in documentation of Unix command options that
take arguments:

.TP
.B \-scale \fIxfac\fR[\fB,\fIyfac\fR]
Multiply the horizontal and vertical window size by
.I xfac
and
.IR yfac ,
respectively.

to the more readable (and, I submit, more writable-by-the-novice):

.TP
.B \-scale \c
.IR xfac [, yfac ]
Multiply the horizontal and vertical window size by
.I xfac
and
.IR yfac ,
respectively.

I used the following technique to see what kind of impact this would
have on rendered man pages.

$ cd /usr/share/man
$ find man* -type f | wc -l
6939
$ for d in man*; do mkdir -p ~/tmp/stock-tp-macro/$d; for f in $d/*; \
do echo $f;  man -Tutf8 -l $f > ~/tmp/stock-tp-macro/${f/%.gz/.utf8.txt}; \
done; done
[install hacked macro to /etc/groff/man.local]
$ for d in man*; do mkdir -p ~/tmp/hacked-tp-macro/$d; for f in $d/*; \
do echo $f;  man -Tutf8 -l $f > ~/tmp/hacked-tp-macro/${f/%.gz/.utf8.txt}; \
done; done
$ cd ~/tmp
$ diff -urN stock-tp-macro hacked-tp-macro > tp.diff
$ diffstat tp.diff
 man1/apropos.1.utf8.txt     |    2 +-
 man1/eqn.1.utf8.txt         |   13 ++++++-------
 man1/geqn.1.utf8.txt        |   13 ++++++-------
 man1/grodvi.1.utf8.txt      |    4 ++--
 man1/ksh.1.utf8.txt         |    2 +-
 man1/ksh93.1.utf8.txt       |    2 +-
 man1/man.1.utf8.txt         |    2 +-
 man1/manpath.1.utf8.txt     |    2 +-
 man1/rksh.1.utf8.txt        |    2 +-
 man1/rksh93.1.utf8.txt      |    2 +-
 man1/ttf2pk.1.utf8.txt      |    2 +-
 man1/whatis.1.utf8.txt      |    2 +-
 man5/groff_out.5.utf8.txt   |    6 +++---
 man7/groff_hdtbl.7.utf8.txt |   18 +++++++++---------
 man7/groff_mm.7.utf8.txt    |   20 ++++++++++----------
 man7/groff_ms.7.utf8.txt    |    2 +-
 16 files changed, 46 insertions(+), 48 deletions(-)

Some of these are dupes due to the fact that I overlooked symlinked
manpages.

...and some of those look like source bugs exposed by my macro change.
I already have patches ready for them, except for the ksh93 page.

Is my idea to change the definition of TP a lunatic one?

And even if it is, is it worth doing given the apparently very low
impact on existing man pages?

Regards,
Branden


From MAILER-DAEMON Mon Apr 24 12:30:06 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2gsI-0004Wy-9T
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 12:30:06 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56655)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2gsF-0004WW-7R
	for groff@gnu.org; Mon, 24 Apr 2017 12:30:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2gsE-0001c6-3k
	for groff@gnu.org; Mon, 24 Apr 2017 12:30:03 -0400
Received: from scc-mailout-kit-01.scc.kit.edu
	([2a00:1398:9:f712::810d:e751]:41816)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d2gsD-0001bk-Ud
	for groff@gnu.org; Mon, 24 Apr 2017 12:30:02 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d2gsA-0005so-FE; Mon, 24 Apr 2017 18:29:59 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d2gs9-0004zR-E7; Mon, 24 Apr 2017 18:29:57 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d2gs9-0000xo-8S; Mon, 24 Apr 2017 18:29:57 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 2f0eaa24;
	Mon, 24 Apr 2017 18:29:57 +0200 (CEST)
Date: Mon, 24 Apr 2017 18:29:57 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Ralph Corderoy <ralph@inputplus.co.uk>, groff@gnu.org
Message-ID: <20170424162957.GC47874@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e751
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 16:30:04 -0000

Hi,

G. Branden Robinson wrote on Mon, Apr 24, 2017 at 11:41:22AM -0400:

> to the more readable (and, I submit, more writable-by-the-novice):
> 
> .TP
> .B \-scale \c
> .IR xfac [, yfac ]
> Multiply the horizontal and vertical window size by

YIKES, that sounds like an absolutely terrible idea!

The \c escape sequence is a horrible hack that should never
be used by end users and should be avoided, if possible,
even in the implementation of macro sets.  Did you read the
description of \c on:

https://www.gnu.org/software/groff/manual/html_node/Line-Control.html

It is horribly complicated, referring to various purely internal
concepts.

Besides, i'm not at all convinced that this is even mildly portable.
For example, the Heirloom nroff/troff User's Manual says that "the
next encountered input text line will be considered to be a
continuation of the same line of input text".  So, the effect is
only defined if both the interrupted line and the continuation
line are *text lines*, and neither ".B ..." nor ".IR ..." qualify
as text lines as far as i can tell: both are macro lines.
Even the groff documentation talks about "the next input text line".

It may happen to more or less work in some cases with the current
groff implementation, but relying on that would seem unwise to me.

Yours,
  Ingo


P.S.
There is little you can do to make writing legacy man(7) code
easier for the novice.  The problem is that it always requires
mixing two different language levels:  man(7) macros and low-level
roff requests and escapes.  And that it also requires writing
physical rather than semantic markup, which is obviously harder
to do in a consistent manner.

Writing mdoc(7) is much easier for the novice because it's semantic
and because it does not require mixing in low-level roff features.
But trying to make man(7) easier to write is bound for disaster.
The only remaining asset of man(7) is portability, and even that
is becoming less and less of an argument for using it given the
wide availablity of both mdoc(7) itself and the mandoc -Tman
mdoc(7)-to-man(7) converter.  If, by fiddling with man(7) syntax,
you harm man(7) portability, then you really throw it's last remaining
asset overboard.


From MAILER-DAEMON Mon Apr 24 21:22:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2pBe-00027I-7y
	for mharc-groff@gnu.org; Mon, 24 Apr 2017 21:22:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41669)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2pBa-00026y-IP
	for groff@gnu.org; Mon, 24 Apr 2017 21:22:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2pBV-0005iu-Iw
	for groff@gnu.org; Mon, 24 Apr 2017 21:22:34 -0400
Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]:33318)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2pBV-0005iV-Cq
	for groff@gnu.org; Mon, 24 Apr 2017 21:22:29 -0400
Received: by mail-yw0-x242.google.com with SMTP id 203so15333872ywe.0
	for <groff@gnu.org>; Mon, 24 Apr 2017 18:22:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=NHgvs7Go+tsrk8jdK2b+byWlAY6/iD2G6ZoUT1eAjTM=;
	b=YGcKXPbj+nc08o1+liwxSI1mUfSF2Pl0nePa4sIXEtLwDL2S2otZelSJRmDUrn2Q14
	w1p95nRdSZAlQIz2NV6PWlDgdhK9SpMbpSO/Oagg3xaTcir4BJbFIQkb9m6uiS3DwBw8
	0hbTPR9MEI9rf3U1nQdNU09+wZDRzdeYve8Nm9yudLOYoJwA6G1LPAmeIKrniuHjqOVJ
	TC9Ue6ZIWG3a0gYJkBcch3adE2eD89SOyQZANEzDW1cbueY915CbckjMeJeMwOufeBgV
	TP/VdiJpiTOVU6NyFNZVPSxQa+3JVCmopONg4eMLi+WGaKXKr3sbew0dT3oa1WVKmK4w
	p5sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=NHgvs7Go+tsrk8jdK2b+byWlAY6/iD2G6ZoUT1eAjTM=;
	b=SYepYb1jxYYUe9uJB5q7n5Vnq/LbMpCVbGpCBtjZQYJDrJIsG4Pt2kfu3/AAB2X0sd
	rbrcftMHK15fbPggTNUmoKnEvbCkfRMPM/uyngiyDR7q2zifSCs2N/Ktmvt5O4Jz3tS4
	AMuqBh8pqYM+qAgLWZ++kb0GetohR06cLaiFvxWria1SiPxEdfBG8NX0DzXqFyF1V3Ml
	HgqcNI42403+/nf2f9pqdEL2lOmvbJ9qT4T1J+tl31SVWBZs2CecofGspZtrQXFD5j6y
	4C09jK2C0dEX2cgtKyj1lz9OKligFTXbEqGyltYIv1WPY9W9m9OehlM6AVg0hTrxswxC
	Ja0g==
X-Gm-Message-State: AN3rC/4aaUJl2RyQoNPl5z+MBFxp3H7ei8NHV4rZgAIH+ynhJNbEiVL5
	VCQsuWHUncEWCHyWdY4yzw==
X-Received: by 10.13.239.129 with SMTP id y123mr7050934ywe.345.1493083348673; 
	Mon, 24 Apr 2017 18:22:28 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	l17sm7974908ywh.13.2017.04.24.18.22.27
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Mon, 24 Apr 2017 18:22:27 -0700 (PDT)
Date: Mon, 24 Apr 2017 21:22:25 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: Ralph Corderoy <ralph@inputplus.co.uk>, groff@gnu.org
Message-ID: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424162957.GC47874@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::242
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 01:22:36 -0000

At 2017-04-24T18:29:57+0200, Ingo Schwarze wrote:
> Hi,
> 
> G. Branden Robinson wrote on Mon, Apr 24, 2017 at 11:41:22AM -0400:
> 
> > to the more readable (and, I submit, more writable-by-the-novice):
> > 
> > .TP
> > .B \-scale \c
> > .IR xfac [, yfac ]
> > Multiply the horizontal and vertical window size by
> 
> YIKES, that sounds like an absolutely terrible idea!

My example, or the method I proposed to achieve it?  You quoted the
former but proceeded to discuss the latter and I want to make sure I
understand how many objections you're raising.

> The \c escape sequence is a horrible hack that should never
> be used by end users and should be avoided, if possible,
> even in the implementation of macro sets.

In that case we groff fans have some sweeping around our own door to do,
first and foremost with the (arguably) two most excellent macro packages
we have:

$ grep -c '\\c' /usr/share/groff/1.22.3/tmac/*.* | grep -v ':0$' \
	| sort -t : -n -r -k 2,2
/usr/share/groff/1.22.3/tmac/doc.tmac:117
/usr/share/groff/1.22.3/tmac/om.tmac:110
/usr/share/groff/1.22.3/tmac/m.tmac:14
/usr/share/groff/1.22.3/tmac/s.tmac:8
/usr/share/groff/1.22.3/tmac/www.tmac:6
/usr/share/groff/1.22.3/tmac/pdfmark.tmac:6
/usr/share/groff/1.22.3/tmac/pdf.tmac:5
/usr/share/groff/1.22.3/tmac/hyphenex.det:4
/usr/share/groff/1.22.3/tmac/hyphen.sv:3
/usr/share/groff/1.22.3/tmac/hdtbl.tmac:3
/usr/share/groff/1.22.3/tmac/e.tmac:3
/usr/share/groff/1.22.3/tmac/an-old.tmac:3
/usr/share/groff/1.22.3/tmac/spdf.tmac:2
/usr/share/groff/1.22.3/tmac/psatk.tmac:2
/usr/share/groff/1.22.3/tmac/doc-old.tmac:2
/usr/share/groff/1.22.3/tmac/an-ext.tmac:2

> Did you read the
> description of \c on:
> 
> https://www.gnu.org/software/groff/manual/html_node/Line-Control.html
> 
> It is horribly complicated, referring to various purely internal
> concepts.

Yes, I've read it before, plus the brief description in groff(7) which I
find so terse as to be incomprehensible, and Kernighan's description of
it is CSTR #54, which also doesn't leave me terribly enlightened.

> Besides, i'm not at all convinced that this is even mildly portable.
> For example, the Heirloom nroff/troff User's Manual says that "the
> next encountered input text line will be considered to be a
> continuation of the same line of input text".  So, the effect is
> only defined if both the interrupted line and the continuation
> line are *text lines*, and neither ".B ..." nor ".IR ..." qualify
> as text lines as far as i can tell: both are macro lines.
> Even the groff documentation talks about "the next input text line".

I'm happy to examine the impact this change would have on Heirloom
troff.  First I'd like to get some feedback on my specific objective.

> It may happen to more or less work in some cases with the current
> groff implementation, but relying on that would seem unwise to me.

There are only two living implementations of *roff in the world, right?
And everybody 

If \c is documented badly and/or under-specified, let's determine its
precise semantics and document them clearly.

> P.S.
> There is little you can do to make writing legacy man(7) code
> easier for the novice.

I don't agree.  Or perhaps more precisely, I haven't yet given up hope.

> The problem is that it always requires mixing two different language
> levels:  man(7) macros and low-level roff requests and escapes.

"Always requires" is much too strong.  Lots of manpages are written in a
very small subset of the language.

In my experience, one can write an attractive manpage almost without
ever restoring to straight requests.  (People are often ignorant of the
an-ext macros, which are so liberally licensed they can be used
anywhere.)

Font escapes can be eliminated if you:
	1) Don't try for constant-width fonts or bold italics; and
	2) Don't try to put rich material in the first line after a .TP.

It's problem (2) that I'm interested in solving in this thread.

> And that it also requires writing physical rather than semantic
> markup, which is obviously harder to do in a consistent manner.

I entirely agree with the virtues of semantic of "presentation"-based
markup.  However, this could be mitigated by encouraging a consistent
style in groff_man(7) itself.  Some coordination with Michael Kerrisk et
al. of the man-pages project would be valuable as well; I think almost
all of the advice in man-pages(7) of that package is very sound.

> Writing mdoc(7) is much easier for the novice because it's semantic
> and because it does not require mixing in low-level roff features.

And yet, why have so few people outside of the BSD community adopted it?

It's a great macro package and I admire it.  But USENIX and BSD built
it, and "they" didn't come.

People keeep writing in man(7).  Let's do what we can to help them write
it better.

I submit that one reason mdoc didn't take over the world is for the same
reason DocBook didn't--it's too huge.  I think that man(7), even with
the an-ext stuff added on, is small enough to keep in one's head.

That doesn't mean I think it's superior--I simply think it's easier to
sell to software developers who don't want to learn *roff or write man
pages for a living.  When someone gripes a development team to write a
man page for their tool or library, they can pop off for a bit and do
it.

Ideally, I'd like to make some enhancements to man and its documentation
that encourage people to make the leap to mdoc, _especially_ those
people who are enlightened enough to see the sinfulness of
presentation-based, rather than semantic, markup.  We should make it
obvious to them that the groff people aren't fools, either, and want to
help them make that jump.  But for those who don't, here's man with some
semantic training wheels to file the rougher edges off.

> But trying to make man(7) easier to write is bound for disaster.

No; you presume that making it easier to write means making it harder to
write correctly.  That is the opposite of my intention.

People are already writing it wrong--a lot.

> The only remaining asset of man(7) is portability, and even that
> is becoming less and less of an argument for using it given the
> wide availablity of both mdoc(7) itself and the mandoc -Tman
> mdoc(7)-to-man(7) converter.

Of course what we need is a converter that goes in the other direction;
but that requires the encoding of semantic information that is lacking.

> If, by fiddling with man(7) syntax, you harm man(7) portability, then
> you really throw it's last remaining asset overboard.

I'd like to see what we can achieve by fiddling with it _without_
harming its portability.  Even as small as man(7) is, people neglect a
lot of its capabilities.

-- 
Regards,
Branden


From MAILER-DAEMON Tue Apr 25 01:04:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2seW-0004Vi-Bu
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 01:04:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54970)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2seT-0004VB-FP
	for groff@gnu.org; Tue, 25 Apr 2017 01:04:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d2seQ-0006vW-7T
	for groff@gnu.org; Tue, 25 Apr 2017 01:04:37 -0400
Received: from scc-mailout-kit-02.scc.kit.edu ([129.13.231.82]:49980)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d2seP-0006uu-US
	for groff@gnu.org; Tue, 25 Apr 2017 01:04:34 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d2seL-0006n4-1W; Tue, 25 Apr 2017 07:04:30 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d2seK-0005NR-IK; Tue, 25 Apr 2017 07:04:28 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d2seJ-0002UX-UF; Tue, 25 Apr 2017 07:04:28 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id cba36385;
	Tue, 25 Apr 2017 07:04:27 +0200 (CEST)
Date: Tue, 25 Apr 2017 07:04:27 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170425050427.GA37231@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 129.13.231.82
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 05:04:39 -0000

Hi,

G. Branden Robinson wrote on Mon, Apr 24, 2017 at 09:22:25PM -0400:
> At 2017-04-24T18:29:57+0200, Ingo Schwarze wrote:
>> G. Branden Robinson wrote on Mon, Apr 24, 2017 at 11:41:22AM -0400:

>>> to the more readable (and, I submit, more writable-by-the-novice):
>>> 
>>> .TP
>>> .B \-scale \c
>>> .IR xfac [, yfac ]
>>> Multiply the horizontal and vertical window size by

>> YIKES, that sounds like an absolutely terrible idea!

> My example, or the method I proposed to achieve it?

Both, because both only make sense together.  If you don't change the
definition of the .TP macro, you cannot use .TP headers containing
two macro lines.  If you don't want two-line .TP headers, there is no
point in changing the syntax of the .TP macro.

>> The \c escape sequence is a horrible hack that should never
>> be used by end users and should be avoided, if possible,
>> even in the implementation of macro sets.

> In that case we groff fans have some sweeping around our own door to do,
> first and foremost with the (arguably) two most excellent macro packages
> we have:

Sure, i admit roff is not an easy language, so the implementation
of roff macros is often not pretty.  Given that Werner wrote much
of the groff_mdoc(7) implementation, and he really knows what he
is doing, i suspect that most uses of \c could not be avoided.
While mdoc(7) is easy to use, the implementaion is not trivial
at all; in particular the modern groff implementation is quite
a refined thing, much more so than Cynthia's original 4.4BSD
implementation, which was much simpler.

> I'm happy to examine the impact this change would have on Heirloom
> troff.  First I'd like to get some feedback on my specific objective.

It does seems likely that there is some way to harmonize Heirloom
with what gets done in groff.  But i do doubt the basic direction
in this specific respect.

> There are only two living implementations of *roff in the world, right?

Well, and the partial one in mandoc, but mandoc follows groff in
roff matters.

> If \c is documented badly and/or under-specified, let's determine its
> precise semantics and document them clearly.

I do suspect there is room for improvement, or at least clarification,
in the \c specification, so working on that likely makes sense.
But please, regard that as a work to help macro implementors,
**not** end users!

>> There is little you can do to make writing legacy man(7) code
>> easier for the novice.

> I don't agree.  Or perhaps more precisely, I haven't yet given up hope.

Well, as long as one doesn't make matters worse, keeping up hope
is not a sin.  :-)

>> The problem is that it always requires mixing two different language
>> levels:  man(7) macros and low-level roff requests and escapes.

> "Always requires" is much too strong.  Lots of manpages are written in a
> very small subset of the language.

Small subsets, yes.  The roff language is indeed quite large, and
man(7) manual pages typically only need a fraction of it.  But
almost every man(7) manual page requires *some* low-level roff
requests.

> In my experience, one can write an attractive manpage almost without
> ever restoring to straight requests.

And yet you suggest that authors should use the \c escape sequence,
which quite definitely is a very low-level roff feature and not
an element of the man(7) language at all.  In the example you
bring up, there is indeed no viable alternative to using \f font
escapes.  You propose to trade the \f for \c.  I say \c is much
worse than \f.  The syntax and semantics of \f is relatively
easy to understand, and people writing man(7) are used to it, while
\c is quite arcane.

> (People are often ignorant of the an-ext macros, which are so
> liberally licensed they can be used anywhere.)

I admit that the en-ext macros minimally improve semantic capabilities
of the man(7) language, but by so little that man(7) remains an
almost exclusively presentational language even with man-ext.
For that reason, i deem that using man-ext does more damage than
good:  It doesn't substantially improve the language, but it
does cause compat grief on old systems, which is exactly where
the legacy man(7) language is still needed.  Bad tradeoff...

> I entirely agree with the virtues of semantic of "presentation"-based
> markup.  However, this could be mitigated by encouraging a consistent
> style in groff_man(7) itself.  Some coordination with Michael Kerrisk et
> al. of the man-pages project would be valuable as well; I think almost
> all of the advice in man-pages(7) of that package is very sound.

I mostly agree, with very few reservations.  Their section headers
are gratuitiously different from what groff recommends (in
groff_mdoc(7)) and are out of order.  Some should better not be
used (CONFIGURATION, OPTIONS, ATTRIBUTES, NOTES) and some have
unusual titles (EXAMPLE instead of EXAMPLES, CONFORMING TO instead
of STANDARDS, VERSIONS instead of HISTORY).  AUTHORS should be
encouraged rather than discouraged.  Besides, i'd recommend
constant-width/typewriter font for special macros and errno names
rather than bold, and i see no need to make references to other
manual pages bold, the section number in parentheses is obvious
enough.  I would also disagree with part of the advice given below
"Example programs", but all of the above is minor.  The general
direction of man-pages(7) is very useful.

>> Writing mdoc(7) is much easier for the novice because it's semantic
>> and because it does not require mixing in low-level roff features.

> And yet, why have so few people outside of the BSD community adopted it?

Frankly, i'm not sure.  Illumos has, for example; so of the free
operating systems, it's mostly GNU that doesn't use it.  One reason
could likely be that GNU used to use texinfo(1), but that is being
abandoned now.

> It's a great macro package and I admire it.  But USENIX and BSD built
> it, and "they" didn't come.
> 
> People keeep writing in man(7).  Let's do what we can to help them write
> it better.

No real objection to that, if it can be done, but little hope here,
except maybe for style recommendations, and man-pages(7) clearly is
already quite good at that.

> Ideally, I'd like to make some enhancements to man and its documentation
> that encourage people to make the leap to mdoc, _especially_ those
> people who are enlightened enough to see the sinfulness of
> presentation-based, rather than semantic, markup.  We should make it
> obvious to them that the groff people aren't fools, either, and want to
> help them make that jump.  But for those who don't, here's man with some
> semantic training wheels to file the rougher edges off.

Sounds good to me.

> People are already writing it wrong--a lot.

That is certainly true.  I see it in our ports tree.  Average quality
of hand-written third party man(7) - unless from Kerrisk, of course -
is usually below average quality of hand-written mdoc(7).  Usually,
the least problematic man(7) code you find in the wild is pod2man(1)
output.

>> The only remaining asset of man(7) is portability, and even that
>> is becoming less and less of an argument for using it given the
>> wide availablity of both mdoc(7) itself and the mandoc -Tman
>> mdoc(7)-to-man(7) converter.

> Of course what we need is a converter that goes in the other direction;

I have very little hope for that.  The best we can hope for would
be a tool to convert from man(7) to mdoc(7), doing some guessing of
the required markup, but requiring considerable manual postprocessing.
I know that a full converter is not a realistic goal because i am
maintaining pod2mdoc(1), which is about the same difficulty, and i
used it to convert the complete corpus of OpenSSL manuals, so i
know quite well which amout of postprocessing is required, and
which problems you face when trying to improve the automatic
guessing.

>> If, by fiddling with man(7) syntax, you harm man(7) portability, then
>> you really throw its last remaining asset overboard.

> I'd like to see what we can achieve by fiddling with it _without_
> harming its portability.

Sure, but your proposed change from .it to .itc together with the
changed .TP idiom you propose very seriously breaks portability.
If people would start using that, their manuals would severly
misformat on old systems.  And legacy systems that no longer get
properly updated and maintained is exactly where man(7) matters
most nowadays.

Yours,
  Ingo


From MAILER-DAEMON Tue Apr 25 06:47:48 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2y0Z-0001DJ-O8
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 06:47:47 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53963)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <carsten.kunze@arcor.de>) id 1d2y0X-0001AU-Tz
	for groff@gnu.org; Tue, 25 Apr 2017 06:47:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <carsten.kunze@arcor.de>) id 1d2y0T-0001pH-RG
	for groff@gnu.org; Tue, 25 Apr 2017 06:47:45 -0400
Received: from vsmx010.vodafonemail.xion.oxcs.net ([153.92.174.88]:38178)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <carsten.kunze@arcor.de>)
	id 1d2y0T-0001hV-Kd
	for groff@gnu.org; Tue, 25 Apr 2017 06:47:41 -0400
Received: from vsmx002.vodafonemail.xion.oxcs.net (unknown [192.168.75.192])
	by mta-6-out.mta.xion.oxcs.net (Postfix) with ESMTP id 2E829803D1
	for <groff@gnu.org>; Tue, 25 Apr 2017 10:47:35 +0000 (UTC)
Received: from app-36.app.xion.oxcs.net (app-36.app.xion.oxcs.net [10.10.1.36])
	by mta-6-out.mta.xion.oxcs.net (Postfix) with ESMTPA id 361323C020C
	for <groff@gnu.org>; Tue, 25 Apr 2017 10:47:32 +0000 (UTC)
Date: Tue, 25 Apr 2017 12:47:25 +0200 (CEST)
From: Carsten Kunze <carsten.kunze@arcor.de>
Reply-To: Carsten Kunze <carsten.kunze@arcor.de>
To: groff@gnu.org
Message-ID: <1938619013.157418.1493117252773@mail.vodafone.de>
In-Reply-To: <20170424143915.GA47874@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.8.3-Rev20
X-Originating-Client: com.openexchange.ox.gui.dhtml
X-VADE-STATUS: LEGIT
X-VADE-SCORE: 20
X-VADE-REASON: gggruggvucftvghtrhhoucdtuddrfeeliedrgedvgdefhecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevfgfuvffqoffgtfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddtnecuogfthfevqddquegrugfkmhhpohhrthgrnhgtvgculddvtddmnecujfgurhepfffhrhfvkfgjfhfugggtgffrkgfosehtjegstdertdejnecuhfhrohhmpeevrghrshhtvghnucfmuhhniigvuceotggrrhhsthgvnhdrkhhunhiivgesrghrtghorhdruggvqeenucfkphepuddtrddutddruddrfeeinecurfgrrhgrmhepmhhouggvpehsmhhtphdqohhuthdphhgvlhhopegrphhpqdefiedrrghpphdrgihiohhnrdhogigtshdrnhgvthdpihhnvghtpedutddruddtrddurdefiedpmhgrihhlfhhrohhmpegtrghrshhtvghnrdhkuhhniigvsegrrhgtohhrrdguvgdprhgtphhtthhopehgrhhofhhfsehgnhhurdhorhhg
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 153.92.174.88
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 10:47:46 -0000

> Ingo Schwarze <schwarze@usta.de> hat am 24. April 2017 um 16:39 geschrieben:
> 
> Assuming this is considered the right direction, how would one
> best implement, in doc.tmac-u and an-old.tmac, - == \- == U+002D
> for all devices?

Isn't it already done for UTF-8 in the files you mentioned?
Both contain:

.if '\*[.T]'utf8' \{\
.  rchar \- - ' `
.
.  char \- \N'45'
.  char  - \N'45'
.  char  ' \N'39'
.  char  ` \N'96'
.\}

Tests did show that groff's HTML output of manpages does not look good and has bugs (results in wrong formatting). Well HTML formatted manpages are often processed by other tools (non-roff tools which just know the -man and -mdoc language). So changing groff's HTML should not be necessary--or there would be much more work to do beyond '-' and '\-'.


From MAILER-DAEMON Tue Apr 25 07:15:09 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2yR3-0000Sc-GN
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 07:15:09 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:32962)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2yR0-0000OV-5t
	for groff@gnu.org; Tue, 25 Apr 2017 07:15:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2yQw-0000bN-NZ
	for groff@gnu.org; Tue, 25 Apr 2017 07:15:06 -0400
Received: from mail-yw0-x229.google.com ([2607:f8b0:4002:c05::229]:35429)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2yQw-0000aw-I2
	for groff@gnu.org; Tue, 25 Apr 2017 07:15:02 -0400
Received: by mail-yw0-x229.google.com with SMTP id u70so93982065ywe.2
	for <groff@gnu.org>; Tue, 25 Apr 2017 04:15:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=csEV6yyYC4yviaJduwD2WWgA/rKoxPYpbNDBq1exR6I=;
	b=K81C61VP16WQTsvKN56Go2lpEYEjqpPc2Kch//tQuRanexmoLmJeFpZEXWU7ZyBpqq
	gkwEACXw9+d7clc33uaw7IJ9T4pzxMJbgHvA5xkzakMV+vHcEZZDsdkVSuaM3Ce1etqr
	3xgQ065dWxVzEHXxavB1lTkaHgSpk5gRvtWvqKAWtJzpY51YZ9i/4pURVF7UdjwmobAp
	FuzxX73yCDd5ldnWxJ99+EYnK2nnfSBkOpV1W7V5xSK0ZO6lrln4+mRwcwrDOWHYXgpl
	95GlCoxyHyCJ6WfAneoa3FGmGCjd4ACqciJ0jC0ll5TuSCGIg3/WP79d/7vGZfJ97Zhq
	TjrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=csEV6yyYC4yviaJduwD2WWgA/rKoxPYpbNDBq1exR6I=;
	b=qaOyFs3tfk8YbMah2k8qHo0YqvlT14dbFee8NA/bkRSguxGk2ev3yydGVSQ+dDyOez
	Vq1iZPjHmtYFvgKOjxBChbggjaHJm1x89ZO5Vq2Ept2Qvnl9N9s8kNypocQLWDp24Up+
	dmqSQU71gB2oZQqFBRx5Yp5VR7Gt+S0G3RUdxyDSJzkwb8xxyzHPwgzhFGUkGF5gzhqd
	sGvE7sKif29zicrVtBinCNfhvEPs1sepvrGoKM5Z+l4Z2bQ928zPoMFbdAO4BZUCQiQC
	7LJlCFklMCNF//WT8fiLf4SoRsrxI+dk6VxUrICR64L+zRsoUbX+0V9pRMtm6PFfHK9y
	Dn+A==
X-Gm-Message-State: AN3rC/4FncPtfawcNw4MqzirEh3yEgn9Rv0Bc+H7SCDKUrKcVCASVuxA
	vwyuL95GuHYxQA==
X-Received: by 10.13.209.129 with SMTP id t123mr8232569ywd.183.1493118901423; 
	Tue, 25 Apr 2017 04:15:01 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id u83sm8438651ywa.4.2017.04.25.04.15.00
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Tue, 25 Apr 2017 04:15:00 -0700 (PDT)
Date: Tue, 25 Apr 2017 07:14:58 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: groff@gnu.org
Message-ID: <20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425050427.GA37231@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::229
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 11:15:08 -0000

At 2017-04-25T07:04:27+0200, Ingo Schwarze wrote:
> Hi,
> 
> G. Branden Robinson wrote on Mon, Apr 24, 2017 at 09:22:25PM -0400:
> > At 2017-04-24T18:29:57+0200, Ingo Schwarze wrote:
> >> G. Branden Robinson wrote on Mon, Apr 24, 2017 at 11:41:22AM -0400:
> 
> >>> to the more readable (and, I submit, more writable-by-the-novice):
> >>> 
> >>> .TP
> >>> .B \-scale \c
> >>> .IR xfac [, yfac ]
> >>> Multiply the horizontal and vertical window size by
> 
> >> YIKES, that sounds like an absolutely terrible idea!
> 
> > My example, or the method I proposed to achieve it?
> 
> Both, because both only make sense together.  If you don't change the
> definition of the .TP macro, you cannot use .TP headers containing
> two macro lines.  If you don't want two-line .TP headers, there is no
> point in changing the syntax of the .TP macro.

No, what I really want is a TP-ish macro that lets you break the tag
across multiple input lines, so the writer doesn't have to use font
escapes.

If that means a new macro, I'm fine with that.

> >> The \c escape sequence is a horrible hack that should never
> >> be used by end users and should be avoided, if possible,
> >> even in the implementation of macro sets.
> 
> > In that case we groff fans have some sweeping around our own door to do,
> > first and foremost with the (arguably) two most excellent macro packages
> > we have:
> 
> Sure, i admit roff is not an easy language, so the implementation
> of roff macros is often not pretty.  Given that Werner wrote much
> of the groff_mdoc(7) implementation, and he really knows what he
> is doing, i suspect that most uses of \c could not be avoided.
> While mdoc(7) is easy to use, the implementaion is not trivial
> at all; in particular the modern groff implementation is quite
> a refined thing, much more so than Cynthia's original 4.4BSD
> implementation, which was much simpler.

This is fine, but it says to me that your original complaint ("a
horrible hack [to be] avoided ... even in the implementation of macro
sets") is overstated.

Maybe \c it's like inline assembly in C.  Something best reserved to
experts under special circumstances, perhaps, but not a horrible hack.

> > I'm happy to examine the impact this change would have on Heirloom
> > troff.  First I'd like to get some feedback on my specific objective.
> 
> It does seems likely that there is some way to harmonize Heirloom
> with what gets done in groff.  But i do doubt the basic direction
> in this specific respect.

You confuse my methods for my goals.  I am no Werner Lemberg and I am
wide open to alternative implementation proposals.  I was simply
surprised at how easy it was to get what I wanted, and how little
collateral damage there was by doing so.

> > There are only two living implementations of *roff in the world, right?
> 
> Well, and the partial one in mandoc, but mandoc follows groff in
> roff matters.

I need to look more deeply into that; I don't know how you'd implement
mandoc without implementing the bulk of *roff.

> > If \c is documented badly and/or under-specified, let's determine its
> > precise semantics and document them clearly.
> 
> I do suspect there is room for improvement, or at least clarification,
> in the \c specification, so working on that likely makes sense.
> But please, regard that as a work to help macro implementors,
> **not** end users!

Well, fine, let's proceed with that, then.  See end of this mail.

> Small subsets, yes.  The roff language is indeed quite large, and
> man(7) manual pages typically only need a fraction of it.  But
> almost every man(7) manual page requires *some* low-level roff
> requests.

I don't agree, but we have different opinions about the utility of
an-ext.tmac.  I think it's valuable.  With EX/EE, for example, one
hardly needs .nf/.fi requests for the purposes I've seen it used: code
or shell session examples.

The groff community needs to be singing from the same hymnal when it
comes to recommended best practices.  If an-ext.tmac should be
deprecated and avoided, that needs to be formally established and
reflected in the software releases, maybe with a .tm warning in its
source.

How do others in the group feel about an-ext?

> > In my experience, one can write an attractive manpage almost without
> > ever restoring to straight requests.
> 
> And yet you suggest that authors should use the \c escape sequence,
> which quite definitely is a very low-level roff feature and not
> an element of the man(7) language at all.

Yes, but so are character escapes, which are unavoidable in good manpage
writing.

The reason \c attracted my attention was because it enabled the
suppression of word-breaking, which in turn enables the use of macros
for font changes rather than escapes.  I mentioned this before, but I
hate font escapes.  I think we should give man(7) users a way to write a
good manpage without ever using them.

> In the example you bring up, there is indeed no viable alternative to
> using \f font escapes.  You propose to trade the \f for \c.  I say \c
> is much worse than \f.  The syntax and semantics of \f is relatively
> easy to understand, and people writing man(7) are used to it, while \c
> is quite arcane.

Okay.  What alternatives can you propose for getting rid of \f in man
pages, short of migrating the universe to mdoc?

> > (People are often ignorant of the an-ext macros, which are so
> > liberally licensed they can be used anywhere.)
> 
> I admit that the en-ext macros minimally improve semantic capabilities
> of the man(7) language, but by so little that man(7) remains an
> almost exclusively presentational language even with man-ext.
> For that reason, i deem that using man-ext does more damage than
> good:  It doesn't substantially improve the language, but it
> does cause compat grief on old systems, which is exactly where
> the legacy man(7) language is still needed.  Bad tradeoff...

What I'm hearing is that you feel that man(7) is a lost cause:

A.  It desparately needs improvement because of its presentational,
    rather than semantic, focus.
B.  Improvement will break portability.

This basically amounts to doing nothing and letting man(7) die of its
own accord.

But it hasn't.  Look at the past 20 years.  It's still alive, and what
vibrancy it has lost, it has lost to stuff like Markdown which is even
_less_ semantic.  Not to mdoc.

I think an-ext has taken a good approach; add semantic markup to the
language, and license the macros so permissively that man page authors
have no reason _not_ to inline them if they care to target legacy
systems.

My recommendation is to take the momentum an-ext has, however small, and
press it:

a.  Add more macros to fit semantic needs and the hiding of lower-level
    requests and escapes.
b.  Hand-hold users to the nth degree with examples and recommended best
    practices.
c.  Show people a mapping from groff's "extended" man macro package to
    mdoc, so that the route for switching over is clearly signposted.

> > I entirely agree with the virtues of semantic of "presentation"-based
> > markup.  However, this could be mitigated by encouraging a consistent
> > style in groff_man(7) itself.  Some coordination with Michael Kerrisk et
> > al. of the man-pages project would be valuable as well; I think almost
> > all of the advice in man-pages(7) of that package is very sound.
> 
> I mostly agree, with very few reservations.  Their section headers
> are gratuitiously different from what groff recommends (in
> groff_mdoc(7)) and are out of order.  Some should better not be
> used (CONFIGURATION, OPTIONS, ATTRIBUTES, NOTES) and some have
> unusual titles (EXAMPLE instead of EXAMPLES, CONFORMING TO instead
> of STANDARDS, VERSIONS instead of HISTORY).  AUTHORS should be
> encouraged rather than discouraged.  Besides, i'd recommend
> constant-width/typewriter font for special macros and errno names
> rather than bold, and i see no need to make references to other
> manual pages bold, the section number in parentheses is obvious
> enough.  I would also disagree with part of the advice given below
> "Example programs", but all of the above is minor.  The general
> direction of man-pages(7) is very useful.

I have my pet peeves as well; I don't like the shouty caps in arguments
to TH and SH.  That's information-losing and presentationy.  Why not
encourage people to have site-local files that redefine these macros to
do a ".tr aAbBcC" etc. if they insist on seeing screaming caps?

The first half of your complaints (which section headings should be
present, and in what order) are not presentational, on the other hand,
and IMO would be best sorted out by convening a working group.  I don't
see any other way to attack that problem.  Two independent sources of
fiat have not brought about harmonization.

> >> Writing mdoc(7) is much easier for the novice because it's semantic
> >> and because it does not require mixing in low-level roff features.
> 
> > And yet, why have so few people outside of the BSD community adopted it?
> 
> Frankly, i'm not sure.  Illumos has, for example; so of the free
> operating systems, it's mostly GNU that doesn't use it.  One reason
> could likely be that GNU used to use texinfo(1), but that is being
> abandoned now.

Is that official?  The last time I checked their list archives (a few
months ago), they were openly wondering "whither texinfo?" but hadn't
yet decided to abandon the project.

> I have very little hope for that.  The best we can hope for would
> be a tool to convert from man(7) to mdoc(7), doing some guessing of
> the required markup, but requiring considerable manual postprocessing.
> I know that a full converter is not a realistic goal because i am
> maintaining pod2mdoc(1), which is about the same difficulty, and i
> used it to convert the complete corpus of OpenSSL manuals, so i
> know quite well which amout of postprocessing is required, and
> which problems you face when trying to improve the automatic
> guessing.

Yes, the problem is "AI-hard" which is why I don't consider it viable.

> > I'd like to see what we can achieve by fiddling with it _without_
> > harming its portability.
> 
> Sure, but your proposed change from .it to .itc together with the
> changed .TP idiom you propose very seriously breaks portability.
> If people would start using that, their manuals would severly
> misformat on old systems.  And legacy systems that no longer get
> properly updated and maintained is exactly where man(7) matters
> most nowadays.

I'm perfectly willing to abandon my hare-brained itc hack, but my
underlying objective remains, and I disagree with your final statement.
man(7) matters most where it is being read--and that's on every *nix
system that still supports a terminal interface.

The mdocification of the universe has not happened of its own accord and
it won't.  If we want to get people there, we have to show them a way.
Throwing mdoc(7), groff_mdoc(7), and mdoc.samples(7) at them has not
done it.

I emphasize: GNU roff's _own_ man pages are written predominantly in man
rather than mdoc.  If we are physicians, we had better heal ourselves.

This discussion is sprawling quite a bit.  I see three further
directions that are largely independent:

1.  Let's document, for the newbs and ourselves, what the heck "\c"
    really means.

2.  Let's figure out whether we have any consensus for the further
    development of an-ext.

3.  Let's talk to the man-pages folks about harmonizing style
    recommendations.  If full consensus cannot be achieved, I note that
    mdoc already supports "ATT" vs. "BSD" style conventions in some
    places.  With care, an-ext could support "GNU" vs. "LNX" (say)
    conventions, and the man page author could declare his or her
    allegiance with a single macro call at the top of the page source.
    Plus it would keep the "GNU/Linux" wars going, and they're in dire
    need of a new front in the flame wars.  ;-)

I don't propose to undertake (3) right away, but I'd like to solicit
opinions on (1) and (2) now to direct my own work.

Are there items you'd like to add?

Regards,
Branden


From MAILER-DAEMON Tue Apr 25 07:26:43 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2ycE-0006kB-NI
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 07:26:42 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36711)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2ycB-0006hK-FW
	for groff@gnu.org; Tue, 25 Apr 2017 07:26:41 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d2yc8-0002Cj-Q2
	for groff@gnu.org; Tue, 25 Apr 2017 07:26:39 -0400
Received: from mail-yb0-x235.google.com ([2607:f8b0:4002:c09::235]:35604)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d2yc8-0002CC-Km
	for groff@gnu.org; Tue, 25 Apr 2017 07:26:36 -0400
Received: by mail-yb0-x235.google.com with SMTP id p143so612102yba.2
	for <groff@gnu.org>; Tue, 25 Apr 2017 04:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=fe1+jl0PKAMZdpHrR0Z7Uk+NAy2W+e6bLP8Ezz6wT1M=;
	b=Un37TS+bJtiNXY6EZGXVwikQiT7KEhJCFwvjcT/pPGVL/NZ/19syF7g5BIWQS151hk
	iE06tGAjVWckVJSk9Nd6hrVzrlF+vgV6DLhFFWjAj6cGHlJqJwzVNYJSj9MYpqoCulkK
	qBJX7R+5ouGKTsOkz8DNMbTZsgb8ohz36kaAdFfxLtlk7ByNnCGE6ydxsKrA2W2+ivsB
	SePx9Rr5z9MeaStdQnrEILGFXuKIzx3+jhyN7CVfpuYMplkdDkLcKiJxDOW/CvVzCVnK
	kmPMQkahbtk2fCeCBZ5OhR2VA7S9947fjWzqUaa2LlTyR+lA/t3QfwhG/UJkB2Xv+xfu
	r1LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=fe1+jl0PKAMZdpHrR0Z7Uk+NAy2W+e6bLP8Ezz6wT1M=;
	b=Oq9+n6YBhG748f8FVvJL80NqgzPUOs0YhKSoOj7fift4NJM5D5mgONJico3XpfkRG7
	erp0Fpc+5mjnk3FpBEAExLyTl+LvDDs0ThUOcbQJ0QixgRmIYSjvJ1OchsW/CovXw6ln
	cDJ7khpSBg/AcEmyb+HlYCi6+KOTEqcIcsYrlI5oTex5vr2Gwh/jepc2aOe4jdAsK7e5
	/Ewsi2ADve1/Fw9dNdT7YDyp3BiV7VE6TFTEtPmsdCyS27111dzZXL7kwFtDcqUhOEeN
	ZbjigTuxAKhXb86xarrVbl5YTiGLxISayUIn5swIVy7a0WG7rp/Z4F3Y0Ys13cBxn2Iq
	o96g==
X-Gm-Message-State: AN3rC/5HlsXnKZdf7hOhXbG/qu19I+kswObG8DGIfusW53VKc8WTBr2+
	4W4ZetAe86AkYoADxkU=
X-Received: by 10.37.170.101 with SMTP id s92mr8890519ybi.124.1493119595731;
	Tue, 25 Apr 2017 04:26:35 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	i136sm8433334ywg.66.2017.04.25.04.26.34 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Tue, 25 Apr 2017 04:26:34 -0700 (PDT)
Date: Tue, 25 Apr 2017 07:26:32 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170425112630.2bfpfaormbcruhxr@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<1938619013.157418.1493117252773@mail.vodafone.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="hfe6nhhnouj7cjre"
Content-Disposition: inline
In-Reply-To: <1938619013.157418.1493117252773@mail.vodafone.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::235
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 11:26:41 -0000


--hfe6nhhnouj7cjre
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

At 2017-04-25T12:47:25+0200, Carsten Kunze wrote:
> > Ingo Schwarze <schwarze@usta.de> hat am 24. April 2017 um 16:39 geschrieben:
> > 
> > Assuming this is considered the right direction, how would one
> > best implement, in doc.tmac-u and an-old.tmac, - == \- == U+002D
> > for all devices?
> 
> Isn't it already done for UTF-8 in the files you mentioned?
> Both contain:
> 
> .if '\*[.T]'utf8' \{\
> .  rchar \- - ' `
> .
> .  char \- \N'45'
> .  char  - \N'45'
> .  char  ' \N'39'
> .  char  ` \N'96'
> .\}
> 
> Tests did show that groff's HTML output of manpages does not look good
> and has bugs (results in wrong formatting). Well HTML formatted
> manpages are often processed by other tools (non-roff tools which just
> know the -man and -mdoc language). So changing groff's HTML should not
> be necessary--or there would be much more work to do beyond '-' and
> '\-'.

"hm" appears to be available in the namespace for short character
escapes.  Would "\(hm)" be a good way to offer people U+002D for when
they're absolutely sure they mean it?

In any event, grohtml seems to be mapping all of -, \-, and \(hy to
U+002D (see attachments), which doesn't seem ideal to me given the
capabilities and character repetoire of most HTML renderers.

Regards,
Branden

--hfe6nhhnouj7cjre
Content-Type: application/x-troff-man
Content-Disposition: attachment; filename="foo.man"
Content-Transfer-Encoding: quoted-printable

=2ETH foo 1 bar baz quux=0A.PP=0ABare dash: -=0A.PP=0A\(rs-escaped dash: \-=
=0A.PP=0A\(rshy: \(hy=0A.PP=0A\(rsmi: \(mi=0A.PP=0A\(rsen: \(en=0A.PP=0A\(r=
sem: \(em=0A.PP=0A\(rs[tmi]: \[tmi]=0A
--hfe6nhhnouj7cjre--


From MAILER-DAEMON Tue Apr 25 07:40:56 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d2yq0-0000Y4-MP
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 07:40:56 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40462)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d2ypy-0000WY-EZ
	for groff@gnu.org; Tue, 25 Apr 2017 07:40:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d2ypu-0000Zf-9t
	for groff@gnu.org; Tue, 25 Apr 2017 07:40:54 -0400
Received: from sdaoden.eu ([217.144.132.164]:38758)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d2ypu-0000Xq-2F
	for groff@gnu.org; Tue, 25 Apr 2017 07:40:50 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id C463E16051; Tue, 25 Apr 2017 13:40:47 +0200 (CEST)
Date: Tue, 25 Apr 2017 13:41:00 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org, Ingo Schwarze <schwarze@usta.de>
Message-ID: <20170425114100.Td1IP%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
In-Reply-To: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
Mail-Followup-To: Ingo Schwarze <schwarze@usta.de>, groff@gnu.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 11:40:55 -0000

"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
 |At 2017-04-24T18:29:57+0200, Ingo Schwarze wrote:
 ...
 |I entirely agree with the virtues of semantic of "presentation"-based
 |markup.  However, this could be mitigated by encouraging a consistent
 |style in groff_man(7) itself.  Some coordination with Michael Kerrisk et

I don't think this will work.  Only in an ideal work.

 |al. of the man-pages project would be valuable as well; I think almost
 |all of the advice in man-pages(7) of that package is very sound.

I think at least the structural information guidelines should
somehow end up in the roff_man(7) that ships with roff in the end,
it would mirror what there is roff_mdoc(7).

  ...
 |People keeep writing in man(7).  Let's do what we can to help them write
 |it better.

 |I submit that one reason mdoc didn't take over the world is for the same
 |reason DocBook didn't--it's too huge.  I think that man(7), even with
 |the an-ext stuff added on, is small enough to keep in one's head.
  ...
 |Of course what we need is a converter that goes in the other direction;
 |but that requires the encoding of semantic information that is lacking.

Self-describing macro names may be helpful.
In my opinion mdoc is gross and terrible, and you cannot even use
it to document C code very nicely.  But it has semantic
information and that is necessary for good manuals in a generic
language; you can very well create your own macros and process
them with scripts and tools to create the necessary environment,
but that is not generic.

Currently i think the future is some rich-text thing like asciidoc
or similar, and what would be needed would be good converters to
roff, and then mdoc not man, because it keeps at least a bit of
semantic information.  Or a completely new roff manual language.

I for one keep being disappointed when i see how much work is put
into books and articles, with footnotes, TOC, index, etc.  It
would be nice if you could run mandb and get a real book, cross-
referenced, with index, even better than what texinfo is or was.

 |I'd like to see what we can achieve by fiddling with it _without_
 |harming its portability.  Even as small as man(7) is, people neglect a
 |lot of its capabilities.

Yes, i think people mostly do it by copying over and/or looking
into manual pages they think look good, rather than by reading the
manual, or bying a good tutorial book that leads them step-by-step, 
but fast!, to good results.  That is the material world baby, you
want the burger royal with fifteen, whereas a Ayurveda masseur has
to sit beside his master and wait for i think seven years before
he gets his hands at the subject.

--steffen


From MAILER-DAEMON Tue Apr 25 09:00:42 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d305C-0006yV-Oj
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 09:00:42 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60839)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3055-0006x7-45
	for groff@gnu.org; Tue, 25 Apr 2017 09:00:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3051-0007Ud-8b
	for groff@gnu.org; Tue, 25 Apr 2017 09:00:35 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:47449)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3051-0007UN-1F
	for groff@gnu.org; Tue, 25 Apr 2017 09:00:31 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d304x-0003HQ-6q; Tue, 25 Apr 2017 15:00:28 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d304w-0006oC-F7; Tue, 25 Apr 2017 15:00:26 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d304w-0003gU-7G; Tue, 25 Apr 2017 15:00:26 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id d1c8be7b;
	Tue, 25 Apr 2017 15:00:26 +0200 (CEST)
Date: Tue, 25 Apr 2017 15:00:26 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Carsten Kunze <carsten.kunze@arcor.de>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170425130026.GA74948@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<1938619013.157418.1493117252773@mail.vodafone.de>
	<20170425112630.2bfpfaormbcruhxr@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425112630.2bfpfaormbcruhxr@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 13:00:41 -0000

Hi,

G. Branden Robinson wrote on Tue, Apr 25, 2017 at 07:26:32AM -0400:
> At 2017-04-25T12:47:25+0200, Carsten Kunze wrote:
>> Carsten Kunze wrote:
>>> Ingo Schwarze hat am 24. April 2017 um 16:39 geschrieben:

>>> Assuming this is considered the right direction, how would one
>>> best implement, in doc.tmac-u and an-old.tmac, - == \- == U+002D
>>> for all devices?

>> Isn't it already done for UTF-8 in the files you mentioned?
>> Both contain:
>> 
>> .if '\*[.T]'utf8' \{\
>> .  rchar \- - ' `
>> .
>> .  char \- \N'45'
>> .  char  - \N'45'
>> .  char  ' \N'39'
>> .  char  ` \N'96'
>> .\}

Yes, it is already done for UTF-8.
My question is: Which is a good way to do that consistently,
for *all* output devices?

>> Tests did show that groff's HTML output of manpages does not look good

I don't worry about groff HTML output at all.  By the basic design
of groff, it is unable to produce good HTML, so i basically just
ignore groff HTML output completely.  I fully agree with you that
i see no need to change it.  I'd even go one step further and say
there is no benefit to maintaining it at all.

But groff is very strong with respect to real typesetting output
modes, for example and in particular -Tps and -Tpdf.  I consider
it unfortunate that mdoc(7) and man(7) output of - and \- is
inconsistent between -Tutf8 and these other high quality output
modes.  Consistently producing U+002D in manual pages across -Tascii,
-Tutf8, and -Tpdf was also part of Ralph's original question.

> "hm" appears to be available in the namespace for short character
> escapes.  Would "\(hm)" be a good way to offer people U+002D for
> when they're absolutely sure they mean it?

I don't think that is a good idea.  It would be a step backwards
in terms of simplicity and usability.  In manual pages, you almost
always want U+002D, and both the simple and natural input "-" and
the traditional input "\-" already do that for -Tascii and -Tutf8,
the output modes that people use most for manual pages.

Telling people to use "\(hm" instead would make a simple thing more
complicated and less natural for manual page authors.  I don't think
that is acceptable.  It is OK to tell advanced authors who care
about the finer details of typesetting: "If, in exceptional cases,
you want this particular effect, you can use this escape sequence".
But for the simple stuff everybody needs all the time, simplicity
is paramount, and escape sequences should not enter the picture
unless absolutely unavoidable (like with \e).

> In any event, grohtml seems to be mapping all of -, \-, and \(hy to
> U+002D (see attachments), which doesn't seem ideal to me given the
> capabilities and character repetoire of most HTML renderers.

Right.  Given that HTML supports Unicode entities, HTML output
ought to produce the same characters as -Tutf8.  For example,
mandoc does that.  But again, i consider working on groff HTML
output a waste of time.  PostScript and PDF is what matters most.

Yours,
  Ingo


From MAILER-DAEMON Tue Apr 25 09:21:30 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d30PJ-00079r-Ux
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 09:21:29 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40412)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d30PG-000786-L6
	for groff@gnu.org; Tue, 25 Apr 2017 09:21:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d30PB-00019b-NE
	for groff@gnu.org; Tue, 25 Apr 2017 09:21:26 -0400
Received: from mail-yw0-x243.google.com ([2607:f8b0:4002:c05::243]:34771)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d30PB-00019D-Hw
	for groff@gnu.org; Tue, 25 Apr 2017 09:21:21 -0400
Received: by mail-yw0-x243.google.com with SMTP id u70so16896789ywe.1
	for <groff@gnu.org>; Tue, 25 Apr 2017 06:21:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=wzYBbZ6stq7kBhPl426ZmhUCKFXGf7sV2nCq5GCFB1I=;
	b=LhyexZ62zub20HCVkcK7a61bFkbM07c5bJF2F0lVCjCdAo84SB/JvpCsrUrCcEff9R
	jQQtgeNTpqD5qLPdpHEr2hu5UNMYtbLa1nb6oogwIK6+7hQLVnOCddnzzmm/UYrSz07i
	wLZmPyMw7Gu3f0g5LX9vZzX1myRSs1iPjNvRIrpV+cILGRCqKZasXkkAWJyK+dKUMeL/
	bs1PovMZFWifpGMo1Dn+HGTAJw6b72MRo7xE1XgDzGoqbeSYcOWUVAza9xYoxV1srL5+
	od2Zr65H2XzPzNLtuu9tbGO8Qzhqez6xbIQMZJ2HrZseYGHZhZ39XNQBg/fIjiei5rPF
	w5cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=wzYBbZ6stq7kBhPl426ZmhUCKFXGf7sV2nCq5GCFB1I=;
	b=Zx3oPsZgA2BLA/CDT1O6irWKXEnpLNfG+xBhHgvd1x7d2Jef3YLTEaT7EI3X3H8ZxV
	5Rlwhd+NMtvAtfnfQHr3o35qZmPeuI5n3xkOYA31WdClFfWeQFm2DGX3pcBiafad7KqX
	FTOP/5UBEcVW1MQ2GyHCHwGiTP+2AzfEjAeElkZCg5eCoEZkTA8eV6JV8MfaBgGjbBWc
	gZ28NXJtgSce7P6JluDYO2tv9wi1ZDgCdYysj6kVmRgce/tjIF1nSSFv0kR82EJ3gdqQ
	f2sVa/q/xeuLnfsCBTh2aA4XeMgx28TCb4sB2Xu5dJ2ZeHr372B6GGCBiKCKAocMmBo7
	JcyQ==
X-Gm-Message-State: AN3rC/63WYXRq6GMBVlfc0aCocjtjsjyOVYNScBhzHv0vX7AnM392vH2
	yS/SoSnMksbIFA==
X-Received: by 10.129.181.7 with SMTP id t7mr9783140ywh.26.1493126480815;
	Tue, 25 Apr 2017 06:21:20 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	p66sm3828729ywg.28.2017.04.25.06.21.19
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Tue, 25 Apr 2017 06:21:19 -0700 (PDT)
Date: Tue, 25 Apr 2017 09:21:17 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: Carsten Kunze <carsten.kunze@arcor.de>, groff@gnu.org
Message-ID: <20170425132114.pacqjrgnbq7rljbw@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<1938619013.157418.1493117252773@mail.vodafone.de>
	<20170425112630.2bfpfaormbcruhxr@crack.deadbeast.net>
	<20170425130026.GA74948@athene.usta.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425130026.GA74948@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::243
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 13:21:28 -0000

At 2017-04-25T15:00:26+0200, Ingo Schwarze wrote:
> I don't worry about groff HTML output at all.  By the basic design
> of groff, it is unable to produce good HTML, so i basically just
> ignore groff HTML output completely.  I fully agree with you that
> i see no need to change it.  I'd even go one step further and say
> there is no benefit to maintaining it at all.

It sounds like there is a lot in groff you'd like to throw away.

an-ext.tmac, grohtml, ...

> > "hm" appears to be available in the namespace for short character
> > escapes.  Would "\(hm)" be a good way to offer people U+002D for
> > when they're absolutely sure they mean it?
> 
> I don't think that is a good idea.  It would be a step backwards
> in terms of simplicity and usability.  In manual pages, you almost
> always want U+002D, and both the simple and natural input "-" and
> the traditional input "\-" already do that for -Tascii and -Tutf8,
> the output modes that people use most for manual pages.

Yes.  How is this an argument against?  Our other conversation aside,
I'm not thinking only of the use case of the drooling newbie.  The man
and mdoc macros should do the right thing requiring the least thought
for the common case, and documenting U+002D-prefixed command-line
arguments is extremely common.

What's simple and usable about the status quo?  If I want to represent
ASCII 45 decimal in my document, what's the simple and usable way to
make sure I get the glyph I want, with today's *roff?

Does this simple and usable way port across output devices?  Across
macro packages?

> Telling people to use "\(hm" instead would make a simple thing more
> complicated and less natural for manual page authors.  I don't think
> that is acceptable.  It is OK to tell advanced authors who care
> about the finer details of typesetting: "If, in exceptional cases,
> you want this particular effect, you can use this escape sequence".
> But for the simple stuff everybody needs all the time, simplicity
> is paramount, and escape sequences should not enter the picture
> unless absolutely unavoidable (like with \e).

You confuse me.  Having \(hm is a bad idea--okay.

How, then, to enable the sophisticated writer to get a guaranteed U+002D
regardless of the output device?  Make them write a bunch of .if and .ie
macros and test the .T string register every time?

You asked:

> My question is: Which is a good way to do that consistently,
> for *all* output devices?

It sounds like we don't have one.  How about we make one?

> > In any event, grohtml seems to be mapping all of -, \-, and \(hy to
> > U+002D (see attachments), which doesn't seem ideal to me given the
> > capabilities and character repetoire of most HTML renderers.
> 
> Right.  Given that HTML supports Unicode entities, HTML output
> ought to produce the same characters as -Tutf8.  For example,
> mandoc does that.  But again, i consider working on groff HTML
> output a waste of time.  PostScript and PDF is what matters most.

Do you have something to tell people wishing to improve grohtml besides
"it's a bad idea and a waste of time"?

-- 
Regards,
Branden


From MAILER-DAEMON Tue Apr 25 10:52:39 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d31pX-0007n9-6F
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 10:52:39 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37307)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d31pS-0007kR-EJ
	for groff@gnu.org; Tue, 25 Apr 2017 10:52:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d31pN-0004OT-RT
	for groff@gnu.org; Tue, 25 Apr 2017 10:52:34 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:59262)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d31pN-0004Mr-Gz
	for groff@gnu.org; Tue, 25 Apr 2017 10:52:29 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d31pE-0008N5-SM; Tue, 25 Apr 2017 16:52:25 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d31pE-00047i-7I; Tue, 25 Apr 2017 16:52:20 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d31pE-0005pK-1V; Tue, 25 Apr 2017 16:52:20 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 59cf17eb;
	Tue, 25 Apr 2017 16:52:20 +0200 (CEST)
Date: Tue, 25 Apr 2017 16:52:20 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170425145219.GB74948@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 14:52:38 -0000

Hi,

G. Branden Robinson wrote on Tue, Apr 25, 2017 at 07:14:58AM -0400:

> No, what I really want is a TP-ish macro that lets you break the tag
> across multiple input lines, so the writer doesn't have to use font
> escapes.
> 
> If that means a new macro, I'm fine with that.

I think that plan is even worse.  Even in mdoc(7), i think extremely
carefully before proposing a new macro and avoid it if it is somehow
possible, even though in mdoc(7) it would be less of a problem
because legacy implementations virtually don't exist: everybody is
using mandoc, groff, or Heirloom, so extending the language would
be viable - but it is still better to avoid it.  I don't think i
invented a single new macro during during the about seven years
that i maintain mdoc(7).

For man(7), introducing new macros would be worse.  There, it would
utterly break portability because other implementations do exist,
for example on commercial Solaris and maybe on other commercial
systems, and man(7) still matters as the fallback language to use
when installing portable software and its documentation on legacy
systems, even if that documentation is written in mdoc(7).  So i
don't think we can afford inventing new man(7) macros.  Using them
would utterly destroy portability of the affected manuals.

> This is fine, but it says to me that your original complaint ("a
> horrible hack [to be] avoided ... even in the implementation of macro
> sets") is overstated.

In that sense, maybe, though i said "to be avoided if possible".

> Maybe \c it's like inline assembly in C.  Something best reserved to
> experts under special circumstances, perhaps, but not a horrible hack.

I guess we can agree on that, yes.


> At 2017-04-25T07:04:27+0200, Ingo Schwarze wrote:

>> Well, and the partial one in mandoc, but mandoc follows groff in
>> roff matters.

> I need to look more deeply into that; I don't know how you'd implement
> mandoc without implementing the bulk of *roff.

I explained that during an international conference in 2011:

  https://www.openbsd.org/papers/bsdcan11-mandoc-openbsd.html

Pages 7, 12, 13, 14, 20, 24 are particularly relevant to your question.

There are newer presentations, see http://mdocml.bsd.lv/press.html,
in particular the recent overview

  https://www.openbsd.org/papers/eurobsdcon2015-mandoc.pdf


>> G. Branden Robinson wrote on Mon, Apr 24, 2017 at 09:22:25PM -0400:

>>> If \c is documented badly and/or under-specified, let's determine its
>>> precise semantics and document them clearly.

>> I do suspect there is room for improvement, or at least clarification,
>> in the \c specification, so working on that likely makes sense.
>> But please, regard that as a work to help macro implementors,
>> **not** end users!

> Well, fine, let's proceed with that, then.  See end of this mail.

I don't see any patch there...
Did you forget to append it?

> The groff community needs to be singing from the same hymnal when it
> comes to recommended best practices.  If an-ext.tmac should be
> deprecated and avoided, that needs to be formally established and
> reflected in the software releases, maybe with a .tm warning in its
> source.

I agree that would be better.

>>> In my experience, one can write an attractive manpage almost without
>>> ever restoring to straight requests.

>> And yet you suggest that authors should use the \c escape sequence,
>> which quite definitely is a very low-level roff feature and not
>> an element of the man(7) language at all.

> Yes, but so are character escapes, which are unavoidable in good
> manpage writing.

Well, mandoc_char says:

  DESCRIPTION
     This page documents the roff(7) escape sequences accepted by
     mandoc(1) to represent special characters in mdoc(7) and man(7)
     documents.

     The rendering depends on the mandoc(1) output mode; in ASCII
     output, most characters are completely unintelligible.  For
     that reason, using any of the special characters documented
     here, except those discussed in the DESCRIPTION, is strongly
     discouraged; they are supported merely for backwards compatibility
     with existing documents.

     In particular, in English manual pages, do not use special-character
     escape sequences to represent national language characters in
     author names; instead, provide ASCII transcriptions of the
     names.

And then it lists the following characters under DESCRIPTION

  \& \(mi \(en \(em "\ " \(dq \(ga \(aq \(ti \e

in the sense that none of the many others should be used, and even
most of these few are rarely needed.  Only \& and \e are common.

So you may be slightly overstating the case for character escapes.

>> In the example you bring up, there is indeed no viable alternative to
>> using \f font escapes.  You propose to trade the \f for \c.  I say \c
>> is much worse than \f.  The syntax and semantics of \f is relatively
>> easy to understand, and people writing man(7) are used to it, while \c
>> is quite arcane.

> Okay.  What alternatives can you propose for getting rid of \f in man
> pages, short of migrating the universe to mdoc?

I am not away of any way to do that without utterly breaking
compatibility.  Unfortunately.  If you find one, great, but i
doubt that any is possible.

>>> (People are often ignorant of the an-ext macros, which are so
>>> liberally licensed they can be used anywhere.)

>> I admit that the en-ext macros minimally improve semantic capabilities
>> of the man(7) language, but by so little that man(7) remains an
>> almost exclusively presentational language even with man-ext.
>> For that reason, i deem that using man-ext does more damage than
>> good:  It doesn't substantially improve the language, but it
>> does cause compat grief on old systems, which is exactly where
>> the legacy man(7) language is still needed.  Bad tradeoff...

> What I'm hearing is that you feel that man(7) is a lost cause:
> 
> A.  It desparately needs improvement because of its presentational,
>     rather than semantic, focus.
> B.  Improvement will break portability.
> 
> This basically amounts to doing nothing and letting man(7) die of its
> own accord.

Exactly.

I'm a strong believer in incremental software development.  But
there are exceptional cases where incremental improvements are not
viable, in particular when the basic paradigm employed is busted
and the language is a dense tangle of historically cemented layering
violations.  The man(7) language is one of these cases.  Fortunately,
it has been obsolete for 25 years now, and mdoc(7) is mature and
readily available.  That GNU is the last major free operating system
that did not adopt it yet does not preclude future progress.

> But it hasn't.  Look at the past 20 years.  It's still alive,
> and what vibrancy it has lost, it has lost to stuff like Markdown
> which is even _less_ semantic.

Agreed:  Markdown (and probably ASCIIdoc, too) are worse than man(7):

  http://undeadly.org/cgi?action=article&sid=20170304230520

> Not to mdoc.

Look at the last seven years. 

mdoc(7) and mandoc(1) are firmly established in all *BSD projects
and in Minix 3.  Illumos (formerly OpenSolaris) switched to mdoc(7)
in 2014.  Even in the GNU/Linux camp, there is some movement.  Debian
has an official mandoc port since 2016, Arch Linux since 2010.
Alpine Linux and Void Linux use mandoc by default (rather than the
man-db + groff combo) since 2014.

Changes take time.  I haven't given up on GNU just yet.

> My recommendation is to take the momentum an-ext has, however small, and
> press it:
> 
> a.  Add more macros to fit semantic needs and the hiding of lower-level
>     requests and escapes.
> b.  Hand-hold users to the nth degree with examples and recommended best
>     practices.
> c.  Show people a mapping from groff's "extended" man macro package to
>     mdoc, so that the route for switching over is clearly signposted.

It seems to me that b) is fine, a) is very problematic because it
severely harms portability, and c) may or may not help to convince
people.  I'm not sure the intermediate step of reinventing man(7)
as a semantic language will make the transition easier.  Why should
people have to learn a new man(7) language in between, in addition
to the old man(7) and in addition to mdoc(7)?

> I have my pet peeves as well; I don't like the shouty caps in arguments
> to TH and SH.  That's information-losing and presentationy.

Admitted, i don't like that either, but that (ugly) convention is
uncontroversial: all existing documentation recommends it.

What i was talking about was not "pet peeves", but unnecessary
divergence from previously established standards.  The Linux man
pages project was started in 1993.  By that time, groff already
unambiguously documented most of the points i listed.  Yet man-pages(7)
gratuitiously diverged in these - admittedly minor - respects.

> Why not encourage people to have site-local files that redefine
> these macros to do a ".tr aAbBcC" etc. if they insist on seeing
> screaming caps?

That old AT&T UNIX era convention could probably simply be dropped
without replacement, but it doesn't seem high priority.


>>> At 2017-04-24T18:29:57+0200, Ingo Schwarze wrote:

>>>> Writing mdoc(7) is much easier for the novice because it's semantic
>>>> and because it does not require mixing in low-level roff features.

>>> And yet, why have so few people outside of the BSD community adopted it?

>> Frankly, i'm not sure.  Illumos has, for example; so of the free
>> operating systems, it's mostly GNU that doesn't use it.  One reason
>> could likely be that GNU used to use texinfo(1), but that is being
>> abandoned now.

> Is that official?  The last time I checked their list archives (a few
> months ago), they were openly wondering "whither texinfo?" but hadn't
> yet decided to abandon the project.

https://lists.gnu.org/archive/html/groff/2014-02/msg00104.html


> 1.  Let's document, for the newbs and ourselves, what the heck "\c"
>     really means.

Sure, but i don't see the patch you promised.

> 3.  Let's talk to the man-pages folks about harmonizing style
>     recommendations.

Sure, though that may be a slow process and some differences will
likely remain.  The Linux man pages project is only one project,
while the conventions documented in groff and mandoc documentation
are used across four major projects, and the Linux man pages project
is the one that deviated from established practices in the few minor
points noticed in the first place (side note: OpenSolaris diverged
even more).  Yet, i would understand the Linux man pages project
would hesitate to edit all their pages for harmonization.

Such slight differences between different projects are also not
fatal, even if they put a slight strain on casual readers in
heterogenous environments.

Yours,
  Ingo


From MAILER-DAEMON Tue Apr 25 14:19:15 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d353T-00028C-HN
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 14:19:15 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45825)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d353Q-000267-H2
	for groff@gnu.org; Tue, 25 Apr 2017 14:19:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d353M-0006Wd-Eu
	for groff@gnu.org; Tue, 25 Apr 2017 14:19:12 -0400
Received: from sdaoden.eu ([217.144.132.164]:38774)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d353M-0006WK-3f
	for groff@gnu.org; Tue, 25 Apr 2017 14:19:08 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 5866316051; Tue, 25 Apr 2017 20:19:06 +0200 (CEST)
Date: Tue, 25 Apr 2017 20:19:21 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>, groff@gnu.org
Message-ID: <20170425181921.kz2kB%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
In-Reply-To: <20170425145219.GB74948@athene.usta.de>
Mail-Followup-To: Ingo Schwarze <schwarze@usta.de>, groff@gnu.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 18:19:13 -0000

Ingo Schwarze <schwarze@usta.de> wrote:
 |G. Branden Robinson wrote on Tue, Apr 25, 2017 at 07:14:58AM -0400:
 ...
 |> If that means a new macro, I'm fine with that.
 ...
 |For man(7), introducing new macros would be worse.  There, it would
 |utterly break portability because other implementations do exist,

Now i really oppose that.  That is utterly shit, Ingo.  You can do
whatever you want, except for "security sandbox" restrictions
(iirc some commands don't work).  You could use the painting
commands if the output works fine on the tty even.  You could
dynamically generate parts of the manual page.  Most people don't,
but they could be almost completely free if they want to, and
i for one consider this as something important.

Of course such things won't work in mandoc then, but 99.9 percent
of all manuals will do just fine, and much, much faster than roff
will ever be able to serve.  While you complain about the somewhat
broken grohtml, the HTML output of mandoc used repeated
per-paragraph style directives and a CSS file, which caused
enormous bloat, last time i tried.

  ...
 |I'm a strong believer in incremental software development.  But
 |there are exceptional cases where incremental improvements are not
 |viable, in particular when the basic paradigm employed is busted
 |and the language is a dense tangle of historically cemented layering
 |violations.  The man(7) language is one of these cases.  Fortunately,
 |it has been obsolete for 25 years now, and mdoc(7) is mature and

Oh, come on Ingo.  man is obsolete for 25 years?  In the BSD
world, of which i feel part of for almost fifteen years myself,
but that is not the motor of the software world, by far.  Of
course you can build a car with only stolen parts.  Still, those
have to come from somewhere.

Btw., if you want really clean man(7) you should point people to
the really good guys, e.g., the plan9port manuals are a phantastic
example of minimalistic and pure pages.

 |> My recommendation is to take the momentum an-ext has, however small, and
 |> press it:
 |> 
 |> a.  Add more macros to fit semantic needs and the hiding of lower-level
 |>     requests and escapes.
 |> b.  Hand-hold users to the nth degree with examples and recommended best
 |>     practices.
 |> c.  Show people a mapping from groff's "extended" man macro package to
 |>     mdoc, so that the route for switching over is clearly signposted.
 |
 |It seems to me that b) is fine, a) is very problematic because it
 |severely harms portability, and c) may or may not help to convince
 |people.  I'm not sure the intermediate step of reinventing man(7)
 |as a semantic language will make the transition easier.  Why should
 |people have to learn a new man(7) language in between, in addition
 |to the old man(7) and in addition to mdoc(7)?

Even though still without voice, a) is in no way problematic if
the original roff command set is used and no wild and funny
programming sessions lead to mandoc incompatibilities.  b) is
fantastic, c) i don't really believe in, mdoc has quite some
similarities to brainfuck, things like

  .Op : Ns Fl c Ar cc-addr Ns \&:
or
  .Fl S Ar var Ns Op Ns = Ns Ar value Ns

are nice for teaching, but no one can really promote something
like this, can he.

And sometimes things have to be adjusted a bit so that things can
overall stay the same.  The roff system is a fantastic
achievement, and if at all possible i will use it until the day
i die.  I am looking forward for my thing.

--steffen


From MAILER-DAEMON Tue Apr 25 19:00:37 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d39Rk-0002YG-US
	for mharc-groff@gnu.org; Tue, 25 Apr 2017 19:00:36 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44339)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d39Ri-0002WV-1n
	for groff@gnu.org; Tue, 25 Apr 2017 19:00:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d39Re-0002O6-03
	for groff@gnu.org; Tue, 25 Apr 2017 19:00:34 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:33284)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1d39Rd-0002NY-SK
	for groff@gnu.org; Tue, 25 Apr 2017 19:00:29 -0400
Received: from coolidge.cs.Dartmouth.EDU (coolidge.cs.dartmouth.edu
	[129.170.213.217])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v3PN0RSW004704
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
	for <groff@gnu.org>; Tue, 25 Apr 2017 19:00:27 -0400
Received: from coolidge.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTP id
	v3PN0QLT009879 for <groff@gnu.org>; Tue, 25 Apr 2017 19:00:26 -0400
Received: (from doug@localhost)
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v3PN0QCi009878
	for groff@gnu.org; Tue, 25 Apr 2017 19:00:26 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
Date: Tue, 25 Apr 2017 19:00:26 -0400
To: groff@gnu.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 23:00:34 -0000

> .TP
> .B \-scale \c
> .IR xfac [, yfac ]

Very clever. I wish I'd thought of it when I was editing
the v7 manual. Then it would have become a standard idiom.
Has nobody tried this during the nearly 40 years since?

Doug


From MAILER-DAEMON Wed Apr 26 08:43:56 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3MIW-00031p-2U
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 08:43:56 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35161)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3MIT-00030P-RM
	for groff@gnu.org; Wed, 26 Apr 2017 08:43:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3MIP-0001Nc-OM
	for groff@gnu.org; Wed, 26 Apr 2017 08:43:53 -0400
Received: from mail-yb0-x230.google.com ([2607:f8b0:4002:c09::230]:33053)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3MIP-0001Mu-Eu
	for groff@gnu.org; Wed, 26 Apr 2017 08:43:49 -0400
Received: by mail-yb0-x230.google.com with SMTP id 11so1120402yby.0
	for <groff@gnu.org>; Wed, 26 Apr 2017 05:43:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=QEFaQ6hUW3G8qzg65M8RqxQvUQwkaK+YUB7RnVwGOiA=;
	b=WnQXMVylAU6EzYpzbGAAz6jeFVBZ1BPUvRZk83TvJBLgl9y/jDA48tITWmorMtt8Fp
	rFSgdor9XAwBFCEkp55nQANAA7DCVRULVekd1rY63VT6vUrkiF/CMYtcCS2OYM1UD4qM
	N64CKa1Ab1nYFdSM2WdvGJXtS4HNVCUbToYjshJ5DRd/BaK1k8EVhMQeor82xiwM/VxF
	Nib5bJh5fLO/KXcF3xJY+cBPjhKMUx90s90FWw8X6DOHbZyLrcqsgW1AhyWUUnbh86eL
	Quz+5JIgM8NakzVivuE2kKiTtGblU7ovHHg/GJEL/T0a7fWMCe105gDGbh61331gr5EK
	Grrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=QEFaQ6hUW3G8qzg65M8RqxQvUQwkaK+YUB7RnVwGOiA=;
	b=qrRvNcx2bF6Cw+1fgz1WWkJVLc+nu9g0aOz1bzBZTIlVgAU+1JmcA8VTWV8g0jUL+A
	tkiCQGiEtt1xwEL2b2P7Bk2OY2GH3VS9hK6aFBBahLZODxES0SSV8BeEVJzukSa5+a6I
	QGsS0jOolioFFSQ9Eq7tiUx5el4io0tM624xvfDDKHqM65nSzrz5PuaaKVbmji3LrVGj
	3VDF1gojBZyiHSMvbbyZ86drMlLeYzouJHzznWrw7eNbFq3U18+lqhDH7WENax0EnjkO
	R7C5O2Cf/Ll1ZL34HXNuFf96fQrbbWC87MxjcqX8Rb0phpw+WabgMbTuaUyeQACIqOd7
	FUHw==
X-Gm-Message-State: AN3rC/6h9sP3SoqOOt1CAoa2QxxQRU1xO1nouqsa0zlINJYWmqZBd8NE
	nrmytGyEuAV0KA==
X-Received: by 10.37.178.40 with SMTP id i40mr13528209ybj.5.1493210628281;
	Wed, 26 Apr 2017 05:43:48 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id j10sm53984ywa.21.2017.04.26.05.43.46
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 05:43:47 -0700 (PDT)
Date: Wed, 26 Apr 2017 08:43:44 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: groff@gnu.org
Message-ID: <20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="otwnfadtwfalgpws"
Content-Disposition: inline
In-Reply-To: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::230
Subject: [Groff] Applications of \c in man pages in the wild [LONG] (was:
 Nesting font macros in man pages)
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 12:43:55 -0000


--otwnfadtwfalgpws
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-25T19:00:26-0400, Doug McIlroy wrote:
> > .TP
> > .B \-scale \c
> > .IR xfac [, yfac ]
>=20
> Very clever. I wish I'd thought of it when I was editing
> the v7 manual. Then it would have become a standard idiom.

Thanks, Doug!

> Has nobody tried this during the nearly 40 years since?

Well, that exact example doesn't work with the stock GNU troff man
macros, because as noted earlier, TP sets an input trap for the next 1
lines (.it 1), counting interrupted lines.

However, the trick of using \c to "get out of" a man font macro without
introducing unwanted whitespace has some precedent (see below).  A few
souls appear to have figured it out before.

So in hopes of settling the issue of the meaning of \c and its usage in
man pages, I undertook a survey of several thousand man pages on my
Debian stretch system.  I documented my method below[1].

I found uses of \c in 210 out of 6,939 non-symlink man pages.

In the following survey I'll skip over uses of \c inside macro
definitions, as that sort of use is what Ingo and I seem to agree is
"expert mode".

\~\c at the ends of lines seems to be a reasonably common technique for
preventing a line break when using font-changing macros in phrases like

    For each \~\c
    .I x
    such that
    .I x\~\c
    <\~0,

Examples of this usage can be found in chem(1), eqn(1), gropdf(1),
and grops(1).

Man pages generated by docbook-to-man, like those in git and patchutils,
use \c inside expressions like this, apparently generated by
docbook-to-man.

    .sp
    .RS 4
    .ie n \{\
    \h'-04' 1.\h'+01'\c
    .\}
    .el \{\
    .sp -1

tracker-extract(1) follows the above pattern too (without the
conditional on nroff), but the man page has some basic style problems,
looks hand-written, and I think the usage was cargo-culted from
elsewhere.

chmod(1) uses \c simply to break a really long line.  I think they meant
"\<newline>" instead.  Notably, the page was generated by help2man.

dvipdfmx(1) seems to have a legitimate use case:

    .SH SYNOPSIS
    .B dvipdfmx
    or
    .B dvipdfm
    .RI [ options ]
    .I file\c
    .RB [ .dvi ]

dvipdft(1) is similar.

extractbb(1) uses \c to get out of a font-change macro without
introducing a word break:

    .PP
    For each
    .SM JPEG\c
    ,
    .SM PNG\c
    , or
    .SM PDF
    file given on the command line,

=2E..as does gawk(1):

    .TP
    .B ?:
    The C conditional expression.  This has the form
    .IB expr1 " ? " expr2 " : " expr3\c
    \&.

=2E..and grep(1):

    .SS "Back References and Subexpressions"
    The back-reference
    .BI \e n\c
    \&, where

=2E..and groff(1):

    Include macro file
    .IB name .tmac
    (or
    .BI tmac. name\c
    ); see also
    .BR \%groff_tmac (5).

=2E..and groffer(1):

    A locale name is typically of the form
    .nh
    .IR language [\c
    .B _\c
    .IR territory [\c
    .B .\c
    .IR codeset [\c
    .B @\c
    .IR modifier ]]],
    .hy

=2E..and grohtml(1):

    .TP
    .B \-h
    Generate section and number headings by using
    .BR <B> .\|.\|. </B>
    and increasing the font size, rather than using the
    .BI <H n >\c
    \&.\|.\|.\c
    .BI </H n >
    tags.

=2E..and imgtool(1):

    .br
    .B imgtool get
    .I format image file
    .RI [ newname ]
    .RB [ \-\-filter=3D\c
    .IR filter ]
    .RB [ \-\-fork=3D\c
    .IR fork ]
(similar examples follow in the same page)

=2E..and (as noted in the forked-from thread) ksh93(1):

    .SS Field Splitting.
    After parameter expansion and command substitution,
    the results of substitutions are scanned for the field separator
    characters (those found in
    .SM
    .B IFS\^\c
    )
    and split into distinct fields where such characters are found.

=2E..and man(1), which uses this trick extensively:

    .B man
    .RB [\| \-C
    .IR file \|]
    .RB [\| \-d \|]
    .RB [\| \-D \|]
    .RB [\| \-\-warnings \|\c
    .RI [\|=3D warnings \|]\|]
    .RB [\| \-R
[...]
    .RB [\| \-t \|]
    .RB [\| \-T \|\c
    .RI [\| device \|]\|]
    .RB [\| \-H \|\c
    .RI [\| browser \|]\|]
    .RB [\| \-X \|\c
    .RI [\| dpi \|]\|]
(14 more instances in the page, not including:)
    .\"
    .\" Need a \c to make sure we don't get a space where we don't want one
    .\"

Groff's own gdiffmk appears to have some useless uses of \c:

    .OP \-d \%deletemark
    [\ \c
    .B \-D
    .OP \-B
    .OP \-M "mark1 mark2"
    ]
    .OP \-x \%diffcmd
    .OP \-\-
    .OP \-\-help
    .OP \%\-\-version
    .I \%file1
    .I \%file2
    [\ \c
    .IR \%output \ \c
    ]
    .br

I rewrote the above as follows with no visible effect on the utf8 and ps
devices:

--- gdiffmk.stock.1     2017-04-26 08:13:55.757049173 -0400
+++ gdiffmk.hacked.1    2017-04-26 08:08:56.875417280 -0400
@@ -53,7 +53,7 @@
 .OP \-a \%addmark
 .OP \-c \%changemark
 .OP \-d \%deletemark
-[\ \c
+[
 .B \-D
 .OP \-B
 .OP \-M "mark1 mark2"
@@ -64,8 +64,8 @@
 .OP \%\-\-version
 .I \%file1
 .I \%file2
-[\ \c
-.IR \%output \ \c
+[
+.I \%output
 ]
 .br
 .ad \na

grodvi(1) uses the following construction, whose purpose I cannot guess:

    The fonts are grouped into families
    .B T
    and
    .B H\ \c
    having members in each of these styles:

In context, both escapes look like no-ops to me.  Maybe a bold space is
slightly wider than a roman one on some output devices?  Since it's an
adjustable space anyway I wonder at the signficance.  Perhaps there was
a third font family once, and this .B used to be a .BR which needed more
care.

That gets me to page 110 of the 210 I'm looking at.

I'll see what kind of commentary my survey provokes before returning to
the remainder, but I expect it'll be mostly more of the same.

Contra Ingo, I find little in these uses of \c to shock me.  I was more
shocked by some of the stuff I saw inserted by transformation tools that
generate man documents as output.

Regards,
Branden

[1] Method:

$ find /usr/share/man/man* -type f -and -not -type l \
        | xargs zgrep -l '[^\]\\c' | sort >| /tmp/backslash-c.txt

--otwnfadtwfalgpws
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkAlfUACgkQ0Z6cfXEm
bc59Bw//U972OxzBT0m9nEAqvE7MOWiL0xxzHpP5wHV37td6GbuPRQoH3EBxem5e
NjBy02OXyvm1r7737BQWA5TOvGAovsGfswqYRsSIIwrCwjZ0BPhC7BCO1mvpraPW
z+ug1TZQIStUpNSg6gVb6PduTLvD10RYUgWE1Xxi/88ncfM+1mQr0c5C95vUL7WZ
RD5B9hzNltS41wc5y72YgyRytkrkrPCb9AckodNMayHk09k/bJdDwXbW8Mhdixru
kGLRmLGTrpfa37nIUR6yMLllJiWbCYEopRwSbg0SSDyWDtIlklfyHiWPZV/7GIVB
3P/yO9mdBLF4ze+BYHmhB5lIUwpviQDrbLQA15SrmdsSd4TwOeRsf4kWyCb3d73b
cbQB7qXms/ZFtr+8iIWPNAtpB+wI4dKcc000j2B8av95o2DHdZJSHgLPAmN1SctG
SSPfKyJRpjFIGrHnyW3YZdzLvv9FyhyUMMAmqJ7Cc8UVqHam0zN3vqYdVSfGcgDY
qYWyBOyC9QXK3idiWpFtVtCXfPsRW94N/4122vGxm25kkq7y0rFLL4dkm5/YNag3
BOZSYV5I1CMHUto8qKBzUXinzKr8idp4Sv6go8SxLZsBNzBe9moYP7glgUUPzNIM
HZ5nnGAmtFBij65EW/RDp3/hxR4oSZ1O4o1P9n7zxqgH6fVTT94=
=8Sno
-----END PGP SIGNATURE-----

--otwnfadtwfalgpws--


From MAILER-DAEMON Wed Apr 26 09:28:14 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3MzN-0000J2-U6
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 09:28:13 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44213)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3MzJ-0000Fx-2s
	for groff@gnu.org; Wed, 26 Apr 2017 09:28:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3MzD-0002U0-1W
	for groff@gnu.org; Wed, 26 Apr 2017 09:28:09 -0400
Received: from mail-yw0-x233.google.com ([2607:f8b0:4002:c05::233]:35990)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3MzC-0002So-RH
	for groff@gnu.org; Wed, 26 Apr 2017 09:28:02 -0400
Received: by mail-yw0-x233.google.com with SMTP id l18so109400ywh.3
	for <groff@gnu.org>; Wed, 26 Apr 2017 06:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=AN8XRrnk6ew2u0soR2xXNKo9dtUjo+3VhjrcX1ENVi4=;
	b=dPMUhMoE6/n5qyTw2j9NdvPRpZu1ItHT9craGFkVFsiUV0c5StrwxdZdreYvL4PABf
	YEToMuwofayqypXv4HDb9ONJxkHKKfEch0DLtZW3C+tXZTmUgFfujDmymVYMPs3cGBxS
	mY4W9VZHa12w5kzJ/dI+xp9hOV6KRa/WgVABLp4/qM4XiWehyUtCZqFYx0sRUL/Y+7gb
	WLNaR8U+W7kNqP7y2WhaIYO4LoSc+3iLWQx1e31IDbVmyz/4a4wrskp+c+ol+FwpzNkK
	XlKMmOfmoLhYAZKR2BW8Ly+AQS18CaW5COGtdWQMpZk7+DiTeueu39pXQouU6qXTfhoC
	4Fbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=AN8XRrnk6ew2u0soR2xXNKo9dtUjo+3VhjrcX1ENVi4=;
	b=jjz1gVs9v54UxqdI4vs9ekQW/6R1hFvcudGjBjDG+EPA7Y5NwD2ZptQmJ9WGqnV6Cg
	dvywSzBSM2tgX6OGg1JhyCbwnesymGdwYDzjEBrtvcRiEVzyrhsO3yEr4dQIO/7FI75G
	3krtZAINjHamOmKs+yvnz77Q/VUvLgp+SbtY5RdRloib8c4F964sw109dsMKYBqCNzfN
	rz8eroRT93h1zya8a9z/mjVJFsu6m6KWWOV+ugRIZ3PFUQeC+hy8H+ZIkXKzgjy61VlC
	yzlYQoDfGOGm59JTEMArWEySq7YuO+3R5GFf1rMsi78L8BkbMiZcdo4FGjN24JYEulAP
	PfYg==
X-Gm-Message-State: AN3rC/7vi7w3sqa70dc3HEyhHIAk63ogiu/3MSkDv1ithizyjHsbrmHh
	seE9nx2qK/qfSPy8XGmNug==
X-Received: by 10.13.237.5 with SMTP id w5mr14618978ywe.70.1493213281502;
	Wed, 26 Apr 2017 06:28:01 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id p1sm93852ywh.77.2017.04.26.06.27.59
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 06:28:00 -0700 (PDT)
Date: Wed, 26 Apr 2017 09:27:58 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426132755.bywvghd2onf4acjt@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="m3ktnwuinshkgcio"
Content-Disposition: inline
In-Reply-To: <20170425145219.GB74948@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::233
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 13:28:12 -0000


--m3ktnwuinshkgcio
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-25T16:52:20+0200, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Tue, Apr 25, 2017 at 07:14:58AM -0400:
>=20
> > No, what I really want is a TP-ish macro that lets you break the tag
> > across multiple input lines, so the writer doesn't have to use font
> > escapes.
> >=20
> > If that means a new macro, I'm fine with that.
>=20
> I think that plan is even worse.  Even in mdoc(7), i think extremely
> carefully before proposing a new macro and avoid it if it is somehow
> possible, even though in mdoc(7) it would be less of a problem
> because legacy implementations virtually don't exist: everybody is
> using mandoc, groff, or Heirloom, so extending the language would
> be viable - but it is still better to avoid it.  I don't think i
> invented a single new macro during during the about seven years
> that i maintain mdoc(7).

I'm not suggesting recklessness.  Any proposals to extend the man macro
package should be mooted in a discussion involving experts and users,
not thrown over the wall, take-it-or-leave-it style.

Any extensions _I_ propose I expect to be evaluated in a context of
"rough consensus and working code".

> For man(7), introducing new macros would be worse.  There, it would
> utterly break portability because other implementations do exist,
> for example on commercial Solaris and maybe on other commercial
> systems, and man(7) still matters as the fallback language to use
> when installing portable software and its documentation on legacy
> systems, even if that documentation is written in mdoc(7).  So i
> don't think we can afford inventing new man(7) macros.  Using them
> would utterly destroy portability of the affected manuals.

No, because we have the long precedent of an-ext.tmac and its licensing.
Any man macros not declared in the Cretaceous can be defined inline in
man page sources.  Those who care about portability to legacy
environments can do this, and those who don't can leave them out.

> > Maybe \c it's like inline assembly in C.  Something best reserved to
> > experts under special circumstances, perhaps, but not a horrible hack.
>=20
> I guess we can agree on that, yes.

Sadly for our consensus, I'm finding evidence against this position in
existing man pages.  I've started a new thread for that.

> > At 2017-04-25T07:04:27+0200, Ingo Schwarze wrote:
>=20
> >> Well, and the partial one in mandoc, but mandoc follows groff in
> >> roff matters.
>=20
> > I need to look more deeply into that; I don't know how you'd implement
> > mandoc without implementing the bulk of *roff.
>=20
> I explained that during an international conference in 2011:
>=20
>   https://www.openbsd.org/papers/bsdcan11-mandoc-openbsd.html
>=20
> Pages 7, 12, 13, 14, 20, 24 are particularly relevant to your question.
>=20
> There are newer presentations, see http://mdocml.bsd.lv/press.html,
> in particular the recent overview
>=20
>   https://www.openbsd.org/papers/eurobsdcon2015-mandoc.pdf

Thanks!  I'll have a look at these.

> >>> If \c is documented badly and/or under-specified, let's determine its
> >>> precise semantics and document them clearly.
>=20
> >> I do suspect there is room for improvement, or at least clarification,
> >> in the \c specification, so working on that likely makes sense.
> >> But please, regard that as a work to help macro implementors,
> >> **not** end users!
>=20
> > Well, fine, let's proceed with that, then.  See end of this mail.
>=20
> I don't see any patch there...
> Did you forget to append it?

I haven't written it yet.  I don't feel I have a full understanding of
\c yet, just an intuitive "feel" which won't do for technical
documentation.

> > The groff community needs to be singing from the same hymnal when it
> > comes to recommended best practices.  If an-ext.tmac should be
> > deprecated and avoided, that needs to be formally established and
> > reflected in the software releases, maybe with a .tm warning in its
> > source.
>=20
> I agree that would be better.

I don't advocate this course of action; I'm reminding you that you
aren't the dictator of What Shall Be.  ;-)

> >>> In my experience, one can write an attractive manpage almost without
> >>> ever restoring to straight requests.
>=20
> >> And yet you suggest that authors should use the \c escape sequence,
> >> which quite definitely is a very low-level roff feature and not
> >> an element of the man(7) language at all.

In groff(7) and CSTR #54, \c is given precise parity with every other
escape.

[...]
> So you may be slightly overstating the case for character escapes.

I like mdoc's introduction of macros to replace character escapes in man
pages sources.  It's something I'd like to see in further development of
an-ext.tmac.  Sorry to madden you.  ;-)

> >> In the example you bring up, there is indeed no viable alternative to
> >> using \f font escapes.  You propose to trade the \f for \c.  I say \c
> >> is much worse than \f.  The syntax and semantics of \f is relatively
> >> easy to understand, and people writing man(7) are used to it, while \c
> >> is quite arcane.
>=20
> > Okay.  What alternatives can you propose for getting rid of \f in man
> > pages, short of migrating the universe to mdoc?
>=20
> I am not away of any way to do that without utterly breaking
> compatibility.  Unfortunately.  If you find one, great, but i
> doubt that any is possible.

As noted in the thread I just started, people have been using \c to
achieve this trick in several high-visibility man pages for many years.

> >> I admit that the en-ext macros minimally improve semantic capabilities
> >> of the man(7) language, but by so little that man(7) remains an
> >> almost exclusively presentational language even with man-ext.
> >> For that reason, i deem that using man-ext does more damage than
> >> good:  It doesn't substantially improve the language, but it
> >> does cause compat grief on old systems, which is exactly where
> >> the legacy man(7) language is still needed.  Bad tradeoff...
>=20
> > What I'm hearing is that you feel that man(7) is a lost cause:
> >=20
> > A.  It desparately needs improvement because of its presentational,
> >     rather than semantic, focus.
> > B.  Improvement will break portability.
> >=20
> > This basically amounts to doing nothing and letting man(7) die of its
> > own accord.
>=20
> Exactly.
>=20
> I'm a strong believer in incremental software development.  But
> there are exceptional cases where incremental improvements are not
> viable, in particular when the basic paradigm employed is busted
> and the language is a dense tangle of historically cemented layering
> violations.  The man(7) language is one of these cases.  Fortunately,
> it has been obsolete for 25 years now, and mdoc(7) is mature and
> readily available.  That GNU is the last major free operating system
> that did not adopt it yet does not preclude future progress.

Progress demands a path.  People are not rewriting all of their man(7)
pages in mdoc(7).  How do you propose to incentivize them?  Even if
someone funded a third-party mass-rewriting effort, you have no
guarantee that upstream authors and maintainers would accept the
transition.

You cannot strike the world with lightning and remold it your wishes.
What do you propose to do instead?

> Look at the last seven years.=20
>=20
> mdoc(7) and mandoc(1) are firmly established in all *BSD projects
> and in Minix 3.  Illumos (formerly OpenSolaris) switched to mdoc(7)
> in 2014.  Even in the GNU/Linux camp, there is some movement.  Debian
> has an official mandoc port since 2016, Arch Linux since 2010.
> Alpine Linux and Void Linux use mandoc by default (rather than the
> man-db + groff combo) since 2014.
>=20
> Changes take time.  I haven't given up on GNU just yet.

Nothing I aim to propose should prevent anyone from migrating to mdoc if
it's attractive to them.  I think some of the worst habits of man page
writers can be addressed with parts "a" and "b" of my proposal below,
but I don't expect to be able to semanticize man(7) pages to the degree
that mdoc(7) can.  The former has too much legacy and technical debt.

You want to scoop up the people who are willing to do a wholesale
rewrite of their man pages from man(7) to mdoc(7).

My aim is to improve the man(7) usage of people who _aren't_.

> > My recommendation is to take the momentum an-ext has, however small, and
> > press it:
> >=20
> > a.  Add more macros to fit semantic needs and the hiding of lower-level
> >     requests and escapes.
> > b.  Hand-hold users to the nth degree with examples and recommended best
> >     practices.
> > c.  Show people a mapping from groff's "extended" man macro package to
> >     mdoc, so that the route for switching over is clearly signposted.
>=20
> It seems to me that b) is fine, a) is very problematic because it
> severely harms portability,

You're making a testable assertion here.

1. Portability is not harmed if extended man macros are inlined in pages
   where portability to legacy systems is desired.
2. All *roff/man processors generate output.  These outputs can be
   prepared.

I am not interested in portability problems to platforms that do not
exist in the real world.

I am prepared to measure the impact of my proposals.

> and c) may or may not help to convince people.

Then I respectfully submit that mdoc(7) has a big problem appealing to
people.  That's going to seriously frustrate your initiative.

> I'm not sure the intermediate step of reinventing man(7)
> as a semantic language will make the transition easier.  Why should
> people have to learn a new man(7) language in between, in addition
> to the old man(7) and in addition to mdoc(7)?

Why should they have to learn the old man(7)?  Write in the new one.

> > I have my pet peeves as well; I don't like the shouty caps in arguments
> > to TH and SH.  That's information-losing and presentationy.
>=20
> Admitted, i don't like that either, but that (ugly) convention is
> uncontroversial: all existing documentation recommends it.

It's easy enough to kill off, especially for TH, since almost no man
pages in all of *nix-dom have non-ASCII characters in their names.

=2ESH is a little trickier since these strings are localizable.  However,
the domain of section titles in man pages is small, and in CJK languages
there aren't case distinctions anyway.

> What i was talking about was not "pet peeves", but unnecessary
> divergence from previously established standards.  The Linux man
> pages project was started in 1993.  By that time, groff already
> unambiguously documented most of the points i listed.  Yet man-pages(7)
> gratuitiously diverged in these - admittedly minor - respects.

Well, bold and brave Linux hackers weren't just going to take GNU's word
for anything.  :-|

> > Why not encourage people to have site-local files that redefine
> > these macros to do a ".tr aAbBcC" etc. if they insist on seeing
> > screaming caps?
>=20
> That old AT&T UNIX era convention could probably simply be dropped
> without replacement, but it doesn't seem high priority.

Yeah, I'd love to take it out back and shoot it but it's not near the
top of my list, either.

> > Is that official?  The last time I checked their list archives (a few
> > months ago), they were openly wondering "whither texinfo?" but hadn't
> > yet decided to abandon the project.
>=20
> https://lists.gnu.org/archive/html/groff/2014-02/msg00104.html

Thanks.  I see that this involves an Eric Raymond initiative.

> > 1.  Let's document, for the newbs and ourselves, what the heck "\c"
> >     really means.
>=20
> Sure, but i don't see the patch you promised.

See above.  I'm not yet prepared to write it.  But I will once I have
achieved sufficient understanding, if no one beats me to it.

> > 3.  Let's talk to the man-pages folks about harmonizing style
> >     recommendations.
>=20
> Sure, though that may be a slow process and some differences will
> likely remain.  The Linux man pages project is only one project,
> while the conventions documented in groff and mandoc documentation
> are used across four major projects, and the Linux man pages project
> is the one that deviated from established practices in the few minor
> points noticed in the first place (side note: OpenSolaris diverged
> even more).  Yet, i would understand the Linux man pages project
> would hesitate to edit all their pages for harmonization.

Somewhere in the man-pages suite there are words to the effect that they
expected a superior macro package to come along some day.  If I stumble
across it again I'll be sure and raise it to the group's attention.

Unless you can point me to evidence that the man-pages folks are
cussedly recalcitrant I'm going to assume they're as cooperative as any
mature development group.

> Such slight differences between different projects are also not
> fatal, even if they put a slight strain on casual readers in
> heterogenous environments.

Yes, and I'm not sure the section ordering problem is insuperable.
With a little tweak to the SH macro, for example, sections could be
pushed into diversions and then popped in a site-configurable order, for
example.

Okay, I said that just to give you a heart attack.  ;-)

Regards,
Branden

--m3ktnwuinshkgcio
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkAoFIACgkQ0Z6cfXEm
bc7LzhAAk8oGboEdxu1ZoVyqRHbAXUTGEscjMyz7j+OpHVJZDpGz1mX78YJCEt/w
F6oDrymsGsTAKNWQnU5LE+t9VbUH9oudZI4RgjQAVPMox/+mYIxwgSNEhlM+0KbI
4+pSwTj2gFpIkN3qOPLhrK2YW0jWYatBfR2IPjnwXgmq5HEAitMPAGYGg+V8ljg1
KZdpN9xC0bNIgQsRSCdTa8zG4uQsbmz/l9aYqado0OMw0Vwzsk6ujIl0vfzcw2zl
ZbZmV8GrbWez02qOnebde7Hr7Sduw7/y1BfCDWK3dFX+HXmfU86hBLZ4MAGSo0oL
M3dUkXO5IzZin0g8WA6BOnjspMiXbSgEGZImLRi2SOMU6r9ieRIiBNvrPmWHCw7X
y1Ok6/eW0DFIM2EjuLCj+kxiccuiauyqDgB6e1rD3j8TnIqlmCVf1TTk2YkPAgvo
+nrF0TuM0Er+10QLReeqhapXmsOKzrvW9EpXIdF8KsgsFcVlv+T5esTE3sw9AqOY
ndVxPIJPAFn9NSILeGMhpdM7riBntoMmbHpu3//WBuPNKH6RjIM9K+AqAyUg859A
SRHR3suw0fgxvB556FULv+BCbXs4vU9xZZxx5nWZdlzoP97MWFyaHwBiPbs55BX9
d72HxXqozes0nHjATAVgC+og48yKWeqL/C9TKJrVv+dzofFAL3Q=
=hTaQ
-----END PGP SIGNATURE-----

--m3ktnwuinshkgcio--


From MAILER-DAEMON Wed Apr 26 09:46:56 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3NHU-0001Ot-G1
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 09:46:56 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49451)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3NHR-0001LI-Dp
	for groff@gnu.org; Wed, 26 Apr 2017 09:46:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3NHM-0002Ad-BN
	for groff@gnu.org; Wed, 26 Apr 2017 09:46:53 -0400
Received: from mail-yw0-x22a.google.com ([2607:f8b0:4002:c05::22a]:35892)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3NHM-0002AK-5V
	for groff@gnu.org; Wed, 26 Apr 2017 09:46:48 -0400
Received: by mail-yw0-x22a.google.com with SMTP id l18so398581ywh.3
	for <groff@gnu.org>; Wed, 26 Apr 2017 06:46:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=ykIV4SS+o1pLYCcKyR5+FFNkcOftRq1MSZgEEgfR6kU=;
	b=sJbnJFbA9NUZjJ/s2xdcEWeneROcDlV3/Ul3I68c3gU9xYaisiqUovpf6a/pe/zv1f
	JZZ0y+MXcPEijVX3M8t4uQaelATDrx93dOQ59aGRoE+oIt/bb57MHPK45Mwrr/9wXNpL
	ZOzD28lEjFV5g3hZ4lOefU8cTEZbpYnql2lVuJG5i4HQYQGh9ypj0hzK/ei8vKj5fsL/
	I9bm99m5V2z0Op6p44ox+Rs7GYIQMIK4ieqR9jZz7qu+zfm2CGB28ezpQ+TXVENfjPfq
	sZzV7sS77G8X3ZDPyEE8grQ9UyjaYUSbKyuy160mFq4db8MYhBkJWPLjXxoouQv4rWIV
	ONKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=ykIV4SS+o1pLYCcKyR5+FFNkcOftRq1MSZgEEgfR6kU=;
	b=gWs10O/lRXxZYRPpHu5P8s1jwkZVyNl1zisCSA7ZerJHIrhCPBnkgPJeghVj4Tarvm
	9Oghii/2eCuY/J2NE6foHFe8TBFUix6+7STO1JCvuEQuofOf+Yj+S7zF33jzEooymEZm
	qN/RL1/XsA/NNOdaba0aqVKwg8dvoN/jlybuNBhsM4Y6XcdXdi1XNPCLYOtA0Tcma4Y1
	LDOREc1cNp1zjbe5CUjpva5SgsT06wQc3FHNdIzaykbvkIQ1/3at9YdzXv1E+v90Rm6Y
	2pxoNK7e3sPKzcO2CW6cRnPp5yFEYL9ZZckIMfcolspYcxdxvJlp9Z8PK/4H90OnyGZX
	+Rcw==
X-Gm-Message-State: AN3rC/5JCQklVJl9I+pBe5A2DsDo5TNblobQL8F8yMdeSM/qnQX2r0Im
	3mfpPFZKr4okbG/lVxRZKA==
X-Received: by 10.129.68.16 with SMTP id r16mr13161592ywa.168.1493214407090;
	Wed, 26 Apr 2017 06:46:47 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id m189sm95945ywd.68.2017.04.26.06.46.45
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 06:46:45 -0700 (PDT)
Date: Wed, 26 Apr 2017 09:46:43 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="mnhfextwoiev7qb7"
Content-Disposition: inline
In-Reply-To: <20170425181921.kz2kB%steffen@sdaoden.eu>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22a
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 13:46:54 -0000


--mnhfextwoiev7qb7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-25T20:19:21+0200, Steffen Nurpmeso wrote:
> Btw., if you want really clean man(7) you should point people to
> the really good guys, e.g., the plan9port manuals are a phantastic
> example of minimalistic and pure pages.

I'd love to, as I'm the sort who's still excited by Plan 9 (and its
successor Inferno), however, http://code.swtch.com/plan9port/ is a 404
for me.

Do you have an up-to-date link?

>  |> My recommendation is to take the momentum an-ext has, however small, =
and
>  |> press it:
>  |>=20
>  |> a.  Add more macros to fit semantic needs and the hiding of lower-lev=
el
>  |>     requests and escapes.
>  |> b.  Hand-hold users to the nth degree with examples and recommended b=
est
>  |>     practices.
>  |> c.  Show people a mapping from groff's "extended" man macro package to
>  |>     mdoc, so that the route for switching over is clearly signposted.
>  |
>  |It seems to me that b) is fine, a) is very problematic because it
>  |severely harms portability, and c) may or may not help to convince
>  |people.  I'm not sure the intermediate step of reinventing man(7)
>  |as a semantic language will make the transition easier.  Why should
>  |people have to learn a new man(7) language in between, in addition
>  |to the old man(7) and in addition to mdoc(7)?
>=20
> Even though still without voice, a) is in no way problematic if
> the original roff command set is used and no wild and funny
> programming sessions lead to mandoc incompatibilities.  b) is
> fantastic, c) i don't really believe in, mdoc has quite some
> similarities to brainfuck, things like
>=20
>   .Op : Ns Fl c Ar cc-addr Ns \&:
> or
>   .Fl S Ar var Ns Op Ns =3D Ns Ar value Ns
>=20
> are nice for teaching, but no one can really promote something
> like this, can he.

I have two gripes about mdoc:

1. The slavish devotion to two-letter names for things, which like the
   man macro package and the oldest parts of *roff itself, make it
   self-anti-documenting.  I may be tempting mockery by saying this from
   a vi session inside an xterm, but good Lord, we've gotten past the
   days of ASR 33 teletypes by now[1].  (That said, I'm sure this
   unfriendliness was imposed by the existing *roff implementations at
   the time mdoc was designed.)

2. Most of mdoc's own documentation is too technical, even in
   mdoc.samples.  I find the glib and frequent usage of the term
   "domains" off-putting and inaccessible, and I don't think I'm
   unusually stupid.  (Pauses for a beat.)

But, not to pound on Ingo's beloved too much, from what I understand of
mdoc's design, I find it much, much better considered than man(7).  It
clearly benefited from having a large corpus of existing man pages to
consider, so it knew better than man(7) did what sort of problems it was
going to have to solve.

> And sometimes things have to be adjusted a bit so that things can
> overall stay the same.  The roff system is a fantastic
> achievement, and if at all possible i will use it until the day
> i die.  I am looking forward for my thing.

Agreed.  Any proposals I make are with an eye toward making the roff
system better, not worse.  That could go without saying--but I guess I
should emphasize that I'm here not to bury groff, but to praise it.

Unlike, I think, [2].

Regards,
Branden

[1] Somebody confirm for me that these were run with _remote echo_ at
    110 baud, so that every keystroke was an adventure in
    anticipation...
[2] https://lists.gnu.org/archive/html/groff/2014-02/msg00104.html

--mnhfextwoiev7qb7
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkApLgACgkQ0Z6cfXEm
bc554Q//WMi98b+4pk3agZhe6cRWUJWE8Ljb1Mb8GRdqflHHJ0t+Gb+KczmyZ5oU
KbUab9M9BjSJy/qdf2CVkEVaOlO5hbOUechhi9hXXt3dgkWuWLKtl6hrc1xHAKt7
Rfy9nWZ2LH6+hpjT0lAr0pOvMfZYM84RG724tR6wBp8p7oakpOEG1WKKSstcHSOp
5YI+qQduw0hCnyLqxqXBqCgyf25t3RDeIPknah9QThoOQUU76W1aUHwCV+I4uFxc
na08yJU2h8EzGVBQiCZa1g3RO5+LS5IaENCd++wMGmyDZRG5O+jIewV/g09i6b2v
ktGNtpGurikeHsPxgDXZgU62u8P8rd4P6jdmP05AhGVJyj9oHYjWz9xDXYvA74+V
AT6l3xOTeDsfjVUorFv2nHkIEHHMBHExtIBsbjna3Te/w5lKo44VL+VR9dHEEL4T
E2NmcQGou1X2Pi2WKsg8R34ttb+j/TUhKjvMKdMKDHvnUG6ETbJSSwZIhBiPSCzH
gUXL/m+Yk2kNJQmLzG17OVWUIjLLaYZsCZtSMJgmebMTqYkwn2Ltbhg6RBvZSj0l
J30MaLOcJ9dSJHCgYg94fDLZvVqRYHCCrE/CtmhTWWIl69cRRpymwDAKOr+QjYpS
HDn1hyYWgSGntlV+lDvzahQq3LsUbwPKYTgX6UeTdU79Ct1J7a8=
=wdV/
-----END PGP SIGNATURE-----

--mnhfextwoiev7qb7--


From MAILER-DAEMON Wed Apr 26 10:03:48 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3NXn-0005Gy-Vq
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 10:03:48 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54703)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d3NXi-0005Cp-6y
	for groff@gnu.org; Wed, 26 Apr 2017 10:03:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d3NXd-0000yF-8O
	for groff@gnu.org; Wed, 26 Apr 2017 10:03:42 -0400
Received: from relay01.pair.com ([209.68.5.15]:42192)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d3NXd-0000xj-3m
	for groff@gnu.org; Wed, 26 Apr 2017 10:03:37 -0400
Received: from orac.inputplus.co.uk (212.162.115.87.dyn.plus.net
	[87.115.162.212])
	by relay01.pair.com (Postfix) with ESMTP id 8AE70D010C7
	for <groff@gnu.org>; Wed, 26 Apr 2017 10:03:34 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id B93782038D
	for <groff@gnu.org>; Wed, 26 Apr 2017 15:03:33 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
Date: Wed, 26 Apr 2017 15:03:33 +0100
Message-Id: <20170426140333.B93782038D@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:03:46 -0000

Hi Branden,

> http://code.swtch.com/plan9port/ is a 404 for me.
> Do you have an up-to-date link?

https://github.com/9fans/plan9port#readme

Cheers, Ralph.


From MAILER-DAEMON Wed Apr 26 10:09:22 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3NdB-0007p2-UO
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 10:09:21 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55982)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Nd9-0007ns-H9
	for groff@gnu.org; Wed, 26 Apr 2017 10:09:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Nd0-00033y-22
	for groff@gnu.org; Wed, 26 Apr 2017 10:09:19 -0400
Received: from mail-yb0-x236.google.com ([2607:f8b0:4002:c09::236]:33448)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3Ncz-00033b-Tv
	for groff@gnu.org; Wed, 26 Apr 2017 10:09:09 -0400
Received: by mail-yb0-x236.google.com with SMTP id 11so430349yby.0
	for <groff@gnu.org>; Wed, 26 Apr 2017 07:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=ZEchslB9PlxFQzPCysCWy0QrySo7MSYWU96C0YKp3I8=;
	b=hb43frvOtLSanIvN3d3EuxdDhPoH+ilgnbVkQm+Pz3nNorTqQSvvHx6Ib6g0huKUIy
	ubwiep12Hsh9nCBOBmXE0vcdg0EDpmtDmE9SRvCJdje3tgFrQwNRmDjLTbRVvExGutZN
	nL71VhX2NrqapGz+PoDCGkbTBtsC9nSc81Jvqb2wpiMU7go1RouIR0EU3V0CnDzItxY7
	5pGEL+HrqHoQvNsx2waXzSDDnZqTduDUO6vipabrRJL1EMuwSu5zr0XB7XclBv04kh3u
	Tk6OYCpMV01nbRYh1KacK8Dhnwb5/Zx6D2MIyy0hc/hZbsj9aFk0YjSRPAJPeQ2xjltJ
	bjBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=ZEchslB9PlxFQzPCysCWy0QrySo7MSYWU96C0YKp3I8=;
	b=NOxk1PbQffNomBGr32BvqMUqBz4nxp5SnpDGIJj14ePk1/Gn0JKlNHMol8ehCENerq
	L9N0Jkm46zMdgHtxOWjT+2UJbshOpFRrIOn5hUbGx0mD0BPzhbvKTYffjeBCUCClpY6O
	BpDIQNKKTx9X8t5bHFUVjMOg5JKXZsBoLd6OKmUKkjXEj7Md2L9Wb9HgCSXavKwqxzVf
	ctJb5cIhsd4OusYj9XOPCGcvWwIwP+QV9CmwtQVcgBNdpRH3DESr2/WfS1Ox4yyPd54z
	GNOUye5urCKsGphCdgMlHOSb9IQ/8B/1CrHX2oAmL1YzTY7lp78S87GgBGq33Z8xyOj0
	oWpw==
X-Gm-Message-State: AN3rC/7xdS4DcljVOJunv4O7Ti4ZenIkDTutilVVV3WOppCWSuztv/82
	hteLB/6ihKeqv5exYcXVgA==
X-Received: by 10.37.38.74 with SMTP id m71mr13427105ybm.60.1493215748950;
	Wed, 26 Apr 2017 07:09:08 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	x200sm132566ywx.72.2017.04.26.07.09.07 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 07:09:07 -0700 (PDT)
Date: Wed, 26 Apr 2017 10:09:05 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426140903.6shu7liukn2ge2jc@crack.deadbeast.net>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170426140333.B93782038D@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="trzapkmd6ovm6gh7"
Content-Disposition: inline
In-Reply-To: <20170426140333.B93782038D@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::236
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:09:20 -0000


--trzapkmd6ovm6gh7
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-26T15:03:33+0100, Ralph Corderoy wrote:
> Hi Branden,
>=20
> > http://code.swtch.com/plan9port/ is a 404 for me.
> > Do you have an up-to-date link?
>=20
> https://github.com/9fans/plan9port#readme

Gracias, se=F1or!  Some days I need someone to JFGTFM.  ;-)

Regards,
Branden

--trzapkmd6ovm6gh7
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkAqfIACgkQ0Z6cfXEm
bc53bhAAhJLuebQ9RwgMa59LyMdfZv6SkHf9G3zjlkBM4g5YqxDYHn8k0Z8hHkTG
Ej8fMiwZG1Fgv8mLlXwPGRwoTTLwpOdbb8JPbNpXEDSy2zA4j4IxiVuvvdyI62wi
h/CdAz7AE5+7xpwmX73F/lThIwkMqB21bhxf1Yy7DMT+iSw3G2O3BFTAzvXGuecT
NfP/F4SpE4owtQbzskR6kCk6jLfq1LM8grOJ84SUQEFttjAIxmOsOQMNel0/Gf3S
8yQxSWGRwN7gmsJtce+RswElVgHB0j81c5Ijv51DMSnrq2+OFDrko75wStkM2srS
chxMe7yvflEYpN1XBfS5/ktNQxgXDrPYSRbNAn6ZnncjqGdhFkke5adXFJ8wpA9v
VmCoCwEPdIy8RUmi+ztySVznd2wcxSgDOZipe82FpHWq8yfEfquEjFYBpucz0Y0u
J+5y2ZeFPh2RhG22m9Lt6n5qTj9jZAlMDZmaHDoGS9zvDizwzkG6nwvgDyhkpi4o
rIml4vMXWwCwH40zhStlxeWQsuYRVh5ZsLWYh5iH1r66ovmQmmUBrYlmbcjA3fVO
nh1XH0lL4CvEiP8wtDAwbe3MnUsuP9ta3kCfHUSiC6NA5/qIpta9V7xhah5Iomqw
pXR6q+WZGmR/pidaXttiz4pzezKhaYXP6pOB7OK6XjtsdFwDROc=
=RDso
-----END PGP SIGNATURE-----

--trzapkmd6ovm6gh7--


From MAILER-DAEMON Wed Apr 26 10:13:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3NhK-0001XK-Cf
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 10:13:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56934)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lm@bitkeeper.com>) id 1d3NhC-0001Rx-Lw
	for groff@gnu.org; Wed, 26 Apr 2017 10:13:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lm@bitkeeper.com>) id 1d3Nh8-0004et-Ko
	for groff@gnu.org; Wed, 26 Apr 2017 10:13:30 -0400
Received: from smtp121.iad3a.emailsrvr.com ([173.203.187.121]:40144)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <lm@bitkeeper.com>) id 1d3Nh8-0004eg-GJ
	for groff@gnu.org; Wed, 26 Apr 2017 10:13:26 -0400
Received: from smtp32.relay.iad3a.emailsrvr.com (localhost [127.0.0.1])
	by smtp32.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id
	C595B5A0E; Wed, 26 Apr 2017 10:13:23 -0400 (EDT)
Received: from app25.wa-webapps.iad3a (relay-webapps.rsapps.net
	[172.27.255.140])
	by smtp32.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id
	B8DA959DD; Wed, 26 Apr 2017 10:13:23 -0400 (EDT)
X-Sender-Id: lm@bitkeeper.com
Received: from app25.wa-webapps.iad3a (relay-webapps.rsapps.net
	[172.27.255.140]) by 0.0.0.0:25 (trex/5.7.12);
	Wed, 26 Apr 2017 10:13:23 -0400
Received: from bitkeeper.com (localhost [127.0.0.1])
	by app25.wa-webapps.iad3a (Postfix) with ESMTP id 9E696E0039;
	Wed, 26 Apr 2017 10:13:23 -0400 (EDT)
Received: by apps.rackspace.com
	(Authenticated sender: lm@bitkeeper.com, from: lm@bitkeeper.com) 
	with HTTP; Wed, 26 Apr 2017 07:13:23 -0700 (PDT)
X-Auth-ID: lm@bitkeeper.com
Date: Wed, 26 Apr 2017 07:13:23 -0700 (PDT)
From: "lm@bitkeeper.com" <lm@bitkeeper.com>
To: "Doug McIlroy" <doug@cs.dartmouth.edu>
Cc: groff@gnu.org
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-Type: plain
In-Reply-To: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
Message-ID: <1493216003.646515482@apps.rackspace.com>
X-Mailer: webmail/12.7.11-RC
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 173.203.187.121
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:13:37 -0000

The BitKeeper man page macros use this sort of construct a lot.=0A=0A-----O=
riginal Message-----=0AFrom: "Doug McIlroy" <doug@cs.dartmouth.edu>=0ASent:=
 Tuesday, April 25, 2017 4:00pm=0ATo: groff@gnu.org=0ASubject: Re: [Groff] =
Nesting font macros in man pages=0A=0A> .TP=0A> .B \-scale \c=0A> .IR xfac =
[, yfac ]=0A=0AVery clever. I wish I'd thought of it when I was editing=0At=
he v7 manual. Then it would have become a standard idiom.=0AHas nobody trie=
d this during the nearly 40 years since?=0A=0ADoug=0A=0A



From MAILER-DAEMON Wed Apr 26 10:50:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3OH9-0006PT-Rp
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 10:50:39 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38840)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d3OH6-0006N4-Py
	for groff@gnu.org; Wed, 26 Apr 2017 10:50:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d3OH0-0003lz-NQ
	for groff@gnu.org; Wed, 26 Apr 2017 10:50:36 -0400
Received: from relay01.pair.com ([209.68.5.15]:44634)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d3OH0-0003lM-HE
	for groff@gnu.org; Wed, 26 Apr 2017 10:50:30 -0400
Received: from orac.inputplus.co.uk (212.162.115.87.dyn.plus.net
	[87.115.162.212])
	by relay01.pair.com (Postfix) with ESMTP id B7D34D00B35
	for <groff@gnu.org>; Wed, 26 Apr 2017 10:50:27 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id E9BD12038D
	for <groff@gnu.org>; Wed, 26 Apr 2017 15:50:26 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170424143915.GA47874@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
Date: Wed, 26 Apr 2017 15:50:26 +0100
Message-Id: <20170426145026.E9BD12038D@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:50:38 -0000

Hi,

Ingo wrote:
> Besides, writing manual pages absolutely needs to be simple.  Manual
> pages must be written by programmers who may not know typography and
> who are not prepared to, and shouldn't be required to, acquire
> specialized knowledge just to write the required manuals together with
> their code.

I disagree here, and thus with much of the resulting threads between
Ingo and Brendan.

Writing a man page is writing troff using the -man macros.  Always was,
always will be.  It's not some non-troff mark-up language that happens
to use troff as a back-end.  One must be prepared to understand it's not
just plain text and commands on lines starting with `.':

  =E2=80=A2 That the plain text is significant too, e.g.\& putting that `=
\&'
    after the full stop so the inter-word gap doesn't become
    end-of-sentence if word-wrap should split the line.

  =E2=80=A2 .IR being is just a shorthand for `\f' and `\^' that can be d=
one
    manually when needed, e.g. `.TH'.

  =E2=80=A2 And, yes, what `\c' does, and to use it when required;  the c=
ommon
    case can easily be copied from other man pages.

Fortunately, programmers are the kind of folk that will appreciate the
finesse that can be expressed if they understand the cause, and that
includes attractive PDF output.  I think good PDF representation is a
handy test of whether the man page has flaws, and isn't second-class to
UTF-8 on a TTY.

Note, I'm not talking about writing an mdoc page.  Like others, I find
the macro names too many, too confusing, the result too noisy with its
nested macros, and have never persevered.  That may be my fault and I
should try again.  :-)

> INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
> already now because the three main implementations (including groff)
> don't do that in the quite important -Tutf8 device.

This is because of the bodge to map `-' onto ASCII 45, by Debian
originally, was it?  Rather than stand firm and map just `\-' and tell
complainants that the upstream man page needed fixing.

> INSIDE manual pages (both -man and -mdoc), let's change - and \- to
> always map to U+002D HYPHEN-MINUS for all devices and let's tell
> people to simply use - for HYPHEN-MINUS and stop worrying.

But PDFs then look awful.

A new `\(hm' isn't a go-er for the same reason depending on .itc in .TH,
or a new .TH variant, aren't worthwhile;  man pages have to format on
old systems that haven't these fangled additions.  And we've managed OK
without.

an-ext.tmac I've never used, just read it.  Is it mentioned in a man
page?  I even checked `info groff | cat' and didn't spot it.  :-)  I'm
not keen on embedding it at the start of every man page in a project,
even if they're built from a source just to achieve that.  What's the
alternative?  `.so ../man1/foo-an-ext.tmac' and release it to sit
alongside the foo project's other man{1,8} pages.  It obviously mustn't
appear as a page itself in indexes, etc.

Cheers, Ralph.


From MAILER-DAEMON Wed Apr 26 10:55:11 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3OLX-0001I2-Ey
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 10:55:11 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40222)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3OLV-0001GV-Lv
	for groff@gnu.org; Wed, 26 Apr 2017 10:55:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3OLQ-0005rD-2D
	for groff@gnu.org; Wed, 26 Apr 2017 10:55:09 -0400
Received: from mail-yw0-x229.google.com ([2607:f8b0:4002:c05::229]:35313)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3OLP-0005qu-Tt
	for groff@gnu.org; Wed, 26 Apr 2017 10:55:04 -0400
Received: by mail-yw0-x229.google.com with SMTP id u70so1536981ywe.2
	for <groff@gnu.org>; Wed, 26 Apr 2017 07:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=nwjNHQCCnb2IFA/boT8iXx45Vv+8ulEmZfEEer5TxG4=;
	b=rcaP3fjoE9rYEHcVGc4CkQxOrkmzgyLiWiSY+Bgyl8/S/bSg0e4T6O0bKCOci+SUmm
	Ls09BKxJw3PyesshGQDvPFfPZa1AG81ukQz87fu9629iFuKCxw4i2UG0qdZ8puAJM7LV
	cLbGJageBUFAyKBh6O3LozA7RH00t4LSCz9Uwdihwb1u1AhPf+fIbt54xDjsdKEUYl8T
	sYomRZJ5BeoTUJp/r5FzhGvbRoQU3rdiPWL1QikbA+Eo2Le7+VnjgkTpxvLsMzdwmsxY
	RZKBOwfmVlQJLcSPdGYIoJOEI0jO57M4GU1wrxZ0xMFWS5+onme6udQ6UhMQhkBS4sBu
	V2jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=nwjNHQCCnb2IFA/boT8iXx45Vv+8ulEmZfEEer5TxG4=;
	b=Lw1fGAM19kIuMMwbhwN0TKAOjjbDEr84dBjDDKwH65twDuFlhi9epJTpA78ZL/Lntk
	alEkimPk0eovskt+cBZGoIdEm1YFPisSLg1w0KlEr//KxeQC0FXGt4jzozBMbaTgNcja
	vV9MbAd8obF80w6lTeUk211g45ZTIVewvy0PuCSvVgYy5MGj4BoMUIXUzHTchByJ7gM1
	/nHxpzSPEP1tl3e/gpe+JOUexmdnzJKy4sCUnU8AwSxyenSLzNdpRfGxhFAl/oGyCvYC
	Oi63YM3sZE+6dF2vdStfNB4H9ijEQbpzpALnAOnk9BTwepqEe+DybI5VkGF06gBIFgpR
	Ls0w==
X-Gm-Message-State: AN3rC/5kINrN4P6sg5I+UPOPu/Wt9PXaiwV/O/yT2NUScjPULFCLAGCr
	ifdRAosZypxMVy5qumjIkw==
X-Received: by 10.129.104.195 with SMTP id d186mr139330ywc.244.1493218502858; 
	Wed, 26 Apr 2017 07:55:02 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id a83sm170829ywe.65.2017.04.26.07.55.01
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 07:55:01 -0700 (PDT)
Date: Wed, 26 Apr 2017 10:54:59 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426145457.kn4ncc3233pdr234@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170426132755.bywvghd2onf4acjt@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="mkb4zh5cr6uxklt5"
Content-Disposition: inline
In-Reply-To: <20170426132755.bywvghd2onf4acjt@crack.deadbeast.net>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::229
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:55:10 -0000


--mkb4zh5cr6uxklt5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-26T09:27:56-0400, G. Branden Robinson wrote:
> > It seems to me that b) is fine, a) is very problematic because it
> > severely harms portability,
>=20
> You're making a testable assertion here.
>=20
> 1. Portability is not harmed if extended man macros are inlined in pages
>    where portability to legacy systems is desired.
> 2. All *roff/man processors generate output.  These outputs can be
>    prepared.

s/pre/com/

Rather regrettable thinko, there.

> I am not interested in portability problems to platforms that do not
> exist in the real world.
>=20
> I am prepared to measure the impact of my proposals.

Regards,
Branden

--mkb4zh5cr6uxklt5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkAtK8ACgkQ0Z6cfXEm
bc65QRAAkwjBDeSmv5aJak30Ajo/jlBJOV2EpLVTbImkR0lNBKByp1GxveftH/MV
Xx2psnJ5J6AFI2t2jPhuRhXsOX3JIAUCsa+80yq9DfJ0Fjd8kYbU2QYiGPEZaz96
hnAvqO+gictZvYRONfUeWQFlzln8cqzlCbkYRA7p7+uEFRwkumgB3mli/UhViBF6
zvMJNiyUmR12s7Le9R5j8HugRODrjpF92FdB2OY52AByiUc/dKYNvU/ys6e7ZJn0
CZLN+uGKYQ/mEK093tRGd9Mc/FWvp9bN+daFHjXe7qGELbL82H89JmpFOcbt6VJQ
ErWP2QoUYVMlG2XerVTt126En1nyk4WstRl/gYsALN5aFtZgLWQrpBk+N2rZ1pPF
CtzTSGmIxbSl/BZCnr+5aBaLPCCkAIfXNdU1uSeJa+7qakkAo/PkmVCFWOApGtqk
+uOE7NZhZWy3lsZ09r1YEOjmxo/lU17iA0cUrUGeTI5wHsnE+uNek5ssojdcUzpB
dcG7hNTvR+urTox7Qmor6Kz/VSEsImo3iXO4ExFqFofGRu1KNkuF4A1BOA8l3rmX
K6VKe7E+VGEMTESJi6UcYef+4fVQJ3e/yfEClYx4CN8ndeuXz8FPGyx63taOSvZN
uBgnbVRPfSJrA2mn8wEQRmwzeNewvI3Uc8ehAGUSWGW6U7RvbTs=
=mm6E
-----END PGP SIGNATURE-----

--mkb4zh5cr6uxklt5--


From MAILER-DAEMON Wed Apr 26 11:54:33 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3PGz-0003Ea-Fe
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 11:54:33 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54097)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3PGw-0003ET-4m
	for groff@gnu.org; Wed, 26 Apr 2017 11:54:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3PGs-0000jW-6H
	for groff@gnu.org; Wed, 26 Apr 2017 11:54:30 -0400
Received: from mail-yw0-x22b.google.com ([2607:f8b0:4002:c05::22b]:33534)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3PGr-0000jF-Vs
	for groff@gnu.org; Wed, 26 Apr 2017 11:54:26 -0400
Received: by mail-yw0-x22b.google.com with SMTP id 203so2539035ywe.0
	for <groff@gnu.org>; Wed, 26 Apr 2017 08:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=suUh14jN9xrLQJpLhSS3UdS4PyfwMLDTu8Ty7pUiBMs=;
	b=eXcunmBIH3w4rmNek951paNL1b2YXYunKuVjkHVI4klV2FGvmBh08JMsz4sFcIOk/U
	y15avPK3zRssLNjz3LrfkoHCdGJR08WxH7HerDoLMO4PlFn5UX6qQZeu+NY58Bo+7zA4
	P5bWPrKOLktYnAxO8N5iK9beVZgbraRf3LgQ95/RCEX66XqdkRn5Qe/XnXue1ukJitjf
	LtIHU23kFLBzLt0ikmmL5V/Flmmhab2WDC8MLFWukxA3Z8QHflmT+2pcxB8ve76B3deP
	OTK2vQN41S6/wjzvXg9UchlwaZXwVLYGKZOGwrcrTt6LfuVswlsakuxSKdX5NTMKFLoD
	p/hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=suUh14jN9xrLQJpLhSS3UdS4PyfwMLDTu8Ty7pUiBMs=;
	b=tS5vc5jeFguMBUinwbPuPSNRjFQtRC+iYUdr6P/8YRc/RJYBNg2ryOb/7vn70AJ91Y
	yEKICNjSHKr9Ep7ZLjwe3tTwcxOA1IZ52oT4CB4IauB5poZfgdoUUDJA4hiduKwt94Bk
	WIK4WgonZROgvzxeCCA54VkXxs4b7bgz7N8qAXLzOxtOtda2lim3ySWMfvYRrlgfnHM7
	Wivbz4QkxbsPKcsrJIgsdj46IHE5FtmDJdGj/T6xze3ccN0Zh/ny/O0wTYkCUm8o7/5m
	41rhfbs1ew98aM1/MeBk+X4HI9hSiZCNNTrtVIgS+RSs/PFhRk9UPYHq1tQO7QlaWo/A
	+T8g==
X-Gm-Message-State: AN3rC/73bfIIukJwrR3u5fpziLvbbhjpCyVQzExomGzZ0hJQR2sjX8pX
	BQ6R2mdK/uBdYrsF5WvrwQ==
X-Received: by 10.13.209.193 with SMTP id t184mr362768ywd.293.1493222064408;
	Wed, 26 Apr 2017 08:54:24 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	f130sm241593ywc.41.2017.04.26.08.54.22 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 08:54:23 -0700 (PDT)
Date: Wed, 26 Apr 2017 11:54:21 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="sv5az7to4ogrijlp"
Content-Disposition: inline
In-Reply-To: <20170426145026.E9BD12038D@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22b
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 15:54:32 -0000


--sv5az7to4ogrijlp
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote:
> Writing a man page is writing troff using the -man macros.  Always was,
> always will be.  It's not some non-troff mark-up language that happens
> to use troff as a back-end.  One must be prepared to understand it's not
> just plain text and commands on lines starting with `.':

You may be right, but then it's long past time we talked to the
man-pages folks about about man(7), and revisited the discussion in
groff_man(7).

Here's groff_man(7):

PORTABILITY AND TROFF REQUESTS
       Since the man macros consist of groups of groff requests, one  can, =
 in
       principle, supplement the functionality of the man macros with indiv=
id=E2=80=90
       ual groff requests where necessary.  See the groff  info  pages  for=
  a
       complete reference of all requests.

       Note,  however,  that  using  raw troff requests is likely to make y=
our
       page render poorly on the (increasingly common) class of  viewers  t=
hat
       render  it  to  HTML.   Troff  requests make implicit assumptions ab=
out
       things like character and page sizes that may break in an HTML envir=
on=E2=80=90
       ment; also, many of these viewers don't interpret the full troff voc=
ab=E2=80=90
       ulary, a problem that can lead to portions of your text being  silen=
tly
       dropped.

       For  portability  to  modern  viewers,  it  is  best to write your p=
age
       entirely in the requests described on this page.  Further, it  is  b=
est
       to  completely  avoid  those  we have described as =E2=80=98presenta=
tion=E2=80=90level=E2=80=99
       (.HP, .PD, and .DT).

       The macros we  have  described  as  extensions  (.EX/.EE,  .SY/.OP/.=
YS,
       .UR/.UE,  and .MT/.ME) should be used with caution, as they may not =
yet
       be built in to some viewer that is important to your audience.   If =
 in
       doubt, copy the implementation onto your page.

Note that these macros that this page proclaims to be "portable" include
_all_ of the ones from an-ext.tmac, which you passed over quickly in
your comments below.

And here's man(7) from Linux man-pages:

   Safe subset
       Although technically man is a troff macro package, in reality  a  la=
rge
       number  of  other tools process man page files that don't implement =
all
       of troff's abilities.  Thus, it's best to avoid some  of  troff's  m=
ore
       exotic  abilities  where  possible  to permit these other tools to w=
ork
       correctly.  Avoid using the various troff preprocessors (if  you  mu=
st,
       go  ahead and use tbl(1), but try to use the IP and TP commands inst=
ead
       for two=E2=80=90column tables).  Avoid using  computations;  most  o=
ther  tools
       can't  process them.  Use simple commands that are easy to translate=
 to
       other formats.  The following troff macros  are  believed  to  be  s=
afe
       (though  in many cases they will be ignored by translators): \", ., =
ad,
       bp, br, ce, de, ds, el, ie, if, fi, ft, hy, ig, in, na, ne, nf, nh, =
ps,
       so, sp, ti, tr.

       You may also use many troff escape sequences (those sequences beginn=
ing
       with \).  When you need to include the backslash  character  as  nor=
mal
       text, use \e.  Other sequences you may use, where x or xx are any ch=
ar=E2=80=90
       acters and N is any digit, include: \', \`, \=E2=80=90, \., \", \%, =
\*x, \*(xx,
       \(xx,  \$N,  \nx,  \n(xx,  \fx,  and  \f(xx.   Avoid  using  the esc=
ape
       sequences for drawing graphics.

       Do not use the optional parameter for bp (break page).  Use only  po=
si=E2=80=90
       tive  values  for  sp (vertical space).  Don't define a macro (de) w=
ith
       the same name as a macro in this or the mdoc macro package with a  d=
if=E2=80=90
       ferent  meaning;  it's  likely that such redefinitions will be ignor=
ed.
       Every positive indent (in) should be paired with  a  matching  negat=
ive
       indent  (although  you  should  be using the RS and RE macros instea=
d).
       The condition test (if,ie) should only have 't' or 'n'  as  the  con=
di=E2=80=90
       tion.  Only translations (tr) that can be ignored should be used.  F=
ont
       changes (ft and the \f escape sequence) should only have the values =
 1,
       2,  3,  4,  R,  I, B, P, or CW (the ft command may also have no para=
me=E2=80=90
       ters).

       If you use capabilities beyond these, check the  results  carefully =
 on
       several tools.  Once you've confirmed that the additional capability=
 is
       safe, let the maintainer of this document know about the  safe  comm=
and
       or sequence that should be added to this list.

I'm sorry for the lengthy quotes, but we're simply not telling man macro
package users what you think we are, and we haven't been for many years.

It's well past time we decided if any of the non-*roff man page
"parsers" have shown any merit.  To most people, HTML is not as sexy now
as it was in 1997--thank God.

>   =E2=80=A2 That the plain text is significant too, e.g.\& putting that `=
\&'
>     after the full stop so the inter-word gap doesn't become
>     end-of-sentence if word-wrap should split the line.
>=20
>   =E2=80=A2 .IR being is just a shorthand for `\f' and `\^' that can be d=
one
>     manually when needed, e.g. `.TH'.

FYI, .IR does not give you this "italic correction" in groff 1.22.3:

	.de1 IR
	.  if \\n[.$] \{\
	.    ds an-result \&\f[I]\\$1\f[R]\"
	.    shift
	.    while (\\n[.$] >=3D 2) \{\
	.      as an-result \/\\$1\f[I]\,\\$2\f[R]\"
	.      shift 2
	.    \}
	.    if \\n[.$] .as an-result \/\\$1\"
	\\*[an-result]
	.    ft R
	.  \}
	..

>   =E2=80=A2 And, yes, what `\c' does, and to use it when required;  the c=
ommon
>     case can easily be copied from other man pages.

Yes.  I'm pretty enthused by what I've found.  \c does indeed appear to
be a long-used, time-tested way of avoiding \f font escapes in favor of
man font-changing macros.  I do so love killing off '\f's.

> Fortunately, programmers are the kind of folk that will appreciate the
> finesse that can be expressed if they understand the cause, and that
> includes attractive PDF output.  I think good PDF representation is a
> handy test of whether the man page has flaws, and isn't second-class to
> UTF-8 on a TTY.

I entirely agree, and when I was recently modernizing about 112kB of man
page sources, utf8 in an xterm with a good font and PDF were the two
output formats I ensured looked good.  I spot-checked HTML output for
any egregious ugliness, but regarded it as second-class to the other
two, since as I understand it, grohtml is a work in (arrested?)
progress.

> Note, I'm not talking about writing an mdoc page.  Like others, I find
> the macro names too many, too confusing, the result too noisy with its
> nested macros, and have never persevered.  That may be my fault and I
> should try again.  :-)

I think that it, too, is salvageable with documentation written by
someone who _doesn't_ know its internals inside out, and perhaps with a
nice fat front-end of nothing but .als requests to supply macro names
comprehensible by English-speaking humans.  ;-)

> > INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
> > already now because the three main implementations (including groff)
> > don't do that in the quite important -Tutf8 device.
>=20
> This is because of the bodge to map `-' onto ASCII 45, by Debian
> originally, was it?  Rather than stand firm and map just `\-' and tell
> complainants that the upstream man page needed fixing.

I was around at the time that decision was taken and IIRC was one of the
people talking to Colin Watson about it.  It was done because there were
so _damned many_ pages frustrating our users with cut-and-paste
problems.  We stuck that bodge in /etc/groff/man.local and documented
exactly what and why it was done so that experts could reverse it.

$ cat -n /etc/groff/man.local | sed -n '17,24p'
    17  .  \" Debian: Strictly, "-" is a hyphen while "\-" is a minus sign,=
 and the
    18  .  \" former may not always be rendered in the form expected for th=
ings like
    19  .  \" command-line options.  Uncomment this if you want to make sur=
e that
    20  .  \" manual pages you're writing are clear of this problem.
    21  .  \" UNCOMMENTED: branden, 2017-04-08
    22  .  if '\*[.T]'utf8' \
    23  .    char - \[hy]
    24  .

Also, the linitan(1) tool that is a huge part of Debian package QA
checks man pages for many problems, and I think this is one of them.
Debian _is_ trying to bring about the day when that bodge can be
reversed.  As with so many things, human effort is often in short supply
on the packaging and/or upstream end, and frankly the ergonomics of \-
work against us.  All of our instincts tell us to document our Unix
commands the same way we type them.  I don't support the recommendation
immediately below, but I am deeply sympathetic to the motivation behind
it.

> > INSIDE manual pages (both -man and -mdoc), let's change - and \- to
> > always map to U+002D HYPHEN-MINUS for all devices and let's tell
> > people to simply use - for HYPHEN-MINUS and stop worrying.
>=20
> But PDFs then look awful.
>=20
> A new `\(hm' isn't a go-er for the same reason depending on .itc in .TH,
> or a new .TH variant, aren't worthwhile;  man pages have to format on
> old systems that haven't these fangled additions.  And we've managed OK
> without.

I think you mean .TP, right?

I find these two issues much more distinct that you do.  We can
reasonably expect .TP to be a recognized macro name with mostly
predictable semantics on _any_ environment that can render man pages.

\hm would be a brand-new thing, and to be portable would require
conditional definition in man pages targeting old systems.  Except I
don't think we can define new character escapes[2], just strings.  Well,
that's what we have conditionals and register tests for, I guess.

I'm still not dissuaded from my .TP/.itc hack.  As I noted in the first
place, the impact on groff-based systems is practically zero; the only
man page it seems to regress is ksh93, and I'm not sure that's my hack's
fault since the usage that regresses _isn't even in_ a .TP macro.  There
may be an underlying bug.  In any case, I do need see if my hack
regresses existing, reasonably-well-formed man pages when they're
rendered with other implementations.  That's on the to-do list.

As I said to Ingo, I'm only worried about doing damage to
actually-existing *roff implementations, not some that might exist in an
alternate universe under an alternative interpretation of the
nowhere-formally-standardized *roff language.

> an-ext.tmac I've never used, just read it.  Is it mentioned in a man
> page?  I even checked `info groff | cat' and didn't spot it.  :-)

On groff-using systems, it's everywhere and you get it whether you like
it or not.  :)

man(1) foists its input off onto the andoc "macro package", which to my
eye simply does some trickery using the fact of the totally-disjunctive
namespace of the an and doc macros to overload TH and Dd to cause an mso
of the relevant package.

In groff, loading the an macro package means loading an-old.tmac, which
goes ahead and loads an-ext.tmac _for_ you.  Unconditionally.

$ grep -4 -nH an-ext\\. $(pwd)/an-old.tmac
/usr/share/groff/current/tmac/an-old.tmac-684-.  char  ` \N'96'
/usr/share/groff/current/tmac/an-old.tmac-685-.\}
/usr/share/groff/current/tmac/an-old.tmac-686-.
/usr/share/groff/current/tmac/an-old.tmac-687-.\" Load man macro extensions.
/usr/share/groff/current/tmac/an-old.tmac:688:.mso an-ext.tmac
/usr/share/groff/current/tmac/an-old.tmac-689-.
/usr/share/groff/current/tmac/an-old.tmac-690-.\" Load local modifications.
/usr/share/groff/current/tmac/an-old.tmac-691-.mso man.local
/usr/share/groff/current/tmac/an-old.tmac-692-.

> I'm not keen on embedding it at the start of every man page in a
> project, even if they're built from a source just to achieve that.
> What's the alternative?  `.so ../man1/foo-an-ext.tmac' and release it
> to sit alongside the foo project's other man{1,8} pages.  It obviously
> mustn't appear as a page itself in indexes, etc.

=2Emso an-ext.tmac already does that.  The embedding is only for *roff
implementations that don't have that file.  But I see what you mean.  I
think a more canonical approach would be to install foo-an-ext.tmac to
/usr/share/groff/current/tmac and .mso it.  Autoconf can of course help
with determining the installation directory.

Anyway, I think it's fine to leave this sort of decision up to package
authors/maintainers.  They can:

1.  Cut-and-paste the an-ext macros they use into the header of their
    man pages, as groff_man(7) recommends; or
2.  Ship a package-specific "fork" (copy) of an-ext.tmac, perhaps
    stripped down to just the macros they want to use (but why)? and
    .mso it from their pages; or
3.  Check for the definition of one of the an-ext macros that one is
    actually using in the page and .ab out if it's missing; or
4.  Ignore legacy environments completely.

Mind you, the status quo is that lots[1] of man pages are written doing
only #4, _today_.  Who here is aware of complaints of pages not
rendering right because EX, EE, SY, YS, OP, UR, UE, and so forth not
being defined?  Or do people experiencing this problem largely lack the
knowledge to diagnose it, and think the page is just ugly?  If that's
the case, nothing I am proposing is going to make that problem _visibly_
worse.  Invisible problems will stay invisible.  _Any_ of the first 3
techniques above is an improvement on that situation.

Regards,
Branden

[1] I'll be doing a count of man pages using any of the "extended"
    macros in the near future, and report my findings.
[2] I tried ".char hm \N'45'", without success.

--sv5az7to4ogrijlp
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkAwqIACgkQ0Z6cfXEm
bc45Rg/9HSzrMgwGpdcNDy23J1xZgsqokOXL7HmXKz7GLqYnJSAw/YEMxiLgf1II
ZSM9MDKOcTyweLhsocTyiDpImJH9wkYSZoVfixJ+h5XmuZ2MOjpEJwynuu+yUNb3
bbFtRyA4IbS6iKFO2hsSRbHZVaLEsxtIas/81Ywx1HqXP7Nof5I/Pyf3k7KWfE2x
8/6Qf+R0kVDVLVIjfdkgPd7m7YYQ+sbSAou4YTLMK2/vRUWhsmdNyb2dX4IP/xbt
MmPZVQr4LeLTLCV4Pr62wF8J4BHoPii0BO7i1ingC2bYhajXZXGqeAPxmvqxHO0v
hOOAGSy5isNJj/TkMBwrxpu+ecAlh2FhFou2Tido0twzvfTxyHOsTZrNgvWzpQ33
qCMXAjyHaG/+bX8H/flK6htxkqol9ANvG11U0ZtNfHdkhsVfhR1vUUcAw98UZK7Z
h0Qt6rAGFaUw317TcjJfo+tQZkzbNAnAq0v5xYL1aWzFqZiL2NnrRkA2FukTf4HT
y92QSvUbI7V0kMEv2U+RRpcHXigWJqOMnKhCePBI1wASM1CqSZ6x4BwrQxnXfJlq
MKACLOgjAb/qkGvt2UfZbZebTHKNfe12YieWQhHRVhq+ff45lfDml9FiQvgsH46S
/bWoZrMWJHNrdali5Txw0Hi3L2dA/7xkiog9n89QnjZtWiOKv+Q=
=DfcM
-----END PGP SIGNATURE-----

--sv5az7to4ogrijlp--


From MAILER-DAEMON Wed Apr 26 12:02:16 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3POR-0006sM-SR
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 12:02:15 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55846)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d3POP-0006qU-IF
	for groff@gnu.org; Wed, 26 Apr 2017 12:02:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d3POL-0003X3-LR
	for groff@gnu.org; Wed, 26 Apr 2017 12:02:13 -0400
Received: from mail-io0-x243.google.com ([2607:f8b0:4001:c06::243]:34020)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <anthony@cathet.us>) id 1d3POL-0003Wl-Ej
	for groff@gnu.org; Wed, 26 Apr 2017 12:02:09 -0400
Received: by mail-io0-x243.google.com with SMTP id h41so972293ioi.1
	for <groff@gnu.org>; Wed, 26 Apr 2017 09:02:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=cathet-us.20150623.gappssmtp.com; s=20150623;
	h=sender:from:to:cc:subject:in-reply-to:references:comments
	:mime-version:content-id:date:message-id;
	bh=v29UTcwxREiU1sIsgfrAOxozfxyRuGTDRY2HbXhVIY4=;
	b=RR2LbJZtKj/LTjYvQfGMhV7xtq2n+x5+K6P97Hkondvdl2p8ro80cSlQmYGdGkWr+e
	xBg1XOe1uJyWRpeWnXT1EgrRJTXxH8HtdRwvlT9qiPAKHnWr99fxLIrhOOuMmidIvDy7
	H/hqb+ZtYEyRh2rh4Pre1DTwPmidu2fUyEnMzx5CEZ5ELGuMVvDe2yVCN0ysSe5JB9Q8
	iG7dnBRueTnFy/iONdFjP+APKkwGRyh1EvVX7rJHLQmRZYjN1isT/GoO7Zo2Qp7PmTCg
	klJ9DG9hubRvYV6C4IHY2eqoHzHkOVYCeZ+f1pK6dCFmKU1peQsCFcBvD7hSQiC5/LSm
	aFCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references
	:comments:mime-version:content-id:date:message-id;
	bh=v29UTcwxREiU1sIsgfrAOxozfxyRuGTDRY2HbXhVIY4=;
	b=cIsYuowYqsjz6wuaFiKUnKy59NVStpBtCoSn2LLYtT11RpQ2tlOueBJ+xHtQsMChC1
	47sUDjiEdDjU854IVzoh3qTC08SvVrJ31q7/2UCHvAQln4gKdTnj8Kycy/pJfMhGS0PV
	UcfxOruGaQ8ZBEOHqbDFupYHnK274kfseViab61IywReHgpdInGWPjk1Y33rgCDFiEmK
	/rOtf3KxWmkT0XvDmelDwD68Byul/rfNmbS1zgWinLQUwU2NJCw5kB54Xwse7Lg/RWau
	uiunH+0AvdTN9o18GmLmTZQ/LkHqyHAKavfySYJ/GLSgrz+BrTQMlZ+LY8bpcyMWeufN
	F2Cg==
X-Gm-Message-State: AN3rC/4pjrFxJtowMzStpDpBgVyO597GIPexnIsxQhMw1OF+K75JCnpX
	s1cK9CMtk9+TR/TZ
X-Received: by 10.107.146.139 with SMTP id u133mr495877iod.160.1493222527857; 
	Wed, 26 Apr 2017 09:02:07 -0700 (PDT)
Received: from cathet.us. (97-123-212-98.albq.qwest.net. [97.123.212.98])
	by smtp.gmail.com with ESMTPSA id t136sm9529ita.22.2017.04.26.09.02.06
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 09:02:07 -0700 (PDT)
Sender: "Anthony J. Bentley" <anthony@cathet.us>
Received: from cathet.us (localhost [127.0.0.1])
	by cathet.us. (OpenSMTPD) with ESMTP id 46705157;
	Wed, 26 Apr 2017 10:02:06 -0600 (MDT)
From: "Anthony J. Bentley" <anthony@anjbe.name>
To: Ralph Corderoy <ralph@inputplus.co.uk>
cc: groff@gnu.org
In-reply-to: <20170426145026.E9BD12038D@orac.inputplus.co.uk>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
Comments: In-reply-to Ralph Corderoy <ralph@inputplus.co.uk>
	message dated "Wed, 26 Apr 2017 15:50:26 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <68488.1493222525.1@cathet.us>
Date: Wed, 26 Apr 2017 10:02:06 -0600
Message-ID: <85076.1493222526@cathet.us>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4001:c06::243
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:02:14 -0000

Ralph Corderoy writes:
> > INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
> > already now because the three main implementations (including groff)
> > don't do that in the quite important -Tutf8 device.
> 
> This is because of the bodge to map `-' onto ASCII 45, by Debian
> originally, was it?  Rather than stand firm and map just `\-' and tell
> complainants that the upstream man page needed fixing.
> 
> > INSIDE manual pages (both -man and -mdoc), let's change - and \- to
> > always map to U+002D HYPHEN-MINUS for all devices and let's tell
> > people to simply use - for HYPHEN-MINUS and stop worrying.
> 
> But PDFs then look awful.

This is a case where troff and the rest of the world simply moved in
different directions.

Nobody in 1973 anticipated that terminals would become typographically
rich, able to display real dashes and apostrophes. Nobody anticipated
that using typeset output as input to the terminal via copy & paste
would become commonplace.

Using \- as both a typographic minus sign and as the command-line flag
character '-' is just not compatible with modern usage. A manual that
uses \- for flags (certainly an extremely widespread and long-lived
tradition), displayed in a nroff that converts \- to minus, will be
unusable. It breaks copy/paste and displays differently than expected.

This is not the only such case in troff. How many people realize that ~
becomes U+02DC, and to portably get a real tilde in a manual you *must*
use \(ti? How many people neglect to escape ' and ` as \(aq and \(ga in
their manuals, which is *required* if you don't really mean U+2019 and
U+2018? And don't get me started on misuse of angle quotes...

Avoiding \- is quite easy in mdoc: .Fl displays '-' in ASCII output
format and a fixed-width font '-' in typeset output, which seems like a
pretty reasonable compromise. Typical non-flag usages are rarer and
sensibly covered by .Nd, \(en, or \(mi.

But mdoc provides no help for ~, `, and '. Perhaps it would make sense
to change mdoc: make macros that produce fixed-width text skip
converting these characters. Is that a sensible idea? Probably needs a
check against a large manpage corpus to see if it's feasible...

-- 
Anthony J. Bentley


From MAILER-DAEMON Wed Apr 26 12:55:24 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3QDs-00071I-As
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 12:55:24 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39153)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3QDp-00071A-LP
	for groff@gnu.org; Wed, 26 Apr 2017 12:55:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3QDo-0000WW-F2
	for groff@gnu.org; Wed, 26 Apr 2017 12:55:21 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:45285)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3QDo-0000WE-5c
	for groff@gnu.org; Wed, 26 Apr 2017 12:55:20 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3QDj-0004dX-7N; Wed, 26 Apr 2017 18:55:16 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3QDi-0002Al-7B; Wed, 26 Apr 2017 18:55:14 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3QDi-0003Nv-1j; Wed, 26 Apr 2017 18:55:14 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 164d70e0;
	Wed, 26 Apr 2017 18:55:14 +0200 (CEST)
Date: Wed, 26 Apr 2017 18:55:14 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170426165513.GB50994@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170426145026.E9BD12038D@orac.inputplus.co.uk>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:55:23 -0000

Hi Ralph,

i think it is fair to say that our priorities differ slightly here;
i value simplicity for writers slightly higher than you seem to,
and you seem to value typeset (e.g., PDF) output slightly higher
than i tend to.  No doubt, both priorities have some merit.

I don't deny that writing good manual pages requires some understanding
of the roff(7) language, no matter which macro set you use, even mdoc(7),
and the required understanding goes beyond understanding that request
and macro lines start with a dot and text lines don't.  The mandoc mdoc(7)
manual says as much near the top, in the fifth paragraph of the
description.

As a consequence of the slightly different priorities described above,
we might (or might not) disagree about whether certain low-level roff
best practices should be recommended for manual pages, too, but i don't
see evidence of substantial disagreement in that respect yet.
I certainly don't object if people write "e.g.\&", though i might
not try to train less prolific authors to pay attention to that.
I claim that \c is not needed (and should not be used) in mdoc(7),
but you didn't deny that.  I claim that man(7) requires more low-level
roff constructs than mdoc(7), and you didn't deny that.  So the fact
that \c is occasionally used in man(7), in particular in pages
written by unusually skilled typesetters like in the groff manuals
themselves, does not seem all that surprising to me, even though i
don't like it.  That fact that docbook autogeneration spews it
surprises me even less.  No matter how you judge \c usage in man(7),
docbook is no doubt notorious to be the man(7) autogenerator that
produces the lowest quality and least portable man(7) output available
anywhere on the market, even though generators producing acceptable
quality do exist, for example pod2man(1) - not all of that is pretty,
either, but it works quite reliably.


Ralph Corderoy wrote on Wed, Apr 26, 2017 at 03:50:26PM +0100:
> Ingo wrote:

>> INSIDE manual pages, - for \(hy or \- for \(mi is a terrible idea
>> already now because the three main implementations (including groff)
>> don't do that in the quite important -Tutf8 device.

> This is because of the bodge to map `-' onto ASCII 45, by Debian
> originally, was it?  Rather than stand firm and map just `\-' and
> tell complainants that the upstream man page needed fixing.

That is an argument to be taken very seriously.  *If* we value high
quality manual page output enough to worry about hyphens in normal
English words to be rendered as U+002D HYPHEN-MINUS in text lines,
then we have a second problem to solve (in -Tutf8) in addition to
not having a good way to request U+002D HYPHEN-MINUS where that is
really the character we want.

That leads to a natural suggestion solving *both* of these problems:

 - Make sure *all* output devices (even UTF-8) render - as a
   typographic hyphen (U+2010 HYPHEN) even in manual pages.
   That solves the second problem brought up in this mail.
   Yes, it will require fixing lots of manual pages, but if
   we decide that way, i think i'm willing to try and convince
   the BSD camp and help fixing OpenBSD manuals, even though
   i anticipate that will require some work.  That has good
   chances to work out because quite a few people are already
   at least half-aware that the input - is not quite the same
   as an output ASCII HYPHEN-MINUS.

 - Make sure *all* output devices (even PDF) render \- as
   U+002D HYPHEN-MINUS.  That is admittedly a deviation from current
   practice, but it thoroughly solves Ralph's original problem for
   the future, and i think it is close to what \- was originally
   intended to mean in historical roff implementations, so i don't
   view it as trampling on roff traditions.  Also, the visual
   appearance of U+002D HYPHEN-MINUS and U+2212 MINUS SIGN is so
   similar in most fonts that this change is unlikely to cause
   much outrage.

 - Educate people to always use \(mi rather than \- if they want a
   typographic minus sign U+2212 MINUS SIGN (say, in mathematical
   formula) as opposed to an ASCII minus sign (say, in sample C code).

 - Nothing changes for \(en and \(em.

After the above code changes in groff, Heirloom, mandoc, and the
related documentation, and until manual pages adapt, people may
see slighly wrong typography in practice - but none of that will
harm understanding.  The same goes for people using legacy roff
implementations other than the three mentioned, or old versions
of groff.  So incompatibility costs are minor and the transition
paths are more or less benign.

Thoughts?

If people like that direction, i'm even willing to draft patches.

This route is slightly more complicated for authors than my first
simplistic proposal, but i cannot deny Ralph's point that my proposal
harms manual page PDF output, and i can understand if people object
to that: the ability to produce uncompromisingly good typeset output
is among the most famous assets of the system of manual pages as a
whole.

This route is also technically cleaner and easier to implement than
my first simplistic proposal.

In any case, I'd love to have clear, easy-to-understand rules about
what - \- \(hy \(mi mean.  Lots of people have repeatedly asked me
about that, and i have never been able to answer in a very convincing
way.  The current macro set dependency and the absence of U+002D
output in typeset output makes this a deplorable mess.

Yours,
  Ingo


From MAILER-DAEMON Wed Apr 26 16:34:42 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3Te5-0004uO-Tz
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 16:34:41 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38657)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Te2-0004u9-RV
	for groff@gnu.org; Wed, 26 Apr 2017 16:34:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Tdt-0003Yb-TL
	for groff@gnu.org; Wed, 26 Apr 2017 16:34:38 -0400
Received: from mail-yb0-x22a.google.com ([2607:f8b0:4002:c09::22a]:33297)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3Tdt-0003YI-PZ
	for groff@gnu.org; Wed, 26 Apr 2017 16:34:29 -0400
Received: by mail-yb0-x22a.google.com with SMTP id 11so3278700yby.0
	for <groff@gnu.org>; Wed, 26 Apr 2017 13:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mime-version:content-disposition
	:user-agent; bh=MlmqN8PtA901VWCdDwcyt/knRCoYRXLm8i+A6Kh+m10=;
	b=G6ZXnOpjxbNOPQTgBDNReOd2u/f9ugmpWHRO/iKSoaL09dSp9fxxPKM6t7z72rR1mn
	41uZxIp4PtlbIE5BZHGTTPi5B2jSmmT2elNshvrmOr0fTnp/B4YSWsox63pvzF23WWkI
	uJec9y8UfDRsPvpA6iGycLBcGSa+kXH9K3f4Feozn034bc4NzG/Y07xsREXz7T+lxR9i
	YESeiClRdTMRENMHMtONCTgpLndRgpzOuDhhzvoUBa+pnpkNdtLH1AczsQUqQzBSqREd
	w1IQfBDc0dtGG9YZ3Gh2AiSklnzcfQBfbSEV8F69gIDa9Xuc7dcKPqtlCzrVkH36RDJ8
	YprQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-disposition:user-agent;
	bh=MlmqN8PtA901VWCdDwcyt/knRCoYRXLm8i+A6Kh+m10=;
	b=ZfKx2C7/4Rgcpel4UUo18yCMMvXnB8D2WEtJNZqq+IH1MJV71wAg8hlVbeiOuG5Cdw
	t6j82uJs3GSmvzqutggQdfdZGJUfeLNhttkS+MQBzqsfsUPUN9bvBRFg1QWPgoWzJTLP
	2e6SqAO/T/PGgV8lxMx/1/KWDLklMrWmEJi/Yp+LOOH7z3egQJGJwDabya28jHeQB4MQ
	qf+qmyhlIrmgQkN0zeLVtqNqBI6rf9ccI3NDuojtsHRNKFmWjItdADaIQVXmnsFAmfDv
	YLVu+7xpviGM7xxWFWoAb1V0MCqVZ8QdSkFC7646w7GVcECVgNajjD2A3F2FokYZEYCe
	QtAQ==
X-Gm-Message-State: AN3rC/6lRdPndbLXwphluxmswo5bFNQlUcN+CNeHt5lfSzhROcZALBwN
	vP1HA0XN96UI6hveSKY05g==
X-Received: by 10.37.172.86 with SMTP id r22mr1546890ybd.128.1493238868832;
	Wed, 26 Apr 2017 13:34:28 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	k188sm129798ywf.70.2017.04.26.13.34.27 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 13:34:27 -0700 (PDT)
Date: Wed, 26 Apr 2017 16:34:25 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426203423.6nbxflryrsfaaa5s@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="47zqtxjeufpslgse"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::22a
Subject: [Groff] [PATCH] ' and " in groff_char(7)
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:34:40 -0000


--47zqtxjeufpslgse
Content-Type: multipart/mixed; boundary="rk7dstyybdwe5kmm"
Content-Disposition: inline


--rk7dstyybdwe5kmm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

The attached patch:

1.  Makes sure that the bare ' renders as the closing quote the adjacent
    text says it is, even on UTF-8 devices where the stated rule is
    broken.

2.  Adds " to the list of characters that don't render as themselves,
    because it doesn't as part of arguments to macros.

Regards,
Branden

--rk7dstyybdwe5kmm
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="groff_char.diff"

--- groff_char.stock.7	2017-04-26 16:18:12.514128437 -0400
+++ groff_char.hacked.7	2017-04-26 16:27:59.628887175 -0400
@@ -260,10 +260,16 @@
 .
 .TP
 .B \*(aq
-the ISO \%latin1 \[oq]Apostrophe\[cq] (code\ 39) prints as ', a right
+the ISO \%latin1 \[oq]Apostrophe\[cq] (code\ 39) prints as \[cq], a right
 single quotation mark; the original character can be obtained with
 \[oq]\f(CW\e(aq\fP\[cq].
 .
+.TP
+.B \(dq
+the ISO \%latin1 \[oq]Quotation Mark\[cq] (code 34) prints as itself,
+but is also used to quote arguments to macros and will not appear in
+output in that context; the original character can be obtained in any
+context with \[oq]\f(CW\e(dq\fP\[cq].
 .
 .TP
 .B -

--rk7dstyybdwe5kmm--

--47zqtxjeufpslgse
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkBBEUACgkQ0Z6cfXEm
bc7HaBAAgrh9NM6LxwYV9TnMu7RzQ8YlQ0dec6WBAhIAYdtsAif0agPg9vDPX2gw
OuVkiPkkGitNNMRzx7NIU5jcNwpzvkzUBP1ol1SNj0ZdeLaeVVOSwdjVSsQA8cqI
ZNhy2eLiUDogSn3tPuZXfsX5RQ91kInBSFsYerWsruLqv7i9TuB9ASrQkhaS35Jl
VITgnOydSrl5USe3tpak81EmsB2MdgdOD9kE1ckD3sJdDLuZII/SfXOvUPCjCAoE
iKgkXUgByMDZpAtcN1ksUHl77r1KrLLfz/FrouFL05xJi/Gdk+bASHeII8nAxpdX
tO2asK0T8OD5h4dUNSWDKNF8iMPn67pm/tejDD4jtqc4fBiuqW3o+MROSbv+CUyx
li6633/vkeATr/09p/Rk7BXAH4WJ7ixcidbLxK8+Sq12cXbdEgIJ0mzAD9Mwbx8w
SQsqlrD5k4c113PziwbRRUtJtAC4KVX3QkjqQ96EgZMisC6mSFW2cTAxSubz7kwj
YK9CJCwdzsCQGy+isVz34A0thc6TXOsk3orrdq+qoNuJ7eCRb1vC9h0YMnLsT8re
G6Lj8EC4U3GNVJhOZbxE373uEoju4W0LAv0tq/D8Yooqka5DDM9Qoa1VdfLIieXl
Fl0WRM+ugitUKKigjq4skLQksnobZKFW9IUAy7OOLCodzFVHk+s=
=eBqV
-----END PGP SIGNATURE-----

--47zqtxjeufpslgse--


From MAILER-DAEMON Wed Apr 26 17:37:07 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3UcV-00073U-Ot
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 17:37:07 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50040)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d3UcT-00071a-4L
	for groff@gnu.org; Wed, 26 Apr 2017 17:37:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d3UcQ-0005ox-1U
	for groff@gnu.org; Wed, 26 Apr 2017 17:37:05 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:36850)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1d3UcP-0005op-TZ
	for groff@gnu.org; Wed, 26 Apr 2017 17:37:01 -0400
Received: from coolidge.cs.Dartmouth.EDU (coolidge.cs.dartmouth.edu
	[129.170.213.217])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v3QLavtp016530
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
	Wed, 26 Apr 2017 17:36:57 -0400
Received: from coolidge.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTP id
	v3QLavRE026274; Wed, 26 Apr 2017 17:36:57 -0400
Received: (from doug@localhost)
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v3QLauLR026273; 
	Wed, 26 Apr 2017 17:36:56 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
Date: Wed, 26 Apr 2017 17:36:56 -0400
To: groff@gnu.org, esr@snark.thyrsus.com, bwk@cs.princeton.edu
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: [Groff] pic syntax blemishes
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 21:37:06 -0000

This pic fragment
        d = 3
        circle radius 2d
draws a circle of radius 2, not 6 as one might suppose. It is parsed as
        circle radius 2 d
and the "irrelevant attribute" d is ignored.

In another context
        d = 3
        move 2d
the parsing results in a move of 2 then of d. Thus 2d is sometimes
taken as 2 and sometimes as 2+d, but never as 2*d.

Yet another confusion arises here:
        nd = 3
        move 2 nd
        move 2nd
The first move behaves like move 2+nd, but the second (pun not intended)
is an error, because the pic tokenizer recognizes 2nd (also 2st and 2th)
as an ordinal.

The treatment of irrelevant attributes also allows crazy code like
        box radius 3

The convention of dropping irrelevant attributes may have been justified
during the experimental days of pic's development, but seems cheesy now,
nearly 40 years on.

The fact that 2d gets tokenized differently from 2nd is also disconcerting.

I suggest that irrelevant attributes and constructions like 2d should
be errors. Any previously working code that such a tightening of syntax
might reject will be easy to fix.

What do folks think about this issue? Depending on response, I may try to
do something about it.

Doug


From MAILER-DAEMON Wed Apr 26 18:15:57 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3VE5-0002f9-Bn
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 18:15:57 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59710)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <robert@thorsby.com.au>) id 1d3VE3-0002f2-Mt
	for groff@gnu.org; Wed, 26 Apr 2017 18:15:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <robert@thorsby.com.au>) id 1d3VDy-0006KS-OK
	for groff@gnu.org; Wed, 26 Apr 2017 18:15:55 -0400
Received: from ihm-port-irony1.ihm.iinet.net.au ([203.113.243.211]:35575)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <robert@thorsby.com.au>) id 1d3VDy-0006Jk-Bd
	for groff@gnu.org; Wed, 26 Apr 2017 18:15:50 -0400
IronPort-PHdr: =?us-ascii?q?9a23=3AJcLexBVNqkMAB9Mro4df0NT7vPPV8LGtZVwlr6E/?=
	=?us-ascii?q?grcLSJyIuqrYbRyAt8tkgFKBZ4jH8fUM07OQ6PG+HzBdqs/Z+Fk5M7V0Hycfjs?=
	=?us-ascii?q?sXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFRrwLxd6?=
	=?us-ascii?q?KfroEYDOkcu3y/qy+5rOaAlUmTaxe71/IRG3oAnLucQbgYRuJrstxhDUvnZGZu?=
	=?us-ascii?q?NayH9yK1mOhRj8/MCw/JBi8yRUpf0s8tNLXLv5caolU7FWFSwqPG8p6sLlsxnD?=
	=?us-ascii?q?VhaP6WAHUmoKiBpIAhPK4w/8U5zsryb1rOt92C2dPc3rUbA5XCmp4ql3RBP0ji?=
	=?us-ascii?q?oMKiU0+3/LhMNukK1boQqhpx1hzI7SfIGVL+d1cqfEcd8HWWZNQsNdWipcCY2+?=
	=?us-ascii?q?coQPFfIMM+hYoYfguVUOoxmxCw6vCuzg1jBHm3D43awh3uQ9CAHLxhAsEsgSvH?=
	=?us-ascii?q?jKqtj+KaccUfqyzKnN1TjNc/RW1izj54jSbhAqvO+CXbJ3ccrL0kkgDAPEhUiX?=
	=?us-ascii?q?pIz/ODOazfoCs3KH7+d7SeKvi2knqxtqoje0xsYgkJXGhoUQylze7yp53Z84KN?=
	=?us-ascii?q?ulQ0B4ed6pCIZcuz2AO4drQ84uWWNltDsgxrAGpJK3ZDYGxIgpyhLFdvCKc4uF?=
	=?us-ascii?q?7gjjWeuVOzt0mW5pdK65ih2v60av0Pf8WdOx0FtSqypFlcTDuW4V2hzI78iHVu?=
	=?us-ascii?q?N9/kC82TaTzwzT6v9LIUQzlafDLp4u2L8wlp4JvUvdES75hEX2g7WQdkUr5Oek?=
	=?us-ascii?q?8eXnYrTgppCCK494kAf+PboymsClG+s4LxACX2md+euiyL3u5VD1TKlQgvErk6?=
	=?us-ascii?q?TVqpLXKdkBqqO5HgNZyoMj5Ay+Dzei3tQYh34HLFdddRKdiIjmIE/BIOrkDfqk?=
	=?us-ascii?q?n1SskDBrx+rdPrL6ApTBNGTMkLDkfbpn8UFc1RI/zcpD6JJMFrEBPPXzV1fvu9?=
	=?us-ascii?q?zDFB80KBe0w+D9B9Vn1YMSQ36PAq+ZMaPIql+I+/kvL/OQa48SvTb3M+Il6OL2?=
	=?us-ascii?q?jX8lhV8derGk0oAZaXC7BflpP16ZbWD0gtcbEGcKuBYxQ/L2iF2FVz5ffWi9UL?=
	=?us-ascii?q?8h5jsjEoKpEZ/DRpyxgLyGxCq0A5pWZn1JCl2XDXjobJ+IVOoWZyKIPs9hlzsE?=
	=?us-ascii?q?VaW9S48hzx2hqhL1y6d/JOrO5iIYrY7j1MRy5+DLmhEy7zt0D8qT02yWQGF0mH?=
	=?us-ascii?q?4ISyUx3KBlrkwugmuEhIR/nvMQMNdy4+lOQ09uOZnBwMRxEJb+Uxjde9CUVFbg?=
	=?us-ascii?q?T9m7V2IfVNU0luUJaUtnB52ejhfZxCC7S+sPkLaGHoAc7qLbxWP7NoB2zHOA3b?=
	=?us-ascii?q?R33ApueddGKWDz3v03zAPUHYOc1hzBz6s=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2CvAwA9GwFZ/zNHEApdDgwBAQEBAgEBA?=
	=?us-ascii?q?QEIAQEBARUBAQEBAgEBAQEIAQEBAYUenyAhjG+LC4YcCAKEbRQBAQEBAQEBAQE?=
	=?us-ascii?q?BAWoogjMiAYJAAQU6PxAIAw0LHhA8GwYOhgOEHK19JgKKegEBAQcBAQEBJAkBh?=
	=?us-ascii?q?kqCFIJkhF+FZQWWUoZ+ZZMTfgGJJ4ZMlCc2IYEHJx0IFRmGc0+ISwGBDAEBAQ?=
X-IPAS-Result: =?us-ascii?q?A2CvAwA9GwFZ/zNHEApdDgwBAQEBAgEBAQEIAQEBARUBAQE?=
	=?us-ascii?q?BAgEBAQEIAQEBAYUenyAhjG+LC4YcCAKEbRQBAQEBAQEBAQEBAWoogjMiAYJAA?=
	=?us-ascii?q?QU6PxAIAw0LHhA8GwYOhgOEHK19JgKKegEBAQcBAQEBJAkBhkqCFIJkhF+FZQW?=
	=?us-ascii?q?WUoZ+ZZMTfgGJJ4ZMlCc2IYEHJx0IFRmGc0+ISwGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,256,1488805200"; d="scan'208";a="51416991"
Received: from unknown (HELO mail.exchange.iinet.net.au) ([10.16.71.51])
	by ihm-port-irony1-out.ihm.iinet.net.au with ESMTP;
	27 Apr 2017 08:15:40 +1000
Received: from mullet (203.158.59.100) by IHM-CAM-E13M01.prdhosting.local
	(10.16.71.51) with Microsoft SMTP Server (TLS) id 15.0.1076.9;
	Thu, 27 Apr 2017 08:15:40 +1000
Date: Thu, 27 Apr 2017 08:15:27 +1000
From: Robert Thorsby <robert@thorsby.com.au>
To: Doug McIlroy <doug@cs.dartmouth.edu>
CC: <groff@gnu.org>, <esr@snark.thyrsus.com>, <bwk@cs.princeton.edu>
References: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
In-Reply-To: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU> (from
	doug@cs.dartmouth.edu on Thu Apr 27 07:36:56 2017)
X-Mailer: Balsa 2.4.11
Message-ID: <1493244927.2714.0@mullet>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [203.158.59.100]
X-ClientProxiedBy: IHM-PORT-E13C01.prdhosting.local (10.16.70.221) To
	IHM-CAM-E13M01.prdhosting.local (10.16.71.51)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 203.113.243.211
Subject: Re: [Groff] pic syntax blemishes
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 22:15:56 -0000

On 27/04/17 07:36:56, Doug McIlroy wrote:
> I suggest that irrelevant attributes and constructions like 2d should =20
> be errors. Any previously working code that such a tightening of =20
> syntax might reject will be easy to fix.
>=20
> What do folks think about this issue? Depending on response, I may =20
> try to do something about it.

WOW.  After 40 years they're not errors, merely idiosyncrasies.

I admire your courage.

Robert
=


From MAILER-DAEMON Wed Apr 26 19:57:55 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3Wol-0007Kf-8Q
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 19:57:55 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48022)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Woi-0007KE-CK
	for groff@gnu.org; Wed, 26 Apr 2017 19:57:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3Wof-0003eS-Ab
	for groff@gnu.org; Wed, 26 Apr 2017 19:57:52 -0400
Received: from mail-yw0-x236.google.com ([2607:f8b0:4002:c05::236]:35976)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3Wof-0003eL-3d
	for groff@gnu.org; Wed, 26 Apr 2017 19:57:49 -0400
Received: by mail-yw0-x236.google.com with SMTP id l18so8258632ywh.3
	for <groff@gnu.org>; Wed, 26 Apr 2017 16:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=lekFBg4eSKtzETwWfIMsP0oOKUXk8pbA6eyNCwzocXE=;
	b=j0MbwJRzGcPElAVBXD4V4lF7bllyhhfIHsN53n4rutzJEEUfi076whfu8yuqjtpIIB
	BeGzA08sc3U/WxIjkfYW8gLLE/UL7TzD/7fQZv+cN2sprwPpN4k1PknZBS7CwqvJnume
	kOBcQn2WcOJjmAF9oI+QWR3NeGo29INVkltFPkkDgXXW1awl8MhzRXMQjwUWM2K4FvON
	GnVXjRUDxc+aIZ69wekc6DQCcRq12NT28oWRwRsqWXRAb4B4uLJNo61iMZpzH0Fn75wo
	p5X8nRG1CQVdru8mDMF3Sjnyw/zsGtDGwrFA62Wtrig8mZtENUsWRGwkT1kq8lF2IlGh
	cadw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=lekFBg4eSKtzETwWfIMsP0oOKUXk8pbA6eyNCwzocXE=;
	b=g5nyx+sP58rWvx1hkAaRJWYu9rZ8UbRY8yq485MFaqN3MdwdJXPCzj9RlyCNzArUQy
	6szDp9h6eoDjDiTesDpJOLaTmksDEDqGOliWVbrLf44gfAV5RhhfsVCvUs+nB5DRArgE
	/c1bpVWTnyFCUUjHqnCP8Ih0qyd7uYt0o1fPN7+wadQuWsMX/Blf/Zqz6JUZy5AuQPnR
	Kq1BtxfXVD6rKDPdB9WgVbvkiCiDHEAGlo2bmA5fmhgoLTcW/wlOx4uuJ/wzLT0tBv0/
	W2cg/d9s8Z0GCjAjANedpS/qXOSXhcMYj49W6a+LBqkAajsSyp0fsyNRph9YCLru5gtV
	wrag==
X-Gm-Message-State: AN3rC/6jO7Sj8HlIYUZ3FAcBPdr4Kjr3O29kukQfxRhfPbDCPqV8LIWg
	vdJs63sqHYzTAProbaj5VA==
X-Received: by 10.129.115.212 with SMTP id o203mr2135440ywc.55.1493251067946; 
	Wed, 26 Apr 2017 16:57:47 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id m184sm674968ywm.9.2017.04.26.16.57.46
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Wed, 26 Apr 2017 16:57:46 -0700 (PDT)
Date: Wed, 26 Apr 2017 19:57:44 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="dkdzbhvhajpugyyg"
Content-Disposition: inline
In-Reply-To: <20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::236
Subject: Re: [Groff] Applications of \c in man pages in the wild [LONG]
 (was: Nesting font macros in man pages)
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 23:57:53 -0000


--dkdzbhvhajpugyyg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

The thrilling conclusion, featuring the remaining 100 of the 210 man
pages out of the 6,939 on my system.

Here's a recap of the categories we've already seen, plus a few minor
variants I added in this pass:

Category TILDE_C: "\~\c" immediately before a font change macro
    Use case: prevent a line break in a phrase that includes font
              changes via macros
    Examples: chem(1), eqn(1), gropdf(1), grops(1)

Category DOCBOOK_C: \c spewed as part of docbook-to-man's emissions of
                    .RS/.RE blocks
    Use case: only the docbook-to-man people know why
    Examples: git*(1), rediff(1) from patchutils

Category FONT_MACRO_C: \c immediately before or at the end of a font
                       macro line (e.g., ".I")
    Use case: suppressing a spacing word break between font-changing
               macros
    Examples: many, incl. gawk(1), grep(1), groff(1), ksh93(1), man(1)

Category SMALL_C: \c immediately before an .SM macro
    Use case: like TILDE_C; there are no "combo" macros for .SM as there
              are for bold, italic, and roman
    Examples: strace(1)

Category PRIVATE_FONT_MACRO_C: \c immediately before a private macro to
                               change the font, typically to \f(CW
    Use case: like SMALL_C
    Examples: ttk2pk(1), groff(7)

Category SPURIOUS_C_1: cargo-culting of DOCBOOK_C into hand-written
markup
    Use case: n/a
    Examples: tracker-extract(1)

Category SPURIOUS_C_2: using \c when all you need is \<newline>
    Use case: n/a
    Examples: chmod(1) [this is actually help2man's fault]

Category SPURIOUS_C_3: useless use of \c [has no effect]
    Use case: n/a
    Examples: gdiffmk(1), grodvi(1)

Category SPURIOUS_C_4: \c shows up unintentionally (author unaware of
                       its special meaning, and expected it to be
                       interpreted literally)
    Use case: n/a
    Examples: mame(6)

Category SPURIOUS_C_5: \c used adjacent to a font macro unnecessarily
    Use case: n/a (.RB could have been used instead of .BR, for example)
    Examples: mount(8)

Category COMMENT_C: using \c at the end of a commented line
    Use case: n/a
    Examples: des_crypt(3)

Again, uses of \c inside macro definitions (.de requests) are _not_
counted.  This brings the total number of pages categorized well below
210.

The remaining man pages categorize as follows:

mandb(1)                        FONT_MACRO_C
nmcli(1)                        DOCBOOK_C
passwd(1)                       DOCBOOK_C
pdfroff(1)                      FONT_MACRO_C
piuparts(1)                     DOCBOOK_C
pnmtotiffcmyk(1)                FONT_MACRO_C (with nice, frank comments)
posh(1)                         DOCBOOK_C
rediff(1)                       DOCBOOK_C
strace(1)                       SMALL_C (writer wanted semantic for keycap)
systemd-analyze(1)              DOCBOOK_C
systemd-ask-password(1)         DOCBOOK_C
systemd-machine-id-setup(1)     DOCBOOK_C
systemd(1)                      DOCBOOK_C
tbl(1)                          TILDE_C
tor(1)                          DOCBOOK_C
tracker-daemon(1)               SPURIOUS_C_1
ttf2pk(1)                       PRIVATE_FONT_MACRO_C, SPURIOUS_C_3,
                                _and_ FONT_MACRO_C
ttf2tfm(1)                      FONT_MACRO_C, PRIVATE_FONT_MACRO_C
unoconv(1)                      DOCBOOK_C
valgrind(1)                     DOCBOOK_C
vgdb(1)                         DOCBOOK_C
whatis(1)                       FONT_MACRO_C
yash(1)                         DOCBOOK_C
init-module(2)                  FONT_MACRO_C
vfork(2)                        SPURIOUS_C_3
XAllowDeviceEvents(3)           DOCBOOK_C
XIChangeProperty(3)             DOCBOOK_C
des_crypt(3)                    COMMENT_C
hd(4)                           FONT_MACRO_C
apt.conf(5)                     DOCBOOK_C
apt_preferences(5)              DOCBOOK_C
ext4(5)                         SPURIOUS_C_2
gitattributes(5)                DOCBOOK_C
githooks(5)                     DOCBOOK_C
gitignore5)                     DOCBOOK_C
gitrepository-layout(5)         DOCBOOK_C
gitweb.conf(5)                  DOCBOOK_C
groff_font(5)                   FONT_MACRO_C, TILDE_C
groff_out(5)                    FONT_MACRO_C, TILDE_C
groff_tmac(5)                   FONT_MACRO_C, TILDE_C
limits.conf(5)                  DOCBOOK_C
nm-settings-keyfile(5)          DOCBOOK_C
nm-settings(5)                  DOCBOOK_C
passwd(5)                       DOCBOOK_C
sepermit.conf(5)                DOCBOOK_C
sources.list(5)                 DOCBOOK_C
subgid(5)                       DOCBOOK_C
subuid(5)                       DOCBOOK_C
mame(6)                         SPURIOUS_C_4 (page has other problems)
daemon(7)                       DOCBOOK_C
gitcli(7)                       DOCBOOK_C
gitcore-tutorial(7)             DOCBOOK_C
gitcredentials(7)               DOCBOOK_C
gitdiffcore(7)                  DOCBOOK_C
giteveryday(7)                  DOCBOOK_C
gitglossary(7)                  DOCBOOK_C
gitnamespaces(7)                DOCBOOK_C
gitrevisions(7)                 DOCBOOK_C
gittutorial-2(7)                DOCBOOK_C
gittutorial(7)                  DOCBOOK_C
gitworkflows(7)                 DOCBOOK_C
groff(7)                        TILDE_C, PRIVATE_FONT_MACRO_C
groff_diff(7)                   TILDE_C (plus one eye-watering exception)
groff_hdtbl(7)                  TILDE_C, PRIVATE_FONT_MACRO_C
groff_man(7)                    TILDE_C
groff_mm(7)                     TILDE_C, FONT_MACRO_C
groff_mom(7)                    FONT_MACRO_C
groff_ms(7)                     FONT_MACRO_C, TILDE_C
gvfs(7)                         FONT_MACRO_C
roff(7)                         FONT_MACRO_C
systemd.generator(7)            DOCBOOK_C
systemd.offline-updates(7)      DOCBOOK_C
systemd.time(7)                 DOCBOOK_C
apt-cache(8)                    DOCBOOK_C
apt-secure(8)                   DOCBOOK_C
dmsetup(8)                      SPURIOUS_C_2
dmstats(8)                      FONT_MACRO_C
grpck(8)                        DOCBOOK_C
mount(8)                        SPURIOUS_C_2, SPURIOUS_C_5
nss-myhostname(8)               DOCBOOK_C
pam_systemd(8)                  DOCBOOK_C
pam_umask(8)                    DOCBOOK_C
pklocalauthority(8)             DOCBOOK_C
pwck(8)                         DOCBOOK_C
systemd-journald.service(8)     DOCBOOK_C
systemd-logind.service(8)       DOCBOOK_C
systemd-resolved.service(8)     DOCBOOK_C
udisks(8)                       DOCBOOK_C

That's it.

Regards,
Branden

--dkdzbhvhajpugyyg
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkBM+0ACgkQ0Z6cfXEm
bc7rbhAAkGOL2UiuKYx/HTsfu/shXKHUF55fdFLCBRiwLMRIT3HwCf7QL/VQKKLc
01qaXnpn+7TbzvGGwVy1slc27yzj4SENCdnVTkUltoOobO34mpzLHGydEBqlTG5/
vqxgC9u9mJkfaFb7ytCS5wSirMiV/D7jv8dJEC4XqTXAgc6NdHaVcvGk/T29Tnu3
pRV4rD8hnBAr0+vRyEiF5EkDq4rUFiuR0otcJU7+iric19bLfjDRGT7IzRleP5Jp
9BG2A3y6njqdBahTzRn1RKhCrMzpqYArr03f/u3f13xawJwn40jcwpdi0AOdPbTB
nOP2jzch4/tKzH91eGguX253KvBEgaEXwv+yIzXyqqJ0RozVFaEtnwekXV/Vcb9l
ifJeerrzrBuiRhOOwEorgLBd7oUaNMezmC5lMeFrsyVapezEoS8am2e1oyUDS/4o
GC/VcVq7X2bTQN9I5/ZkPdKiTvDkvHvlE6kESJbcdQkSa/dg/O2TJWKNxI6DXv9Y
BguGgs79ncv99vl/6hBFpCnWKhmqwqKKAtLUPB7+WK5aGFpeKLHhYv+daegh8mhm
St5Vgb5lJGEuk8bjbeVzkxIG6X7xRZOLIGD2rnadlZsi5Via1pU5fGoZsLglD5oq
zzekyhkICS6LvcB0yW4DWlzHhLYDsAaiOhgXB0ld2JKx+ACU3l0=
=jw8V
-----END PGP SIGNATURE-----

--dkdzbhvhajpugyyg--


From MAILER-DAEMON Wed Apr 26 23:09:41 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3ZoL-0001xt-Ku
	for mharc-groff@gnu.org; Wed, 26 Apr 2017 23:09:41 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57919)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d3ZoJ-0001wo-Pv
	for groff@gnu.org; Wed, 26 Apr 2017 23:09:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <doug@cs.dartmouth.edu>) id 1d3ZoG-0006Dq-LV
	for groff@gnu.org; Wed, 26 Apr 2017 23:09:39 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100]:55552)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <doug@cs.dartmouth.edu>)
	id 1d3ZoG-0006DQ-HB
	for groff@gnu.org; Wed, 26 Apr 2017 23:09:36 -0400
Received: from coolidge.cs.Dartmouth.EDU (coolidge.cs.dartmouth.edu
	[129.170.213.217])
	by mail.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTPS id v3R39UdU008808
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
	Wed, 26 Apr 2017 23:09:30 -0400
Received: from coolidge.cs.Dartmouth.EDU (localhost.localdomain [127.0.0.1])
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2) with ESMTP id
	v3R39Tbf028867; Wed, 26 Apr 2017 23:09:29 -0400
Received: (from doug@localhost)
	by coolidge.cs.Dartmouth.EDU (8.15.2/8.15.2/Submit) id v3R39SXJ028866; 
	Wed, 26 Apr 2017 23:09:28 -0400
From: Doug McIlroy <doug@cs.dartmouth.edu>
Message-Id: <201704270309.v3R39SXJ028866@coolidge.cs.Dartmouth.EDU>
Date: Wed, 26 Apr 2017 23:09:28 -0400
To: robert@thorsby.com.au, doug@cs.dartmouth.edu
Cc: groff@gnu.org, esr@snark.thyrsus.com, bwk@cs.princeton.edu
References: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
	<1493244927.2714.0@mullet>
In-Reply-To: <1493244927.2714.0@mullet>
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 129.170.212.100
Subject: Re: [Groff] pic syntax blemishes
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 03:09:40 -0000

> WOW.  After 40 years they're not errors, merely idiosyncrasies.

> I admire your courage.

Merely senority. The eruption was triggered by my ineptness at
figuring out how an old pic script that literally contained 2d
could ever have worked. The idiosyncrasies are not part of my
mental working set and probably never were.

Doug


From MAILER-DAEMON Thu Apr 27 00:15:17 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3app-00067P-AA
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 00:15:17 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36970)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bwk@cs.princeton.edu>) id 1d3ViR-0002Wv-8E
	for groff@gnu.org; Wed, 26 Apr 2017 18:47:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bwk@cs.princeton.edu>) id 1d3ViO-0002fv-3r
	for groff@gnu.org; Wed, 26 Apr 2017 18:47:19 -0400
Received: from yellowcard.cs.princeton.edu ([128.112.136.66]:49051)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <bwk@cs.princeton.edu>)
	id 1d3ViN-0002d8-Vi
	for groff@gnu.org; Wed, 26 Apr 2017 18:47:16 -0400
Received: from soak.CS.Princeton.EDU (soak.CS.Princeton.EDU [128.112.155.170])
	(authenticated bits=0)
	by yellowcard.cs.princeton.edu (8.14.4/8.14.4) with ESMTP id
	v3QMl7g3001061
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=NOT); Wed, 26 Apr 2017 18:47:07 -0400
Date: Wed, 26 Apr 2017 18:47:07 -0400 (EDT)
From: Brian Kernighan <bwk@CS.Princeton.EDU>
To: Doug McIlroy <doug@cs.dartmouth.edu>
cc: groff@gnu.org, esr@snark.thyrsus.com
In-Reply-To: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
Message-ID: <alpine.LRH.2.20.1704261845350.26254@soak.cs.princeton.edu>
References: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 128.112.136.66
X-Mailman-Approved-At: Thu, 27 Apr 2017 00:15:15 -0400
Subject: Re: [Groff] pic syntax blemishes
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 22:47:20 -0000

The number of (g)pic users in the world must be pretty small
by this point, though I am among them, thanks to gpic et al.

Oddly the sequence
 	d = 3
 	r = 2d
does draw an error message from gpic.

On Wed, 26 Apr 2017, Doug McIlroy wrote:

> This pic fragment
>        d = 3
>        circle radius 2d
> draws a circle of radius 2, not 6 as one might suppose. It is parsed as
>        circle radius 2 d
> and the "irrelevant attribute" d is ignored.
>
> In another context
>        d = 3
>        move 2d
> the parsing results in a move of 2 then of d. Thus 2d is sometimes
> taken as 2 and sometimes as 2+d, but never as 2*d.
>
> Yet another confusion arises here:
>        nd = 3
>        move 2 nd
>        move 2nd
> The first move behaves like move 2+nd, but the second (pun not intended)
> is an error, because the pic tokenizer recognizes 2nd (also 2st and 2th)
> as an ordinal.
>
> The treatment of irrelevant attributes also allows crazy code like
>        box radius 3
>
> The convention of dropping irrelevant attributes may have been justified
> during the experimental days of pic's development, but seems cheesy now,
> nearly 40 years on.
>
> The fact that 2d gets tokenized differently from 2nd is also disconcerting.
>
> I suggest that irrelevant attributes and constructions like 2d should
> be errors. Any previously working code that such a tightening of syntax
> might reject will be easy to fix.
>
> What do folks think about this issue? Depending on response, I may try to
> do something about it.
>
> Doug
>


From MAILER-DAEMON Thu Apr 27 00:21:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3avy-00075h-3z
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 00:21:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47366)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bjarniig@hi.is>) id 1d3avw-00074F-3N
	for groff@gnu.org; Thu, 27 Apr 2017 00:21:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bjarniig@hi.is>) id 1d3avv-0005hf-3U
	for groff@gnu.org; Thu, 27 Apr 2017 00:21:36 -0400
Received: from mx2.hi.is ([2a00:c88:4000:1650::165:104]:40782)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <bjarniig@hi.is>) id 1d3avu-0005fk-Me
	for groff@gnu.org; Thu, 27 Apr 2017 00:21:35 -0400
Received: from hekla.rhi.hi.is (hekla.rhi.hi.is
	[IPv6:2a00:c88:4000:1650::165:2])
	by mx2.hi.is (8.14.7/8.14.7) with ESMTP id v3R40VVZ000720
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=NO); Thu, 27 Apr 2017 04:00:33 GMT
Received: from hekla.rhi.hi.is (localhost [127.0.0.1])
	by hekla.rhi.hi.is (8.14.4/8.14.4) with ESMTP id v3R40VE2022252;
	Thu, 27 Apr 2017 04:00:31 GMT
Received: (from bjarniig@localhost)
	by hekla.rhi.hi.is (8.14.4/8.14.4/Submit) id v3R40TBk022214;
	Thu, 27 Apr 2017 04:00:29 GMT
Date: Thu, 27 Apr 2017 04:00:29 +0000
From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Ralph Corderoy <ralph@inputplus.co.uk>, groff@gnu.org
Message-ID: <20170427040029.GA6144@rhi.hi.is>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
User-Agent: Mutt/1.5.20 (2009-12-10)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:c88:4000:1650::165:104
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 04:21:37 -0000

On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote:
> At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote:
> > .SM affect the next input line as it uses an input trap, `.it'.  `\c'
> > doesn't make an input line continue to the next as far as input traps
> > are concerned;  groff has .itc for that.  So the .SM is over by the `)'.
> 
> That's exactly the hack I wanted to make to the TP macro.  I want to
> change its .it to an itc, thus:
> 

  I have made a similar suggestion, see bug number #42907 (or look for
'itc').

[...]
> 
> .TP
> .B \-scale \c
> .IR xfac [, yfac ]
> Multiply the horizontal and vertical window size by
> .I xfac
> and
> .IR yfac ,
> respectively.
> 

  One can use the transparent line indicator (\!) to use macros in a label,
without changing the '.TP' macro:

.TH testman 1 2017-04-DD
.TP
\!.B \-scale \c 
.IR xfac [, yfac ]
Multiply the horizontal and vertical window size by

  or a little different output (with a necessary longer indent):

.TH testman 1 2017-04-DD
.TP 20n
\!.B \-scale \c
\!.IR xfac [\c
\!.B ,\c
.IR yfac ]
Multiply the horizontal and vertical window size by


  The difference in output (compared to a '.TP' with escapes in the label)
is a small increase in the horizontal space caused by the used italic
correction in the macro '.IR'.

-- 
Bjarni I. Gislason


From MAILER-DAEMON Thu Apr 27 07:39:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3hlr-0006Rj-UC
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 07:39:39 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48051)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3hlp-0006Rc-AO
	for groff@gnu.org; Thu, 27 Apr 2017 07:39:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3hlo-0002YR-FY
	for groff@gnu.org; Thu, 27 Apr 2017 07:39:37 -0400
Received: from scc-mailout-kit-01.scc.kit.edu
	([2a00:1398:9:f712::810d:e751]:51623)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3hlo-0002YE-95
	for groff@gnu.org; Thu, 27 Apr 2017 07:39:36 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3hlk-0007aQ-Ng; Thu, 27 Apr 2017 13:39:33 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3hlk-00002M-8G; Thu, 27 Apr 2017 13:39:32 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3hlk-0003Cf-3N; Thu, 27 Apr 2017 13:39:32 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id b8ce77dc;
	Thu, 27 Apr 2017 13:39:32 +0200 (CEST)
Date: Thu, 27 Apr 2017 13:39:32 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>, groff@gnu.org
Message-ID: <20170427113932.GB37287@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170427040029.GA6144@rhi.hi.is>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170427040029.GA6144@rhi.hi.is>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e751
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 11:39:38 -0000

Hi,

Bjarni Ingi Gislason wrote on Thu, Apr 27, 2017 at 04:00:29AM +0000:
> On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote:
> > At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote:

>>> .SM affect the next input line as it uses an input trap, `.it'.  `\c'
>>> doesn't make an input line continue to the next as far as input traps
>>> are concerned;  groff has .itc for that.  So the .SM is over by the `)'.

>> That's exactly the hack I wanted to make to the TP macro.  I want to
>> change its .it to an itc, thus:

> One can use the transparent line indicator (\!) to use macros in a label,
> without changing the '.TP' macro:
> 
> .TH testman 1 2017-04-DD
> .TP
> \!.B \-scale \c 
> .IR xfac [, yfac ]
> Multiply the horizontal and vertical window size by

The \! escape seems at least as arcane as \c.  Besides, the
documentation for groff and Heirloom is noticeably different.
Groff talks about diversions only, while Heirloom says that diversions
are merely one example where this escape can be applied.

I'm not even sure anything requires that .TP must be implemented
in terms of diversions.  My impression is that this use of \! depends
on internal properties of the particular implementation in groff.

Please, when designing recommendations for how to write manual
pages, let's not digress into a cleverness contest trying to make
the end-user dig as deeply as possible into roff internals...

You don't really want to say that the above is in any way better
than using well-established, easy-to-understand, and certainly
portable font escapes, right?

Yours,
  Ingo


From MAILER-DAEMON Thu Apr 27 08:20:52 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3iPk-0002tA-7v
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 08:20:52 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58627)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3iPi-0002t1-3Y
	for groff@gnu.org; Thu, 27 Apr 2017 08:20:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3iPe-00024f-TB
	for groff@gnu.org; Thu, 27 Apr 2017 08:20:50 -0400
Received: from sdaoden.eu ([217.144.132.164]:38826)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3iPe-00023x-IZ
	for groff@gnu.org; Thu, 27 Apr 2017 08:20:46 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 4CAC416056; Thu, 27 Apr 2017 14:20:44 +0200 (CEST)
Date: Thu, 27 Apr 2017 14:21:10 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170427122110.7Qbol%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
In-Reply-To: <20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
Mail-Followup-To: groff@gnu.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:20:51 -0000

"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:

Sorry for answering so late, my daily routine has shifted to night
again, almost sunset, and that really makes me frustrated.

 |At 2017-04-25T20:19:21+0200, Steffen Nurpmeso wrote:
 ...
 |>|> c.  Show people a mapping from groff's "extended" man macro package to
 |>|>     mdoc, so that the route for switching over is clearly signposted.
 ...
 |> fantastic, c) i don't really believe in, mdoc has quite some
 |> similarities to brainfuck, things like
 |> 
 |>   .Op : Ns Fl c Ar cc-addr Ns \&:
 |> or
 |>   .Fl S Ar var Ns Op Ns = Ns Ar value Ns
 |> 
 |> are nice for teaching, but no one can really promote something
 |> like this, can he.
 |
 |I have two gripes about mdoc:
 |
 |1. The slavish devotion to two-letter names for things, which like the
 |   man macro package and the oldest parts of *roff itself, make it
 |   self-anti-documenting.  I may be tempting mockery by saying this from
 |   a vi session inside an xterm, but good Lord, we've gotten past the
 |   days of ASR 33 teletypes by now[1].  (That said, I'm sure this
 |   unfriendliness was imposed by the existing *roff implementations at
 |   the time mdoc was designed.)

Sure it was.  I think there are multiple problems.
You have a notion of "callable" and "parsed", and you should be
aware of that or you introduce errors which are hard to find.  It
may be that you don't even see an error in the visual output
because no special font attribute applies or so.  Be aware that
"No" is a command that needs to be escaped.  Not rarely i see *BSD
commits fly by which fix errors in manual pages because of errors
in some nesting level, or missing escaping, and these programmers
use this language for many years or even decades.  Of course this
is part of normal iteration, too, but isn't it better if you have
a as-minimal-as-possible set of commands which clearly stand out.

Generally speaking both of man and mdoc spread the text and make
the source hard to grasp, which i don't consider to be something
viable, and which, together with the missing possibility to add
semantic information, here especially man, for richer output
formats, is surely part of the move away from roff.

  ...
 |2. Most of mdoc's own documentation is too technical, even in
 |   mdoc.samples.  I find the glib and frequent usage of the term
 |   "domains" off-putting and inaccessible, and I don't think I'm
 |   unusually stupid.  (Pauses for a beat.)
 |
 |But, not to pound on Ingo's beloved too much, from what I understand of
 |mdoc's design, I find it much, much better considered than man(7).  It
 |clearly benefited from having a large corpus of existing man pages to
 |consider, so it knew better than man(7) did what sort of problems it was
 |going to have to solve.

If i got that right it came up after the info system, and i will
always wonder why you do have semantic info for targets, but not
for sources, especially if you do invent a command set where many
commands take arguments, e.g., you do have ".Bd -literal", you do
have .Sx to refer to a heading, you do have .Va to refer to
a variable, why not ".Va -index" or the like, so that you can
specify where the .Va has been defined?  That is such a crucial
part of good documentation, especially in science, a good index!,
why was that missing.

 |> And sometimes things have to be adjusted a bit so that things can
 |> overall stay the same.  The roff system is a fantastic
 |> achievement, and if at all possible i will use it until the day
 |> i die.  I am looking forward for my thing.
 |
 |Agreed.  Any proposals I make are with an eye toward making the roff
 |system better, not worse.  That could go without saying--but I guess I

Yes.

 |should emphasize that I'm here not to bury groff, but to praise it.
 |
 |Unlike, I think, [2].

I don't use doclifter.  And i prefer less and the tty over
anything else, really.  A few URLs to kick off, fine, but it is
absurd to go over the internet if the information is often
available locally already.  Anyway..

  ...
 |[2] https://lists.gnu.org/archive/html/groff/2014-02/msg00104.html

--steffen


From MAILER-DAEMON Thu Apr 27 08:30:39 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3iZD-0005mH-Rb
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 08:30:39 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60942)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3iZC-0005m9-3x
	for groff@gnu.org; Thu, 27 Apr 2017 08:30:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3iZB-0006MU-9q
	for groff@gnu.org; Thu, 27 Apr 2017 08:30:38 -0400
Received: from scc-mailout-kit-01.scc.kit.edu
	([2a00:1398:9:f712::810d:e751]:45025)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3iZB-0006Lo-3P
	for groff@gnu.org; Thu, 27 Apr 2017 08:30:37 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3iZ7-0002cg-Ig; Thu, 27 Apr 2017 14:30:34 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3iZ7-00009m-BP; Thu, 27 Apr 2017 14:30:33 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3iZ7-0004BL-43; Thu, 27 Apr 2017 14:30:33 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id b47aeec4;
	Thu, 27 Apr 2017 14:30:33 +0200 (CEST)
Date: Thu, 27 Apr 2017 14:30:33 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170427123033.GC37287@athene.usta.de>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e751
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:30:39 -0000

Hi,

wow, you definitely demonstrate diligence in investigating existing
usage.  Let's have a look at the result.

The only use cases that are (arguably) legitimate are FONT_MACRO_C,
PRIVATE_FONT_MACRO_C, SMALL_C, and TILDE_C.  Not counting the groff
documentation itself (because that might be considered biased by
excessive insider cleverness), if i read your mail correctly, you
found 14 cases of FONT_MACRO_C, 1 additional PRIVATE_FONT_MACRO_C,
1 SMALL_C, and 0 TILDE_C - in just shy of 7000 manuals.

That is (arguably) legitimate use in 0.23% of manuals - or put
another way, almost half the uses are *in groff itself*.
There is on average about one SPURIOUS_C for every two (arguably)
legitimate uses outside groff.

The bulk of existing cases is docbook insanity.

That can be summarized as follows:  Legitimate hand-written use is
almost inexistent, even hand-written abuse is very rare, but unusually
frequent when expressed as a fraction of the instances of use.  The
dominant occurence is abuse by known-bad autogenerators.

Remeber that writing legacy man(7) documents is quite hard and
entices many people to try all kinds of (sometimes unavoidable,
sometimes ill-advised) trickery.  Even when analyzing the use of
easy-to-use languages in the wild, you usually find substantial (in
that case, needless) trickery.  So it is actually surprising that
you found so little.

So, if we would choose to promote \c use for the FONT_MACRO_C use
case, we would actually promote using a low-level feature that is
so far virtually unused in the wild, but where existing practice
in the wild already demonstrates that about 1 out of 3 users who
choose to use it freely get it wrong.  Officially encouraging use
is likely to cause an increase rather than a decrease of abuse.

I think your analysis reinforces the argument that we should refrain
from promoting the use of escape seqeunces in manual pages unless
they are unavoidable, well-established, *and* easy to understand.
Typical examples of escapes matching those criteria are \e, \&, \f.
It is now demonstrated in the wild that \c misses the last criterium,
and it is plausible to assume that \! will also miss it.

Yours,
  Ingo


From MAILER-DAEMON Thu Apr 27 09:11:14 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3jCU-0000v5-Rw
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 09:11:14 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43824)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3jCS-0000uY-4U
	for groff@gnu.org; Thu, 27 Apr 2017 09:11:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3jCO-0006CW-8h
	for groff@gnu.org; Thu, 27 Apr 2017 09:11:12 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:56976)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3jCO-0006An-2j
	for groff@gnu.org; Thu, 27 Apr 2017 09:11:08 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3jCL-0007tm-6K; Thu, 27 Apr 2017 15:11:05 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3jCK-0006J4-G4; Thu, 27 Apr 2017 15:11:04 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3jCJ-00054n-Qv; Thu, 27 Apr 2017 15:11:04 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id e9a36793;
	Thu, 27 Apr 2017 15:11:03 +0200 (CEST)
Date: Thu, 27 Apr 2017 15:11:03 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
Cc: groff@gnu.org
Message-ID: <20170427131103.GD37287@athene.usta.de>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427122110.7Qbol%steffen@sdaoden.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170427122110.7Qbol%steffen@sdaoden.eu>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 13:11:13 -0000

Hi,

Steffen Nurpmeso wrote on Thu, Apr 27, 2017 at 02:21:10PM +0200:

> You have a notion of "callable" and "parsed", and you should be
> aware of that or you introduce errors which are hard to find.

Wrong.  Just assume everything is callable.  Actually, mandoc
warns if you use the name of a macro that is not callable on
a macro line witout escaping it:

schwarze@isnote $ mandoc -mdoc -Tlint 
.Sy Sh
mandoc: <stdin>:1:5: WARNING: macro neither callable nor escaped: Sh

And by the way, so does groff:

schwarze@isnote $ nroff -mdoc      
.Sy Sh
mdoc warning: Using a macro as first argument cancels effect of .Sy (#1)
Usage: .Sh not callable by other macros (#1)


Besides, most macros are parsed and callable nowadays (thanks to
the work done by the groff team, in particular Werner).  So that
distinction did complicate things in the remote past, but it no
longer does for quite some time now.

I'm not going to correct all errors in what you might say in the
future, to save time and avoid noise.

> [...]

Yours,
  Ingo


From MAILER-DAEMON Thu Apr 27 09:46:42 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3jko-0004pS-1F
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 09:46:42 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52482)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3jkj-0004m1-Ip
	for groff@gnu.org; Thu, 27 Apr 2017 09:46:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3jkf-0003YM-HB
	for groff@gnu.org; Thu, 27 Apr 2017 09:46:37 -0400
Received: from mail-yb0-x235.google.com ([2607:f8b0:4002:c09::235]:33363)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3jkf-0003X0-8l
	for groff@gnu.org; Thu, 27 Apr 2017 09:46:33 -0400
Received: by mail-yb0-x235.google.com with SMTP id 11so8056941yby.0
	for <groff@gnu.org>; Thu, 27 Apr 2017 06:46:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=B4TpcOS4u802K1usKNvMvOBHCXxsqj7YwLZ6S/MOjSY=;
	b=VCQi4A/KF6gnnshtiNtUr3p07R6zOGAvjtyZqsvr9JH00yS7Ywdf2uXDmwQWUgCuBI
	+jFc7nOfneWtOIVxgdmxpQW0pjyiXifORYJWxA1ZWD9oyFA2qx5V4A9LCUPic03TsyX0
	x57KOME7jxFoPkjDEn2FPePZ3fejKj1G1pKnvcvyH9RgMOKrK/q9o8dXRW0Mm7iC6R43
	lGj5fFlb1WANqLBiqJ4vaC457DBI87tmNMmdGDKwvMWJ6EuRafj2AXtjQddJpLfucQiG
	dxx3jQ1xwVosZChlyU+r5zjshP6FioLSu6jPSi5vnwyh7WH65hAyoa96wFsFfE7/S8x/
	z+qQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=B4TpcOS4u802K1usKNvMvOBHCXxsqj7YwLZ6S/MOjSY=;
	b=G6psl4OGaA5dhvoKjBFOkrzbcGyG2B9d/xBYD3CasRRzeJYkpGPL9H4mFinIVMgZVF
	3v/ruGky3eLEkBTl3sHbhWX+eqFB5oAki6UBlAJ2rRbsnyDphH+G/hFhhjJsO8KIpUbz
	aqaFwbtjwel5aBnwdaXS4skMjltjOzZ3ScN00Or9p0KZv3iINtSXcvKjT0CCeVx+e/5V
	q1z/vK8MTJ242MdYBDJlSlH2yDMY0IJI7JS3DqQ5ZR+DW2QkcBU2HvSkNdwP2ILyxqkm
	BCpRMdYT5L+NW5Itu8OpzLbJIhE6xYyPolY80hixAx5kPf11fm7EppCDmoDvk5izPkzk
	ob+A==
X-Gm-Message-State: AN3rC/7Ag3PQGfVzVYSEBiPGLcyZ/tf0cv/aH5XwMenSHbo7O95HNgU9
	VZ1xp3ZHxtxTjsKG0Jk=
X-Received: by 10.37.35.210 with SMTP id j201mr4031484ybj.103.1493300791732;
	Thu, 27 Apr 2017 06:46:31 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	c128sm1197101ywh.2.2017.04.27.06.46.29 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 06:46:30 -0700 (PDT)
Date: Thu, 27 Apr 2017 09:46:27 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="efua3a52cx655cgz"
Content-Disposition: inline
In-Reply-To: <20170427123033.GC37287@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::235
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 13:46:39 -0000


--efua3a52cx655cgz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-27T14:30:33+0200, Ingo Schwarze wrote:
> Hi,
>=20
> wow, you definitely demonstrate diligence in investigating existing
> usage.
[...]
> That can be summarized as follows:  Legitimate hand-written use is
> almost inexistent, even hand-written abuse is very rare, but unusually
> frequent when expressed as a fraction of the instances of use.  The
> dominant occurence is abuse by known-bad autogenerators.

If this were a matter of preserving compatibility, you'd argue that
breaking 14 man pages out of 7000 is too many.

Let's review, from earlier in the thread:

BR> What I'm hearing is that you feel that man(7) is a lost cause:
BR>
BR> A.  It desparately needs improvement because of its presentational,
BR>     rather than semantic, focus.
BR> B.  Improvement will break portability.
BR>
BR> This basically amounts to doing nothing and letting man(7) die of its
BR> own accord.

IS> Exactly.

> Remeber that writing legacy man(7) documents is quite hard and
> entices many people to try all kinds of (sometimes unavoidable,
> sometimes ill-advised) trickery.  Even when analyzing the use of
> easy-to-use languages in the wild, you usually find substantial (in
> that case, needless) trickery.  So it is actually surprising that
> you found so little.

Yet, somehow, you do not regard this as evidence of the quality of
man(7) nor of the people who write in it.

> So, if we would choose to promote \c use for the FONT_MACRO_C use
> case, we would actually promote using a low-level feature

It's no lower-level than the escapes to which you've given your
blessing; see groff(7) and CSTR #54, where it has parity.

> that is so far virtually unused in the wild,

Hmm.  210 uses out of ~7,000 makes it about twice as popular as mdoc.

$ find man* -type f -and -not -type l | xargs zgrep '^\.Dd' | wc -l
103

> but where existing practice in the wild already demonstrates that
> about 1 out of 3 users who choose to use it freely get it wrong.
> Officially encouraging use is likely to cause an increase rather than
> a decrease of abuse.

That's conjecture.  What I see is a propensity to cut-and-paste from
examples that are believed to be good.  If we provide good examples,
there's no reason to expect abuse to grow.

My expectations are modest: I think a few people will pick it up and use
it correctly, most will continue to live with bad markup, and
practically no one will see \c as a new toy to play with.  Because, you
see, it isn't new--it's very, very old.  Older than, say, mdoc.

> I think your analysis reinforces the argument that we should refrain
> from promoting the use of escape seqeunces in manual pages unless
> they are unavoidable, well-established, *and* easy to understand.
> Typical examples of escapes matching those criteria are \e, \&, \f.

\e is a bad example; in man(7) pages, people use it expecting to it to
do the same thing as \(rs.  Which is fine until some clever wag
redefines the escape character.

Most of the time, \(rs is what people mean, because--in man
pages--they're discussing the backslash symbol outside of the context of
*roff itself.  Almost always, they're telling C and shell programmers
how to escape and quote things.

Regardless, \c obviously has a couple of indispensable use cases in the
man(7) domain.  We should be documenting them, not ignoring them in
hopes people will just throw up their hands and go use mdoc instead.

> It is now demonstrated in the wild that \c misses the last criterium,
> and it is plausible to assume that \! will also miss it.

I think you're indulging deeply in motivated reasoning in service of the
objective we established earlier.  You don't want people to write man(7)
pages well; you want them to write them badly, if they write them at
all, in the hope that the wretchedness of the result will lead them to
the true light of mdoc(7).

In any event, I checked out Heirloom troff.  Unfortunately its CVS
repository has not seen a commit in almost 6 years.  I tried to build it
using Heirloom devtools; that, unfortunately has not seen a commit in
almost 7 years.  Perhaps not surprisingly, when it came time to compile
a C++ file, the build failed.

Are we sure that Heirloom is still maintained?  Is there any other
living troff on the planet?

If not, then I have to conclude that GNU troff _is_ the standard by dint
of being the sole living implementation, and therefore I'm not too
worried about the impact of my proposal regarding TP, which Bjarni
developed independently back in 2014, and with greater generality to
boot.

Nevertheless, if someone can get Heirloom troff building on Debian
stretch, I'm willing to run A/B comparisons to see what, if anything,
breaks.

Out of those ~7000 pages, I haven't seen a single markup error that can
be unquestionably laid at the feet of Bjarni's and my proposal.

At least we can agree that docbook-to-man produces a true dog's
breakfast of output.  Pretty lamentable.

Regards,
Branden

--efua3a52cx655cgz
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkB9iIACgkQ0Z6cfXEm
bc7O5A//YXPOfDr9RkDxyfWwacafC6dCj3o9GWkoUkV7CTnrUozkNzp5p+dN/gT2
iSxp0h14OjumdFY6Z9coAy1l5slZv8cBB/e6PAXO6X6iObpK8LHS2Cn32iCwfhrq
slVjkpnU485adRu/LfoOLlpVEIC/kbVPghG3zoz2Z1prCgh7R+o6nm3bDEe2uqcw
yBnvarivbDOBa9YYsy4+MJCuvpJmr6KNjsDcUi4v65/LoUamoYxTN5A4dMtWKJJD
deuGjndwFkt88jO5urB11GXh25dYy1ONirI9h5CjpidqzKrdoQUd8nt/+/SVVq3w
15z3j0gS12gjWQPWetaoxvY7UDDAr11gmAWf/FHdioLQH12Fch60W4W+RV0zHyc2
WwVRTWj9uGSPKuhqgclPGaRgcSIjx1febC4AaaWi3Ra9ui2tA7NSbIc7OY+s9Ahi
xeZdWnKPq2tBFhDHFZXjuEhU6Hpm0OL/ofJoX7hO0ASybNgxymwJIBUKdp1x1+ts
25+IbWmU3al36dKRK84sYpZ03YdRNPw223AKC/t1o7rP290qdzLYj4w46XjDtgWX
MHdQhc0IUXey1e7Bepl51eN2enkCY7wjK8/Rr1hBofBshyMd2XESJBaxQY69rpri
jYzIY7rfsueoaWC4HvLD1oWMsJ95qoUei/QVw1LDH5M186FmoSE=
=qHT/
-----END PGP SIGNATURE-----

--efua3a52cx655cgz--


From MAILER-DAEMON Thu Apr 27 09:54:34 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3jsQ-0001St-OU
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 09:54:34 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55443)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3jsO-0001Sf-Dh
	for groff@gnu.org; Thu, 27 Apr 2017 09:54:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3jsK-0008Sz-Ij
	for groff@gnu.org; Thu, 27 Apr 2017 09:54:32 -0400
Received: from mail-yb0-x22c.google.com ([2607:f8b0:4002:c09::22c]:36118)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3jsK-0008Sh-BR
	for groff@gnu.org; Thu, 27 Apr 2017 09:54:28 -0400
Received: by mail-yb0-x22c.google.com with SMTP id s22so8097652ybe.3
	for <groff@gnu.org>; Thu, 27 Apr 2017 06:54:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=xvd0Osg+MJK575vqG/Hc4h/tJh1wDbvykMuf+FOstfE=;
	b=Te5gFBmWv3feOH/sDCouXXuBAe9i4/bw6RF/ZkwOX8ulRFlYdrUcQIUTS10qaGUFOG
	UpZbGyo5f51pvoxMp98Mcbs5L+nv2msvcEENo7k65UXhUB+YhQYHmy+fnorceSZct4WE
	c078Lf4tuuoKOUVSMKyS+JqfDN9EKaJ2Qu6H1gBs3EwTmLN/uvowSCdZJxppTldQF8jE
	YW2sMOES1fI+ic765mCH6n/nDV41QR+9a07yS+mRTuIZ1C2irTf9I1BmR+F1GTu3GTJT
	hvqUayQvalSaepTduYsCl9ame4Z/fRp1YmkYEqJEDM2GJ3Gy+oTHgqjYuXFPwKacxStQ
	9iiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=xvd0Osg+MJK575vqG/Hc4h/tJh1wDbvykMuf+FOstfE=;
	b=KL+46he5ay/i25IkFSmMwAByJsCqGq1GN2UmSbXMZT9fRhbcrqtd5OLjeNqHAosVJh
	4QOU74nXZ6+GR3tEQ46MU07x6NxRo4gwMmIoxSatkEOqKi6TRjxB4r2vsbxWJJ8eZH09
	v91qLRZ4kw2w9+NK3Boof2SK185rSI+Grektn/+KcBxQ4A8FZ2Xsp9nyvngEk2pjAGx0
	I7KY5PL0LZ1Y24pyw0O2dY/XyHSnj3AfrX5GvnRDrKu8NUzkdjFZCEamkb/9LpzRFle2
	P9V6vFHymFJM9wyMelG2g+e8fErC3d1bWL58aWIkTKsepPQwfDZXdx6+u6OTxK1nrK92
	QHVw==
X-Gm-Message-State: AN3rC/7KmQ1pneAq6GGNh7GdxodqYbh4clMEY7SGUqVHj/7wKZQkLowe
	1j/HwubIHlGC+r297Hk=
X-Received: by 10.37.165.38 with SMTP id h35mr4342842ybi.118.1493301267348;
	Thu, 27 Apr 2017 06:54:27 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	o186sm1209666ywc.18.2017.04.27.06.54.25 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 06:54:26 -0700 (PDT)
Date: Thu, 27 Apr 2017 09:54:24 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170427135421.yyyn3b6ypb462kuc@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170427040029.GA6144@rhi.hi.is>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="ngtce3rfqhvscb4x"
Content-Disposition: inline
In-Reply-To: <20170427040029.GA6144@rhi.hi.is>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::22c
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 13:54:33 -0000


--ngtce3rfqhvscb4x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-27T04:00:29+0000, Bjarni Ingi Gislason wrote:
> On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote:
> > At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote:
> > > .SM affect the next input line as it uses an input trap, `.it'.  `\c'
> > > doesn't make an input line continue to the next as far as input traps
> > > are concerned;  groff has .itc for that.  So the .SM is over by the `=
)'.
> >=20
> > That's exactly the hack I wanted to make to the TP macro.  I want to
> > change its .it to an itc, thus:
>=20
>   I have made a similar suggestion, see bug number #42907 (or look for
> 'itc').

Thanks, Bjarni!  I'm glad to know that this has occurred to someone
else.

> [...]
> >=20
> > .TP
> > .B \-scale \c
> > .IR xfac [, yfac ]
> > Multiply the horizontal and vertical window size by
> > .I xfac
> > and
> > .IR yfac ,
> > respectively.
> >=20
>=20
>   One can use the transparent line indicator (\!) to use macros in a labe=
l,
> without changing the '.TP' macro:
>=20
> .TH testman 1 2017-04-DD
> .TP
> \!.B \-scale \c=20
> .IR xfac [, yfac ]
> Multiply the horizontal and vertical window size by
>=20
>   or a little different output (with a necessary longer indent):
>=20
> .TH testman 1 2017-04-DD
> .TP 20n
> \!.B \-scale \c
> \!.IR xfac [\c
> \!.B ,\c
> .IR yfac ]
> Multiply the horizontal and vertical window size by

I agree with Ingo that this looks worse, not better, but to me that
suggests we should save our users the pain by implementing the TP/itc
proposal.

I further note for the benefit of those who did not go check out the
bug[1], that your proposal is to consistent make _all_ of the man macros
that set single-line traps switch to .itc from .it.

At some point, if no one beats me to it, I'll make that change locally
and measure the impact.

Regards,
Branden

[1] https://savannah.gnu.org/bugs/?42907

--ngtce3rfqhvscb4x
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkB+A0ACgkQ0Z6cfXEm
bc798g//XTufmDbqVzRex4hJApUB6kEP4hIs/5Iif0y0lU/ubgwy/Czrj1Y+F3N5
O9OyHspZkP3xtbqZbngdMhZXOnix3Tcr+6g1xMH2AlMgOW9GczKHkMgGOfbvyne0
k6sQUgvgD/66x8uNNoMKvlwUKsBUPpV1d9XCCLe/lZjBMuZ0E3W7VTkSoEeABzEu
9crg0JQEqHAN/GXH/L6LYKejObqpcYtMhZ7hm45UZCANQ9JWbkSWVSMNxjeUv/ZD
VnLg8xirVPgwYbcaSaePJCxx5h1vuAtzp/DE/CWuCYknCjPNFsnjD9ftw1sREhx7
NlNjj6A9+Ulk+BoN7ZK8v6JGeR+S3X1+DDNxX1CA6XSYKHP4UaDYjkY4PlSKPyWG
uHO/emi95VTTDZWNVJR9bde671sD2qF9CIo7gOkirgoqz0nYN5NhvZh0ZTcN1AFP
lesQ7/kRyPPJfx1tgGQrF5rZ+iRnj5SAKPf0jjIzUTIY+JrntZAn/x3ekEIbftP2
0CFEhi7EYf7lZIXSqiHNErZVbsGcGTH/IC8dktjeSgr9q244LV2O21+QkWQL0kFA
XBZ069uyptyLWNB1lduAKQWat+77DrBk3dszPapHh+NymprzmSY679BNLEv+v2EU
CPct3Fqc3+jBcFRFVzKBP6TYyXJD+cmQGk/Q8zTNkuej5mcPFLY=
=HTy3
-----END PGP SIGNATURE-----

--ngtce3rfqhvscb4x--


From MAILER-DAEMON Thu Apr 27 10:54:18 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3koD-0004Pm-VA
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 10:54:17 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46291)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aksr@t-com.me>) id 1d3koB-0004Ol-No
	for groff@gnu.org; Thu, 27 Apr 2017 10:54:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aksr@t-com.me>) id 1d3ko7-0000vv-Rf
	for groff@gnu.org; Thu, 27 Apr 2017 10:54:15 -0400
Received: from mx18.t-com.me ([213.149.114.171]:16914)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <aksr@t-com.me>) id 1d3ko7-0000op-Ed
	for groff@gnu.org; Thu, 27 Apr 2017 10:54:11 -0400
Received: (qmail 9078 invoked by uid 8); 27 Apr 2017 14:53:56 -0000
X-Qmail-Scanner-Diagnostics: from adsl-46-33-l21160.crnagora.net
	(aksr@adsl-46-33-l21160.crnagora.net) by mx18.t-com.me
	(envelope-from <aksr@t-com.me>,
	uid 108) with qmail-scanner-2.10 
	(spamassassin: 3.3.2.  
	Clear:RC:0(46.33.213.160):SA:0(-2.7/4.5):. 
	Processed in 6.439862 secs); 27 Apr 2017 14:53:56 -0000
X-OpenMX-Version: 1.4
X-OpenMX-Size: 1333
Received: from adsl-46-33-l21160.crnagora.net (HELO lap) (aksr@46.33.213.160)
	by mx18.t-com.me with ESMTPA; 27 Apr 2017 14:53:50 -0000
Date: Thu, 27 Apr 2017 16:53:45 +0200
From: aksr <aksr@t-com.me>
To: groff@gnu.org
Message-ID: <20170427145345.GA21070@lap>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
User-Agent: Mutt/1.8.2 (2017-04-18)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
	[fuzzy]
X-Received-From: 213.149.114.171
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 14:54:17 -0000

On Thu, Apr 27, 2017 at 09:46:27AM -0400, G. Branden Robinson wrote:
> In any event, I checked out Heirloom troff.  Unfortunately its CVS
> repository has not seen a commit in almost 6 years.  I tried to build it
> using Heirloom devtools; that, unfortunately has not seen a commit in
> almost 7 years.  Perhaps not surprisingly, when it came time to compile
> a C++ file, the build failed.
> 
> Are we sure that Heirloom is still maintained?  Is there any other
> living troff on the planet?

https://github.com/n-t-roff/heirloom-doctools


From MAILER-DAEMON Thu Apr 27 11:10:08 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3l3X-0002XN-AE
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 11:10:08 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55139)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3l3Q-0002UV-Fa
	for groff@gnu.org; Thu, 27 Apr 2017 11:10:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3l3N-0001WI-Ab
	for groff@gnu.org; Thu, 27 Apr 2017 11:10:00 -0400
Received: from mail-yw0-x236.google.com ([2607:f8b0:4002:c05::236]:36224)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3l3N-0001W0-5b
	for groff@gnu.org; Thu, 27 Apr 2017 11:09:57 -0400
Received: by mail-yw0-x236.google.com with SMTP id l18so17061200ywh.3
	for <groff@gnu.org>; Thu, 27 Apr 2017 08:09:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=xjS10poV8QjFBmNdhi42tggFVHbRA24paGI6FNCUaBQ=;
	b=V2zCCyIo77+LZCeUSaNyxWF+RswvUV3pvXwIX4h1Q6jNempzLQ9oJ0i76KO5ZnREAu
	aofX1dq1FOgdbdBabwBxba2gekhJd/y8hry2FwMYqopX6q9adiwbTpxjubGg9SpSlXti
	pm7twwtxW4ZKs/MiWmpaL3hH6DwEC6Q90ROz/oJ2/qwmsLacxU6ZrdHwpbO1nf9abAYq
	gF3lIivfHUv9zBNcmRZDpQFFeyxO1uvDo9pJHur4bzfoO7lQPosl/AmZCxLY10Pl3o5/
	wSZGVmWPdjO/toc7SEwxT1FRNNPv46H1yDCai6w0L+kJXDPp75XPU1mUv4nSS3QXaAiN
	VJdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=xjS10poV8QjFBmNdhi42tggFVHbRA24paGI6FNCUaBQ=;
	b=RpNaKyVxc98aONzryA9ew7vp9/YVoFs36Dnb+pCfB4pK8I9/ADIMnbD8sqBTBWTLXj
	HF7pWOyDmITEw10kGNPgjzyTC5X/xWs5l6vaNmZZrh7EeK+rmknxXue5cNxAf0Gl9rUY
	GMqydbXCZC7PKOU1pzCEqvK5ee+UH5gX+4Ot8QIG345QIvKuPCuK/KEUbV9oawkMIPqe
	C2BI82BTCu1xGYitP2yn8b94SciasIDFjATrzNzjpmACocHQamiZpxw8BmOCQk6P8ZfR
	4M1uBMDPbbf4uEJIuDSpGQGqAYy91bIQbFKSU8vvjcAttp3+EWHVBb7JNwsJ2dn4qYBS
	GX1w==
X-Gm-Message-State: AN3rC/4VtmsTXGUlN/B/GqCgF2IL/0PVdEjt+7yz88prbmwNc+/TgkT4
	roVLH5h2y1xyB8jk76I=
X-Received: by 10.129.173.23 with SMTP id l23mr4739786ywh.28.1493305796194;
	Thu, 27 Apr 2017 08:09:56 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	w201sm1204158ywg.6.2017.04.27.08.09.54 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 08:09:55 -0700 (PDT)
Date: Thu, 27 Apr 2017 11:09:52 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170427150950.yb73pppdhswe7hcz@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
	<20170427145345.GA21070@lap>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="dowxkwguv2b3lgux"
Content-Disposition: inline
In-Reply-To: <20170427145345.GA21070@lap>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::236
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 15:10:05 -0000


--dowxkwguv2b3lgux
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-27T16:53:45+0200, aksr wrote:
> On Thu, Apr 27, 2017 at 09:46:27AM -0400, G. Branden Robinson wrote:
> > In any event, I checked out Heirloom troff.  Unfortunately its CVS
> > repository has not seen a commit in almost 6 years.  I tried to build it
> > using Heirloom devtools; that, unfortunately has not seen a commit in
> > almost 7 years.  Perhaps not surprisingly, when it came time to compile
> > a C++ file, the build failed.
> >=20
> > Are we sure that Heirloom is still maintained?  Is there any other
> > living troff on the planet?
>=20
> https://github.com/n-t-roff/heirloom-doctools

Thanks!  My bad for trusting Google.

Looks like it's pseudonymously maintained these days!

It builds.  Just gotta do some installation path finaglement.

Regards,
Branden

--dowxkwguv2b3lgux
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkCCa0ACgkQ0Z6cfXEm
bc4bBQ/+OfvHg8s7Vw8rOYkTGOKoZFnkw1djuUbS0UAPw5e6FHcbdkuLYDtUFc3E
+1ex6I0n5jizptgxTqPd7LHJTzDl9zMOf/mndPLTa9wD3gpGBt8LBzU/Kf7C7R0e
mV++Bqw3bq3a5Z/hYs0szm5IdA8AjNwp2abgl/3ck/k5P+S9lHkbMznyWJMvrPRV
OL+A2rlPZh8eG7fmVnbanvL6tzjoO8e8/SoLlt0lATqBhUx8hW+jbnoXUQbJpH0U
1o9RS4/fT4/2vnlpE1B28+QXVvbcx62+rG4vefgBQPSjXjsWowiM2L/M8OOoDlwx
jslt70M7sSFUX5PfvSiPSDlCLyN5w4iKInMEEgl4uIEXX3xdicZI+gY26Xcy4Q19
3tE4hdR78FJQCgpzSxDcapuiLreSBuTgNChm945ITqOUKo9l2nlGA9P5mlYGt1ws
qnJBGXIahW95taduf41Rs5wFIQkCLSsTZAxoCaiSCA7Opqv5Afv7GvIrWbtWwx0q
pXxTJq95camEH1/B1iPVGgJkFR00DMFpXQTJYRyF96Q7O6biCWAfDbCpnkUngmnH
y8gA9i3SU/uPKUtAQNOV9HCu9GeGJKe1ZI5ak1IsZIsfBX2A96FVWIF3TFW2vG1Z
IjFISTLaNQOyYajQxfi4Uf17jS0L82vwZlOi7pAA+E7R7ctZTUI=
=8/zG
-----END PGP SIGNATURE-----

--dowxkwguv2b3lgux--


From MAILER-DAEMON Thu Apr 27 11:37:30 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3lU2-0004OO-26
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 11:37:30 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37337)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3lTy-0004Im-Au
	for groff@gnu.org; Thu, 27 Apr 2017 11:37:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3lTw-00085z-7u
	for groff@gnu.org; Thu, 27 Apr 2017 11:37:26 -0400
Received: from scc-mailout-kit-01.scc.kit.edu
	([2a00:1398:9:f712::810d:e751]:42806)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3lTv-00085D-US
	for groff@gnu.org; Thu, 27 Apr 2017 11:37:24 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3lTp-0006rr-3w; Thu, 27 Apr 2017 17:37:21 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3lTo-0003QJ-4H; Thu, 27 Apr 2017 17:37:16 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3lTn-0007kd-Ux; Thu, 27 Apr 2017 17:37:16 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id f54ff338;
	Thu, 27 Apr 2017 17:37:15 +0200 (CEST)
Date: Thu, 27 Apr 2017 17:37:15 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170427153715.GE37287@athene.usta.de>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e751
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 15:37:28 -0000

Hi,

G. Branden Robinson wrote on Thu, Apr 27, 2017 at 09:46:27AM -0400:
> At 2017-04-27T14:30:33+0200, Ingo Schwarze wrote:

>> wow, you definitely demonstrate diligence in investigating existing
>> usage.
> [...]
>> That can be summarized as follows:  Legitimate hand-written use is
>> almost inexistent, even hand-written abuse is very rare, but unusually
>> frequent when expressed as a fraction of the instances of use.  The
>> dominant occurence is abuse by known-bad autogenerators.

> If this were a matter of preserving compatibility, you'd argue that
> breaking 14 man pages out of 7000 is too many.

Sorry, i don't follow.  Nobody suggested deleting \c from roff.

All i said regarding portability is that implemeting your .TP .itc
in groff, Heirloom, and mandoc and recommending use of \c after .TP
means that *all* pages doing that misrender on all systems using
either older versions of our formatters or legacy formatters.

If a significant language improvement would break 0.2% of existing
manuals, i'd certainly consider going ahead with it and doing the
handful of commits required / sending out the handful of patches
required, but i don't see how that is related to the discussion.

> Let's review, from earlier in the thread:
> 
> BR> What I'm hearing is that you feel that man(7) is a lost cause:
> BR>
> BR> A.  It desparately needs improvement because of its presentational,
> BR>     rather than semantic, focus.
> BR> B.  Improvement will break portability.
> BR>
> BR> This basically amounts to doing nothing and letting man(7) die of
> BR> its own accord.
> 
> IS> Exactly.
> 
>> Remeber that writing legacy man(7) documents is quite hard and
>> entices many people to try all kinds of (sometimes unavoidable,
>> sometimes ill-advised) trickery.  Even when analyzing the use of
>> easy-to-use languages in the wild, you usually find substantial (in
>> that case, needless) trickery.  So it is actually surprising that
>> you found so little.

> Yet, somehow, you do not regard this as evidence of the quality of
> man(7) nor of the people who write in it.

No, it is not, because you can find lots and lots of poorly written
man(7) documents in the wild, even hand-written ones.  All it tells
us is that \c is exceedingly rare in manual pages - both (arguable)
legitimate uses and abuses.  That doesn't imply there aren't other
common problems; in fact, there are.

>> So, if we would choose to promote \c use for the FONT_MACRO_C use
>> case, we would actually promote using a low-level feature

> It's no lower-level than the escapes to which you've given your
> blessing; see groff(7) and CSTR #54, where it has parity.

Admitted.  \f etc. is also low-level.  But it is simpler.

>> that is so far virtually unused in the wild,
 
> Hmm.  210 uses out of ~7,000 makes it about twice as popular as mdoc.
> 
> $ find man* -type f -and -not -type l | xargs zgrep '^\.Dd' | wc -l
> 103

Only if you don't count the about 3000 mdoc(7) manuals in a typical
*BSD base system.  If you count those, \c is about 2% (abuse by
docbook included), mdoc(7) is about 30%.

>> but where existing practice in the wild already demonstrates that
>> about 1 out of 3 users who choose to use it freely get it wrong.
>> Officially encouraging use is likely to cause an increase rather than
>> a decrease of abuse.

> That's conjecture.

Admitted.

> What I see is a propensity to cut-and-paste from examples that are
> believed to be good.  If we provide good examples, there's no reason
> to expect abuse to grow.
> 
> My expectations are modest: I think a few people will pick it up and use
> it correctly, most will continue to live with bad markup,

.TP
\fB\-scale\fP \fIxfac\fP[,\fIyfac\fP]

is not bad markup, but decent quality man(7) code that i would
recommend.

> and practically no one will see \c as a new toy to play with.

That might turn out to be true; it's also plausible conjecture,
even though you already reported \c cargo culting right now.

>> I think your analysis reinforces the argument that we should refrain
>> from promoting the use of escape seqeunces in manual pages unless
>> they are unavoidable, well-established, *and* easy to understand.
>> Typical examples of escapes matching those criteria are \e, \&, \f.

> \e is a bad example; in man(7) pages, people use it expecting to it to
> do the same thing as \(rs.  Which is fine until some clever wag
> redefines the escape character.
> 
> Most of the time, \(rs is what people mean, because--in man
> pages--they're discussing the backslash symbol outside of the context of
> *roff itself.  Almost always, they're telling C and shell programmers
> how to escape and quote things.

Here you probably have half a point.  I should probably go ahead
and change the mandoc documentation to recommend \(rs rather than
\e for newly written manual pages.

Scouring the existing manuals is maybe not worth the substatial
amount of work required, because there is no problem in practice:
if someone uses .ec *in a manual page* (seriously?) they are already
responsible for writing \ for \ after that, and "xe" for "x" if
they said, for example, ".ec x".

Besides, if somebody would dare to use .ec in an OpenBSD manual
page, they would be shot and killed almost instantly from multiple
directions, and i guess quite a few other communities would behave
in a similar way.

The reason why manual pages almost consistently use \e rather than \(rs
is that, as far as i see, \(rs did not exist in CSTR54, the beginnings
of many manual pages predate CSTR54, and the recommendation how to
encode backslashes in manual pages that one finds in documentation
predate CSTR54 in any case.

For example, even groff(7) still says:

  Printable backslashes must be denoted as \e.  To be more
  precise, \e represents the current escape character.
  To get a backslash glyph, use \(rs or \[rs].

That has already been improved substantially, but it could maybe
still be worded better.

> Regardless, \c obviously has a couple of indispensable use cases in the
> man(7) domain.  We should be documenting them, not ignoring them in
> hopes people will just throw up their hands and go use mdoc instead.

Document, sure.  Indispensable, no; i have seen none that \f cannot
solve, and \f seems simpler than \c.

>> It is now demonstrated in the wild that \c misses the last criterium,
>> and it is plausible to assume that \! will also miss it.

> I think you're indulging deeply in motivated reasoning in service of the
> objective we established earlier.  You don't want people to write man(7)
> pages well; you want them to write them badly, if they write them at
> all, in the hope that the wretchedness of the result will lead them to
> the true light of mdoc(7).

No, that's not what i want, and that would also be foolish.
Frustrating *users* with badly written manuals helps nothing.
Even frustrating *authors* does not help and does not force good
decisions: it would also increase the risk that authors abandon
manual pages (and roff) outright.  I think i even explicitly said
that helping people to write better man(7) is good.  There are
circumstances where writing man(7) is still required.  Project
policies are merely one example.

All i say is that man(7) will remain hard even with such help,
and that incompatible changes have more downsides in man(7)
than they have in mdoc(7).

> In any event, I checked out Heirloom troff.  Unfortunately its CVS
> repository has not seen a commit in almost 6 years.

You must have looked in the wrong place.  Try

  http://n-t-roff.github.io/heirloom/doctools.html
  https://github.com/n-t-roff/heirloom-doctools/

as linked from

  http://mdocml.bsd.lv/links.html

> Are we sure that Heirloom is still maintained?

Absolutely.  Carsten Kunze maintains it.  He is also one of the
most active groff committers and regularly follows this list.

> Is there any other living troff on the planet?

There is

  https://swtch.com/plan9port/

I think it is neither as good nor as vital as Heirloom, and i'm not
sure to which degree it is alive, but it does exist, and some
operating systems provide it in packaged form (even OpenBSD).  The
Plan9 roff does run on OpenBSD and it is possible to read manual
pages with it, but i neither claim that it works very well nor that
it is broken in any particular way, i simply never really looked
at it in sufficent detail to judge it.

Then there is the roff in commercial Solaris (maybe somewhat
related to Heirloom, but certainly not following current Heirloom
development closely).

AT&T DWB has also been kind of released, but i doubt that "alive"
is the right word to use for it - besides, it looks like AT&T
broke the URI once again:

  http://www2.research.att.com/sw/download

But Carsten Kunze checked it in here:

  https://github.com/n-t-roff/DWB3.3

Finally, there are a number of very obscure implementations,
maybe irrelevant, maybe not:

  http://repo.or.cz/w/neatroff.git = http://litcave.rudi.ir/
  http://www.nesssoftware.com/home/mwc/source.php
  ...

It looks like https://github.com/jgm/pandoc/ can only write,
but not parse manual pages.

It is likely that there are more implementations than i know of,
and some may well be alive.  Besides, i did not even try to list
ad-hoc non-roff man(7) parsers.

> If not, then I have to conclude that GNU troff _is_ the standard

I fully concur.  GNU troff has been the de-facto roff standard for
about 20 years now, in particular on all systems that are somehow
related to Linux or BSD.

> by dint of being the sole living implementation,

Not the sole, but the leading one by far.

> and therefore I'm not too worried about the impact of my proposal
> regarding TP, which Bjarni developed independently back in 2014,
> and with greater generality to boot.
> 
> Nevertheless, if someone can get Heirloom troff building on Debian
> stretch, I'm willing to run A/B comparisons to see what, if anything,
> breaks.

Heirloom and mandoc are not the problem.  If groff goes your way in
this respect, i will make mandoc follow, and it seems liekly to me
that Carsten will eventually make Heirloom follow as well.

> Out of those ~7000 pages, I haven't seen a single markup error that can
> be unquestionably laid at the feet of Bjarni's and my proposal.

Did you test your proposed new syntax (.TP using \c to include
two macro lines in the head) on

 - Oracle Solaris 9, 10, or 11
 - illumos
 - Plan9 (not sure whether that is still relevant)
 - DWB (may well be irrelevant by now)
 - Any other commercial system like HP-UX, AIX, etc.: i don't
   have the slightest idea what those systems use today.

> At least we can agree that docbook-to-man produces a true dog's
> breakfast of output.  Pretty lamentable.

Indeed.

Yours,
  Ingo


From MAILER-DAEMON Thu Apr 27 14:12:18 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3ntq-0004qS-3G
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 14:12:18 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47478)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3nto-0004lq-5P
	for groff@gnu.org; Thu, 27 Apr 2017 14:12:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d3ntm-00047N-VI
	for groff@gnu.org; Thu, 27 Apr 2017 14:12:16 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:53905)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d3ntm-00044a-Ot
	for groff@gnu.org; Thu, 27 Apr 2017 14:12:14 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d3nti-00074n-3I; Thu, 27 Apr 2017 20:12:11 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d3nth-0006gN-ID; Thu, 27 Apr 2017 20:12:09 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d3nth-00028B-CC; Thu, 27 Apr 2017 20:12:09 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 108a310c;
	Thu, 27 Apr 2017 20:12:09 +0200 (CEST)
Date: Thu, 27 Apr 2017 20:12:09 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
Cc: groff@gnu.org
Message-ID: <20170427181209.GI37287@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170425181921.kz2kB%steffen@sdaoden.eu>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 18:12:17 -0000

Hi,

Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:

> the HTML output of mandoc used repeated per-paragraph style
> directives and a CSS file, which caused enormous bloat, last
> time i tried.

Does that still apply to

  view-source:http://man.openbsd.org/ksh

I spent a few weeks in 2017 improving mandoc HTML output,
both with respect to functionality (better markup) and with
respect to HTML code quality.

In case there are still aspects that can be improved (in particular,
simplified) without loss of semantic markup quality and without
loss of presentational quality, specific hints are very welcome.

Yours,
  Ingo


P.S.
Only bacause i'm replying anyway and it's just five lines:

>   .Op : Ns Fl c Ar cc-addr Ns \&:
>   .Fl S Ar var Ns Op Ns = Ns Ar value Ns

That's full of cargo cult, things are actually much simpler
even for describing such unusually complicated syntax:

.Oo : Ns Fl c Ar cc-addr : Oc
.Eo [: Fl c Ar cc-addr Ec :]

.Fl S Ar var Ns Op = Ns Ar value
.Fl S Ar var Ns Op Pf = Ar value


From MAILER-DAEMON Thu Apr 27 15:32:54 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3p9q-00089s-Ja
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 15:32:54 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38428)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bjarniig@hi.is>) id 1d3p9p-00089j-5e
	for groff@gnu.org; Thu, 27 Apr 2017 15:32:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bjarniig@hi.is>) id 1d3p9o-0002Tf-2N
	for groff@gnu.org; Thu, 27 Apr 2017 15:32:53 -0400
Received: from mx1.hi.is ([2a00:c88:4000:1650::165:103]:50286)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <bjarniig@hi.is>) id 1d3p9n-0002Sc-Ll
	for groff@gnu.org; Thu, 27 Apr 2017 15:32:51 -0400
Received: from hekla.rhi.hi.is (hekla.rhi.hi.is
	[IPv6:2a00:c88:4000:1650::165:2])
	by mx1.hi.is (8.14.7/8.14.7) with ESMTP id v3RJBTV3023898
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=NO); Thu, 27 Apr 2017 19:11:31 GMT
Received: from hekla.rhi.hi.is (localhost [127.0.0.1])
	by hekla.rhi.hi.is (8.14.4/8.14.4) with ESMTP id v3RJBTZ9010951;
	Thu, 27 Apr 2017 19:11:29 GMT
Received: (from bjarniig@localhost)
	by hekla.rhi.hi.is (8.14.4/8.14.4/Submit) id v3RJBTfO010950;
	Thu, 27 Apr 2017 19:11:29 GMT
Date: Thu, 27 Apr 2017 19:11:29 +0000
From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170427191128.GA4772@rhi.hi.is>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
User-Agent: Mutt/1.5.20 (2009-12-10)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:c88:4000:1650::165:103
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 19:32:54 -0000

On Wed, Apr 26, 2017 at 11:54:21AM -0400, G. Branden Robinson wrote:
> At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote:

[...]

> >   ??? .IR being is just a shorthand for `\f' and `\^' that can be done
> >     manually when needed, e.g. `.TH'.
> 
> FYI, .IR does not give you this "italic correction" in groff 1.22.3:
> 
> 	.de1 IR
> 	.  if \\n[.$] \{\
> 	.    ds an-result \&\f[I]\\$1\f[R]\"
> 	.    shift
> 	.    while (\\n[.$] >= 2) \{\
> 	.      as an-result \/\\$1\f[I]\,\\$2\f[R]\"
> 	.      shift 2
> 	.    \}
> 	.    if \\n[.$] .as an-result \/\\$1\"
> 	\\*[an-result]
> 	.    ft R
> 	.  \}
> 	..
> 

  I reported this bug (and in '.IB') in August 2014, #42906

-- 
Bjarni I. Gislason


From MAILER-DAEMON Thu Apr 27 15:44:26 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3pL0-0002A1-22
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 15:44:26 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41028)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3pKx-00029u-Ll
	for groff@gnu.org; Thu, 27 Apr 2017 15:44:24 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3pKu-00078n-IY
	for groff@gnu.org; Thu, 27 Apr 2017 15:44:23 -0400
Received: from queue01b.mail.zen.net.uk ([212.23.3.242]:35375)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3pKu-00071H-Bw
	for groff@gnu.org; Thu, 27 Apr 2017 15:44:20 -0400
Received: from [212.23.1.1] (helo=smarthost01a.mail.zen.net.uk)
	by queue01b.mail.zen.net.uk with esmtp (Exim 4.72)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3pKf-0005qh-On
	for groff@gnu.org; Thu, 27 Apr 2017 19:44:05 +0000
Received: from [82.71.22.80] (helo=pip.chuzzlewit.co.uk)
	by smarthost01a.mail.zen.net.uk with esmtpsa
	(TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3pKe-000EbC-N9
	for groff@gnu.org; Thu, 27 Apr 2017 19:44:04 +0000
From: Deri James <deri@chuzzlewit.myzen.co.uk>
To: groff@gnu.org
Date: Thu, 27 Apr 2017 20:44:04 +0100
Message-ID: <10251651.1Zt5jh898W@pip.chuzzlewit.co.uk>
User-Agent: KMail/4.14.5 (Linux/4.4.59-desktop-1.mga5; KDE/4.14.30; x86_64; ; )
In-Reply-To: <20170427181209.GI37287@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
MIME-Version: 1.0
X-Originating-smarthost01a-IP: [82.71.22.80]
Feedback-ID: 82.71.22.80
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x [fuzzy]
X-Received-From: 212.23.3.242
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7Bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 19:44:24 -0000

On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote:
> Does that still apply to
> 
>   view-source:http://man.openbsd.org/ksh

compared with a PDF version:-

http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

From MAILER-DAEMON Thu Apr 27 17:46:13 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3rEr-0007De-Gp
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 17:46:13 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41070)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rEp-0007DW-3z
	for groff@gnu.org; Thu, 27 Apr 2017 17:46:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rEl-0003Zy-5e
	for groff@gnu.org; Thu, 27 Apr 2017 17:46:11 -0400
Received: from sdaoden.eu ([217.144.132.164]:38852)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rEk-0003YF-Tm
	for groff@gnu.org; Thu, 27 Apr 2017 17:46:07 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 6CE4C16056; Thu, 27 Apr 2017 23:46:05 +0200 (CEST)
Date: Thu, 27 Apr 2017 23:46:34 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: groff@gnu.org
Message-ID: <20170427214634.Y8Kbn%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
In-Reply-To: <20170427181209.GI37287@athene.usta.de>
Mail-Followup-To: Ingo Schwarze <schwarze@usta.de>, groff@gnu.org
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 21:46:12 -0000

Ingo Schwarze <schwarze@usta.de> wrote:
 |Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
 |> the HTML output of mandoc used repeated per-paragraph style
 |> directives and a CSS file, which caused enormous bloat, last
 |> time i tried.
 |
 |Does that still apply to
 |
 |  view-source:http://man.openbsd.org/ksh
 |
 |I spent a few weeks in 2017 improving mandoc HTML output,
 |both with respect to functionality (better markup) and with
 |respect to HTML code quality.

It seems to have improved.  I would not be the first who is
astonished about the title attributes, but i still see quite some
style="margin-left: 6.60ex;" and also style="margin-top: 0.00em;".
It surely will be iterated over as time goes by.  I.e., having
a special class "Bl-item-compact" which inherits that
style="margin-top: 0.00em;" to all of its items.

 |In case there are still aspects that can be improved (in particular,
 |simplified) without loss of semantic markup quality and without
 |loss of presentational quality, specific hints are very welcome.

As above.  That is all for today, i spent three hopeless hours in
the pic lex code, even shallow cloned 67 MB of gnulib for a few KB
of datatable that doesn't get used the right way, and felt more
and more scatological.

 |P.S.
 |Only bacause i'm replying anyway and it's just five lines:

Sure.

 |>   .Op : Ns Fl c Ar cc-addr Ns \&:
 |>   .Fl S Ar var Ns Op Ns = Ns Ar value Ns
 |
 |That's full of cargo cult, things are actually much simpler
 |even for describing such unusually complicated syntax:
 |
 |.Oo : Ns Fl c Ar cc-addr : Oc
 |.Eo [: Fl c Ar cc-addr Ec :]

  .Op : Ns Fl c Ar cc-addr Ns \&:
  .Eo [: Fl c Ar cc-addr Ns :] Ec
  .Oo : Ns Fl c Ar cc-addr : Oc

I would like the last one best, if the Ns could go from the front.
.Eo, hmm this is in SYNOPSIS.  But yes, .Oo is better.  Also

  .Op Fl M Ar type | Fl m Ar file | Fl q Ar file | Fl t

will i think become

  .Oo Fl M Ar type | Fl m Ar file | Fl q Ar file | Fl t Oc

because that is better.  ^.^

 |.Fl S Ar var Ns Op = Ns Ar value
 |.Fl S Ar var Ns Op Pf = Ar value

That indeed is

  .Oo : Ns
  .Fl S Ar var Ns Op Ns = Ns Ar value Ns
  .Pf \&: Oc

Do you have any idea (and yes, i use .Pf, why not also before the
=, i don;t know) how to place this on one line?
Will do, ciao.

--steffen


From MAILER-DAEMON Thu Apr 27 17:48:06 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3rGg-0008Dn-9H
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 17:48:06 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41891)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rGe-0008Dh-To
	for groff@gnu.org; Thu, 27 Apr 2017 17:48:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rGb-0004qX-0p
	for groff@gnu.org; Thu, 27 Apr 2017 17:48:04 -0400
Received: from sdaoden.eu ([217.144.132.164]:38854)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d3rGa-0004qH-Q4
	for groff@gnu.org; Thu, 27 Apr 2017 17:48:00 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 38A6E16056; Thu, 27 Apr 2017 23:48:00 +0200 (CEST)
Date: Thu, 27 Apr 2017 23:48:29 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Deri James <deri@chuzzlewit.myzen.co.uk>
Cc: groff@gnu.org
Message-ID: <20170427214829.HhjoE%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<10251651.1Zt5jh898W@pip.chuzzlewit.co.uk>
In-Reply-To: <10251651.1Zt5jh898W@pip.chuzzlewit.co.uk>
Mail-Followup-To: groff@gnu.org,
 Deri James <deri@chuzzlewit.myzen.co.uk>
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 21:48:06 -0000

Deri James <deri@chuzzlewit.myzen.co.uk> wrote:
 |On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote:
 |> Does that still apply to
 |> 
 |>   view-source:http://man.openbsd.org/ksh
 |
 |compared with a PDF version:-
 |
 |http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

Terrible, see the spacing errors surrounding the command list
before the "Substitution" heading!  Not your fault of course, but
grrrrr...

--steffen


From MAILER-DAEMON Thu Apr 27 20:19:50 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3tdW-0007vM-4W
	for mharc-groff@gnu.org; Thu, 27 Apr 2017 20:19:50 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45772)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3tdT-0007vE-Aj
	for groff@gnu.org; Thu, 27 Apr 2017 20:19:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3tdP-0002FV-VY
	for groff@gnu.org; Thu, 27 Apr 2017 20:19:47 -0400
Received: from smarthost01a.mail.zen.net.uk ([212.23.1.1]:51537)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3tdP-0002Ex-Q9
	for groff@gnu.org; Thu, 27 Apr 2017 20:19:43 -0400
Received: from [82.71.22.80] (helo=pip.chuzzlewit.co.uk)
	by smarthost01a.mail.zen.net.uk with esmtpsa
	(TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80)
	(envelope-from <deri@chuzzlewit.myzen.co.uk>) id 1d3tdO-000GAY-8M
	for groff@gnu.org; Fri, 28 Apr 2017 00:19:42 +0000
From: Deri James <deri@chuzzlewit.myzen.co.uk>
To: groff@gnu.org
Date: Fri, 28 Apr 2017 01:19:41 +0100
Message-ID: <2968858.L7YnZTQ9kF@pip.chuzzlewit.co.uk>
User-Agent: KMail/4.14.5 (Linux/4.4.59-desktop-1.mga5; KDE/4.14.30; x86_64; ; )
In-Reply-To: <20170427214829.HhjoE%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<10251651.1Zt5jh898W@pip.chuzzlewit.co.uk>
	<20170427214829.HhjoE%steffen@sdaoden.eu>
MIME-Version: 1.0
X-Originating-smarthost01a-IP: [82.71.22.80]
Feedback-ID: 82.71.22.80
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 212.23.1.1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7Bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 00:19:48 -0000

On Thu 27 Apr 2017 23:48:29 Steffen Nurpmeso wrote:
> Terrible, see the spacing errors surrounding the command list
> before the "Substitution" heading!  Not your fault of course, but
> grrrrr...
> 
> --steffen

Well, turns out it WAS my fault! Bug in gropdf, will commit after more 
testing. Thanks for the heads up, is this Ok?

http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

From MAILER-DAEMON Fri Apr 28 00:14:15 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3xIN-0005j3-Lc
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 00:14:15 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42883)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d3xIL-0005ip-7Z
	for groff@gnu.org; Fri, 28 Apr 2017 00:14:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d3xIG-0003gV-96
	for groff@gnu.org; Fri, 28 Apr 2017 00:14:13 -0400
Received: from rrcs-50-74-108-158.nyc.biz.rr.com ([50.74.108.158]:62175
	helo=mail.schemamania.org) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d3xIG-0003gD-3Z
	for groff@gnu.org; Fri, 28 Apr 2017 00:14:08 -0400
Received: from oak.schemamania.org (localhost [IPv6:::1])
	by mail.schemamania.org (Postfix) with ESMTP id 6EC4C256F7C3
	for <groff@gnu.org>; Thu, 27 Apr 2017 23:38:23 -0400 (EDT)
Date: Thu, 27 Apr 2017 23:38:23 -0400
From: "James K. Lowden" <jklowden@schemamania.org>
To: groff@gnu.org
Message-Id: <20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
In-Reply-To: <20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
Reply-To: groff@gnu.org
X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; x86_64--netbsd)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 50.74.108.158
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 04:14:14 -0000

On Wed, 26 Apr 2017 09:46:43 -0400
"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:

> 1. The slavish devotion to two-letter names for things, which like the
>    man macro package and the oldest parts of *roff itself, make it
>    self-anti-documenting.  

Having written one user guide in DocBook, I have to disagree.  

The troff system was designed to be typed at a keyboard.  The
dot-on-the-left rule might be ugly, and the requests/macros terse,
but the benefit to the user is relatively few keystrokes above those
needed for the text.  The nearest modern cousin might be HTML, with its
single-letter tags. 

Most SGML derivatives, on the other hand, presupposed Interleaf-like
tools that would shield users from the markup syntax. That "assume a can
opener" design theory freed them to be verbose. When the tools never
materialized, users started looking for a way to avoid their verbosity
tax.  Markdown is only the latest product of that search.  

Short names are actually *easier* to use than long ones!  Why?  

	Brevity rewards experience.  

If .SH or .Sx is hard to read, they're also easy to write, and easy to
remember when transferring them from the manpage to the document at
hand.  If it's hard to remember what the "next page" request is, .bp is
no harder than remembering whether it's .BreakPage or .PageBreak.  

Stroustrup has an interesting observation about language brevity based
on the evolution of C++.  Users, he says, want novel features to be
"loud" and well-understood paradigms to be terse.  Trouble is, today's
novel is tomorrow's obvious.  As a result, C++ has been losing syntax,
making implicit that which 20 years ago was explicit.  But, of course,
the new language features recently added are "loud".  

In today's world, to most programmers troff is 100% novel, and they find
its terseness inscrutable and off-putting.  Too hard to understand!  

Ah.  But so easy to use.  

--jkl







From MAILER-DAEMON Fri Apr 28 00:43:13 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3xkP-00016x-FR
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 00:43:13 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52931)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <damianm@esi.com.au>) id 1d3xkN-00016m-WA
	for groff@gnu.org; Fri, 28 Apr 2017 00:43:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <damianm@esi.com.au>) id 1d3xkK-0002eV-V6
	for groff@gnu.org; Fri, 28 Apr 2017 00:43:12 -0400
Received: from key0.esi.com.au ([192.84.230.32]:51913 helo=key0l.esi.com.au)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <damianm@esi.com.au>) id 1d3xkK-0002V6-Iu
	for groff@gnu.org; Fri, 28 Apr 2017 00:43:08 -0400
Received: from key0.esi.com.au (key0l.esi.com.au [127.0.0.1])
	by key0l.esi.com.au (Postfix) with ESMTP id CB6D9802F6
	for <groff@gnu.org>; Fri, 28 Apr 2017 14:42:47 +1000 (AEST)
Received: from localhost (damianm@localhost)
	by key0.esi.com.au (8.14.4/8.14.4/Submit) with ESMTP id v3S4glhL012287
	for <groff@gnu.org>; Fri, 28 Apr 2017 14:42:47 +1000
X-Authentication-Warning: key0.esi.com.au: damianm owned process doing -bs
Date: Fri, 28 Apr 2017 14:42:47 +1000 (AEST)
From: Damian McGuckin <damianm@esi.com.au>
To: groff@gnu.org
In-Reply-To: <20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
Message-ID: <alpine.LRH.2.02.1704281436340.11947@key0.esi.com.au>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 192.84.230.32
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 04:43:12 -0000

On Thu, 27 Apr 2017, James K. Lowden wrote:

> The troff system was designed to be typed at a keyboard.  The 
> dot-on-the-left rule might be ugly, and the requests/macros terse, but 
> the benefit to the user is relatively few keystrokes above those needed 
> for the text.

A corollary of this is that if you find that a document has a high 
percentage of troff (macro) commands within it, your document will 
probably not read so well.

In the case of man-pages, this could mean that the explanation of the 
command or library/device interface in question is overly complicated.

Regards - Damian

Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here
Views & opinions here are mine and not those of any past or present employer


From MAILER-DAEMON Fri Apr 28 00:44:37 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3xll-0001Ij-GN
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 00:44:37 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53592)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3xli-0001IM-PA
	for groff@gnu.org; Fri, 28 Apr 2017 00:44:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3xlf-0003Mq-Mq
	for groff@gnu.org; Fri, 28 Apr 2017 00:44:34 -0400
Received: from mail-yb0-x236.google.com ([2607:f8b0:4002:c09::236]:33936)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3xlf-0003MB-Cs
	for groff@gnu.org; Fri, 28 Apr 2017 00:44:31 -0400
Received: by mail-yb0-x236.google.com with SMTP id 8so12933631ybw.1
	for <groff@gnu.org>; Thu, 27 Apr 2017 21:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=RuifSp7FmEV888OdKmj8yedFDF6PslAo85mZ6u78VHg=;
	b=WZh4fVACMV3u0E4t3hEqmdbeBN04J7Pz0viAuVOsdaIYkJuYb7n7Q90Re5Qr8AgMk/
	xSunFh5I3VlfOIyal6+PDTpFNCvYfsQuPLfb1tqUBV3m8I9KB5l0dR6g7Gk/RRis3mTP
	me6QSY0c68DWal9NwWd/I8wMw+79qmlQnmxujL4uu2dkid2rGR90iG6Tb/ZpQRC/GOQd
	vXzq1WKp1NKXwqJ8gofYUdA1hRxOAj9xwDPAqP+Q+k3ekyedpYZO+qchsyFjYflTlJ/O
	C0IwBd5DZjpzjQuGWeY0g2wz97pihmL7zWno3U7VnhMoASYPahVJHdVJ8FX5zE/sB462
	FAJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=RuifSp7FmEV888OdKmj8yedFDF6PslAo85mZ6u78VHg=;
	b=sx89DWJ2jpm/T5x/LtbbFtB8ToVqhFH40VHNQ2V0lDqAuJZ+ajo/ZaTlowZ7PPBqsZ
	68uEflulCJniFV5CXjcFcgODU43NASZQ/6UQT0FFCrTgxkuM17rxEDnQq4CrdadbMeZu
	P5G2PRuf8g5Kw9ARLhGO+Fti6co/pjjqiVyJzrlRlizChZZNFPe6HCXcwWG8MquVIm+F
	L+4xC7CxpeXXVzf5Kyr9zWb/49oPyJKOL5L/kDunTmdnPZSYf7y1OFGj9icNMICkoP5J
	Sdu6MYGw4pGhi9VnCFgHIXgwpXRTgmyMq57ZiW+SAV4QDJ88+Uj7R+29MMtyGeqfyXgR
	TEaw==
X-Gm-Message-State: AN3rC/42RreCLLUTH5vSqfZum/5j/kYCvV3Hebx03e3LcI8stw84Mj/m
	9SP4HCCTGP7wCL/sCSs=
X-Received: by 10.37.54.4 with SMTP id d4mr7556516yba.106.1493354670368;
	Thu, 27 Apr 2017 21:44:30 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	f127sm2057620ywb.17.2017.04.27.21.44.28 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 21:44:28 -0700 (PDT)
Date: Fri, 28 Apr 2017 00:44:26 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="c6rac442kdnlfpxh"
Content-Disposition: inline
In-Reply-To: <20170427191128.GA4772@rhi.hi.is>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::236
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 04:44:35 -0000


--c6rac442kdnlfpxh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-27T19:11:29+0000, Bjarni Ingi Gislason wrote:
> On Wed, Apr 26, 2017 at 11:54:21AM -0400, G. Branden Robinson wrote:
> > At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote:
>=20
> [...]
>=20
> > >   ??? .IR being is just a shorthand for `\f' and `\^' that can be done
> > >     manually when needed, e.g. `.TH'.
> >=20
> > FYI, .IR does not give you this "italic correction" in groff 1.22.3:
> >=20
> > 	.de1 IR
> > 	.  if \\n[.$] \{\
> > 	.    ds an-result \&\f[I]\\$1\f[R]\"
> > 	.    shift
> > 	.    while (\\n[.$] >=3D 2) \{\
> > 	.      as an-result \/\\$1\f[I]\,\\$2\f[R]\"
> > 	.      shift 2
> > 	.    \}
> > 	.    if \\n[.$] .as an-result \/\\$1\"
> > 	\\*[an-result]
> > 	.    ft R
> > 	.  \}
> > 	..
> >=20
>=20
>   I reported this bug (and in '.IB') in August 2014, #42906

It'd be nice if 3 year-old bugs could get some feedback from the
maintenance team.

What needs to happen to make that possible?

Regards,
Branden

--c6rac442kdnlfpxh
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkCyKgACgkQ0Z6cfXEm
bc6RehAAm6KPLFRq7yff1ysBQRIlByq5xSf6ytrSS7dmVTPN5gDRUjoHv32GTkb/
w/nA+0NIF5oAEm77D0FvodqAdaLGRHJEW3M9aaPOxri1xXF9DVyPBVyMOC/tx+l+
yXB3ULyNEwTdUvbDgzrP5A00BRDYF1/y7kHv0Rul2qfR9wtzCWwghpY43SmJNnzM
yUL+RvLYLmKiEX3agC5blCxubMAOxb33hV3WPlhWQ88xN+cz8UEjE9uY+QUN/spe
qMMO1FOcFqauFmfNmL+6Y+GegTw74DYU9QB1Lmq2uhvVn5daTu+CmCv0SiHt8BBl
p1E6WTjCbBHrdaEeGWrVDZ9iip+wSuNbrdiF6XBMlszqEfc2cC+feYfNCqbVsGwp
sRaDuSHoLq/cgGzZI7u4srPKQ5WMte1OLd5TYnnFsEwnXUgY67VmtDOUVSZf8Jzs
r/uSSNz0gF6oCfMltUH3ilSFh4mQOcTs+/lj7ldBNVbQ7tgC5p4yeVSisi4c4hWs
EErjCNgtRS88UAS9JDIooizWnE/E1hgWTqd2/stYzpVkli/AqesPLzw3A4vsS+WR
N5WdibBJTZ9/T+ZeIqeeDmDkoDT0LT9C14VVzUP1D2PgXVabG8z+yppfYabALj7a
tumWbFwmryQwSuQIVeBmrzegOdyYZoyci3l2msBrAMRV1/EtIM4=
=3YGV
-----END PGP SIGNATURE-----

--c6rac442kdnlfpxh--


From MAILER-DAEMON Fri Apr 28 01:15:16 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3yFQ-0004PN-F3
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 01:15:16 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35335)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3yFN-0004PE-Lt
	for groff@gnu.org; Fri, 28 Apr 2017 01:15:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3yFK-0006Hg-Dy
	for groff@gnu.org; Fri, 28 Apr 2017 01:15:13 -0400
Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]:35104)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3yFK-0006HP-7I
	for groff@gnu.org; Fri, 28 Apr 2017 01:15:10 -0400
Received: by mail-yw0-x242.google.com with SMTP id k11so4225508ywb.2
	for <groff@gnu.org>; Thu, 27 Apr 2017 22:15:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=EiuIYn1xsw5GClZc3ZSyfjuMvYEtmO/nzxq5f9pmRVk=;
	b=CuXJFk/luDOMhV2w/AZazm3DPcwYp2nNVvO5/lXT0Vjmebu9BsEjWfPYcRbktR94Jw
	xP7f6m118azKmsE8Ryr5ZXrQSGX+Rpa6iy6icTHtZaZ1nSFM0/KiY8e4iLomSyJa1LKP
	yYcLTxrkqvoy5cN9jj75YYSdED3kiRBBFzy23BPtH+aImYX6mfZcxS83cNYHMHz8gfjZ
	xvdR3TorDnig1Il5UbaoED35FZdG79kR5QDIFBas9vtWyUwmsAgDJuWsQZz5oFZyAvm1
	nTj7l66ssXtIHuCEvU04pJwHlar7cEzJ5fiqcGgKZoGosOoR+d6zAc6C+zHpODU/2k7t
	8suw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=EiuIYn1xsw5GClZc3ZSyfjuMvYEtmO/nzxq5f9pmRVk=;
	b=ebipKQRHF0l/3k/XSgvHho22Q4JU6BbbZAzrMGI99ADgRthhgYp8rg8Pbqe2CCuX+W
	26Xd26fdqnlMAsztHFnRdlPZnxjh+8n/aIit9oGgygDwkqrY8FMB2CvXmBifvKkBv9V3
	NAb5GOAtA+Dc9kyaa8sXR6xs08pZf35hS7ScoCYwh5OLtxUqBnNSSNeramM1U2pp+ym8
	kRi4swwXTWrqfF8ESFClittkOg8KhZZyPnI6RalzCPsa/y+FUcBYmC+TOLxuzIKrXx/c
	np8PCTdOrXziFE0PUCqnpVlkvXFkAQ5E3IdftRe3rEqekZoh3TgQN1+pBmWDrSORfLpw
	xKNw==
X-Gm-Message-State: AN3rC/7BNfM/d64LePxMrJQB03WsrmdGBHQKWdjcpf/9IkOtEXeRUp5g
	xpYcy7b0RK9Ba9hsDC8=
X-Received: by 10.13.249.193 with SMTP id j184mr7390962ywf.48.1493356509340;
	Thu, 27 Apr 2017 22:15:09 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	u195sm2126125ywg.54.2017.04.27.22.15.07 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 22:15:08 -0700 (PDT)
Date: Fri, 28 Apr 2017 01:15:05 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="zsfgtjjvhglx5kff"
Content-Disposition: inline
In-Reply-To: <20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::242
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 05:15:15 -0000


--zsfgtjjvhglx5kff
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-27T23:38:23-0400, James K. Lowden wrote:
> On Wed, 26 Apr 2017 09:46:43 -0400
> "G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
>=20
> > 1. The slavish devotion to two-letter names for things, which like the
> >    man macro package and the oldest parts of *roff itself, make it
> >    self-anti-documenting. =20
>=20
> Having written one user guide in DocBook, I have to disagree. =20
>=20
> The troff system was designed to be typed at a keyboard.  The
> dot-on-the-left rule might be ugly, and the requests/macros terse,
> but the benefit to the user is relatively few keystrokes above those
> needed for the text.

Did you write your DocBook-based user guide in ed?

Nothing has come close to saving me more keystrokes than <TAB> at the
shell prompt and CTRL-N in Vim.

We have powerful, robust, and programmable text-completion systems these
days.

I have second-hand nostalgia for the early Bell Labs Unix days (too?),
but we don't live in those times.  We have ludicrously more processor
horsepower and memory, and we've even, occasionally, found some good
applications for the surfeit.

> Most SGML derivatives, on the other hand, presupposed Interleaf-like
> tools that would shield users from the markup syntax. That "assume a can
> opener" design theory freed them to be verbose. When the tools never
> materialized, users started looking for a way to avoid their verbosity
> tax.  Markdown is only the latest product of that search. =20
>=20
> Short names are actually *easier* to use than long ones!  Why? =20
>=20
> 	Brevity rewards experience. =20

Well, that's part of the problem.  Few people are full-time *roff or
macro package users.  They're programmers.  Some of them are difficult
to coerce into writing documentation _at all_.

A lot of people hate Fortran, but I don't.  In the 20+ years since I
first saw it I've come to recognize a huge virtue in its insistence on
unabbreviated English words for its keywords; they're more ergonomic for
the scientists and (non-software) engineers who have been off doing
science or engineering for several months and only occasionally have to
do code maintenance or development.

That's the analogy I recommend for macro packages targeting
documentation of software systems.  You can even lead the horses to
literate programming, as Knuth tried to do decades ago, and most of them
will stubbornly spend the great bulk of their time in the part that gets
tangled rather then the part that gets woven.

It doesn't matter for our discussion why that is--it's a fact and the
state of our discipline.  Maybe they're snooty elitists or code cowboys
or rock stars or maybe they simply spend their time where the problems
are.

The competing models of "recognition" vs. "recall" have occupied a lot
of writing on user experience.

I submit to you that for most of its users, the man macro package needs
to work the "recognition" side of the street.

> If .SH or .Sx is hard to read, they're also easy to write, and easy to
> remember when transferring them from the manpage to the document at
> hand.

I don't understand this claim.  Section headings would be pretty obvious
most of the time even if they weren't marked up at all.  You're not
transferring the macros, surely, but rather their parameters, right?  Do
you remember off the top of your head in what order the 6 arguments to
=2ETH get placed at header-left, header-middle, header-right, footer-left,
footer-middle, and footer-right?

Even the ne plus ultra of terseness among successful languages, C,
adopted designated initializers, a sop to those who can't recall what
order a struct's fields come in.  (Though I wouldn't bet on whether
Ritchie would have thought it was a good idea.)

> In today's world, to most programmers troff is 100% novel, and they find
> its terseness inscrutable and off-putting.  Too hard to understand! =20
>=20
> Ah.  But so easy to use. =20

=2E..and yet again so hard to use correctly.

Regards,
Branden

--zsfgtjjvhglx5kff
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkCz88ACgkQ0Z6cfXEm
bc7XvBAAhWrrfu/oqZB5oXI+SYJdwMpeveCmJS9F4WjKaSeLzvS/y/stCKwnOAiB
Nm2yizHqt/ZvGWLvxSLMAnk3Azebk3FPYBrYNGaOk2PxbZnEjpRMn09IJ6eGS8Kb
l8GsBQpK3oiD8MLbC2GFWT4LjrCsbuUq7OAvDER5nSX5d2H/XIl8CRB4ro9VDMvv
AI99h5rG0qn5PfPURB1ZJZyCY/WtmXZMaI6x39xNncIXqMkP3lKwbEjZKUXOFhTp
ZS6ay8JMLn6AycbhjjnTMvSaoIsEXG8qEmm4s6bBdJncNUMiYcT3IBkWHNNrEe3a
vPoX5SGjRGQ9EY3WDftND1UKgybe374NoKIUwr2qHODUMln62G6Idtjub82b8aao
+v3anOf3JFMCCfpx11eMNA8JN2YjEyecG8riI7RYdX/gvTsb51a6ECIjO/xGCKe/
0A2UZe+LuQW5sNm+bH3YVanQL0PNdSPjhDI+E3+fiybt6zBFtXWI/j+0DaINGInY
EIXJ97qGd2dd5EHksT3NEHJZIf15qMLMUtJDwiwFqh6iC94k7ybwpAQKxE9cWnTh
1QE5aySDpciHviScWwY/9rtxo2sZ/j00AYvLjn1z6/aGa+1y9NVyMOSaqDHwpDUV
iyhj6gj+d1XPek2lRxrq7PyZ6B9ZkIIi1B28nYEf1QCz7rbHfo4=
=j7D8
-----END PGP SIGNATURE-----

--zsfgtjjvhglx5kff--


From MAILER-DAEMON Fri Apr 28 01:28:12 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3yRw-0005ll-7m
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 01:28:12 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40133)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d3yRs-0005lI-1T
	for groff@gnu.org; Fri, 28 Apr 2017 01:28:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d3yRq-0008Q7-31
	for groff@gnu.org; Fri, 28 Apr 2017 01:28:08 -0400
Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]:36319)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d3yRp-0008PM-Rq
	for groff@gnu.org; Fri, 28 Apr 2017 01:28:06 -0400
Received: by mail-yw0-x242.google.com with SMTP id j9so4235576ywj.3
	for <groff@gnu.org>; Thu, 27 Apr 2017 22:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=H2R4DqHkBOpMy3ujuEoXgv679Sduk/zkPaxuT2E2zIg=;
	b=vXApwxan2zSXm2KlW1vipevIUU2OYj5tnBEQRD8hHxqFWogJP8ZdJKAt8Wa0+sOPj1
	VRsA6oCvhjnjytsDKfYz0b60WWo5xTVK2qlXNGG1GvTjvmjiJOKOp3h1xcIVR9o/0AtB
	6Vb6/mbnfDMO0GXJZilJS0b5nTOT/m0XdVDQxCqe7SwwJ1BOQBpfpga76ZPFvJypo1/z
	gamgdxLyt1uySAnHHB9BmrpdLalfcfyffvyvWRiCTFX/ZSYId+aK3yrj6Kll5BeRI1zD
	OkSXCpEnGwh/mqhiris02Jkj9HNUb1zYcaXBZubnL6zZoVYPeaidVAngmHvG+U2gguXK
	z0IQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=H2R4DqHkBOpMy3ujuEoXgv679Sduk/zkPaxuT2E2zIg=;
	b=DZtRzvcHvbvEKgiY5WLfP6Afrb3+7vhJU+pNlajzjuW/vXvFiXV06iKk1EXtJN+knH
	xVRetV6GXx8ggMyqorXUXqlYMjpIexYqcl1bNtqwDhh2wawz6Divx5CfQojO1zMzRMAv
	9mhsrNs1wlethnQSKKEjqd2HyHGx2IRkybgwPoYCwUTtz2exgKWmi2s5kL1gVUm8buPM
	vdjKp9/LHdUU6wr1sAwqFIGWzKjx3Wk3YN/D6fqJgMzGWg8151vDuUMNYfz1qriWj9Ek
	fITtVDtLAwMqgFvnku4rnettjR1m5HMbnw0CA10upCnoNHIbqoW6DM4jKJnIVJumw3ig
	79xQ==
X-Gm-Message-State: AN3rC/4WuCVuo0niGEKtPnVjL0fQp54k+oEKmR9PEPJe0jpejD9B2suL
	5B8PYZz9q8B43gm6mgS6J8U0Sb00uw==
X-Received: by 10.13.210.65 with SMTP id u62mr7644289ywd.159.1493357285070;
	Thu, 27 Apr 2017 22:28:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Thu, 27 Apr 2017 22:27:48 -0700 (PDT)
In-Reply-To: <20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
	<20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
From: John Gardner <gardnerjohng@gmail.com>
Date: Fri, 28 Apr 2017 15:27:48 +1000
Message-ID: <CAGcdaje7JFjxnnVWLJ=AEiMhx_kTwWvV2CCMA2u68SyRgAWhxQ@mail.gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::242
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 05:28:10 -0000

This touches on something I experienced recently. I wanted to write a
JavaScript module that would help developers generate manual-pages for
their projects (because there's a searing lack of manpages in the Node
community...).

I ended up ditching that idea when I realised developers would still be
asking for the possibility of converting Markdown into Roff commands... and
I realised I'd be going through endless effort to spoon-feed close-minded
devs who can't be bothered making an attempt to learn even basic manpage
authoring. I laughed at how complex a JavaScript-based documentation
generator would become when compared to the simplicity and power of a
simple, plain, correctly-written manpage.

As Branden said: you can lead a horse to its troff, but you can't make them
drink.

(I know it's pronounced "tee-roff", not "trough", but c'mon, that pun was
unavoidable...)

On 28 April 2017 at 15:15, G. Branden Robinson <g.branden.robinson@gmail.com
> wrote:

> At 2017-04-27T23:38:23-0400, James K. Lowden wrote:
> > On Wed, 26 Apr 2017 09:46:43 -0400
> > "G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
> >
> > > 1. The slavish devotion to two-letter names for things, which like the
> > >    man macro package and the oldest parts of *roff itself, make it
> > >    self-anti-documenting.
> >
> > Having written one user guide in DocBook, I have to disagree.
> >
> > The troff system was designed to be typed at a keyboard.  The
> > dot-on-the-left rule might be ugly, and the requests/macros terse,
> > but the benefit to the user is relatively few keystrokes above those
> > needed for the text.
>
> Did you write your DocBook-based user guide in ed?
>
> Nothing has come close to saving me more keystrokes than <TAB> at the
> shell prompt and CTRL-N in Vim.
>
> We have powerful, robust, and programmable text-completion systems these
> days.
>
> I have second-hand nostalgia for the early Bell Labs Unix days (too?),
> but we don't live in those times.  We have ludicrously more processor
> horsepower and memory, and we've even, occasionally, found some good
> applications for the surfeit.
>
> > Most SGML derivatives, on the other hand, presupposed Interleaf-like
> > tools that would shield users from the markup syntax. That "assume a can
> > opener" design theory freed them to be verbose. When the tools never
> > materialized, users started looking for a way to avoid their verbosity
> > tax.  Markdown is only the latest product of that search.
> >
> > Short names are actually *easier* to use than long ones!  Why?
> >
> >       Brevity rewards experience.
>
> Well, that's part of the problem.  Few people are full-time *roff or
> macro package users.  They're programmers.  Some of them are difficult
> to coerce into writing documentation _at all_.
>
> A lot of people hate Fortran, but I don't.  In the 20+ years since I
> first saw it I've come to recognize a huge virtue in its insistence on
> unabbreviated English words for its keywords; they're more ergonomic for
> the scientists and (non-software) engineers who have been off doing
> science or engineering for several months and only occasionally have to
> do code maintenance or development.
>
> That's the analogy I recommend for macro packages targeting
> documentation of software systems.  You can even lead the horses to
> literate programming, as Knuth tried to do decades ago, and most of them
> will stubbornly spend the great bulk of their time in the part that gets
> tangled rather then the part that gets woven.
>
> It doesn't matter for our discussion why that is--it's a fact and the
> state of our discipline.  Maybe they're snooty elitists or code cowboys
> or rock stars or maybe they simply spend their time where the problems
> are.
>
> The competing models of "recognition" vs. "recall" have occupied a lot
> of writing on user experience.
>
> I submit to you that for most of its users, the man macro package needs
> to work the "recognition" side of the street.
>
> > If .SH or .Sx is hard to read, they're also easy to write, and easy to
> > remember when transferring them from the manpage to the document at
> > hand.
>
> I don't understand this claim.  Section headings would be pretty obvious
> most of the time even if they weren't marked up at all.  You're not
> transferring the macros, surely, but rather their parameters, right?  Do
> you remember off the top of your head in what order the 6 arguments to
> .TH get placed at header-left, header-middle, header-right, footer-left,
> footer-middle, and footer-right?
>
> Even the ne plus ultra of terseness among successful languages, C,
> adopted designated initializers, a sop to those who can't recall what
> order a struct's fields come in.  (Though I wouldn't bet on whether
> Ritchie would have thought it was a good idea.)
>
> > In today's world, to most programmers troff is 100% novel, and they find
> > its terseness inscrutable and off-putting.  Too hard to understand!
> >
> > Ah.  But so easy to use.
>
> ...and yet again so hard to use correctly.
>
> Regards,
> Branden
>

From MAILER-DAEMON Fri Apr 28 01:31:52 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3yVU-00061Z-92
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 01:31:52 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41755)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d3yVR-00061T-81
	for groff@gnu.org; Fri, 28 Apr 2017 01:31:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d3yVP-00027Q-PT
	for groff@gnu.org; Fri, 28 Apr 2017 01:31:49 -0400
Received: from mail-yw0-x232.google.com ([2607:f8b0:4002:c05::232]:35284)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d3yVP-000279-K3
	for groff@gnu.org; Fri, 28 Apr 2017 01:31:47 -0400
Received: by mail-yw0-x232.google.com with SMTP id u70so26090849ywe.2
	for <groff@gnu.org>; Thu, 27 Apr 2017 22:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=tMs9je5QFfsub2ecdLTiCSPL/SUU58l08RLzv22ZMMI=;
	b=DDlF+84afKAnK+LPiZAp9+oMOEHmuMjKrqprN6nvgwqq+dxqokUgXiWHVZ3xYRVHOp
	O9QbXhUS6wj7tCiSPxMchG6GkL3EMIgOyfGdjSom46Y9LkZW4Xq3L/sINUerYoeDzLwZ
	mFTBCJ8zhwLtKGjCJt5QSWGtREF4/Ce+FYqUjYMzOcg7nj0Wp6c91NUjPWZgAunNyrZM
	NJQUnkDZ50dEKGBmUdjs7JJnOwlJ9/9l0nCpSWEf4WDFDW/8/KDdmfQfGHO9fQ3LRSkL
	r70TNfIHqVv+iH68YjhSwLAPdTTpj4hG3/J/xED1zg2UaXRWD6xA0qdfYchkSJY01Red
	s/uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=tMs9je5QFfsub2ecdLTiCSPL/SUU58l08RLzv22ZMMI=;
	b=FxxS4jeTKYhViz3Tu98wYRcW7odZW1oy6Y8Y3IpZtJuR8U68knQt4ewm8DTTe0BFge
	QS2SQPArc+Bj+NcE4ajRiLqt/wvHuX5vXZPMry4tHJQtpGNGXhRTMETCHuXpMl3xBh38
	7+WOmTeV4CrX+/ZJh9nzqjVkQyulin1uF9hApsBxg6+c15xirQKo2newZAM3cKUxVitJ
	oQDo2R2uh45MeB0pjcuMFQp/8ZgKOZAGvhCdEN87VUkB1O4VZO7qCSU2pSHuGOUjdIb+
	IQNsMS5JZEpeDCxx5Xk6f9yt08wUMGYepXnZEnR1G5eOj5NS+7P4kBkfzqgjWe+FAXW8
	roIw==
X-Gm-Message-State: AN3rC/51MRHMe9zA/vbxLOtOtUfF5ePK+Mww5Z2OVLDpUfo1ZoBHggK6
	gBlt87dOkj1dSAcJ0O1das3nqQQZ25XgFjQ=
X-Received: by 10.129.73.72 with SMTP id w69mr6040941ywa.190.1493357506006;
	Thu, 27 Apr 2017 22:31:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Thu, 27 Apr 2017 22:31:30 -0700 (PDT)
From: John Gardner <gardnerjohng@gmail.com>
Date: Fri, 28 Apr 2017 15:31:30 +1000
Message-ID: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
To: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::232
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 05:31:50 -0000

Hello!

Some time ago, I announced my intent to build a man-page previewer for a
text-editor named Atom <https://atom.io/>. Work is coming along nicely: this
page
<https://cdn.rawgit.com/Alhadis/language-roff/a7c07744a9d44adf32a546646f7a8d57d52e6e58/preview-tty.html>
was generated using a lightweight tokeniser
<https://github.com/Alhadis/language-roff/blob/renderer/lib/tokeniser.js>
written in JavaScript, which processes Groff's intermediate output language
into web-based formats. That's the nroff preview... I'm now halfway through
developing the troff previewer, which uses HTML5 canvas
<https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D>
technology to draw realtime previews of an opened Roff document.

So far, so good!
<https://cloud.githubusercontent.com/assets/2346707/25514878/732e09ea-2c23-11e7-97ea-9674d3845dd1.png>
I'm
proud of how this is turning out: bear in mind, that preview updates as the
user types, so it'll feel like an efficient replacement for a word
processing program, haha.

I'm currently stuck with drawing arcs
<https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/arc>.
This
might be the wrong forum to ask for help with trigonometry, but I was
planning to announce progress eventually anyway.

Now, this pic code:

.PS
> "+" at 0,0
> arc -> from 0.5,0 to 0,0.5
> arc -> cw from 0,0 to 1,0.5
> arc -> cw from 0,0 to 2,0 rad 15
> .PE


... should look like this
<https://cloud.githubusercontent.com/assets/2346707/25515071/4bc46870-2c25-11e7-9883-9248e4b4aa68.png>.
Instead, it, uh, looks like this
<https://cloud.githubusercontent.com/assets/2346707/25515084/5d84eed6-2c25-11e7-8cdd-bdb65f7804e9.png>
.

Groff's output gives me these coordinates to go by:

   - startX, startY - Coordinates of the arc's starting point
   - centreX, centreY - Coordinates of the arc's centre
   - endX, endY - Coordinates of the arc's terminal point

But the canvas arc method I'm working with requires all of these:

   - x - The x coordinate of the arc's centre.
   - y - The y coordinate of the arc's centre.
   - radius - The arc's radius.
   - startAngle - The angle at which the arc starts, measured clockwise
   from the positive x axis and expressed in radians.
   - endAngle - The angle at which the arc ends, measured clockwise from
   the positive x axis and expressed in radians.

It's embarrassing to be stuck on something so obvious, but this is what's
blocking further progress...

From MAILER-DAEMON Fri Apr 28 01:55:07 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3yrz-00009D-DP
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 01:55:07 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49901)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <werner.lemberg@gmx.de>) id 1d3yrx-00008e-9k
	for groff@gnu.org; Fri, 28 Apr 2017 01:55:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <werner.lemberg@gmx.de>) id 1d3yrs-0007KF-Ec
	for groff@gnu.org; Fri, 28 Apr 2017 01:55:05 -0400
Received: from mout.gmx.net ([212.227.15.18]:59484)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <werner.lemberg@gmx.de>)
	id 1d3yrs-0007Jj-40
	for groff@gnu.org; Fri, 28 Apr 2017 01:55:00 -0400
Received: from gnu.org ([91.141.0.66]) by mail.gmx.com (mrgmx003
	[212.227.17.190]) with ESMTPSA (Nemesis) id 0MJSQ7-1d5tkI1c1z-0035ZF;
	Fri, 28 Apr 2017 07:54:57 +0200
Date: Fri, 28 Apr 2017 07:54:55 +0200 (CEST)
Message-Id: <20170428.075455.1859991191870751849.wl@gnu.org>
To: g.branden.robinson@gmail.com
Cc: groff@gnu.org
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
References: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
	<20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
X-Mailer: Mew version 6.7 on Emacs 26.0.50 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: <werner.lemberg@gmx.de>
X-Provags-ID: V03:K0:uE2uQRdb084NxhVQzy3F5O/KK2fxvf29sOXzQjcVapA9eTguuMk
	GT4orwjfJLfHuKiSLKhNUTZ81cPibGxpRkcVIL2NOCW7+q1Z5PSRfkZO0mvMp3xmu5nNgfK
	yRCg4Vkz9M4ywYgD/tmpyQ3nZEffiToY2HoR0ZP7ybbbQN/JbMHrVMUwm64V/gYADfSBG12
	ne57/hj47INYmAnn0MSfQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:tL8dS14bdsc=:P93WYPDsNy4ekR+wLbrNUS
	zfFIjG540eLs/vZYMpmSoHoJv0jMzIHA9sSr9WipuulHfq6IZsm9PGyWOMNI6JuQJcAMN6boc
	waa3uQIutDcuIETGo0wSZdMTBccJFI9qH25zsNTvF5/6j7wxQH46vS+u/8sZHfE7b5uk3whvC
	WTriLzfc0gv8QyjmaqCjCA7ozHBPlLMtO0vjyCR4lbibKd/ffO3P2g/GbVx8TXduDRp87LCkn
	k2S5yDIYC6V6xqy9EBk9bUi00GyiK8H2G0GY3S6m1QKKYzH9nhWC52v6a1F1vfKvJhqX5SAuI
	nnzjVkxfc8x6O4BmqACjVIV3T8rM8jKWajgu7dxDTIAcFgZXBeR1Tt+x8egKDzNjVbbLAoHHd
	0cRv/Ja0bl3i+R5nE+MfklJoIEfTDQeF4mvyxVjmP6s5OcrfY1uwOj+ssfqa8iOLSTP9RLErK
	CTPTz+dV15fSiYIBWSVGoXQEfmCLMP1o/H6ZWKMCmqt5YJwHp46lVc3ULHsWYhp0yqlXcJMrD
	g/QwynQ+WJmyqcq4KKK7JS/1VeBsUJqPDwtd5z/Dwmz14IROk/+NPyIp6sujqFrP1ZrGdt2My
	VykkTmaDVTkjjK0qxkfsFKlngJinDUSjOcndr5atvTwv70u08GF0SfGyB0hkndvqSDFvluxQI
	EeTg5kZEEF+Y9vlKtf0KOLUnKapPDABO1xmEPz8LYbEz996+cMM04amK8zvgI6zTKytIWeBXX
	oG9AS+b87UAAsLUHokpaXlEEdiR6dpZ7fiOkLpZuPw2fHC7CpIpqKGjtSuCYnlVkynRnlJGHU
	PszKBGwunetSs5x6kYYZostjkcOtg==
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 212.227.15.18
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 05:55:06 -0000


>>   I reported this bug (and in '.IB') in August 2014, #42906
> 
> It'd be nice if 3 year-old bugs could get some feedback from the
> maintenance team.
> 
> What needs to happen to make that possible?

A new maintainer.


    Werner


From MAILER-DAEMON Fri Apr 28 02:22:58 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d3zIw-0004ae-Cp
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 02:22:58 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60675)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3zIt-0004a8-Hg
	for groff@gnu.org; Fri, 28 Apr 2017 02:22:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d3zIq-0006rb-Bo
	for groff@gnu.org; Fri, 28 Apr 2017 02:22:55 -0400
Received: from mail-yb0-x22f.google.com ([2607:f8b0:4002:c09::22f]:36034)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d3zIq-0006qq-7D
	for groff@gnu.org; Fri, 28 Apr 2017 02:22:52 -0400
Received: by mail-yb0-x22f.google.com with SMTP id s22so13238232ybe.3
	for <groff@gnu.org>; Thu, 27 Apr 2017 23:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=fKedru44epcppQLxcZrSTAt/yfhC23CireMoGq4dW4s=;
	b=PgsRllfPzC/45ke7T53d9hwdm9MxU3hfNMm2kEjOpKhR1HTreG7z79qJ0EhVxuUnMR
	wf0L3sG0mgdOKGP5qP265HChaaoOTOd4VgPh79tGpC9FxuaHHlZUBLRa0ieHIrI+KHhH
	TN0dgqdjyqyCgltbB4h1oJdwxX5XQr7alt89cvsf/Xy5cAU8/uylim92Gvh3P2mz10gO
	SVa1wlc5buENe00uFk2T8wezTkHP/kKIIiDk17LHT42OA1HTaPbeLp1H3VTN83WkaIB3
	Q0+3RREe57JBrhuJi0HDsLCBl8LL0Y1b/vWnXvScGMmj3AdNrGz2ca7g5ushpfQOq+fn
	8TIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=fKedru44epcppQLxcZrSTAt/yfhC23CireMoGq4dW4s=;
	b=OMX4WmjknN+JO1r883BoB4SP8IrXWLrT6vJXfezI1MBTcGf8ppEXTBfwI/zkEkjORj
	PlBdZkhWK3qnc/nCwA3TxjRvoEGZHjcNGjNg2Kebs4O0OCV0S0k3q9p+xlI3WXYVvKlJ
	S+/Q6vyLEKQLhh6/69UgAcjdmyk5h2Af5NL1qE+mia7L59dXXMN1qzNbdKFTh0RsfTPn
	8SB9U+waQ6bhv5bGvnJR8MrVbaRdihKsdtbPuXmQdTbhVimNYZb8Jm/iFVtj6KMCx2Vm
	jO8ZsVNzrNyHSS2T3kDXo1mWNQjprqCgCNxfoJqzfCxHna+o7yiJb+TmzsiZN8x6Vz7p
	MIWw==
X-Gm-Message-State: AN3rC/4QrmmJqmjZzi9w4eztHpVM3/uBR4GdeiwNHWNqQyfztHcCM8vw
	WXqMHgQuBt+Vbill6fo=
X-Received: by 10.37.221.5 with SMTP id u5mr7383911ybg.51.1493360571171;
	Thu, 27 Apr 2017 23:22:51 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id u83sm2545958ywa.4.2017.04.27.23.22.49
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Thu, 27 Apr 2017 23:22:49 -0700 (PDT)
Date: Fri, 28 Apr 2017 02:22:47 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff <groff@gnu.org>
Message-ID: <20170428062245.nsmvvcp6nvpdhul5@crack.deadbeast.net>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="qbn3tkirf4l4cyj2"
Content-Disposition: inline
In-Reply-To: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::22f
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 06:22:56 -0000


--qbn3tkirf4l4cyj2
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-28T15:31:30+1000, John Gardner wrote:
> This might be the wrong forum to ask for help with trigonometry, but I
> was planning to announce progress eventually anyway.

I have no experience with pic, but I faintly recall some trig.  Maybe I
can help.

> Now, this pic code:
>=20
> .PS
> > "+" at 0,0
> > arc -> from 0.5,0 to 0,0.5
> > arc -> cw from 0,0 to 1,0.5
> > arc -> cw from 0,0 to 2,0 rad 15
> > .PE
>=20
>=20
> ... should look like this
> <https://cloud.githubusercontent.com/assets/2346707/25515071/4bc46870-2c2=
5-11e7-9883-9248e4b4aa68.png>.
> Instead, it, uh, looks like this
> <https://cloud.githubusercontent.com/assets/2346707/25515084/5d84eed6-2c2=
5-11e7-8cdd-bdb65f7804e9.png>
> .
>=20
> Groff's output gives me these coordinates to go by:
>=20
>    - startX, startY - Coordinates of the arc's starting point
>    - centreX, centreY - Coordinates of the arc's centre
>    - endX, endY - Coordinates of the arc's terminal point
>=20
> But the canvas arc method I'm working with requires all of these:
>=20
>    - x - The x coordinate of the arc's centre.
>    - y - The y coordinate of the arc's centre.
>    - radius - The arc's radius.
>    - startAngle - The angle at which the arc starts, measured clockwise
>    from the positive x axis and expressed in radians.
>    - endAngle - The angle at which the arc ends, measured clockwise from
>    the positive x axis and expressed in radians.
>=20
> It's embarrassing to be stuck on something so obvious, but this is what's
> blocking further progress...

According to pic.ms, the default radius for an arc is 0.5 inches.  I
mention this because to convert between angles and arc endpoint
coordinates you need to know the radius.

The coordinates of the endpoint of the terminal side of an angle are
expressed by this relation:

Let =CE=B8 be an angle in radians between the initial (i) and final (f) rad=
ii
connecting the endpoints of an arc to their common center.

Then x and y, the cartesian coordiates of the arc's endpoint are given
by

x =3D r cos =CE=B8

and

y =3D r sin =CE=B8

where r is the radius of the arc.

It sounds like you need the inverse relations, beause you have (x_i,
y_i) [startX and startY] and (x_f, y_f) [endX and endY] but you want =CE=B8=
_i
and =CE=B8_f for the canvas object.  Solving for =CE=B8 we find:

=CE=B8 =3D arccos(x/r) =3D arcsin(y/r)

The trig functions are periodic, not one-to-one, so you will need to
keep track of the signs on x and y so that the =CE=B8 you find is in the
correct quadrant.

Be prepared to add or subtract multiples of =CF=80/2 to the =CE=B8 you find=
 to
account for the quadrant.  My guess is that Kernighan chose the approach
he did when designing pic (contra that of the HTML canvas folks) because
it preserves more information.

Does this help or did I manage to misunderstand you completely?

Regards,
Branden

--qbn3tkirf4l4cyj2
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkC36oACgkQ0Z6cfXEm
bc7aQg//TUWJJimKhDym2WmnirxuZd+/TFX6Q0f1KDtzWurAAySvVu/2FBfpKnrd
+KFiE+F/iMZ/S3rpBgstMSzhliDxfK5Iu/nbC1f2fTT5yS3fbqD1Nea/NLWuYdXA
5eEtQZ1tkBVBVRpfjeBVLHbfsYFRzk6MIfRxExPRJ2cUF5rzMQHovuHn434kXt+R
lYmKls58AO8a7WIdT8rpSEXIk5WcPWrmQkr6vcjXg+mIYc9QLetlVfElea4hr4zg
0gQ7C06j8fIgWbVbwcgQshpU+P3uTsmrbVgRiXDpwrScM16cP112LryFlDGnMqiY
rYZSBrvQ/P2wmR4CvC3W/zec9X6FsxVi+rYC8cCN0zhlNkjysxQVJxUm3naVIkuA
cEg6J2hymdILe2l7y9NJD44aKoH2eiXT1gzFcabu5AqdgPN1s3a0vIwLKi741xy/
Y+/e4JbJS5nVcCSo2fU4RCIHhVREEVZo1gkflx6O1tRieb5D8AdzFVo7G6NS7grf
mZFTz8m78SO9XkMVqilN12ykTiKiU5x4CLk4GZQW8sQBoyF3MKd0zmZ4eERgPfPH
OgD+X6qPZBcVSos8aqCS7TfLJIjB8as0kuE7PQ3E1AIiR4cqFvnjPKfOKnDEz3cp
xTj0/QzuhbnJiHVoSLT66+bzeyyPDxeWiomY8nyd+dk9QOeNiQE=
=8xFa
-----END PGP SIGNATURE-----

--qbn3tkirf4l4cyj2--


From MAILER-DAEMON Fri Apr 28 03:40:59 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d40WR-00047V-9N
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 03:40:59 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55128)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d40WN-00047P-UC
	for groff@gnu.org; Fri, 28 Apr 2017 03:40:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d40WM-00018v-5M
	for groff@gnu.org; Fri, 28 Apr 2017 03:40:55 -0400
Received: from mail-yw0-x22a.google.com ([2607:f8b0:4002:c05::22a]:34330)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d40WL-00018p-Ps
	for groff@gnu.org; Fri, 28 Apr 2017 03:40:54 -0400
Received: by mail-yw0-x22a.google.com with SMTP id k11so26996477ywb.1
	for <groff@gnu.org>; Fri, 28 Apr 2017 00:40:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=nXQjHCiOICbi8ZZYKQkHkmRozt8mTlF8dKYT+GwmpDo=;
	b=eYwCCQsyqagNwxP3aQCDZbj4r4C+EXwACSUoarCZLJOFuyAiDnklTt3eAp40RxyLRO
	H7n1G0i3gqpwAY94wKsDlAYtVOH9u2qXFBx8if8JUUyWhafgzAyDkXucnSflveEBJVT1
	+ieiFHspqJMQxL/xemEG0BCGPVgrP5Hb0A3E7wGxYxECZED0pNq/fFrYtGUoAkhtsC56
	E5vekrm7zSo7K/CGE69z7fXb9nmCccDsYmkkMzdZskHdH7w/IvqVqWqAYKawcLXwh6xE
	NXSSVrbgH45Y8pBctZ5Dfp35qLkAe0yV0I1rGPnVuQedVQYC3Bqy/mdBP++dtuJZa6dH
	v0Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=nXQjHCiOICbi8ZZYKQkHkmRozt8mTlF8dKYT+GwmpDo=;
	b=VQ+oJuhPhC05k5GS0Mj2sitc+e0BuWteu5yMQHrFZ6/V4mJt5pURnVajzq8bQnLrxr
	jrHc8iV5C/Tq/OMlm8NSKq8sOjWPeWDIwyKLl2VhGc43wU5g2NfcC+2wWdjWzu83G9sm
	L6tMvwdJEtr4d4QL4d9OZIIJgu/OspyIikUa5CmhupApbRFehDvPjotoWdlUnBRi0A5g
	uH4PAUpd/1AzfgJe8CkBVOe5kkbHw/GKaOJN9+GQ97Lq3tYxiHoqR3lXNmn6DcPjWHZG
	gzY2fiR6T//4ml6R8Sfu6Zp/sGdwnm9onwsGekFmLyCzaz+Qm2uCKZP2inmPYCKX6Etk
	nVZw==
X-Gm-Message-State: AN3rC/7YOLYT5By3wWVSlneGtiEEeLUEaQYWSDUBxhttQe/fCN1jH6gT
	c21X1acgmF+Dg3yYMl638B6IY4+J/w==
X-Received: by 10.13.236.199 with SMTP id v190mr7703602ywe.65.1493365253069;
	Fri, 28 Apr 2017 00:40:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Fri, 28 Apr 2017 00:40:37 -0700 (PDT)
In-Reply-To: <20170428062245.nsmvvcp6nvpdhul5@crack.deadbeast.net>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
	<20170428062245.nsmvvcp6nvpdhul5@crack.deadbeast.net>
From: John Gardner <gardnerjohng@gmail.com>
Date: Fri, 28 Apr 2017 17:40:37 +1000
Message-ID: <CAGcdajcLje47Wph1xAkdzkzNsvSd5rbqij=EkFQibdym6E7wDw@mail.gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 07:40:58 -0000

>
> Does this help or did I manage to misunderstand you completely?


I'm afraid so... the issue isn't with calculating radii, but calculating
the `startAngle` and `endAngle`. This is perhaps better explained with an
example:

https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/a=
rc#frame_Playable_code

The following line draws a complete circle using the `arc` method:

ctx.arc(50, 50, 50, 0, 2 * Math.PI, false);


Where:
- Radius =3D 50px
- Start angle =3D 0
- End angle =3D 6.2832=E2=80=A6 radians (360 degrees)
- Arc centre =3D 50px, 50px

Of course, that's a deceptively simple-looking demo. Drawing partial curves
is proving more difficult.

In the demo's editor
<https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/=
arc#frame_Playable_code>,
press *Edit *and run this code instead:

let x =3D 100;
> let y =3D 100;
> let radius =3D 50;
> let startAngle =3D degToRad(45);
> let endAngle =3D degToRad(180);



ctx.beginPath();
> ctx.arc(x, y, radius, startAngle, endAngle);
> ctx.stroke();
> function radToDeg(value){
> return value * 180 / Math.PI;
> }
> function degToRad(value){
> return value * Math.PI / 180;
> }


If you tinker with the angles passed to `startAngle` and `endAngle`, you'll
see how the curvature is calculated.

Honestly, I'm starting to think this implementation is really backwards.
Kernighan's approach is much easier to get my head around...


On 28 April 2017 at 16:22, G. Branden Robinson <g.branden.robinson@gmail.co=
m
> wrote:

> At 2017-04-28T15:31:30+1000, John Gardner wrote:
> > This might be the wrong forum to ask for help with trigonometry, but I
> > was planning to announce progress eventually anyway.
>
> I have no experience with pic, but I faintly recall some trig.  Maybe I
> can help.
>
> > Now, this pic code:
> >
> > .PS
> > > "+" at 0,0
> > > arc -> from 0.5,0 to 0,0.5
> > > arc -> cw from 0,0 to 1,0.5
> > > arc -> cw from 0,0 to 2,0 rad 15
> > > .PE
> >
> >
> > ... should look like this
> > <https://cloud.githubusercontent.com/assets/2346707/25515071/4bc46870-
> 2c25-11e7-9883-9248e4b4aa68.png>.
> > Instead, it, uh, looks like this
> > <https://cloud.githubusercontent.com/assets/2346707/25515084/5d84eed6-
> 2c25-11e7-8cdd-bdb65f7804e9.png>
> > .
> >
> > Groff's output gives me these coordinates to go by:
> >
> >    - startX, startY - Coordinates of the arc's starting point
> >    - centreX, centreY - Coordinates of the arc's centre
> >    - endX, endY - Coordinates of the arc's terminal point
> >
> > But the canvas arc method I'm working with requires all of these:
> >
> >    - x - The x coordinate of the arc's centre.
> >    - y - The y coordinate of the arc's centre.
> >    - radius - The arc's radius.
> >    - startAngle - The angle at which the arc starts, measured clockwise
> >    from the positive x axis and expressed in radians.
> >    - endAngle - The angle at which the arc ends, measured clockwise fro=
m
> >    the positive x axis and expressed in radians.
> >
> > It's embarrassing to be stuck on something so obvious, but this is what=
's
> > blocking further progress...
>
> According to pic.ms, the default radius for an arc is 0.5 inches.  I
> mention this because to convert between angles and arc endpoint
> coordinates you need to know the radius.
>
> The coordinates of the endpoint of the terminal side of an angle are
> expressed by this relation:
>
> Let =CE=B8 be an angle in radians between the initial (i) and final (f) r=
adii
> connecting the endpoints of an arc to their common center.
>
> Then x and y, the cartesian coordiates of the arc's endpoint are given
> by
>
> x =3D r cos =CE=B8
>
> and
>
> y =3D r sin =CE=B8
>
> where r is the radius of the arc.
>
> It sounds like you need the inverse relations, beause you have (x_i,
> y_i) [startX and startY] and (x_f, y_f) [endX and endY] but you want =CE=
=B8_i
> and =CE=B8_f for the canvas object.  Solving for =CE=B8 we find:
>
> =CE=B8 =3D arccos(x/r) =3D arcsin(y/r)
>
> The trig functions are periodic, not one-to-one, so you will need to
> keep track of the signs on x and y so that the =CE=B8 you find is in the
> correct quadrant.
>
> Be prepared to add or subtract multiples of =CF=80/2 to the =CE=B8 you fi=
nd to
> account for the quadrant.  My guess is that Kernighan chose the approach
> he did when designing pic (contra that of the HTML canvas folks) because
> it preserves more information.
>
> Does this help or did I manage to misunderstand you completely?
>
> Regards,
> Branden
>

From MAILER-DAEMON Fri Apr 28 07:23:18 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d43za-0006Z2-Mr
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 07:23:18 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55228)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d43zY-0006Xe-3j
	for groff@gnu.org; Fri, 28 Apr 2017 07:23:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d43zS-0000r7-L8
	for groff@gnu.org; Fri, 28 Apr 2017 07:23:13 -0400
Received: from sdaoden.eu ([217.144.132.164]:38904)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d43zS-0000qI-Do
	for groff@gnu.org; Fri, 28 Apr 2017 07:23:10 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 3D16E16056; Fri, 28 Apr 2017 13:23:09 +0200 (CEST)
Date: Fri, 28 Apr 2017 13:23:41 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: groff@gnu.org
Message-ID: <20170428112341.6YPlP%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<10251651.1Zt5jh898W@pip.chuzzlewit.co.uk>
	<20170427214829.HhjoE%steffen@sdaoden.eu>
	<2968858.L7YnZTQ9kF@pip.chuzzlewit.co.uk>
In-Reply-To: <2968858.L7YnZTQ9kF@pip.chuzzlewit.co.uk>
Mail-Followup-To: groff@gnu.org
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 11:23:17 -0000

Deri James <deri@chuzzlewit.myzen.co.uk> wrote:
 |On Thu 27 Apr 2017 23:48:29 Steffen Nurpmeso wrote:
 |> Terrible, see the spacing errors surrounding the command list
 |> before the "Substitution" heading!  Not your fault of course, but
 |> grrrrr...
 |> 
 |> --steffen
 |
 |Well, turns out it WAS my fault! Bug in gropdf, will commit after more 
 |testing. Thanks for the heads up, is this Ok?
 |
 |http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

Yes.

--steffen


From MAILER-DAEMON Fri Apr 28 08:40:28 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d45CG-0007JN-6p
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 08:40:28 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43432)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d45CD-0007JH-V5
	for groff@gnu.org; Fri, 28 Apr 2017 08:40:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d45CA-0002vY-Sc
	for groff@gnu.org; Fri, 28 Apr 2017 08:40:25 -0400
Received: from sdaoden.eu ([217.144.132.164]:38912)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d45CA-0002vL-L6
	for groff@gnu.org; Fri, 28 Apr 2017 08:40:22 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 8D69C16056; Fri, 28 Apr 2017 14:40:20 +0200 (CEST)
Date: Fri, 28 Apr 2017 14:40:51 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Bertrand Garrigues <bertrand.garrigues@laposte.net>
Cc: groff@gnu.org, Ingo Schwarze <schwarze@usta.de>
Message-ID: <20170428124051.K_NLG%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170427214634.Y8Kbn%steffen@sdaoden.eu>
In-Reply-To: <20170427214634.Y8Kbn%steffen@sdaoden.eu>
Mail-Followup-To: Ingo Schwarze <schwarze@usta.de>, groff@gnu.org,
	Bertrand Garrigues <bertrand.garrigues@laposte.net>
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 12:40:26 -0000

i wrote:
 |Ingo Schwarze <schwarze@usta.de> wrote:
 ||Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
 ...
 |As above.  That is all for today, i spent three hopeless hours in
 |the pic lex code, even shallow cloned 67 MB of gnulib for a few KB
 |of datatable that doesn't get used the right way, and felt more
 |and more scatological.

FYI, every change of a pic source file triggered regeneration of
font-files++ (i always did ^C once pic was done).

--steffen


From MAILER-DAEMON Fri Apr 28 09:09:59 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d45ep-0002TH-SZ
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 09:09:59 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50972)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d45en-0002T9-MT
	for groff@gnu.org; Fri, 28 Apr 2017 09:09:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d45em-0005ZU-QF
	for groff@gnu.org; Fri, 28 Apr 2017 09:09:57 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:43691)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d45em-0005ZF-KA
	for groff@gnu.org; Fri, 28 Apr 2017 09:09:56 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d45ej-0007Sr-Iu; Fri, 28 Apr 2017 15:09:54 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d45ej-0007uF-8e; Fri, 28 Apr 2017 15:09:53 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d45ej-0005Mb-2O; Fri, 28 Apr 2017 15:09:53 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id ae86544a;
	Fri, 28 Apr 2017 15:09:53 +0200 (CEST)
Date: Fri, 28 Apr 2017 15:09:53 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: groff@gnu.org
Cc: g.branden.robinson@gmail.com
Message-ID: <20170428130953.GB45079@athene.usta.de>
References: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
	<20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
	<20170428.075455.1859991191870751849.wl@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170428.075455.1859991191870751849.wl@gnu.org>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:09:58 -0000

Hi,

Werner LEMBERG wrote on Fri, Apr 28, 2017 at 07:54:55AM +0200:
> g.branden.robinson wrote: 

>> It'd be nice if 3 year-old bugs could get some feedback from the
>> maintenance team.
>> 
>> What needs to happen to make that possible?

> A new maintainer.

While that would no doubt be excellent, a few additional people who
regularly propose bugfix patches and who regularly review and commit
existing bugfix patches would already mitigate the worst problems,
even if those people do not take the hat of "maintainer" right away.

Carsten Kunze has demonstrated recently that providing relevant help
of exactly that kind is feasible and very worthwhile, even without
becoming "the maintainer".

Bertrand Garrigues has even volunteered to coordinate a release,
and even though that project isn't finished yet, given the excellent
experience with his work on automake integration, i trust that he
will eventually complete it.  Unless i missed something, he did
not say that he intends to become "the maintainer", either.

Yours,
  Ingo


P.S.
Past experience has demonstrated that willingness to take
maintainership alone is insuffient to help the project if it
is not accompagnied by actively doing some real work on the
project.

In practice, people who actively both contribute patches and review
and commit patches sent in by others are most likely to eventually
become fit for and agree to take maintainer responsibility -
without having to commit to full responsibility early on.

Admittedly, in a core GNU project, this normal process of acquiring
new developers is harder than in other projects because new committers
are required to sign the FSF Copyright Assignment (a legal contract
under the law of the State of Massachusetts).  That contract does
not only attempt to transfer ownership of Copyright, but also
contains additional clauses requiring the developer to provide some
specific warranties to the FSF and hold the FSF harmless from damage
arising out of breach of that warranty.  While it may not seem
likely that a well-meaning, diligent developer suffers financial
loss due to unintentional breach of those clauses, some developers
(myself included) are unwilling to sign such provisions (both
regarding transfer of Copyright and regarding warranties) and hence
cannot become committers.

Those artificial barriers make it even more important that those
people who do not mind signing an FSF Copyright assignment do
actively contribute, and if that should result in an invitation to
join the groff project, become committers and help to review and
commit (or reject if need be) those patches that would otherwise
be stuck in the bugtracker.


From MAILER-DAEMON Fri Apr 28 09:15:16 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d45jw-00076O-N7
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 09:15:16 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52842)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d45jt-00073P-IW
	for groff@gnu.org; Fri, 28 Apr 2017 09:15:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d45js-00088S-6x
	for groff@gnu.org; Fri, 28 Apr 2017 09:15:13 -0400
Received: from mail-yw0-x241.google.com ([2607:f8b0:4002:c05::241]:35190)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d45js-00088O-0O
	for groff@gnu.org; Fri, 28 Apr 2017 09:15:12 -0400
Received: by mail-yw0-x241.google.com with SMTP id k11so4896753ywb.2
	for <groff@gnu.org>; Fri, 28 Apr 2017 06:15:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=XOhtmVmCYlrnLqCfnhbXcGMOZ0u6YLk2yoaU7n7RPfc=;
	b=aHXHzt5SmSQeqBwiUVgNHXid/wGChA7zPgVHqU63EKtHY+obVFTQtzDke3ZBNBaCHc
	glFddVTJvj7XyngLWyw1oGE+3exweCzZrsECYOcWcxL2qb2OLJfg4fO/IgPxKM8V0RWR
	UELtck0XMThjY7MuH08bXv0e2F10JlMg3quhiMGyjqwxL43Uu6ONFrCrys50XZzZnIIi
	zENFEB5z3C2CDSPoOHMKmt+pkyCPGshZfYafk3x39LTYskBYPXDzXdFX9rgQh47nTo05
	viqGiu8WMnrj78l/8JHfESlfICrWkFNRooqK88PJOthLTTZa8XgOz0gzlksg8XAGNNPt
	WBPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=XOhtmVmCYlrnLqCfnhbXcGMOZ0u6YLk2yoaU7n7RPfc=;
	b=jYpI6YAQtyrH10X/h3Wd/0TyOJmtAJ/BNtNDTzrhZ/wlzhqJ5ybJhtmQ/1hIpm4nDi
	g2ianwQK3jocxpWom5XjCWhQGWWcKIHUKnaQZrszu1VmovwDlsHYk5I/kEL6uDhTcp5h
	4KgB4GyggDHHoJe8SQ6NIygvPpnsZ54w56LFXWHAejMydV6CyVmtke6L1G8+RB+vl9kF
	xj1KPXVo8I+llDQrCVFvLV/eq3J96vZGrTaRnIRtl3eNoeceOaHROa663BlHOD8UMX/o
	kZCaZtWYVi2ftb+wmT6fG8VA7IztG6kk+HH697Oo0k86KnHHRjQp411JG7Xl4sIm49Jo
	HbBQ==
X-Gm-Message-State: AN3rC/7vPVyQJMXbLJRYs90qQQYvAMbgjvfAgQh/BlKKQzb8MqcBTNhJ
	c6cVs/SEIA7i3P0HbhfskQYihPiQIw==
X-Received: by 10.129.49.144 with SMTP id x138mr8917582ywx.171.1493385311458; 
	Fri, 28 Apr 2017 06:15:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Fri, 28 Apr 2017 06:14:55 -0700 (PDT)
In-Reply-To: <20170428130953.GB45079@athene.usta.de>
References: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
	<20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
	<20170428.075455.1859991191870751849.wl@gnu.org>
	<20170428130953.GB45079@athene.usta.de>
From: John Gardner <gardnerjohng@gmail.com>
Date: Fri, 28 Apr 2017 23:14:55 +1000
Message-ID: <CAGcdajfLV0P+w+wtGbpYyqq4NYpWGLxZr49PTs5+QkhiHLAJMQ@mail.gmail.com>
To: groff <groff@gnu.org>, Ingo Schwarze <schwarze@usta.de>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::241
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:15:15 -0000

Yikes, that's an ugly dark side.


> Those artificial barriers make it even more important that those
> people who do not mind signing an FSF Copyright assignment do
> actively contribute, and if that should result in an invitation to
> join the groff project, become committers and help to review and
> commit (or reject if need be) those patches that would otherwise
> be stuck in the bugtracker.


ISC forever!

On 28 April 2017 at 23:09, Ingo Schwarze <schwarze@usta.de> wrote:

> Hi,
>
> Werner LEMBERG wrote on Fri, Apr 28, 2017 at 07:54:55AM +0200:
> > g.branden.robinson wrote:
>
> >> It'd be nice if 3 year-old bugs could get some feedback from the
> >> maintenance team.
> >>
> >> What needs to happen to make that possible?
>
> > A new maintainer.
>
> While that would no doubt be excellent, a few additional people who
> regularly propose bugfix patches and who regularly review and commit
> existing bugfix patches would already mitigate the worst problems,
> even if those people do not take the hat of "maintainer" right away.
>
> Carsten Kunze has demonstrated recently that providing relevant help
> of exactly that kind is feasible and very worthwhile, even without
> becoming "the maintainer".
>
> Bertrand Garrigues has even volunteered to coordinate a release,
> and even though that project isn't finished yet, given the excellent
> experience with his work on automake integration, i trust that he
> will eventually complete it.  Unless i missed something, he did
> not say that he intends to become "the maintainer", either.
>
> Yours,
>   Ingo
>
>
> P.S.
> Past experience has demonstrated that willingness to take
> maintainership alone is insuffient to help the project if it
> is not accompagnied by actively doing some real work on the
> project.
>
> In practice, people who actively both contribute patches and review
> and commit patches sent in by others are most likely to eventually
> become fit for and agree to take maintainer responsibility -
> without having to commit to full responsibility early on.
>
> Admittedly, in a core GNU project, this normal process of acquiring
> new developers is harder than in other projects because new committers
> are required to sign the FSF Copyright Assignment (a legal contract
> under the law of the State of Massachusetts).  That contract does
> not only attempt to transfer ownership of Copyright, but also
> contains additional clauses requiring the developer to provide some
> specific warranties to the FSF and hold the FSF harmless from damage
> arising out of breach of that warranty.  While it may not seem
> likely that a well-meaning, diligent developer suffers financial
> loss due to unintentional breach of those clauses, some developers
> (myself included) are unwilling to sign such provisions (both
> regarding transfer of Copyright and regarding warranties) and hence
> cannot become committers.
>
> Those artificial barriers make it even more important that those
> people who do not mind signing an FSF Copyright assignment do
> actively contribute, and if that should result in an invitation to
> join the groff project, become committers and help to review and
> commit (or reject if need be) those patches that would otherwise
> be stuck in the bugtracker.
>
>

From MAILER-DAEMON Fri Apr 28 09:32:42 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d460o-0007oa-Oq
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 09:32:42 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57556)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d460m-0007oC-2J
	for groff@gnu.org; Fri, 28 Apr 2017 09:32:41 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d460l-0008LM-8x
	for groff@gnu.org; Fri, 28 Apr 2017 09:32:40 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:50994)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d460l-0008Ki-37
	for groff@gnu.org; Fri, 28 Apr 2017 09:32:39 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d460h-0003d0-38; Fri, 28 Apr 2017 15:32:36 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d460g-0004pp-Ne; Fri, 28 Apr 2017 15:32:34 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d460g-0005l3-II; Fri, 28 Apr 2017 15:32:34 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 45521cc3;
	Fri, 28 Apr 2017 15:32:34 +0200 (CEST)
Date: Fri, 28 Apr 2017 15:32:34 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: John Gardner <gardnerjohng@gmail.com>
Cc: groff <groff@gnu.org>
Message-ID: <20170428133234.GC45079@athene.usta.de>
References: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
	<20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
	<20170428.075455.1859991191870751849.wl@gnu.org>
	<20170428130953.GB45079@athene.usta.de>
	<CAGcdajfLV0P+w+wtGbpYyqq4NYpWGLxZr49PTs5+QkhiHLAJMQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGcdajfLV0P+w+wtGbpYyqq4NYpWGLxZr49PTs5+QkhiHLAJMQ@mail.gmail.com>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:32:41 -0000

Hi John,

John Gardner wrote on Fri, Apr 28, 2017 at 11:14:55PM +1000:

> ISC forever!

Well, kind of "no" in the present context.

While i do personally prefer the ISC license for software that
i write myself, i also fully respect James Clark's decision to
publish groff under the GPL, and i do acknowledge that the FSF
owns groff and is free to define policies for it.

So, promoting the ISC license, no matter whether it may or may not
be laudable in general, is not a very efficient way to help the
groff project, and the list <groff@gnu.org> is arguably not the
ideal place for such advocacy.

While it is useful to remain aware that it is harder for a core
GNU project to gain developers than for an ISC-based project,
the task *here* is to bring in developers for groff all the same.

Yours,
  Ingo


From MAILER-DAEMON Fri Apr 28 09:36:47 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d464k-0000Rw-Qr
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 09:36:46 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58790)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d464i-0000QA-FQ
	for groff@gnu.org; Fri, 28 Apr 2017 09:36:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d464h-0002JA-IW
	for groff@gnu.org; Fri, 28 Apr 2017 09:36:44 -0400
Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]:35665)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d464h-0002Ix-E8
	for groff@gnu.org; Fri, 28 Apr 2017 09:36:43 -0400
Received: by mail-yw0-x242.google.com with SMTP id k11so4942032ywb.2
	for <groff@gnu.org>; Fri, 28 Apr 2017 06:36:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=f9/Dm3djSoxBbbgJPFQ0komOHYn9Wt3un0+I6rUq3rA=;
	b=p6mdenrCll66Vgkq0kkFjtveQXUaCdE6gdSo9ghKt+rqw+/43bH68dTXcgKs8oxxoe
	KLQ1J2bc3Ht6n1IB3eyMrMdAP23HirVWSo5kKazv6NHx7nBHIZ5BX6Wczf1mt+suxCpj
	Zz21pxNiL+r8iFxxE/m0CmZP+hqA5ivVOvvB4zeBmF+JZqEnVRTF19rlD7omxasU0ypC
	oEBUh5r5EYtHuHa7VuB+3v7YJpqGs177f/li4Olqn1HghNET729v830p0r0xEgJxAOpB
	cx6TIJjydyusxbavNmvk6Ho9huJPHwviZJH0iZhGTcNQWoR5P1/46y8XLN0AvuTSiDp3
	3n6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=f9/Dm3djSoxBbbgJPFQ0komOHYn9Wt3un0+I6rUq3rA=;
	b=Xq1MU/sQN0h5oBuv5fCw3klXhoHayzKGcbXOiG8F42INAxF/N+XHym0gkckkIJmHm6
	vayHzqNaKLB0ul7YKrpekAT81LKi2y94SK6eSg0Ah6onay5HxVmCI8yJSb5bYDYF9vql
	VSfTfMm+raPrbfwu1+GoGB4XyytJ4i+WeOgDC9PhRrMVY7fT2C9OXGBBYdLXhzvWeZvQ
	GqZGLjlDGHxOnpvuzeXxTQmX9AW4T1BwcQpO7PNc1NOStlCz0IX9yDN+xL+x9BZ999AQ
	KWrZOCh8uZrc5+Lcu+hBIYzxM52nCU82C+Gy8RqmxWE4CkGTgGwjga+kDGtUp3e9dIb7
	S61Q==
X-Gm-Message-State: AN3rC/4i/wYaXwQNVOV6qvtta+KbgVmxS0weXeAMGcploDqhKXoaQ35I
	BWJBJ9Xv+zW/Qb3CPdtA8jZI7lFm/g==
X-Received: by 10.129.49.144 with SMTP id x138mr9009294ywx.171.1493386602615; 
	Fri, 28 Apr 2017 06:36:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Fri, 28 Apr 2017 06:36:25 -0700 (PDT)
In-Reply-To: <20170428133234.GC45079@athene.usta.de>
References: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170427191128.GA4772@rhi.hi.is>
	<20170428044424.p2x7jlwqueyl6vgz@crack.deadbeast.net>
	<20170428.075455.1859991191870751849.wl@gnu.org>
	<20170428130953.GB45079@athene.usta.de>
	<CAGcdajfLV0P+w+wtGbpYyqq4NYpWGLxZr49PTs5+QkhiHLAJMQ@mail.gmail.com>
	<20170428133234.GC45079@athene.usta.de>
From: John Gardner <gardnerjohng@gmail.com>
Date: Fri, 28 Apr 2017 23:36:25 +1000
Message-ID: <CAGcdajfL8Q0bxmniTqRqoG38ALCZOVizT3+-SNvG=jqiVirxtQ@mail.gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::242
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:36:45 -0000

Haha, don't worry, I respect all open-source licenses. That was intended as
a jovial remark.

Picking a license is, of course, a developer's personal decision.
Personally, I just prefer simplicity and openness, hence my preference for
the ISC license.

Didn't expect that would be taken too seriously, BTW.


On 28 April 2017 at 23:32, Ingo Schwarze <schwarze@usta.de> wrote:

> Hi John,
>
> John Gardner wrote on Fri, Apr 28, 2017 at 11:14:55PM +1000:
>
> > ISC forever!
>
> Well, kind of "no" in the present context.
>
> While i do personally prefer the ISC license for software that
> i write myself, i also fully respect James Clark's decision to
> publish groff under the GPL, and i do acknowledge that the FSF
> owns groff and is free to define policies for it.
>
> So, promoting the ISC license, no matter whether it may or may not
> be laudable in general, is not a very efficient way to help the
> groff project, and the list <groff@gnu.org> is arguably not the
> ideal place for such advocacy.
>
> While it is useful to remain aware that it is harder for a core
> GNU project to gain developers than for an ISC-based project,
> the task *here* is to bring in developers for groff all the same.
>
> Yours,
>   Ingo
>

From MAILER-DAEMON Fri Apr 28 11:24:27 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d47kx-0006iU-DO
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 11:24:27 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59709)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lawrence.jones@siemens.com>) id 1d47ku-0006iK-Qu
	for groff@gnu.org; Fri, 28 Apr 2017 11:24:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lawrence.jones@siemens.com>) id 1d47kq-0003Cf-SO
	for groff@gnu.org; Fri, 28 Apr 2017 11:24:24 -0400
Received: from usslmhub002.ugs.com ([134.244.32.85]:30831 helo=ugs.com)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <lawrence.jones@siemens.com>)
	id 1d47kq-0003BQ-MK
	for groff@gnu.org; Fri, 28 Apr 2017 11:24:20 -0400
Received: from USSLMMBX005.net.plm.eds.com (161.134.138.55) by
	USSLMHUB002.net.plm.eds.com (134.244.32.85) with Microsoft SMTP Server
	(TLS) id 14.3.319.2; Fri, 28 Apr 2017 10:03:38 -0500
Received: from USCIMMBX004.net.plm.eds.com (161.134.134.38) by
	USSLMMBX005.net.plm.eds.com (161.134.138.55) with Microsoft SMTP Server
	(TLS) id 14.3.319.2; Fri, 28 Apr 2017 10:03:37 -0500
Received: from USCIMMBX005.net.plm.eds.com ([fe80::b42e:6879:70b6:85d0]) by
	USCIMMBX004.net.plm.eds.com ([fe80::2df3:5d11:461b:6797%23]) with mapi
	id 14.03.0319.002; Fri, 28 Apr 2017 11:03:37 -0400
From: "Jones, Larry" <lawrence.jones@siemens.com>
To: John Gardner <gardnerjohng@gmail.com>
CC: "groff@gnu.org" <groff@gnu.org>
Thread-Topic: [Groff] Problems with arcs and angles
Thread-Index: AQHSv+DDa1olNV6000urzabswhQgb6Ha1JgQgAAI/GA=
Date: Fri, 28 Apr 2017 15:03:37 +0000
Message-ID: <F9035A933A372F4D85559B6B253DC408013894151F@USCIMMBX005.net.plm.eds.com>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [146.122.224.49]
X-TM-AS-Product-Ver: SMEX-12.0.0.1727-8.100.1062-23036.005
X-TM-AS-Result: No--32.904700-0.000000-31
X-TM-AS-MatchedID: 1-150567-700949-702020-139010-139006-710556-187165-110462
	-188199-703786-106660-863828-701923-700115-139705-101349-705388-700537-1360
	70-701632-188019-706891-707467-700040-702796-121577-705441-704921-701155-70
	4179-700756-701817-700840-700423-703963-703283-709823-701611-700942-136307-
	701604-707190-705901-708863-300010-701337-148004-148046-148133-20026-36048-
	42000-42003-52000
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-detected-operating-system: by eggs.gnu.org: Windows 7 or 8 [fuzzy]
X-Received-From: 134.244.32.85
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:24:26 -0000

U29ycnksIEkganVzdCBub3RpY2VkIHRoYXQgeW91ciBkcmF3aW5nIGNhbnZhcyBtZWFzdXJlcyB0
aGUgYW5nbGVzIGNsb2Nrd2lzZSByYXRoZXIgdGhhbiB0aGUgdHJhZGl0aW9uYWwgY291bnRlcmNs
b2Nrd2lzZSBzbyB5b3UgbmVlZCB0byBuZWdhdGUgdGhlIHkgY29vcmRpbmF0ZXMgdG8gYXRhbjI6
DQoNCnN0YXJ0QW5nbGUgPSBNYXRoLmF0YW4yKGNlbnRyZVkgLSBzdGFydFksIHN0YXJ0WCAtIGNl
bnRyZVgpDQplbmRBbmdsZSA9IE1hdGguYXRhbjIoY2VudHJlWSAtIGVuZFksIGVuZFggLSBjZW50
cmVYKQ0KDQotTGFycnkNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBK
b25lcywgTGFycnkgKERGIFBMIFBEUyBFSSBVUykNCj4gU2VudDogRnJpZGF5LCBBcHJpbCAyOCwg
MjAxNyAxMDoyNyBBTQ0KPiBUbzogJ0pvaG4gR2FyZG5lcicgPGdhcmRuZXJqb2huZ0BnbWFpbC5j
b20+DQo+IFN1YmplY3Q6IFJFOiBbR3JvZmZdIFByb2JsZW1zIHdpdGggYXJjcyBhbmQgYW5nbGVz
DQo+IA0KPiBzdGFydEFuZ2xlID0gYXRhbjIoc3RhcnRZIC0gY2VudHJlWSwgc3RhcnRYIC0gY2Vu
dHJlWCkNCj4gZW5kQW5nbGUgPSBhdGFuMihlbmRZIC0gY2VudHJlWSwgZW5kWCAtIGNlbnRyZVgp
DQo+IHJhZGl1cyA9IHNxcnQoKHN0YXJ0WSAtIGNlbnRyZVkpICogKHN0YXJ0WSAtIGNlbnRyZVkp
ICsgKHN0YXJ0WCAtIGNlbnRyZVgpICoNCj4gKHN0YXJ0WCAtIGNlbnRyZVgpKQ0KPiANCj4gLUxh
cnJ5DQo+IA0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogR3JvZmYg
W21haWx0bzpncm9mZi0NCj4gYm91bmNlcytsYXdyZW5jZS5qb25lcz1zaWVtZW5zLmNvbUBnbnUu
b3JnXQ0KPiA+IE9uIEJlaGFsZiBPZiBKb2huIEdhcmRuZXINCj4gPiBTZW50OiBGcmlkYXksIEFw
cmlsIDI4LCAyMDE3IDE6MzIgQU0NCj4gPiBUbzogZ3JvZmYgPGdyb2ZmQGdudS5vcmc+DQo+ID4g
U3ViamVjdDogW0dyb2ZmXSBQcm9ibGVtcyB3aXRoIGFyY3MgYW5kIGFuZ2xlcw0KPiA+DQo+ID4g
SGVsbG8hDQo+ID4NCj4gPiBTb21lIHRpbWUgYWdvLCBJIGFubm91bmNlZCBteSBpbnRlbnQgdG8g
YnVpbGQgYSBtYW4tcGFnZSBwcmV2aWV3ZXIgZm9yIGENCj4gPiB0ZXh0LWVkaXRvciBuYW1lZCBB
dG9tIDxodHRwczovL2F0b20uaW8vPi4gV29yayBpcyBjb21pbmcgYWxvbmcgbmljZWx5Og0KPiA+
IHRoaXMgcGFnZSA8aHR0cHM6Ly9jZG4ucmF3Z2l0LmNvbS9BbGhhZGlzL2xhbmd1YWdlLQ0KPiA+
IHJvZmYvYTdjMDc3NDRhOWQ0NGFkZjMyYTU0NjY0NmY3YThkNTdkNTJlNmU1OC9wcmV2aWV3LXR0
eS5odG1sPg0KPiA+IHdhcyBnZW5lcmF0ZWQgdXNpbmcgYSBsaWdodHdlaWdodCB0b2tlbmlzZXIN
Cj4gPiA8aHR0cHM6Ly9naXRodWIuY29tL0FsaGFkaXMvbGFuZ3VhZ2UtDQo+IHJvZmYvYmxvYi9y
ZW5kZXJlci9saWIvdG9rZW5pc2VyLmpzPg0KPiA+IHdyaXR0ZW4gaW4gSmF2YVNjcmlwdCwgd2hp
Y2ggcHJvY2Vzc2VzIEdyb2ZmJ3MgaW50ZXJtZWRpYXRlIG91dHB1dA0KPiBsYW5ndWFnZQ0KPiA+
IGludG8gd2ViLWJhc2VkIGZvcm1hdHMuIFRoYXQncyB0aGUgbnJvZmYgcHJldmlldy4uLiBJJ20g
bm93IGhhbGZ3YXkNCj4gdGhyb3VnaA0KPiA+IGRldmVsb3BpbmcgdGhlIHRyb2ZmIHByZXZpZXdl
ciwgd2hpY2ggdXNlcyBIVE1MNSBjYW52YXMNCj4gPiA8aHR0cHM6Ly9kZXZlbG9wZXIubW96aWxs
YS5vcmcvZW4tDQo+ID4gVVMvZG9jcy9XZWIvQVBJL0NhbnZhc1JlbmRlcmluZ0NvbnRleHQyRD4N
Cj4gPiB0ZWNobm9sb2d5IHRvIGRyYXcgcmVhbHRpbWUgcHJldmlld3Mgb2YgYW4gb3BlbmVkIFJv
ZmYgZG9jdW1lbnQuDQo+ID4NCj4gPiBTbyBmYXIsIHNvIGdvb2QhDQo+ID4NCj4gPGh0dHBzOi8v
Y2xvdWQuZ2l0aHVidXNlcmNvbnRlbnQuY29tL2Fzc2V0cy8yMzQ2NzA3LzI1NTE0ODc4LzczMmUw
OWVhLQ0KPiA+IDJjMjMtMTFlNy05N2VhLTk2NzRkMzg0NWRkMS5wbmc+DQo+ID4gSSdtDQo+ID4g
cHJvdWQgb2YgaG93IHRoaXMgaXMgdHVybmluZyBvdXQ6IGJlYXIgaW4gbWluZCwgdGhhdCBwcmV2
aWV3IHVwZGF0ZXMgYXMgdGhlDQo+ID4gdXNlciB0eXBlcywgc28gaXQnbGwgZmVlbCBsaWtlIGFu
IGVmZmljaWVudCByZXBsYWNlbWVudCBmb3IgYSB3b3JkIHByb2Nlc3NpbmcNCj4gPiBwcm9ncmFt
LCBoYWhhLg0KPiA+DQo+ID4gSSdtIGN1cnJlbnRseSBzdHVjayB3aXRoIGRyYXdpbmcgYXJjcw0K
PiA+IDxodHRwczovL2RldmVsb3Blci5tb3ppbGxhLm9yZy9lbi0NCj4gPiBVUy9kb2NzL1dlYi9B
UEkvQ2FudmFzUmVuZGVyaW5nQ29udGV4dDJEL2FyYz4uDQo+ID4gVGhpcw0KPiA+IG1pZ2h0IGJl
IHRoZSB3cm9uZyBmb3J1bSB0byBhc2sgZm9yIGhlbHAgd2l0aCB0cmlnb25vbWV0cnksIGJ1dCBJ
IHdhcw0KPiA+IHBsYW5uaW5nIHRvIGFubm91bmNlIHByb2dyZXNzIGV2ZW50dWFsbHkgYW55d2F5
Lg0KPiA+DQo+ID4gTm93LCB0aGlzIHBpYyBjb2RlOg0KPiA+DQo+ID4gLlBTDQo+ID4gPiAiKyIg
YXQgMCwwDQo+ID4gPiBhcmMgLT4gZnJvbSAwLjUsMCB0byAwLDAuNQ0KPiA+ID4gYXJjIC0+IGN3
IGZyb20gMCwwIHRvIDEsMC41DQo+ID4gPiBhcmMgLT4gY3cgZnJvbSAwLDAgdG8gMiwwIHJhZCAx
NQ0KPiA+ID4gLlBFDQo+ID4NCj4gPg0KPiA+IC4uLiBzaG91bGQgbG9vayBsaWtlIHRoaXMNCj4g
Pg0KPiA8aHR0cHM6Ly9jbG91ZC5naXRodWJ1c2VyY29udGVudC5jb20vYXNzZXRzLzIzNDY3MDcv
MjU1MTUwNzEvNGJjNDY4NzAtDQo+ID4gMmMyNS0xMWU3LTk4ODMtOTI0OGU0YjRhYTY4LnBuZz4u
DQo+ID4gSW5zdGVhZCwgaXQsIHVoLCBsb29rcyBsaWtlIHRoaXMNCj4gPg0KPiA8aHR0cHM6Ly9j
bG91ZC5naXRodWJ1c2VyY29udGVudC5jb20vYXNzZXRzLzIzNDY3MDcvMjU1MTUwODQvNWQ4NGVl
ZDYtDQo+ID4gMmMyNS0xMWU3LThjZGQtYmRiNjVmNzgwNGU5LnBuZz4NCj4gPiAuDQo+ID4NCj4g
PiBHcm9mZidzIG91dHB1dCBnaXZlcyBtZSB0aGVzZSBjb29yZGluYXRlcyB0byBnbyBieToNCj4g
Pg0KPiA+ICAgIC0gc3RhcnRYLCBzdGFydFkgLSBDb29yZGluYXRlcyBvZiB0aGUgYXJjJ3Mgc3Rh
cnRpbmcgcG9pbnQNCj4gPiAgICAtIGNlbnRyZVgsIGNlbnRyZVkgLSBDb29yZGluYXRlcyBvZiB0
aGUgYXJjJ3MgY2VudHJlDQo+ID4gICAgLSBlbmRYLCBlbmRZIC0gQ29vcmRpbmF0ZXMgb2YgdGhl
IGFyYydzIHRlcm1pbmFsIHBvaW50DQo+ID4NCj4gPiBCdXQgdGhlIGNhbnZhcyBhcmMgbWV0aG9k
IEknbSB3b3JraW5nIHdpdGggcmVxdWlyZXMgYWxsIG9mIHRoZXNlOg0KPiA+DQo+ID4gICAgLSB4
IC0gVGhlIHggY29vcmRpbmF0ZSBvZiB0aGUgYXJjJ3MgY2VudHJlLg0KPiA+ICAgIC0geSAtIFRo
ZSB5IGNvb3JkaW5hdGUgb2YgdGhlIGFyYydzIGNlbnRyZS4NCj4gPiAgICAtIHJhZGl1cyAtIFRo
ZSBhcmMncyByYWRpdXMuDQo+ID4gICAgLSBzdGFydEFuZ2xlIC0gVGhlIGFuZ2xlIGF0IHdoaWNo
IHRoZSBhcmMgc3RhcnRzLCBtZWFzdXJlZCBjbG9ja3dpc2UNCj4gPiAgICBmcm9tIHRoZSBwb3Np
dGl2ZSB4IGF4aXMgYW5kIGV4cHJlc3NlZCBpbiByYWRpYW5zLg0KPiA+ICAgIC0gZW5kQW5nbGUg
LSBUaGUgYW5nbGUgYXQgd2hpY2ggdGhlIGFyYyBlbmRzLCBtZWFzdXJlZCBjbG9ja3dpc2UgZnJv
bQ0KPiA+ICAgIHRoZSBwb3NpdGl2ZSB4IGF4aXMgYW5kIGV4cHJlc3NlZCBpbiByYWRpYW5zLg0K
PiA+DQo+ID4gSXQncyBlbWJhcnJhc3NpbmcgdG8gYmUgc3R1Y2sgb24gc29tZXRoaW5nIHNvIG9i
dmlvdXMsIGJ1dCB0aGlzIGlzIHdoYXQncw0KPiA+IGJsb2NraW5nIGZ1cnRoZXIgcHJvZ3Jlc3Mu
Li4NCg==


From MAILER-DAEMON Fri Apr 28 11:33:02 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d47tF-0002TX-G5
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 11:33:01 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34192)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d47tD-0002Rx-8z
	for groff@gnu.org; Fri, 28 Apr 2017 11:33:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d47tA-0000gR-3P
	for groff@gnu.org; Fri, 28 Apr 2017 11:32:59 -0400
Received: from mail-yw0-x236.google.com ([2607:f8b0:4002:c05::236]:35542)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d47t9-0000fe-VM
	for groff@gnu.org; Fri, 28 Apr 2017 11:32:56 -0400
Received: by mail-yw0-x236.google.com with SMTP id u70so32692439ywe.2
	for <groff@gnu.org>; Fri, 28 Apr 2017 08:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=dHL8s+OIgvt2Ftj2tRet7QGWEVZXYz5Vmh1INHzCvoI=;
	b=hmNNGldpCKz5NSm/buKNLTHKCt2DTfMP2utWYyorAvA40imH8nTn5VoJsmGf6dUDeG
	+X87c5KKhptUUqt2wuAx8c7ELqaQwUH+s13Kk1Esz6VzlUlHQHu8+wOiPH/bC4yZFbOo
	VnDNmMQTzd+v42+Q01ELs9LzgPmEnu/wSDbKA8crq44cXpydX3A3e29OzVQbw0BRr+yE
	6Ro/uT9Xd0+V1fPB7vwckMcb5llMAo7dV88jbn1QtvNPILVdMZKhwk1RxclbSBhyAHAt
	/8xc6zscOsrZonZAtrDGcJnYciNfo73voSpnI26eZPwJWN0sSrfORPoF2Fk8TnmyjLRP
	f9FA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=dHL8s+OIgvt2Ftj2tRet7QGWEVZXYz5Vmh1INHzCvoI=;
	b=sl+hckONCtrCFVxjkGHhwaxtvn8J/n9iR8HK9now1xWRR3774lS8WFRJI+Wim0ackP
	KFp8NGYXRB7SJt9vl46WVXjIaTQ5VVhTnp+3nRk9mHfneK4yelTQwNmXf1oWyeu3sgVR
	2JIwIOMy9HIzXLJm4I099/CD2qU4vMGOyciyeVTrCteIgMDeNBkp4VEm/7dt7cPFJQ8P
	tHGg213lCUYN/qVDLih4ppIpl4i6xqXPJapcveXbnbOl2nDC6KVL7w1wZFFqmwLbR1mm
	x737hY+Db9jdgYG7kqXoyPscZpQVzNuisy0ToPZgmXz8SOysRRY1p+/OK0o6boNzi8kd
	9Cng==
X-Gm-Message-State: AN3rC/7c9t2ewoQwyUVDx/HQ80SNgFmDrTSqT7O6GqKFK6INU8VdKcIr
	KUJJxsbMzPpsh1ayhPE=
X-Received: by 10.129.161.206 with SMTP id y197mr7755649ywg.166.1493393574668; 
	Fri, 28 Apr 2017 08:32:54 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	q127sm3200088ywd.69.2017.04.28.08.32.52 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Fri, 28 Apr 2017 08:32:53 -0700 (PDT)
Date: Fri, 28 Apr 2017 11:32:51 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff <groff@gnu.org>
Message-ID: <20170428153249.6g7742e72mfu6beo@crack.deadbeast.net>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
	<20170428062245.nsmvvcp6nvpdhul5@crack.deadbeast.net>
	<CAGcdajcLje47Wph1xAkdzkzNsvSd5rbqij=EkFQibdym6E7wDw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="q4guz226yuoy5nhb"
Content-Disposition: inline
In-Reply-To: <CAGcdajcLje47Wph1xAkdzkzNsvSd5rbqij=EkFQibdym6E7wDw@mail.gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::236
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:33:00 -0000


--q4guz226yuoy5nhb
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-28T17:40:37+1000, John Gardner wrote:
> >
> > Does this help or did I manage to misunderstand you completely?
>=20
>=20
> I'm afraid so... the issue isn't with calculating radii, but calculating
> the `startAngle` and `endAngle`.

Right.  I got that but apparently communicated poorly.  Sorry.

To calculate the angles you need 3 things:
1. A library with arccos() and arcsin() functions.
2. The x and y coordinates of each point of interest, relative to the
   center.
3. The radius of the arc, measured from its center.

The arccos() and arcsin() functions answer the question: "Given this
point (x, y) on the arc of a circle, how do I find the angle that puts
me there?"

startAngle =3D arccos(x_start / radius)

endAngle =3D arccos(x_end / radius)

Depending on which quadrant the angles are in, you might find it easier
to use:

startAngle =3D arcsin(y_start / radius)

endAngle =3D arcsin(y_end / radius)

Or you can just use one of the functions and adjust the signs yourself.
This is what I was getting at when I talked about the inverse trig
functions not being one-to-one.  This is because, for example, both =CF=80/4
and 7=CF=80/4 have the same cosine, i.e., you get the same x coordinate from
those angles.  But if you take the algebraic signs of both your x and y
coordinates in to account, you should be able to get the angle values
you need.

Is this any sort of improvement?

Regards,
Branden

--q4guz226yuoy5nhb
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkDYJcACgkQ0Z6cfXEm
bc6XvBAAkPk/YziV9iIEIbZoSBwNRO1MO4XnSjPokECXVn/5WrgIWYicvJUKmK/7
STjv+af0X0AsxoP27EMD9fBRehmYcQScIaEOJD0pOF1lfqC1MM8Ej5hPnV80C5m9
L/hPbhuXu0T3/89ALP+30zyKsoEvZIMJHwzL0mv9nkzj17rBCk9cicJgHAOa7BJj
Bj24uys+kGqLvoYkM3wOJE75fyGI/59+iUustd/2AiDWmuvG5+/WynWDGerawT+D
AGQrQTWa90HGUGYS/mAaq29HW4va6gw5Yrh+NDK95/9Sz/8tJ7ZpF72efannhD1O
cg+RGmRbEk1qZzK07qGDtaMncpmjhmDrHbDROKw3a+W0mGTFRIePiJmwUfKAOoa0
7nmUwd28k05DoN2lxB9dDuqQ7l9TrUGx+lj0GUhLTSvWe5VfAJ2XYXcyVhcR3Q3/
fLV9U5Srh32WAX4B/Xi5cm97iYRHnBgtRUf/Z9wKu7KAqnoqcD3wPmZTzgACnT+V
Sk/AuQtngz/eEgtNbXuxkGt9Qk0/IcrK62RV4DZaMW9pzVSfN+YFvxfWjVNb+pAy
+s6Tqz7T+kdMzc9b72EXHp2yOg8tEBx8HQR4qKajpsPU8vOExbpr44GR7F7jEPPv
R7WBKt8x01+zHIbGap2CSTbviuZY+ZaVcwoWCseiJzRS97LW0iw=
=QWRC
-----END PGP SIGNATURE-----

--q4guz226yuoy5nhb--


From MAILER-DAEMON Fri Apr 28 11:38:53 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d47yv-0003zu-Ai
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 11:38:53 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36246)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d47ys-0003zi-JF
	for groff@gnu.org; Fri, 28 Apr 2017 11:38:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d47yp-0004GC-Df
	for groff@gnu.org; Fri, 28 Apr 2017 11:38:50 -0400
Received: from relay01.pair.com ([209.68.5.15]:58302)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d47yp-0004FN-94
	for groff@gnu.org; Fri, 28 Apr 2017 11:38:47 -0400
Received: from orac.inputplus.co.uk (unknown [80.229.181.64])
	by relay01.pair.com (Postfix) with ESMTP id DCE20D01114
	for <groff@gnu.org>; Fri, 28 Apr 2017 11:38:45 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id EDB8520302
	for <groff@gnu.org>; Fri, 28 Apr 2017 16:38:32 +0100 (BST)
To: groff <groff@gnu.org>
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
Date: Fri, 28 Apr 2017 16:38:32 +0100
Message-Id: <20170428153832.EDB8520302@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 15:38:51 -0000

Hi John,

> <https://cdn.rawgit.com/Alhadis/language-roff/a7c07744a9d44adf32a546646=
f7a8d57d52e6e58/preview-tty.html>
> <https://cloud.githubusercontent.com/assets/2346707/25514878/732e09ea-2=
c23-11e7-97ea-9674d3845dd1.png>

Gorgeous.  :-)

> Groff's output gives me these coordinates to go by:
>
>    - startX, startY - Coordinates of the arc's starting point
>    - centreX, centreY - Coordinates of the arc's centre
>    - endX, endY - Coordinates of the arc's terminal point

I'm assuming centreX and centreY are zero as it's just a simple
translation to get there.  And for the moment that startX and startY are
in the x>0, y>0 quadrant.  This gives a right-angled triangle (0, 0),
(startX, 0), (startX, startY).

> But the canvas arc method I'm working with requires all of these:
>
>    - x - The x coordinate of the arc's centre.
>    - y - The y coordinate of the arc's centre.

0, 0.

>    - radius - The arc's radius.

sqrt(startX**2, startY**2) as pic's arcs are always circular.

>    - startAngle - The angle at which the arc starts, measured clockwise
>    from the positive x axis and expressed in radians.

That's the triangle's angle at its origin corner.  That's the arc sine
of the opposite edge's length, startY.  But this assumes the radius,
i.e. triangle's hypotenuse, is 1.  When it's not, it's
asin(startY/radius).

This bit of Python might help.

    >>> from math import *
    >>> def d(r): return r / pi * 180
    ...
    >>> d(asin(0.001))
    0.05729578906238321
    >>> d(asin(0.999))
    87.43744126687686
    >>>
    >>> d(asin(1))
    90.0
    >>> d(asin(-1))
    -90.0
    >>>
    >>> d(asin(-0.001))
    -0.05729578906238321
    >>> d(asin(-0.999))
    -87.43744126687686
    >>>
    >>> d(asin(0.5))
    30.000000000000004
    >>> d(asin(sqrt(0.75)))
    60.0

You can see asin copes with [1, -1], giving [90, -90] in degrees.
You'll need to check the signs of start{X,Y}, making =CF=80/2 adjustments=
 to
the radians you obtain to handle the other quadrants.

Hope that helps.  It's been many decades since I needed this.  :-)

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Fri Apr 28 18:11:51 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4E7D-0000PM-Oh
	for mharc-groff@gnu.org; Fri, 28 Apr 2017 18:11:51 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51326)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d4E7B-0000PA-5C
	for groff@gnu.org; Fri, 28 Apr 2017 18:11:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d4E78-0000Av-02
	for groff@gnu.org; Fri, 28 Apr 2017 18:11:49 -0400
Received: from sdaoden.eu ([217.144.132.164]:38970)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <steffen@sdaoden.eu>) id 1d4E77-00006D-Oj
	for groff@gnu.org; Fri, 28 Apr 2017 18:11:45 -0400
Received: by sdaoden.eu (Postfix, from userid 1000)
	id 6029616056; Sat, 29 Apr 2017 00:11:44 +0200 (CEST)
Date: Sat, 29 Apr 2017 00:12:18 +0200
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: groff@gnu.org
Message-ID: <20170428221218.yQ0Rk%steffen@sdaoden.eu>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170427214634.Y8Kbn%steffen@sdaoden.eu>
In-Reply-To: <20170427214634.Y8Kbn%steffen@sdaoden.eu>
Mail-Followup-To: Ingo Schwarze <schwarze@usta.de>, groff@gnu.org
User-Agent: s-nail v14.9.0-pre4-20-g5500e891
OpenPGP: id=232C220BCB5690A37BD22FFDEB66022795F382CE;
	url=https://www.sdaoden.eu/downloads/steffen.asc
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
	the world can make no bugs.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 217.144.132.164
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 22:11:50 -0000

i wrote:
 |Ingo Schwarze <schwarze@usta.de> wrote:
 ||Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
 ...
 ||P.S.
 ||Only bacause i'm replying anyway and it's just five lines:
 |
 |Sure.
 |
 ||>   .Op : Ns Fl c Ar cc-addr Ns \&:
 ||>   .Fl S Ar var Ns Op Ns = Ns Ar value Ns
 ||
 ||That's full of cargo cult, things are actually much simpler
 ||even for describing such unusually complicated syntax:
 ||
 ||.Oo : Ns Fl c Ar cc-addr : Oc
 ||.Eo [: Fl c Ar cc-addr Ec :]
 |
 |  .Op : Ns Fl c Ar cc-addr Ns \&:
 |  .Eo [: Fl c Ar cc-addr Ns :] Ec
 |  .Oo : Ns Fl c Ar cc-addr : Oc
 |
 |I would like the last one best, if the Ns could go from the front.

Actually i now see it was on purpose: with .Oo .. .Oc and without
the .Ns stuff there may appear linebreaks inside an option, which
i wanted to avoid.

--steffen


From MAILER-DAEMON Sat Apr 29 06:25:41 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4PZN-0006lV-Bv
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 06:25:41 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46852)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4PZL-0006kd-5h
	for groff@gnu.org; Sat, 29 Apr 2017 06:25:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4PZG-0003wb-82
	for groff@gnu.org; Sat, 29 Apr 2017 06:25:39 -0400
Received: from mail-yw0-x230.google.com ([2607:f8b0:4002:c05::230]:34192)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4PZG-0003wX-3S
	for groff@gnu.org; Sat, 29 Apr 2017 06:25:34 -0400
Received: by mail-yw0-x230.google.com with SMTP id k11so40713153ywb.1
	for <groff@gnu.org>; Sat, 29 Apr 2017 03:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mime-version:content-disposition
	:user-agent; bh=KFAPbuU+C0XuDee7rP1DMLAQdSdwLhivYd5W1CR4kCQ=;
	b=W4cWlKYMHcEonBus/qdFoCOWqy5q/akrtvrYLynUyvAKJ6EcQaLzTCoBOl5FMWeD9o
	bAJ+a2uLzO/M7aRv8Ho3QijOcyqKhCixBU11tsvbQFB3MEnGeQPeNkJa6lJVOXbB/dPI
	i2hcAiTKtY1J2Oqi+1vNxeMXUS6+WMXxboaos/mR3gmY7SXb1jKYdSnevROm9GmpInKN
	i99zqUG5eE7hDkzNCiHFp1zIVXTTw5xJrYJLIhaLhYJqTPg2hzrV/1VaolzN76iPqWaG
	cy9LKIURLtDOrn3CaHX1EFbpyw5q7Gd9zBQu7/r2GjB2QBAelCQ8dkpLYRp9uRSLbNSP
	73mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-disposition:user-agent;
	bh=KFAPbuU+C0XuDee7rP1DMLAQdSdwLhivYd5W1CR4kCQ=;
	b=Jbgaspqj/F+AcacC7lR4/MFEiiCYimLWkUdWELQH5NXlGCqEB5AucSo67w1MOeBf3+
	HoYgwD5WzmxJj9cydzvXqrCF81AOpemZ0lOfaRQK1VyoOKAPnWlG/XIlhbaCvCI9Wkvf
	iIVdugbEUDXFaLr4VIejWHlXOm+jf9a3mp1TxxfyTDLGe30uh+fwqPfP4ONK3T7LcGSg
	Bdh4JEM48qcee59biDPJWCH479byOJj2pCEH3SD4N3XAwjcaWZvU43CIfjpzXBNENUXj
	AC3+NH0E98T6c63Y3JmCGLixzJNboUiCCL6p+6JHifC4tKRgXxychzjaaXLJYdg+S5Od
	meGQ==
X-Gm-Message-State: AN3rC/7SiIMxpfmGIcmBSAYKXUv5XP7mTe45K6stw9sNCm2yNB4IEk1t
	Cyn6rYBX4atq50E/viA=
X-Received: by 10.129.116.193 with SMTP id p184mr7582592ywc.84.1493461533210; 
	Sat, 29 Apr 2017 03:25:33 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id z7sm3820909ywz.46.2017.04.29.03.25.31
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 03:25:31 -0700 (PDT)
Date: Sat, 29 Apr 2017 06:25:29 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170429102527.u4plfi33hhcelbkc@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="frw5gzlfuq6wxzci"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::230
Subject: [Groff] Critique this bold-italic private macro for man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 10:25:40 -0000


--frw5gzlfuq6wxzci
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Any advice on how I can improve this?  (I'll take "no, don't even try to
do this" as read, from those who hate man(7). ;-) )

This is a private macro, not something I'm proposing as an extension to
any macro package.

.\" The bold italic font is not accessible via the man macro package.
.de BOLD-ITALIC
.  ie d an-trap \       \" Groff and Heirloom troff have this diversion.
.    ie F BI \{\        \" Is the font available?
.    itc 1 an-trap      \" Set input trap for the next logical line.
.    ft BI              \" Use the font.
.    if \\n[.$] \&\\$*  \" Emit any arguments.
.    \}
.    el \&\\$*          \" Otherwise, simply emit arguments.
.  el \&\\$*            \" Dupe because "&" cannot be used in if clauses.
..

Actual examples of usage:

--------------------------------------------------------------------------------
.RS
.EX
.B SYSTEM (DRIVE=\c
.BOLD-ITALIC d\c
.B ,DRIVER="XTRS8",ENABLE)
Enter unit number ([4]-7): \c
.BOLD-ITALIC u
.EE
.RE
--------------------------------------------------------------------------------
.TP
.B Using \c
.BOLD-ITALIC XTRSHARD/DCT
The
.I XTRSHARD/DCT
driver has been tested and works under both
.I LDOS
5.3.1 for Model I or III and
.IR TRSDOS / LS-DOS
6.3.1 for Model 4/4P.
--------------------------------------------------------------------------------
.\" XXX: .RS/.RE don't indent further within this .SS->.IP environment.  Bug?
.br
.in +1i/2u
.EX
.B SYSTEM (DRIVE=\c
.BOLD-ITALIC d\c
.B ,DRIVER="XTRSHARD",ENABLE)
Enter unit number ([0]-7): \c
.BOLD-ITALIC u
.B FORMAT \c
.BOLD-ITALIC d \c
.B (DIR=1)
.EE
.in -1i/2u
.br
Answer the questions asked by
.I FORMAT
as you prefer.

Regards,
Branden

--frw5gzlfuq6wxzci
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkEag8ACgkQ0Z6cfXEm
bc4Faw/7B9IkczBLvqrqoZiO2Hq1M5HUXUlmhhH2BBDOysI+Z75BLyqYmuqPod6U
ob6yzFoQ+h8fv2yGkjeJvbtOi86rj7JBM3id1gogM5Y8pV2dMpUxvzH8D2YgbnCH
a8dyJ9R/lIzjhwnn2VI+YKxF8V665VzXV1zI3CzbEiWKbwzI8F6AhkDXus6WRj9z
xm8oTWCXgkeFAhu2Jy9NNz9nbZw4dwzOpS9ieStCI0c9/bG6RJVvto6Sytc+5rbd
3Atm6yG+MehtD1gUgKd7o7wA2w6KkqztLq6+oAXligRxyjPm43mop9TKIXzYmJEO
H86MdaYPrtX/BZ8n46dM7agSrnfulQJ/WlyCov+uGV1TiDgWnpVcjnK7srYq+PA8
n4Kub3QPly+tKW3JANjyUF3+YEThcv0sQ6oBh/rmFO2QZNLiJuqG+Pm+aQLxamvG
a2L+vbl20QEYJ2x7jj1wOVkqiP8j2ecmIMSLPc6IfLYAHoMYlAi3alHF9BpdtMp1
J4TO9hp+LauQzxm+SMTDSxfb8Oqa7HbpPp0RWorszLWfrEDxXTRtEKNMbNphUjxl
7x43xH2lstpzbK1arcpELPPnUIYTrPQqxOW38x2Faanvdxq5OPuacKmzK9Q5CHCs
4BEMHqifUrxmapp7E/kMMVa1kt97tsPNE98TvI+qF/R2SoU0t3o=
=VAcx
-----END PGP SIGNATURE-----

--frw5gzlfuq6wxzci--


From MAILER-DAEMON Sat Apr 29 07:26:33 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4QWF-0001km-Bi
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 07:26:33 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56082)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4QWB-0001kX-Ec
	for groff@gnu.org; Sat, 29 Apr 2017 07:26:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4QW4-000856-4Q
	for groff@gnu.org; Sat, 29 Apr 2017 07:26:27 -0400
Received: from mail-yb0-x232.google.com ([2607:f8b0:4002:c09::232]:34213)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4QW3-00084S-UX
	for groff@gnu.org; Sat, 29 Apr 2017 07:26:20 -0400
Received: by mail-yb0-x232.google.com with SMTP id 8so20567553ybw.1
	for <groff@gnu.org>; Sat, 29 Apr 2017 04:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=eWg1QUPviHMNQdicKd5xEimOvW7wVZ0ZrINqAMRq+qI=;
	b=WICp5w1WHu4Irc06UUUHno85QVN/UqxByIhpi8ilLfFl9knFKHl+Q+llxNFTfevNrP
	if0cxt61vQSAwaElH3E+BluL8gBx3ZVIGREecvckEYE36JintiOx77UqtlqPiLTe2DvP
	otRH9yDcSrrWdyCCnHOzQC169nmYoWCKZcfnRGsEIDyGFuSz++2NvkuWag92KK2t+tm5
	grVb6p3soMvO3KfHw6VfB823LDKe9ukRoE7UrZCqawEc6QLMhAKEeSz394B8KpPTcwb6
	P0yma5E3Mc5fqdtUQ8HWoOFCwX6RQYHzAJFiqI/O9/hsyvQGqHosickjaUwvBaU2JRg8
	9+sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:cc:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=eWg1QUPviHMNQdicKd5xEimOvW7wVZ0ZrINqAMRq+qI=;
	b=gZsQRIhqRSKC0LmGG2gzQp1Y0NRBoKcFCOZtg9yr1QPe7hbMUwXUB44ubc+5yNTvpZ
	CSXrV6ng5vrK17rWW+e2nkksUZe8VvykVx/NbSm9KJigIRE0ARUxgo40eoYlZY+7Ty8c
	0TpdJQqwxvtIBqcCTkM7dJvieWEcK41EyiB2YXkjeVofNy3PTEDM2FxBprqXTdo9pZXX
	NMlqEYzJ+zlt42dofDfvdRosoCjxGD1wb3eiOAi1lJXv0l7Gtc4Md3paH/Z2vEmK0vPY
	+JtdqRJx0D+Y2WoQCkpVZqgZgdFUov8CS7SMnbvQFj2vvkogPvEihsjjVbD3j2dlYMz9
	ddQw==
X-Gm-Message-State: AN3rC/5t3Uqcwf1f+/QAkJhT2MHGfNwLNy9HUTGmBYGQMt8JBQ9zN3Iu
	pFXEMxmGA++L9H1b4oU=
X-Received: by 10.37.41.130 with SMTP id p124mr13375348ybp.24.1493465179002;
	Sat, 29 Apr 2017 04:26:19 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	x30sm3894675ywj.44.2017.04.29.04.26.17
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 04:26:17 -0700 (PDT)
Date: Sat, 29 Apr 2017 07:26:15 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: groff@gnu.org
Message-ID: <20170429112613.uprq652tftye4hvu@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
	<20170427153715.GE37287@athene.usta.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="uttim5yjq355dze3"
Content-Disposition: inline
In-Reply-To: <20170427153715.GE37287@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::232
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 11:26:29 -0000


--uttim5yjq355dze3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Thanks to a perfectly pleasant offline conversation with Ingo, I no
longer fear that he is hell-bent on man's destruction.  ;-)

But I figured I'd better address a few remaining points, and
particularly to offer some thanks where it's deserved.

At 2017-04-27T17:37:15+0200, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Thu, Apr 27, 2017 at 09:46:27AM -0400:
> > If this were a matter of preserving compatibility, you'd argue that
> > breaking 14 man pages out of 7000 is too many.
>=20
> Sorry, i don't follow.  Nobody suggested deleting \c from roff.

Good!  I didn't think anyone was, thought.

> All i said regarding portability is that implemeting your .TP .itc
> in groff, Heirloom, and mandoc and recommending use of \c after .TP
> means that *all* pages doing that misrender on all systems using
> either older versions of our formatters or legacy formatters.

The number of pages doing that is really small, hence this subthread.
It's important to me to know the impact of the changes I propose.

> If a significant language improvement would break 0.2% of existing
> manuals, i'd certainly consider going ahead with it and doing the
> handful of commits required / sending out the handful of patches
> required, but i don't see how that is related to the discussion.

Understood.  You and I disagree about whether letting people have
multiple input lines after what I crudely (mis)understand to be an
initial parse phase after invoking man(7) macros that use input traps.

> >> Remeber that writing legacy man(7) documents is quite hard and
> >> entices many people to try all kinds of (sometimes unavoidable,
> >> sometimes ill-advised) trickery.  Even when analyzing the use of
> >> easy-to-use languages in the wild, you usually find substantial (in
> >> that case, needless) trickery.  So it is actually surprising that
> >> you found so little.
>=20
> > Yet, somehow, you do not regard this as evidence of the quality of
> > man(7) nor of the people who write in it.
>=20
> No, it is not, because you can find lots and lots of poorly written
> man(7) documents in the wild, even hand-written ones.  All it tells
> us is that \c is exceedingly rare in manual pages - both (arguable)
> legitimate uses and abuses.  That doesn't imply there aren't other
> common problems; in fact, there are.

Oh, heck yes, I agree with that.  Many dragons to be slain there.

> >> So, if we would choose to promote \c use for the FONT_MACRO_C use
> >> case, we would actually promote using a low-level feature
>=20
> > It's no lower-level than the escapes to which you've given your
> > blessing; see groff(7) and CSTR #54, where it has parity.
>=20
> Admitted.  \f etc. is also low-level.  But it is simpler.

See below for why I hate \f so desperately, though I've mentioned one of
my reasons before.

> >> that is so far virtually unused in the wild,
> =20
> > Hmm.  210 uses out of ~7,000 makes it about twice as popular as mdoc.
> >=20
> > $ find man* -type f -and -not -type l | xargs zgrep '^\.Dd' | wc -l
> > 103
>=20
> Only if you don't count the about 3000 mdoc(7) manuals in a typical
> *BSD base system.  If you count those, \c is about 2% (abuse by
> docbook included), mdoc(7) is about 30%.

Fair point.  I was poking a stick at you with that one, and I have
nothing against the BSDs technologically.  In fact, I've long been
deeply envious of the quality of their man pages, and mdoc has a lot to
do with that.

> .TP
> \fB\-scale\fP \fIxfac\fP[,\fIyfac\fP]
>=20
> is not bad markup, but decent quality man(7) code that i would
> recommend.

Well, thanks.  This is what it looked like before I got to it:

=2ETP
=2EB \-scale \fIxfac[,yfac]\fP

However, _I_ don't like either of the above.  I mentioned before that
having this \fX stuff directly abutting words throws frustrates spell
checkers.  The other reason I hate font escapes in man pages is because
that way "there's more than one way to do it".  As I said elsewhere, I
think to get people writing man pages competently, we need to keep the
"language" small.  Most of them are infrequent users of the language,
and they don't know which parts are the macro package which are "raw"
*roff.  Many of them are sharp enough to make some shrewd guesses but
I'd rather take the guesswork out.

> > and practically no one will see \c as a new toy to play with.
>=20
> That might turn out to be true; it's also plausible conjecture,
> even though you already reported \c cargo culting right now.

True, but less than I feared.  Few enough that it's a tractable
operation to submit patches to fix that stuff.

> Here you probably have half a point.

<laugh>  Thanks.

> I should probably go ahead and change the mandoc documentation to
> recommend \(rs rather than \e for newly written manual pages.
>=20
> Scouring the existing manuals is maybe not worth the substatial
> amount of work required, because there is no problem in practice:
> if someone uses .ec *in a manual page* (seriously?) they are already
> responsible for writing \ for \ after that, and "xe" for "x" if
> they said, for example, ".ec x".

Yeah, that's why \(rs vs. \e is not a high-priority windmill for my
tilting lance right now.  Anyone who uses .ec without putting it back
deserves whatever maelstrom of trash they get.

> For example, even groff(7) still says:
>=20
>   Printable backslashes must be denoted as \e.  To be more
>   precise, \e represents the current escape character.
>   To get a backslash glyph, use \(rs or \[rs].
>=20
> That has already been improved substantially, but it could maybe
> still be worded better.

Agreed.  I'm having trouble even thinking of use case for \e, outside of
scenarios where the escape character might be under some sort of
external control (.rd), or diagnostic messages inside a macro where .ec
is being used.

> > In any event, I checked out Heirloom troff.  Unfortunately its CVS
> > repository has not seen a commit in almost 6 years.
>=20
> You must have looked in the wrong place.  Try
>=20
>   http://n-t-roff.github.io/heirloom/doctools.html
>   https://github.com/n-t-roff/heirloom-doctools/
>=20
> as linked from
>=20
>   http://mdocml.bsd.lv/links.html

Sadly, Gunnar Ritter's Heirloom Doctools site is still the top hit on
Google.  That's what led me astray.  Thanks for the clue.

> > Are we sure that Heirloom is still maintained?
>=20
> Absolutely.  Carsten Kunze maintains it.  He is also one of the
> most active groff committers and regularly follows this list.

Now's a good time for me to say thanks to Carsten for the batch of
recent commits.  Thanks, man!

> > Is there any other living troff on the planet?
>=20
> There is
>=20
>   https://swtch.com/plan9port/
[...]
>   http://www2.research.att.com/sw/download
[...]
>   https://github.com/n-t-roff/DWB3.3
[...]
>   http://repo.or.cz/w/neatroff.git =3D http://litcave.rudi.ir/
>   http://www.nesssoftware.com/home/mwc/source.php
[...]
> It looks like https://github.com/jgm/pandoc/ can only write,
> but not parse manual pages.

Thank you very much for all this!

> It is likely that there are more implementations than i know of,
> and some may well be alive.  Besides, i did not even try to list
> ad-hoc non-roff man(7) parsers.

This may warrant another thread, but how many of _those_ are still
alive?  I'm betting the language in groff_man(7) and man(7) [man-pages]
about portability and safe subsets hasn't been touched in years.  I also
suspect (without much evidence) that a lot of these non-roff man parsers
gave up the effort before achieving quality output with a significant,
representative sample of real-world man pages.

> > Out of those ~7000 pages, I haven't seen a single markup error that can
> > be unquestionably laid at the feet of Bjarni's and my proposal.
>=20
> Did you test your proposed new syntax (.TP using \c to include
> two macro lines in the head) on
>=20
>  - Oracle Solaris 9, 10, or 11
>  - illumos
>  - Plan9 (not sure whether that is still relevant)
>  - DWB (may well be irrelevant by now)
>  - Any other commercial system like HP-UX, AIX, etc.: i don't
>    have the slightest idea what those systems use today.

I sure did not.  I don't have access to any of those at present and I
have a half-strength RMS-style allergy to non-free software.

But I'm willing to use shell accounts to do regression tests.

> > At least we can agree that docbook-to-man produces a true dog's
> > breakfast of output.  Pretty lamentable.
>=20
> Indeed.

docbook-to-man seems to poison everyone who touches it.  It was cast
over the wall by Oasis/OPEN in 1996, picked up by David Bolen in 1999,
and the only people to hack on since then are the Debian folks, and even
there the package has been orphaned multiple times, the latest since
2014.

Regards,
Branden

--uttim5yjq355dze3
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkEeEwACgkQ0Z6cfXEm
bc46CQ/7BWL0A4QXp+LqKwXHvHATib0IReOUuXFzqIj3k8pZRO2sJyll8XoEHnQ3
Du2A6Ih4gHf/Shs8YwCvQGTrVBp/MvpgvA6acFbMSHjQ2bUBSycYaYD0dz3wjdGZ
Y1/ErzmMiSbjWN+RYt3Ms9+d+xt4P95IWlmgBsLypK1wQ3Mmpb4iiI1bYAoVPu3I
z7yBoSxciiqQMF6305tUwNQWiLXM6XCVQ94GTX95Vi2ZP6/ER+fzWUyipAvq9mMw
v5ynLosubX0MR3cTxsxGxe3quAhZZLNrPFjqIupuHdT6NUh8DxOReB2zUWJFb7xv
J2QCWoBx8oIsDyKT7PGWxZyNJcpl7bE+w5G1bRvBXgWnDR+jT4yVw50qryPvRyla
rd7ourxyMQf1HJi2u/gtiDBUKdboO+tdveASD/1e3mbHjK8PJEGYM/D7lXdVc60X
HN3at9EPuoaq7hAyAyzA5p4ZDfGmCom2zF9BxdZLWKN3pAGAXxPgiGQQUJthClSX
umE22laHkLM+v7c+i7VQCNBHDzyK2l5OKQDkvTZwG3bg5FDBQrd4HpcYrgF3uh+2
qXBW5Vx10ELnxnxfwZyUWUupZRXv1rRF0Siu/7X6UHBlOJc+cuT64GUhWnUzeeuk
RWcEl2gI6GK3OBWCa+OQTNcMWOlXwMUt9F93Rc4GEsuhNQ2e6YY=
=5dQS
-----END PGP SIGNATURE-----

--uttim5yjq355dze3--


From MAILER-DAEMON Sat Apr 29 08:33:07 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4RYh-0003dD-L5
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 08:33:07 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36512)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4RYf-0003cC-PD
	for groff@gnu.org; Sat, 29 Apr 2017 08:33:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4RYc-00006I-LP
	for groff@gnu.org; Sat, 29 Apr 2017 08:33:05 -0400
Received: from mail-yb0-x234.google.com ([2607:f8b0:4002:c09::234]:34148)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4RYc-00006E-Gi
	for groff@gnu.org; Sat, 29 Apr 2017 08:33:02 -0400
Received: by mail-yb0-x234.google.com with SMTP id 8so20741993ybw.1
	for <groff@gnu.org>; Sat, 29 Apr 2017 05:33:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mime-version:content-disposition
	:user-agent; bh=MnH0OeJjZeZI1OqewMktSO44Pa2ZcwXYKAow6b4pJLo=;
	b=S0tf0iffJAwWBdLCGOuTqF+5R91AX5gGcW7QoJ8BrJl8d9rGEV5dk7nRbKbAXEbGP5
	la4TbYBqExD4QirEDvlNklAxfEOTpw1sLrYZkmD3Mtc6wMQgX0VMQiFUSwOm/y8yPsdr
	6wNxarw3vvmLbXCmgQzuKF/O0ocPRKT9e7+XiH97MTnBBI93LJobBGXhmvXRYFMZgkjj
	70jSYFBunCIxe6ATu42ncaLdlTKnV4dsCGpVGalBMNp95yhK3OI8TN55+eAPoDwUFMk7
	tGfUz8KBVAibjqHi/21rdsCnNZUBSoeoso9zOEivq73n04n6B3aWnB6Hrqb7R7M/DpLM
	GiRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-disposition:user-agent;
	bh=MnH0OeJjZeZI1OqewMktSO44Pa2ZcwXYKAow6b4pJLo=;
	b=MxeoTatGxo96NTjLRteb5QIPDc44hyF7500m9T7+Yqqmu9gyBhV6i5KM1NFjTUpafz
	AvM3RU4QNgBNm6J0pLITUoYh9uZnX4BUBP+6x9TH/68N4rTXGuotmUH6Sgn8dPJMHfqD
	41/qw7jdYnCEf95rw0AeE8arEnfH8It9kfHLMRzy13QIUMtDhHQUQEf9VWP+1b9WbiAt
	GJrLUXJYRQOA3kR2UJ6EI28IfBa/+2pcBZgKM0iUV6hv7zVrRb4fFsYOkCddO4RkEQmi
	ZwU1QIoAJq3ry/h4vl1jdzJvAahoWSUuCaaqR/KEux2Rorf++DbpnRByhxcwoEWiucrM
	KPdA==
X-Gm-Message-State: AN3rC/48CnEtiS271mKY9W6cVU9LKgGrNGGmpeYjURztJtv5E8xtSlAU
	Ilq3ukb1DyMdiQd7iY8=
X-Received: by 10.37.215.1 with SMTP id o1mr13147941ybg.79.1493469181654;
	Sat, 29 Apr 2017 05:33:01 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	u207sm3763906ywc.60.2017.04.29.05.32.59 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 05:33:00 -0700 (PDT)
Date: Sat, 29 Apr 2017 08:32:57 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="2rns464ncpwxqakt"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::234
Subject: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 12:33:06 -0000


--2rns464ncpwxqakt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I'm noticing that in some of groff's own man pages, the plain-old
long-suffering apostrophe is explcitly avoided in favor of \(aq.

And I don't mean in any fancy technical jargon, I mean in plain language
like:

Don\(aqt listen to Trump\(aqs advisors.

That sure is ugly, and unkind to spell-checkers.  Is this a recommended
style?  If the page author absolutely hates directional single quotes
used as apostrophes, wouldn't it be better to do something like

.tr '\[aq]

near the top of the document?

Regards,
Branden

--2rns464ncpwxqakt
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkEh+8ACgkQ0Z6cfXEm
bc7krg/+J2riePrqQXDUR2f8lYsWmaGaLquGWE7+YJZOl1xMw2m2Bcqp+JFYOGpD
o1JEbk2v9rmRe83KD2r7Ekz5PP3ZTLQOq4mxDpCvPSoUPf0C2KrhT1965fXVN/dc
bOL3dblXNGdc+V6gynlprtM1uTYx+BFoDaZVVS2rmhyI4R4sYN/EznIPu5fRQx1o
c5rBhHiyS/4E8gGCfSjNeO5ac7Wj0amdKXXF70Nl87ZH79EZxwsjFuaP5W3EoNFm
FC0m5dPj/xjN1pSxxFAKbodpZQ1JWNhyPxte9p0LXRHcyPjFMP4nhXgV6NxxZiW5
gXx2MZzq/HfmJl2a1X7UwtL2kXlZlZgHOM8UNdvMXOR6c/XI1O5sqOFv+eAohlPH
fVqXELwrbbIIOt2uy1p03pClI/GzO6l0GQuyRjZQChv8VkLLpr3lHYUJxAe1Z6MO
uH8YGI6b310MbxiHfuPwDhLsSEnuVzABFDYuIf805eMUv495sIYGgMG5Ec1aLobs
FHS/nr+kEKnoe+TcZYUCKMpj5qMJ2Hf3wUCaAwNGOVjnUJDlAG2d5VoE63pOuCFF
xQBNn1O9I6DAeGueTQDFhInzKbWKPcEK8ISnb3V3AYGkwUQQ8LIYtaSzDNqshj1t
H7AMsFYB3UF0Mmip+I/1z5m5clsLt+nAonNlUlLb8LyMHD/HNt4=
=0Ohx
-----END PGP SIGNATURE-----

--2rns464ncpwxqakt--


From MAILER-DAEMON Sat Apr 29 09:40:14 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4Sbe-00009q-Pt
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 09:40:14 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44698)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4Sbc-00009d-H9
	for groff@gnu.org; Sat, 29 Apr 2017 09:40:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4Sbb-0003rE-MH
	for groff@gnu.org; Sat, 29 Apr 2017 09:40:12 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:55124)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d4Sbb-0003p3-GB
	for groff@gnu.org; Sat, 29 Apr 2017 09:40:11 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d4SbW-0000QA-Ou; Sat, 29 Apr 2017 15:40:07 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d4SbW-0006bl-HC; Sat, 29 Apr 2017 15:40:06 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d4SbW-0006I7-BI; Sat, 29 Apr 2017 15:40:06 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id a358ed47;
	Sat, 29 Apr 2017 15:40:06 +0200 (CEST)
Date: Sat, 29 Apr 2017 15:40:06 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170429134006.GB95205@athene.usta.de>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 13:40:13 -0000

Hi,

G. Branden Robinson wrote on Sat, Apr 29, 2017 at 08:32:57AM -0400:

> I'm noticing that in some of groff's own man pages, the plain-old
> long-suffering apostrophe is explcitly avoided in favor of \(aq.
> 
> And I don't mean in any fancy technical jargon, I mean in plain
> language like:
> 
> Don\(aqt listen to Trump\(aqs advisors.
> 
> That sure is ugly, and unkind to spell-checkers.  Is this a recommended
> style?

 $ man groff_char
[...]
REFERENCE
[...]
   7-bit Character Codes 32-126
[...]
   '  the ISO latin1 `Apostrophe' (code 39) prints as ', a right
      single quotation mark; the original character can be obtained
      with `\(aq'.

 $ man mandoc_char
[...]
DESCRIPTION
[...]
   Accents
     In output modes supporting such special output characters, for
     example -T pdf, some roff(7) formatters convert the following
     ASCII input characters to the following Unicode special output
     characters:

        `      U+2018   left single quotation mark
        '      U+2019   right single quotation mark
        ~      U+02DC   small tilde

     In prose, this automatic substitution is often desirable; but
     when these characters have to be displayed as plain ASCII
     characters, for example in source code samples, they require
     escaping to render as follows:

        \(ga   U+0060   grave accent
        \(aq   U+0027   apostrophe
        \(ti   U+007E   tilde

So yes, documentation kind of recommends "Don\(aqt listen".

Arguably, apostrophes are at least as common in english prose
as single quotes, so the decision to make single quotes easier
to type at the expense of making apostophes harder to type
could have been questioned.  But that decision was made a very
long time ago, and changing it now might break large numbers of
non-manual documents.

Right now, mandoc does not do these substitutions, not even in
-Tutf8 output mode, which could maybe be considered a bug.
Or maybe not, since most manual page authors probably
write "don't", and those who really care will probably use
the more explicit \(oq\(cq for single quotes rather than `'.

> If the page author absolutely hates directional single quotes
> used as apostrophes, wouldn't it be better to do something like
> 
> .tr '\[aq]
> 
> near the top of the document?

That would break the rendering of quotes similar to the following:

Golding wrote: \[lq]`They\[aq]re all dead,' said Piggy, `an\[aq]
this is an island.  Nobody don\[aq]t know we\[aq]re here.'\[rq]

Yours,
  Ingo


From MAILER-DAEMON Sat Apr 29 10:48:00 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4TfE-0007eE-O4
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 10:48:00 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51544)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4TfD-0007e3-Dr
	for groff@gnu.org; Sat, 29 Apr 2017 10:48:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4TfA-0001zh-7t
	for groff@gnu.org; Sat, 29 Apr 2017 10:47:59 -0400
Received: from relay01.pair.com ([209.68.5.15]:49532)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4TfA-0001zZ-2p
	for groff@gnu.org; Sat, 29 Apr 2017 10:47:56 -0400
Received: from orac.inputplus.co.uk (unknown [84.93.39.237])
	by relay01.pair.com (Postfix) with ESMTP id E9BB3D00A62
	for <groff@gnu.org>; Sat, 29 Apr 2017 10:47:54 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 701BE2112B
	for <groff@gnu.org>; Sat, 29 Apr 2017 15:47:53 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170427181209.GI37287@athene.usta.de>
References: <20170424150155.f5rga35izh775vxs@crack.deadbeast.net>
	<20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
Date: Sat, 29 Apr 2017 15:47:53 +0100
Message-Id: <20170429144753.701BE2112B@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 14:48:00 -0000

Hi Ingo,

> things are actually much simpler even for describing such unusually
> complicated syntax:
>
> .Oo : Ns Fl c Ar cc-addr : Oc
> .Eo [: Fl c Ar cc-addr Ec :]
>
> .Fl S Ar var Ns Op =3D Ns Ar value
> .Fl S Ar var Ns Op Pf =3D Ar value

This has reminded me of one reason I didn't get on with mdoc.
Only the `Fl' is obviously mdoc's, due to the `.' invocation.  The rest
are a mix of command and data, but without any sigil one's left guessing
unless the command set has been memoised.  It's not helped by the data
typically being small abbreviations for variables and sample parameters
rather than the prose words you might find for running English text,
thus they look like commands.

If, in some made up syntax, it was

    .Fl S .Ar var .Ns .Op .Pf =3D .Ar value

that might be more grokable, though still long-winded for
`-S var[=3Dvalue]'.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sat Apr 29 10:55:19 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4TmJ-0008KQ-MQ
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 10:55:19 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52223)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4TmH-0008K1-0l
	for groff@gnu.org; Sat, 29 Apr 2017 10:55:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4TmD-0003vw-W7
	for groff@gnu.org; Sat, 29 Apr 2017 10:55:17 -0400
Received: from relay01.pair.com ([209.68.5.15]:49597)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4TmD-0003vj-Rk
	for groff@gnu.org; Sat, 29 Apr 2017 10:55:13 -0400
Received: from orac.inputplus.co.uk (unknown [84.93.39.237])
	by relay01.pair.com (Postfix) with ESMTP id 0AB87D00BBB
	for <groff@gnu.org>; Sat, 29 Apr 2017 10:55:13 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 8944C2112B
	for <groff@gnu.org>; Sat, 29 Apr 2017 15:55:11 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
	<20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
Date: Sat, 29 Apr 2017 15:55:11 +0100
Message-Id: <20170429145511.8944C2112B@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 14:55:18 -0000

Hi Branden,

> > The troff system was designed to be typed at a keyboard.  The
> > dot-on-the-left rule might be ugly, and the requests/macros terse,
> > but the benefit to the user is relatively few keystrokes above those
> > needed for the text.
...
> Nothing has come close to saving me more keystrokes than <TAB> at the
> shell prompt and CTRL-N in Vim.

Completion is useful, but `.bp' and `.B<tab>' don't have equivalent cost
even if the latter completes to `.BreakPage'.  `.bp' can be just be
typed whereas completion is an interaction that interrupts the writer.
Has tab proffered the correct expansion?  No, should I tab again, feed
it another character, or move the cursor down two in the list of
alternatives?  Once the interaction is finished, the writer tries to
resume his train of thought.

There's also a cost to the reader as `.bp' is less noisy than
`.BreakPage'.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sat Apr 29 11:24:20 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4UEO-0002w5-18
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 11:24:20 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55062)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4UEL-0002vz-6n
	for groff@gnu.org; Sat, 29 Apr 2017 11:24:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4UEI-0002E1-1c
	for groff@gnu.org; Sat, 29 Apr 2017 11:24:17 -0400
Received: from mail-yb0-x22b.google.com ([2607:f8b0:4002:c09::22b]:33710)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4UEH-0002Dk-Sw
	for groff@gnu.org; Sat, 29 Apr 2017 11:24:13 -0400
Received: by mail-yb0-x22b.google.com with SMTP id 11so21241366yby.0
	for <groff@gnu.org>; Sat, 29 Apr 2017 08:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=iGs7FZtCw6dTMNCC9jyyxLMIGqO4odzRd7vRfANelMg=;
	b=tWJ48h9p43aX13xenMhC6hUofgz3n/BViny+RJCeNpq8Jc4I8tur3XAYYnW197TEA/
	6fslOG0RpLNkUWi+cQFTtXqY8g3XHTg5cg9pruNYBgv0w/8HFqeqjhOoWk6GfLCQWIWN
	ovSJiziuJwGtsQhov2ZB41Vn0IsyaqSlpoFzljwZnkLx3BmEEzoNaiZ0dR1N957ppi7X
	WP1p4El2zCSEyvedlx1gvGvoGMZgrO54WlqiixfUtxAnj7fFu1LqEB7bqM7y8DKm9KEI
	jvBaLgqx2CfjXihQpVoVMCPakQGaXINRTFb4bX3UFPRoKK1NcVPYt/uO5KVOPWE2qMGK
	a/TQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=iGs7FZtCw6dTMNCC9jyyxLMIGqO4odzRd7vRfANelMg=;
	b=bydwA8elLJAUtjXYLA6tX7lY4r5d1w69m2+jAQVW/uTJQ2FlrZypi/qhBWkLAiiVGs
	EvTzFDj9wREPSDlwTFMWTFuJdpK8idXjiNLg1k4p5UI4S/KPKlQJN3dMqmgmHDJvUUie
	uy1SOB6Z3/4Ok2Z0RuspVOrKisjQxaNKXZzAQSfjPk1XMxUgCox+ApR1R2NVYmXQxXEg
	bvcIDQ6o9ix37qysxPSCMArd6dEAlnvqQOQzey7GcT3f+V6fCjpEFOIe9mtluufoMxGU
	oGcPBCmvnBWYBFk0IwdsIYuVZoIToFJFBr9ZgJfE0uV0srUOzleIKB+RmbvS9IgFHCLa
	pUUw==
X-Gm-Message-State: AN3rC/40o+CZ8rtY5VM74pOQYwYXx+z/Pfp9cvdD20AfcYLVJNNwtCf8
	yoQXim+GU6Z5mEgjsgw=
X-Received: by 10.37.202.2 with SMTP id a2mr13868909ybg.129.1493479452700;
	Sat, 29 Apr 2017 08:24:12 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	l205sm2985935ywb.38.2017.04.29.08.24.10 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 08:24:11 -0700 (PDT)
Date: Sat, 29 Apr 2017 11:24:09 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170429152406.riqw4idlfedzxdwl@crack.deadbeast.net>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
	<20170429134006.GB95205@athene.usta.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="neaue3emquqoig5z"
Content-Disposition: inline
In-Reply-To: <20170429134006.GB95205@athene.usta.de>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c09::22b
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 15:24:18 -0000


--neaue3emquqoig5z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:
>  $ man groff_char
> [...]
> REFERENCE
> [...]
>    7-bit Character Codes 32-126
> [...]
>    '  the ISO latin1 `Apostrophe' (code 39) prints as ', a right
>       single quotation mark; the original character can be obtained
>       with `\(aq'.

That reference, I'm familiar with.

>  $ man mandoc_char
[..]

That one, I'd never read before.  :P

> So yes, documentation kind of recommends "Don\(aqt listen".

I don't interpret it that way.  In English typography, apostrophes
traditionally are rendered with a leftward slant.

See, e.g., < https://en.wikipedia.org/wiki/Apostrophe#Typographic_form >.

> Arguably, apostrophes are at least as common in english prose
> as single quotes, so the decision to make single quotes easier
> to type at the expense of making apostophes harder to type
> could have been questioned.  But that decision was made a very
> long time ago, and changing it now might break large numbers of
> non-manual documents.

I'm not interested in changing it.  Not every question I ask is a
prelude to some revolutionary scheme.  :D

> Right now, mandoc does not do these substitutions, not even in
> -Tutf8 output mode, which could maybe be considered a bug.
> Or maybe not, since most manual page authors probably
> write "don't", and those who really care will probably use
> the more explicit \(oq\(cq for single quotes rather than `'.

I agree, and furthermore I advise grievous torture for anyone using a
grave accent and a "neutral" apostrophe as if they were paired,
symmetrical quotation marks.

Sad to say, GNU diagnostic messages have been triggering me for 20+
years by their monomaniacal obsession with this eye-gouging
typographical practice.

> > If the page author absolutely hates directional single quotes
> > used as apostrophes, wouldn't it be better to do something like
> >=20
> > .tr '\[aq]
> >=20
> > near the top of the document?
>=20
> That would break the rendering of quotes similar to the following:
>=20
> Golding wrote: \[lq]`They\[aq]re all dead,' said Piggy, `an\[aq]
> this is an island.  Nobody don\[aq]t know we\[aq]re here.'\[rq]

Looks like a feature to me.  The internal quotation marks should be
rendered with \[oq] and \[cq] instead.

Thanks for sating my curiosity!

Regards,
Branden

--neaue3emquqoig5z
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkEsA0ACgkQ0Z6cfXEm
bc72eRAAjCf1lFG5lDTyHcJJKtekN58QtEZQvkFzQjWGg48G8Mu1xJp/DVP3EN4r
/Q5o1LgLOLCEwQoHH4/0qbHgkpW5eu4EAwRjg3uRtTxjITntGi/EGODpAUO5Wdxa
qim5Yqyd/0qSlUmI/BUCRWlfft8uLOvqaG4Fzjz83idwMjhfuJhsy88Q1g28ELTf
xSJPTz0b4OQPOxaoM1KlCBE+xcHE1EX2A05g/mNp/eyJk+w8v3cnHEEyldKHs+Ls
Y1ZIL3VbmYkTKH6yfv6oYoyEkTVvIu4W6RP3+aqaJUCb2l/Q88eBph1bGetIOWKT
rAJ8kkqfAYJjcLI7xdzv4DTP55eIMY/5MG5aU3xWcsn5LQVYLtB4C99x9NmVTp5e
OYYWW863DdYnsHqOcZVefYkWGDONT9pxAcN6twRc09EpTvZspLH4JosEn31m/MNj
tEBliixkVF/1d+m2rqId4c2/JC7+JICkNKJeVNTcqPAzIsFT2+y8WC6l9+KGigct
8mq+j93+lB5pg0YjzZSneVZOYXO0Br9iKLLkfNR+6kemOUSlKfm7KjdOfriTgPMJ
aRzHKKbHzUxaH1H5v45jugsSvs7X3eeQz4zBVRnVh6yo9ziMXGJGeRk7/dV9iiS3
IoRvKerqWSW4WsVQU1BGfukLX6EtPMQ1OQkC7etMcr6z8lqGXXs=
=1m68
-----END PGP SIGNATURE-----

--neaue3emquqoig5z--


From MAILER-DAEMON Sat Apr 29 11:49:26 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4Ucg-0004l0-La
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 11:49:26 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57697)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d4Ucd-0004jR-U5
	for groff@gnu.org; Sat, 29 Apr 2017 11:49:24 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d4UcZ-000082-2v
	for groff@gnu.org; Sat, 29 Apr 2017 11:49:23 -0400
Received: from mail-io0-x234.google.com ([2607:f8b0:4001:c06::234]:36631)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <anthony@cathet.us>) id 1d4UcY-00007q-Rq
	for groff@gnu.org; Sat, 29 Apr 2017 11:49:19 -0400
Received: by mail-io0-x234.google.com with SMTP id p80so86122118iop.3
	for <groff@gnu.org>; Sat, 29 Apr 2017 08:49:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=cathet-us.20150623.gappssmtp.com; s=20150623;
	h=sender:from:to:cc:subject:in-reply-to:references:comments
	:mime-version:content-id:date:message-id;
	bh=PREgQenTayRqwEnghfdroFbYPxzLl9rG0GNKl8FyZhg=;
	b=wmZ7x3FxDO+Ic4oLsL20e7TZOmBiSAwgqwTrnMZ0+7wBisV+PZXncYapuOGzLv2QIt
	6R0BeM1fPPBTzLuuhLdlE0BWZiVKkfChDWxfjy/5LNiH5Oq9AjHzk/z2N2v+fKbRTed1
	SvWkuA1DfRkqv8lnUX78bZsMuQA7KwG97ziulJlbr9W3AnCh/cjpKlheRCPX9k29NFCJ
	W7p2gFDiB+zQLoSnzRhl+tX99cjSNXtwxZUqAElRfFCyMtgFroheljAq+HV4MgE78SXi
	MwthxbtL+/qdN+FWAxPpb22BHQ/l5QetBLei4RPYw9fmQ3C6I+alFVHXJ+OW1T9NL8st
	Ishg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references
	:comments:mime-version:content-id:date:message-id;
	bh=PREgQenTayRqwEnghfdroFbYPxzLl9rG0GNKl8FyZhg=;
	b=Uhw33kM/3LzaCShbMkfijOgo9pH6xEJl4ZlGK/KkPMY6wwoHyOZZ+LjgN3+/1CttDE
	vhu00M2O0wk0c7zrFKj64NF2JCLxIls8Md/1Ji191z6KK71x/pykShq2Y4rEFzKvBPCz
	hXv6JRWLjnj9d4RIyZU08AVs8mI8Z377My4TOYfAfN2GWnedbJQOfKgSmJ9szRm06LD+
	xZHbHXB4rAyDQvSn9xDkXkPZa7LCN4pxC5OcNzUvYxHgx3VsJNxd1Bra0ZYVViNpceH0
	xxnl7riCM0EtcqcaL7R+yjzMpXB3hHTpgn8oTJMmTIDJFR6jIM5+gIZwwWbRPVwgOf/y
	jnQQ==
X-Gm-Message-State: AN3rC/6Ya/4UTJSB+e1lXZD5np4Dot6B6MNtPNoK/sh1a7XcUDk9rzQc
	shX9kpF/hfQDwoT/
X-Received: by 10.107.7.219 with SMTP id g88mr15120182ioi.34.1493480957332;
	Sat, 29 Apr 2017 08:49:17 -0700 (PDT)
Received: from cathet.us. (97-123-144-191.albq.qwest.net. [97.123.144.191])
	by smtp.gmail.com with ESMTPSA id z26sm1282057ita.8.2017.04.29.08.49.16
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 08:49:16 -0700 (PDT)
Sender: "Anthony J. Bentley" <anthony@cathet.us>
Received: from cathet.us (localhost [127.0.0.1])
	by cathet.us. (OpenSMTPD) with ESMTP id 8086b2bb;
	Sat, 29 Apr 2017 09:49:15 -0600 (MDT)
From: "Anthony J. Bentley" <anthony@anjbe.name>
To: Ingo Schwarze <schwarze@usta.de>
cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>, groff@gnu.org
In-reply-to: <20170429134006.GB95205@athene.usta.de>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
	<20170429134006.GB95205@athene.usta.de>
Comments: In-reply-to Ingo Schwarze <schwarze@usta.de>
	message dated "Sat, 29 Apr 2017 15:40:06 +0200."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5238.1493480955.1@cathet.us>
Date: Sat, 29 Apr 2017 09:49:15 -0600
Message-ID: <86265.1493480955@cathet.us>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4001:c06::234
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 15:49:25 -0000

Hi Ingo,

Ingo Schwarze writes:
>    Accents
>      In output modes supporting such special output characters, for
>      example -T pdf, some roff(7) formatters convert the following
>      ASCII input characters to the following Unicode special output
>      characters:
> 
>         `      U+2018   left single quotation mark
>         '      U+2019   right single quotation mark
>         ~      U+02DC   small tilde
> 
>      In prose, this automatic substitution is often desirable; but
>      when these characters have to be displayed as plain ASCII
>      characters, for example in source code samples, they require
>      escaping to render as follows:
> 
>         \(ga   U+0060   grave accent
>         \(aq   U+0027   apostrophe
>         \(ti   U+007E   tilde
> 
> So yes, documentation kind of recommends "Don\(aqt listen".

Prose does not fall under this category. "Source code samples" is a
pretty limited category in my book.

> Arguably, apostrophes are at least as common in english prose
> as single quotes, so the decision to make single quotes easier
> to type at the expense of making apostophes harder to type
> could have been questioned.

Unicode made the decision a long time ago to consider U+2019 as both
right single quotation mark and apostrophe; see the Apostrophes section
of Unicode 9.0, chapter 6. This matches up with the usage I've seen
ever since becoming interested in typography.

    When text is set, U+2019 RIGHT SINGLE QUOTATION MARK is preferred as
    apostrophe, but only U+0027 is present on most keyboards. Software
    commonly offers a facility for automatically converting the U+0027
    APOSTROPHE to a contextually selected curly quotation glyph. ...

    U+2019 RIGHT SINGLE QUOTATION MARK is preferred where the character
    is to represent a punctuation mark, as for contractions: "We've been
    here before." In this latter case, U+2019 is also referred to as a
    punctation apostrophe.

TeX, for example, does the same thing. There, the conversion to U+2019
is done for text, but in math ' is converted to U+2032 PRIME. (Well,
TeX predates Unicode, but you know what I mean.)

Thus, I typically escape ' in source code listings and other situations
where I need the literal ASCII character '. But when I need an actual
apostrophe, I use ' as-is to take advantage of troff's automatic
conversion. Similarly, I only use " when specifically an ASCII double
quote is needed, such as when referring to C strings, and use
typographic quotes at all other times.

-- 
Anthony J. Bentley


From MAILER-DAEMON Sat Apr 29 12:44:12 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4VTg-0006FP-On
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 12:44:12 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38724)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4VTd-0006FJ-Up
	for groff@gnu.org; Sat, 29 Apr 2017 12:44:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4VTc-0000FB-NT
	for groff@gnu.org; Sat, 29 Apr 2017 12:44:10 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:54424)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d4VTc-0000F1-Dw
	for groff@gnu.org; Sat, 29 Apr 2017 12:44:08 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d4VTZ-0002zs-Ep; Sat, 29 Apr 2017 18:44:06 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d4VTY-0007Q4-Lo; Sat, 29 Apr 2017 18:44:04 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d4VTY-00019B-GP; Sat, 29 Apr 2017 18:44:04 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id 2c94a618;
	Sat, 29 Apr 2017 18:44:04 +0200 (CEST)
Date: Sat, 29 Apr 2017 18:44:04 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff@gnu.org
Message-ID: <20170429164404.GE95205@athene.usta.de>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170429144753.701BE2112B@orac.inputplus.co.uk>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 16:44:11 -0000

Hi Ralph,

Ralph Corderoy wrote on Sat, Apr 29, 2017 at 03:47:53PM +0100:
> Ingo Schwarze wrote:

>> .Fl S Ar var Ns Op Pf = Ar value

> This has reminded me of one reason I didn't get on with mdoc.
> Only the `Fl' is obviously mdoc's, due to the `.' invocation.
> The rest are a mix of command and data, but without any sigil
> one's left guessing unless the command set has been memoised.
> It's not helped by the data typically being small abbreviations
> for variables and sample parameters rather than the prose words
> you might find for running English text, thus they look like
> commands.

As a matter of fact, it *is* helped by *exactly* that.

For novice manual page authors, one of the simple rules i routinely
recomend is this:  "On a macro line, if a word consists of two
letters, the first one capital and the second one not, assume it's
a macro.  If you don't intend it as a macro, escape it with \&."

It turns out almost nothing gets uselessly escaped when following
that rule because capitalized two-letter words are quite rare on
macro lines in practice.

Even in plain english text, capitalized two-letter words are somewhat
rare.  The most common case is short words like "No" and "It", but
only when they occur at the beginning of a sentence.  But plain
English text is rarely seen on macro lines, and in particular the
beginning of a plain English sentence almost never is.

> If, in some made up syntax, it was
> 
>     .Fl S .Ar var .Ns .Op .Pf = .Ar value
> 
> that might be more grokable,

Remebering the above very simple rule about Xx-style words, it is
about the same; maybe the shorter version is even easier to read.

> though still long-winded for `-S var[=value]'.

It is not long-winded at all.  Even in man(7), which has no sematic
annotation, it is

.B -S
.IR var [= value ]

That's 33 bytes (long-winded!?) in mdoc(7) vs. 25 bytes in man(7),
so it's 8 (eight) additional bytes for expressing four semantic
annotations, among them three different semantic annotations:
that "-S" is a flag, that "[]" means "optional", and that "var"
and "value" are placeholders.

Given that in a different program, "var[= value]" or "var[ =value]"
or "var[ = value]" might be the required syntax, and given that
in most syntax, separating tokens by whitespace is the usual case
and joining tokens without whitespace in between is more unusual,
even the design of the no-whitespace macros .Ns and .Pf is fully
optimized for conciseness and simplicity.

This example provided by Steffen in mockery is actually an
excellent example to demonstrate that mdoc(7) syntax meets the
theoretic maximum of conciseness and clarity.  You want to specify:

 * 1+3+5 = 9 letters (S, var, value)	-> min. 9 bytes, 3 tokens
 * 1 punctuation mark (=)		-> min. 1 byte, 1 token
 * 4 semantic annotations (Fl, 2Ar, Op)	-> min. 8 bytes, 4 tokens
 * 2 spacing exceptions			-> min. 4 bytes, 2 tokens
 * token separators for 10 tokens	-> min. 10 bytes of whitespace

That assumes nothing except that expressing a semantic annotation
requires more than one byte (which anybody knowing XML is likely
to readily admit) and that we want to separate tokens with whitespace
(which both human readers and parser programs will probably like).
Note that i did not even count those output characters against the
theoretical minimum that are implicit in the semantic annotations
(the "-" in the .Fl and the "[]" in the .Op).

So the theoretical optimum is 32 bytes.  The mdoc(7) code is 33
bytes.  You call that "long-winded"?  Oh, that additional byte is
the leading roff(7) macro dot, which is actually yet another semantic
annotation ("not plain text") this time really expressed in a single
byte...

The opposite criticism to "long-winded" was "cryptic,
we should use .als".  I don't buy that either.  Here is the
complete list of macros recommended for use in modern mdoc(7):

  .Dd     Document Date   \" preamble macros
  .Dt     Document Title
  .Os     Operating System
  .Nm     NaMe
  .Nd     Name section Description

  .Sh     Section Header   \" structural macros
  .Ss     SubSection header
  .Sx     Section Xref
  .Xr     XRef
  .Pp     Paragraph
  .Bl/El  Block/End List
  .Bd/Ed  Block/End Display
  .D1     Display 1-line
  .Dl     Display Literal
  .Ql     Quote Literal
  .It     ITem in list
  .Ta     TAble cell separator
  .Rs/Re  Reference Start/End

  .Pf     PreFix   \" Spacing control macros
  .Ns     NoSpace

  .Fl     FLag   \" Command-line semantic macros
  .Cm     Command modifier
  .Ar     ARgument
  .Op     OPtional (to end of input line)
  .Oo/Oc  OPtional Open/Close
  .Ic     Internal/Interactive Command
  .Ev     Environment Variable
  .Pa     PAth

  .In     INclude file   \" Function library semantic macros
  .Fd     Function #Define
  .Ft     Function return Type
  .Fn     Function Name
  .Fo/Fc  Function Open/Close
  .Fa     Function Argument
  .Vt     Variable Type
  .Va     VAriable name
  .Dv     #Defined Variable
  .Er     ERrno constant

  .An     Author Name   \" misc semantic macros
  .Lk     hyperLinK
  .Mt     MailTo
  .Cd     kernel Configuration Declaration
  .Em     stress EMphasis
  .Sy     SYmbolic (misnomer, what is ~ HTML5 <strong>)
  .Li     LIteral

  .Dq/Do/Dc  Double Quote/Open/Close    \" Physical enclosures
  .Qq/Qo/Qc  ASCII-" Quote/Open/Close
  .Sq/So/Sc  Single Quote/Open/Close
  .Pq/Po/Pc  Parenthesis Quote/Open/Close
  .Bq/Bo/Bc  square Bracket Quote/Open/Close
  .Eo/Ec     generic Enclosure Open/Close

  .Ex -std   standard command EXit values
  .Rv -std   standard function Return Values
  .St        STandard reference

That's just one page of cheat sheet, available in almost exactly
this form in the mdoc(7) manual, and *all* macro names are strongly
mnemonic, with many additional regularities like the Xq/Xo/Xc
pattern.  Even for an mdoc(7) beginner, it is not really difficult
to pick good macros looking at such a list, at least for people who
have ever coded in any programming or markup language, for example
in C or HTML.  Besides, most beginners start by copying and editing
existing manuals, which simplifies getting to speed further.

Note that longer macro names would make matters much worse, not only
for writing, but also for reading:

  .Fl S Ar var Ns Op Pf = Ar value

  .CommandOption S .CommandArgument var .NoSpace\
    .OptionalToEol = .NoSpace .CommandArgument value

Which of these is more readable?  Also compare to the output
of mandoc -Thtml (title attribute deleted for brevity):

  <b class="Fl">-S</b> <var class="Ar">var</var>[<span class="Op">=<var
  class="Ar">value</var></span>]

Or even:

  <b class="CommandOption">-S</b>
  <var class="CommandArgument">var</var>[<span class="Optional">=<var
  class="CommandArgument">value</var></span>]

The basic concept of mdoc(7) is extremely close to the theoretical
optimum.  I don't deny there are a few minor quirks in the design
and naming of a few of the individual macros that could have been
designed better, but regarding all the common criticism, if you
actually try to design improvements based on it, you find that it
would only make matters worse.

Yours,
  Ingo


From MAILER-DAEMON Sat Apr 29 15:47:55 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4YLT-0002va-8p
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 15:47:55 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39290)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <saint.snit@gmail.com>) id 1d4YLQ-0002vM-W8
	for groff@gnu.org; Sat, 29 Apr 2017 15:47:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <saint.snit@gmail.com>) id 1d4YLQ-0002hB-0o
	for groff@gnu.org; Sat, 29 Apr 2017 15:47:53 -0400
Received: from mail-qt0-x229.google.com ([2607:f8b0:400d:c0d::229]:34457)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <saint.snit@gmail.com>)
	id 1d4YLP-0002gk-Ry
	for groff@gnu.org; Sat, 29 Apr 2017 15:47:51 -0400
Received: by mail-qt0-x229.google.com with SMTP id c45so71197411qtb.1
	for <groff@gnu.org>; Sat, 29 Apr 2017 12:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=Xg0/92oXT4epvncy4/V6RVhKazdNIIrmgwZyA+Zd2YU=;
	b=hbLD+WazWk59JEFr9ucfr2UFtt7zl6tDtKRGzZ5ylwykB7td1lEbojdQYMbm/AXm+S
	EFRogm+rMaIX5RHz1DvVeiFiND4Ylsz+Z0eq8pgiZ+PPQ2Syf8bwoariAurLkvs1rUj4
	K5woFBGemri4KthYHgmWjLszm4IL/d+GoK9r7v+Q2Wy9nwfyHe2bKkwEBB4ixaW/eoHc
	1Qu8Or2VUBDTChdJLhaGRYbVpMi3F8GUDZilu/XNTsZbVy7N6cIKspO5olZMDDeG4fxh
	jFfRHEYZA6FwmX8TaOdRq9LbMCTuKfZgw/DY/Km9FrMciYEa79ONzachIhgYHWMvxxRg
	Ze+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=Xg0/92oXT4epvncy4/V6RVhKazdNIIrmgwZyA+Zd2YU=;
	b=JUrbi60PgPFKCqU+l/db1d7qVB+U6r+JpjNUxYamvWBxi4q8AbdIewMujZxZD2S0zD
	qlCl9rGwbXIBuFhUNfmuZ2s0QEAndUW+lueSzmxzFj9KfIeBqq2xgM0KTcfd4CCaXWJ0
	i+8I4yiZFC+rXglddIYZzzfssNRWuB2hgyYIA9qD+dxjXf4xYRIYbQpmZX1k/luUZQnz
	8A8NJA2pPEe8+20R6pexga3vC1O/RmTZVsSKXi0Hc5/KIqX6mIbRA+EYQo5gOGuUBFTX
	QAo0PTGqHZr0pPTvxYxmHiw6g992y6AM1EMLijCCSSSNdEYQZA4BZP/pxvpDAL9V/spi
	ai1g==
X-Gm-Message-State: AN3rC/6sm52vGhqbBcC9yiADAzsIeszyXFmoOYn0taG1jR0I1MKyjE+2
	RQt4bUFMAHcCcMo004Bb4Cc1D7x2Rg==
X-Received: by 10.200.4.140 with SMTP id s12mr16474861qtg.35.1493495270956;
	Sat, 29 Apr 2017 12:47:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.51.122 with HTTP; Sat, 29 Apr 2017 12:47:50 -0700 (PDT)
In-Reply-To: <86265.1493480955@cathet.us>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
	<20170429134006.GB95205@athene.usta.de> <86265.1493480955@cathet.us>
From: Dave Kemper <saint.snit@gmail.com>
Date: Sat, 29 Apr 2017 14:47:50 -0500
Message-ID: <CACRhBXMhTdyG3tetwf-7M7ACC3NarrA0AYw23z=4Udi2WePTdQ@mail.gmail.com>
To: groff@gnu.org
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:400d:c0d::229
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 19:47:54 -0000

On 4/29/17, G. Branden Robinson <g.branden.robinson@gmail.com> wrote:
> At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:
>> So yes, documentation kind of recommends "Don\(aqt listen".
>
> I don't interpret it that way.

Nor I.

The quoted mandoc_char passage cites things like "source code samples"
as places where one should use \(aq, but seems to explicitly recommend
against constructions like "don\(aqt" by saying, "In prose, this
automatic substitution [of U+2019 for '] is often desirable".

The groff_char passage says only *how* to get a U+0027 in output
without addressing in what cases one might want to do this, so it
gives no recommendation at all.

So I fail to see where the quoted documentation "kind of recommends
'Don\(aqt listen'".



On 4/29/17, Anthony J. Bentley <anthony@anjbe.name> wrote:
> Unicode made the decision a long time ago to consider U+2019 as both
> right single quotation mark and apostrophe; see the Apostrophes section
> of Unicode 9.0, chapter 6.

Yes, and that remains a bad decision, because it conflates two
distinct marks of punctuation that have vastly different semantic
meanings, disallows automated checking for balanced quotation marks,
and causes other problems eloquently described in:

https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-represent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong/


From MAILER-DAEMON Sat Apr 29 18:16:18 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4af4-0001lu-M1
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 18:16:18 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59368)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4af2-0001lo-LS
	for groff@gnu.org; Sat, 29 Apr 2017 18:16:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4af1-0005ds-Kk
	for groff@gnu.org; Sat, 29 Apr 2017 18:16:16 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:46911)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d4af1-0005d4-Du
	for groff@gnu.org; Sat, 29 Apr 2017 18:16:15 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d4aey-0002yU-2s; Sun, 30 Apr 2017 00:16:13 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d4aex-0001rH-FS; Sun, 30 Apr 2017 00:16:11 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d4aex-0006no-BH; Sun, 30 Apr 2017 00:16:11 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id d09069fb;
	Sun, 30 Apr 2017 00:16:11 +0200 (CEST)
Date: Sun, 30 Apr 2017 00:16:11 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Dave Kemper <saint.snit@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170429221611.GA32329@athene.usta.de>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
	<20170429134006.GB95205@athene.usta.de>
	<86265.1493480955@cathet.us>
	<CACRhBXMhTdyG3tetwf-7M7ACC3NarrA0AYw23z=4Udi2WePTdQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACRhBXMhTdyG3tetwf-7M7ACC3NarrA0AYw23z=4Udi2WePTdQ@mail.gmail.com>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 22:16:17 -0000

Hi,

Dave Kemper wrote on Sat, Apr 29, 2017 at 02:47:50PM -0500:
> On 4/29/17, G. Branden Robinson <g.branden.robinson@gmail.com> wrote:
>> At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:

>>> So yes, documentation kind of recommends "Don\(aqt listen".

>> I don't interpret it that way.

> Nor I.

I stand corrected.  As was pointed out to me by three people,
I misread both manual pages.

FYI, i submitted a patch adding a brief sentence to groff_char(7)
making it less likely that others misunderstand it the the same
way, also improving a few other aspects in the vicinity, and Carsten
Kunze promptly checked and committed the patch (thanks for that).

Yours,
  Ingo


P.S.

> On 4/29/17, Anthony J. Bentley <anthony@anjbe.name> wrote:

>> Unicode made the decision a long time ago to consider U+2019 as both
>> right single quotation mark and apostrophe; see the Apostrophes section
>> of Unicode 9.0, chapter 6.

> Yes, and that remains a bad decision, because it conflates two
> distinct marks of punctuation that have vastly different semantic
> meanings, disallows automated checking for balanced quotation marks,
> and causes other problems eloquently described in:
> 
> https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-represent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong/

After reading that and a few of the documents referenced from the
comments, the question what Unicode should do seems complicated to
me, in particular when intending to accomodate different languages
and different times, and i don't think i should try to comment on
whether Unicode ought to be amended in this respect.

At least it is clear that using U+2019 for the apostrophe in English
words is not unusual and that the "'" groff input character is a
normal way to achieve that, so the current version of groff_char(7)
accurately describes the current state of affairs.  Whether that
ought to be changed is another matter.


From MAILER-DAEMON Sat Apr 29 20:22:12 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4ccu-0007FD-CU
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 20:22:12 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43785)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d4ccs-0007Ei-2W
	for groff@gnu.org; Sat, 29 Apr 2017 20:22:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@cathet.us>) id 1d4cco-00016k-Vg
	for groff@gnu.org; Sat, 29 Apr 2017 20:22:10 -0400
Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]:37189)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <anthony@cathet.us>) id 1d4cco-00016f-On
	for groff@gnu.org; Sat, 29 Apr 2017 20:22:06 -0400
Received: by mail-it0-x231.google.com with SMTP id x188so59844602itb.0
	for <groff@gnu.org>; Sat, 29 Apr 2017 17:22:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=cathet-us.20150623.gappssmtp.com; s=20150623;
	h=sender:from:to:cc:subject:in-reply-to:references:comments
	:mime-version:content-id:date:message-id;
	bh=FG3b+ptBk6PceyiHzoW5FrG00IAnzlym7oiJNgHi+vE=;
	b=lftah+opXp4VvXI5GfVfxRBqmD+Lc1TcIohQpZBUfp7o9i7RB/RF7OsjudBGVdTw/r
	SM2qlo4lNNq51nczLpEVce/RO8MUcBwu2eat1GskttG+dxMPzaXO8sZb60pqANI85Qob
	gu3EYE8IA0Si4gT92rDenKgvhIYA5kmUpQVXNET+fGCte68+1STl++taNk6R4idJSbME
	JCRpXMX4YXGAkpfJ35jVZCRu0rhzkVGMEZD0WS6T6gML8dxlSJiTYoQJJ0goSGRhuxEq
	vKKG/oSHZXWRPdc56raJ7kquoIp1fttynUqBAgRI31qzJXBRVh2O7XwdLK6Gt0go0Uzv
	b4kQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references
	:comments:mime-version:content-id:date:message-id;
	bh=FG3b+ptBk6PceyiHzoW5FrG00IAnzlym7oiJNgHi+vE=;
	b=Vl647k0YSXg12GI4qGafSDiAg8HPz0I82l9M5OgGBXb+kjhaGdb8KLFhvjMJqjekz1
	cX1c3qOU0eyy51uKiYzIWxAFY946TQBOiNVpRU/TWJvNcMmV23v6qZzuvcej4uU5Vmn9
	nflRE0C4bCxhuf9y8UC4R/MWRxbQjY5xRvYl7DJcynWe3Zy+dMu80vIKJ2RR25+0nyZ0
	q3odKoYLeSYssayjNWJ9y1jWXSC7I/M8QVRlirYm/rt/R8xFJk4GDCZgFHr6GqQR9Aoh
	fFCZxMRyWiC8J9spJkeaOrHgj3qry1xRSAyCNWlI9t1A8ILgzUS3Dey3gTrnAmmI6MBW
	rkSg==
X-Gm-Message-State: AN3rC/7D2kevPXQBiezMVCYLg+M/qVSD1rpTN0ihi8PsoWnF0oztnLjZ
	3xFq4Zb6suWIjCnZ
X-Received: by 10.36.33.144 with SMTP id e138mr15372755ita.9.1493511725767;
	Sat, 29 Apr 2017 17:22:05 -0700 (PDT)
Received: from cathet.us. (97-123-144-191.albq.qwest.net. [97.123.144.191])
	by smtp.gmail.com with ESMTPSA id
	195sm1790787itk.10.2017.04.29.17.22.04
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sat, 29 Apr 2017 17:22:05 -0700 (PDT)
Sender: "Anthony J. Bentley" <anthony@cathet.us>
Received: from cathet.us (localhost [127.0.0.1])
	by cathet.us. (OpenSMTPD) with ESMTP id 75162c07;
	Sat, 29 Apr 2017 18:22:04 -0600 (MDT)
From: "Anthony J. Bentley" <anthony@anjbe.name>
To: Dave Kemper <saint.snit@gmail.com>
cc: groff@gnu.org
In-reply-to: <CACRhBXMhTdyG3tetwf-7M7ACC3NarrA0AYw23z=4Udi2WePTdQ@mail.gmail.com>
References: <20170429123255.l47vjszelfbgkw4r@crack.deadbeast.net>
	<20170429134006.GB95205@athene.usta.de>
	<86265.1493480955@cathet.us>
	<CACRhBXMhTdyG3tetwf-7M7ACC3NarrA0AYw23z=4Udi2WePTdQ@mail.gmail.com>
Comments: In-reply-to Dave Kemper <saint.snit@gmail.com>
	message dated "Sat, 29 Apr 2017 14:47:50 -0500."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <97387.1493511724.1@cathet.us>
Date: Sat, 29 Apr 2017 18:22:04 -0600
Message-ID: <39407.1493511724@cathet.us>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4001:c0b::231
Subject: Re: [Groff] Using \(aq in plain English words--bad idea?
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 00:22:11 -0000

Dave Kemper writes:
> On 4/29/17, Anthony J. Bentley <anthony@anjbe.name> wrote:
> > Unicode made the decision a long time ago to consider U+2019 as both
> > right single quotation mark and apostrophe; see the Apostrophes section
> > of Unicode 9.0, chapter 6.
> 
> Yes, and that remains a bad decision, because it conflates two
> distinct marks of punctuation that have vastly different semantic
> meanings, disallows automated checking for balanced quotation marks,
> and causes other problems eloquently described in:
> 
> https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-rep
> resent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong/

The "balanced" argument doesn't make sense, because there are times
where quotation marks would not be balanced. I'm thinking particularly
of multi-paragraph quotes, which in English typically have an opening
quote mark on each paragraph, but a closing quote mark only on the final.

I disagree with most of the other arguments on that page too. In any
case, it is a compromise made for historical reasons, quite common
throughout Unicode and hardly the most egregious (certainly when
compared to either UTF-16 or Han unification). But, well, I'm going
quite off topic...

-- 
Anthony J. Bentley


From MAILER-DAEMON Sat Apr 29 20:59:19 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4dCp-00033e-68
	for mharc-groff@gnu.org; Sat, 29 Apr 2017 20:59:19 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47389)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4dCm-00033N-11
	for groff@gnu.org; Sat, 29 Apr 2017 20:59:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4dCk-0000MW-Co
	for groff@gnu.org; Sat, 29 Apr 2017 20:59:16 -0400
Received: from scc-mailout-kit-01.scc.kit.edu
	([2a00:1398:9:f712::810d:e751]:35172)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d4dCk-0000Jr-2X
	for groff@gnu.org; Sat, 29 Apr 2017 20:59:14 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-01.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d4dCg-0003uQ-Sd; Sun, 30 Apr 2017 02:59:11 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d4dCg-0004Ke-88; Sun, 30 Apr 2017 02:59:10 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d4dCf-000203-4k; Sun, 30 Apr 2017 02:59:09 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id aec619b7;
	Sun, 30 Apr 2017 02:59:09 +0200 (CEST)
Date: Sun, 30 Apr 2017 02:59:09 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170430005908.GD32329@athene.usta.de>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
	<20170427153715.GE37287@athene.usta.de>
	<20170429112613.uprq652tftye4hvu@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170429112613.uprq652tftye4hvu@crack.deadbeast.net>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e751
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 00:59:17 -0000

Hi,

G. Branden Robinson wrote on Sat, Apr 29, 2017 at 07:26:15AM -0400:
> At 2017-04-27T17:37:15+0200, Ingo Schwarze wrote:

>> .TP
>> \fB\-scale\fP \fIxfac\fP[,\fIyfac\fP]
>> is not bad markup, but decent quality man(7) code

> Well, thanks.  This is what it looked like before I got to it:
> .TP
> .B \-scale \fIxfac[,yfac]\fP

That's indeed gross: using font escapes inside .B instead of
simply using .BI - which would still be wrong because the
punctuation should clearly not be in \fI.

> However, _I_ don't like either of the above.  I mentioned before that
> having this \fX stuff directly abutting words throws frustrates spell
> checkers.

I admit that spell checkers might complain less about \c than about
\fIxfac, but honestly, that's what deroff(1) is for.  That's
exactly why spell(1) uses deroff(1) by default.  Feeding roff(7)
source into a spell checker without piping it through deroff(1)
first makes very little sense to me.

schwarze@isnote $ deroff
.B \-scale \fIxfac[,yfac]\fP
^D
 scale xfac[,yfac] 

schwarze@isnote $ spell
.B \-scale \fIxfac[,yfac]\fP
^D
xfac
yfac

It just works, nothing to see here, move on...   --->>>

> The other reason I hate font escapes in man pages is because
> that way "there's more than one way to do it".  As I said elsewhere, I
> think to get people writing man pages competently, we need to keep the
> "language" small.  Most of them are infrequent users of the language,
> and they don't know which parts are the macro package which are "raw"
> *roff.  Many of them are sharp enough to make some shrewd guesses but
> I'd rather take the guesswork out.

I fully agree with that, and also with your plan to (sparingly and
carefully) add advice to groff_man(7) about which low-level roff(7)
features are OK (and typically required) for which situations.
Right now, while the general idea of the "PORTABILITY AND TROFF
REQUESTS" section cited earlier is highly laudable, it is of limited
helpfulness to only say "try to avoid low-level roff stuff" while
we all know that completely avoiding it is impossible in man(7).
Some constructive advice would be more helpful.

As Ralph rightly observed, even to work with mdoc(7), you need to
know a number of things about roff(7).  That's exactly why the
DESCRIPTION in the mdoc(7) manual from the mandoc distribution
points to specific sectins of the roff(7) manual (admittedly very
shortly).  A man(7) manual would likely have to mention a few more
low-level roff features that are hard to avoid.


>> G. Branden Robinson wrote on Thu, Apr 27, 2017 at 09:46:27AM -0400:

>>> and practically no one will see \c as a new toy to play with.

>> That might turn out to be true; it's also plausible conjecture,
>> even though you already reported \c cargo culting right now.

> True, but less than I feared.  Few enough that it's a tractable
> operation to submit patches to fix that stuff.

My conjecture is that cargo cult is roughly propertional to the
number of planes you see.  So far, we have seen about a dozen pages
in 10000 with (arguably) legitimate use and about half a dozen
abuses.

Once you start actively promoting

.TP
.B -S \c
.IR var [= val ],

that means there will be more planes in the sky (unless your marketing
campaign utterly fails), so it's a plausible guess that more people
with partial to bad understanding may start randomly adding \c after
their .B macros.

And to measure the damage done by pages misformatting on old systems,
the number of pages using \c right now doesn't matter either, what
matters there is the number of pages that will be converted to avoid
\f after line-scope macros (like .TP) by using \c.  In portable
software, that is.

Also, i still don't understand how educating people that \c is OK -
which has relatively non-obvious functionality, and, for man pages,
was unfamiliar so far even to people like Doug - is any easier than
making it official that \f, which has much simpler functionality,
is sometimes needed, which many are already used to.  In particular
given that spell checking is a problem solved decades ago.


> Sadly, Gunnar Ritter's Heirloom Doctools site is still the top
> hit on Google.  That's what led me astray.  Thanks for the clue.

Several years ago, i once exchanged mail with Gunnar when he was
still active.  Not long after that, lamentably, he quit.  Still
later, more than one person tried contacting him, to politely ask
whether he would consider putting a pointer to the new site onto
his old site.  I don't think anything ever came of it.  :-(

It's sad and strange, because everybody i heard mentioning him
seemed to agree that he is a very nice and kind person.


>> It is likely that there are more implementations than i know of,
>> and some may well be alive.  Besides, i did not even try to list
>> ad-hoc non-roff man(7) parsers.

> This may warrant another thread, but how many of _those_ are still
> alive?  I'm betting the language in groff_man(7) and man(7) [man-pages]
> about portability and safe subsets hasn't been touched in years.  I also
> suspect (without much evidence) that a lot of these non-roff man parsers
> gave up the effort before achieving quality output with a significant,
> representative sample of real-world man pages.

Frankly, i have never searched for man(7) parsers, so i have no idea.

I came across a number of man(7) generators apart form pod2man(1),
pandoc(1), and mandoc -Tman, but that's the opposite direction;
unsorted examples, probably much more incomplete than the list of
roff(7) implementations i sent earlier:

 * http://docutils.sourceforge.net/rst.html
 * http://github.com/rtomayko/ronn
 * https://github.com/GostCrypt/libgcrypt/blob/master/doc/yat2m.c

Oh, and here is one in the direction you are asking for, but i have
no idea about the quality or relevance.  Judging from the size, it
is not likely to be very complete:

 * https://raw.githubusercontent.com/rofl0r/hardcore-utils/master/man.c


>> Did you test your proposed new syntax (.TP using \c to include
>> two macro lines in the head) on
>> 
>>  - Oracle Solaris 9, 10, or 11
>>  - illumos
>>  - Plan9 (not sure whether that is still relevant)
>>  - DWB (may well be irrelevant by now)
>>  - Any other commercial system like HP-UX, AIX, etc.: i don't
>>    have the slightest idea what those systems use today.

> I sure did not.  I don't have access to any of those at present
> and I have a half-strength RMS-style allergy to non-free software.

So do i, but i occasionally look even at commercial systems,
in particular those that are as archaic as Oracle Solaris,
not because i want to use them, because they are so unusual
that they make you find bugs you do not easily find elsewhere.

> But I'm willing to use shell accounts to do regression tests.

I'm able to test on Solaris 9, 10, and 11 and on Plan9,
but i don't have access to other systems either, and i cannot
hand out shell accounts.  If you are an official member of
the groff project, OpenCSW might grant you a shell account,
though:

  https://www.opencsw.org/extend-it/signup/to-upstream-maintainers/

Those are very nice people, just ask them if you need it.


Let's see:

schwarze@unstable11s [unstable11s]:~ > uname -a
SunOS unstable11s 5.11 11.2 sun4u sparc SUNW,SPARC-Enterprise
schwarze@unstable11s [unstable11s]:~ > nroff -man
.TH TEST 1 2017-04-30
.SH DESCRIPTION
initial text
.TP
.B -S \c
.IR var [= val ]
indented text
^D
User Commands                                             TEST(1)

DESCRIPTION
     initial text

     -S   var[=val] indented text

SunOS 5.11           Last change: 2017-04-30                    1


So yes, it does misformat.  The var=val ends up in the body.

schwarze@unstable11s > sed -n '/de TP/,/^\.\./p' /usr/share/lib/tmac/an
.de TP
.if !"\\$1"" .nr )I \\$1n
.sp \\n()Pu
.in \\n()Ru
.nr )E 1
.ns
.it 1 }N
.di ]B
..
schwarze@unstable11s > sed -n '/de }N/,/^\.\./p' /usr/share/lib/tmac/an
.de }N
.if \\n()E .br
.di
.if "\\n()E"0" .}f
.if "\\n()E"1" .}1
.if "\\n()E"2" .}2
.nr )E 0
..

Good luck getting that fixed before the first manned Mars landing.

schwarze@unstable11s [unstable11s]:~ > nroff
.de mT
trap sprang!
..
.it 1 mT
line 1
line 2
^D
line 1 trap sprang!  line 2

schwarze@unstable11s [unstable11s]:~ > nroff
.de mT
trap sprang!
..
.itc 1 mT
line 1 \c
line 2
line 3
^D
line 1 line 2 line 3

Macro names are limited to two bytes, and .itc doesn't exist.

Yours,
  Ingo


From MAILER-DAEMON Sun Apr 30 06:18:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4lw8-00074e-AF
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 06:18:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44752)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4lw3-00073U-Ms
	for groff@gnu.org; Sun, 30 Apr 2017 06:18:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4lw1-0007aN-IY
	for groff@gnu.org; Sun, 30 Apr 2017 06:18:35 -0400
Received: from mail-yw0-x22d.google.com ([2607:f8b0:4002:c05::22d]:33364)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d4lw1-0007aH-Cd
	for groff@gnu.org; Sun, 30 Apr 2017 06:18:33 -0400
Received: by mail-yw0-x22d.google.com with SMTP id 203so46818570ywe.0
	for <groff@gnu.org>; Sun, 30 Apr 2017 03:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=IbLMWBNjWnUO7kTdD2k0/za26otxge7mSuLmZ/Mmsn4=;
	b=gOHEp5zwMgxWPzgvBRohH0uWvp8cUPT0hV67oISavzIoPEOKq5cjrbFrRjM2SqDxLu
	MsqIKaaqP79ldTo5kOu21nuuxMDmaNvLVon/dR7SW44numCNCrdBFk5Cw3t3GsZtua38
	b9taxeQQ1+Np7tVcWSfz2DDyIONJLiBTXRh8qzqRfMzukZKmkpyM2joYS8ymGvOOJmdB
	GkpJdJLFCOpZqs6DMYPYUrsdQaMWyk9J6JavDFTbS8atj1XB08Ij23zsN+tSNgJVJoVK
	70RPPHSlyQYMwrOSYYaT8NHkJ/rNA/0ATw/9UVt1+ubog3aT5Fhwqs6U2oV6sWPw+D+O
	JHCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=IbLMWBNjWnUO7kTdD2k0/za26otxge7mSuLmZ/Mmsn4=;
	b=bw28cd3cqmyo9xUP+Qb7GE7cjpMK7I2ZQyVqTZpj/UxGxKIanrBAH7FtITU8v10HLG
	nLCia2LFC/p7y1PFusvbilz6ARh/WX4cO1FkXvxO/pMWxzFi9Ohm8PSH3Agcq97XunD3
	SuxtV9crS3hVBspvoBSK11xIfrYJ8wg6Rb8WzRHFE5Z91+XeJ3kAQ+H0WgkSYSVfUQ9T
	+IRXLcjNCDQo4m72FVoaRVnG8zzBI+1TBiLLD2vXec8GBXoU9J5UIeC7a1Q2XF4G779A
	GUCUCV5U16QwknADdfxzGjlm1lfmWdoLVR6SEvHKdq8rqVKYjlgwKEouA+wFCwRbNwLm
	BSKQ==
X-Gm-Message-State: AN3rC/4Y+/7uKfY30+YbM8FezLvta4UKMUxRsxHfhBfVcwO74646e2sI
	EJtiXI+l+blHZP+PScXVR35aKKXqoFasADM=
X-Received: by 10.129.73.72 with SMTP id w69mr15152183ywa.190.1493547512505;
	Sun, 30 Apr 2017 03:18:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Sun, 30 Apr 2017 03:18:16 -0700 (PDT)
In-Reply-To: <20170428153832.EDB8520302@orac.inputplus.co.uk>
References: <CAGcdaje8Nz6oJdnDYfnESwQ1opNN0CGD0+XT9jKAUgvkf3PZRQ@mail.gmail.com>
	<20170428153832.EDB8520302@orac.inputplus.co.uk>
From: John Gardner <gardnerjohng@gmail.com>
Date: Sun, 30 Apr 2017 20:18:16 +1000
Message-ID: <CAGcdajd-mz0-a6KQkxpR6XKzGcS=VM9kgHbH=eTNbRNiqcieHg@mail.gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Problems with arcs and angles
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 10:18:38 -0000

Sorry for the delayed response. Some pull-requests needed tending to before
I had a chance to go through all this.

First, thank you all so much for your help and patience! It truly means a
lot. I've not yet got arcs drawing correctly, but I feel I'm coming close.
Branden's pointers on trigonometry cleared some cobwebs that hadn't been
lifted since high-school trigonometry lessons, making all this slightly
easier to follow.

Turns out the HTML5 specification
<https://html.spec.whatwg.org/multipage/scripting.html#dom-context-2d-arc>
itself
offers a much clearer description of arc-drawing than the docs I linked to
earlier:


> *Consider an ellipse that has its origin at (x, y), that has a major-axis
> radius radiusX and a minor-axis radius radiusY, and that is rotated about
> its origin such that its semi-major axis is inclined rotation radians
> clockwise from the x-axis.*


> *If anticlockwise is false and endAngle-startAngle is equal to or greater
> than 2=CF=80, or, if anticlockwise is true and startAngle-endAngle is equ=
al to
> or greater than 2=CF=80, then the arc is the whole circumference of this
> ellipse, and the point at startAngle along this circle's circumference,
> measured in radians clockwise from the ellipse's semi-major axis, acts as
> both the start point and the end point.*



*Otherwise, the points at startAngle and endAngle along this circle's
> circumference, measured in radians clockwise from the ellipse's semi-majo=
r
> axis, are the start and end points respectively, and the arc is the path
> along the circumference of this ellipse from the start point to the end
> point, going anti-clockwise if anticlockwise is true, and clockwise
> otherwise. Since the points are on the ellipse, as opposed to being simpl=
y
> angles from zero, the arc can never cover an angle greater than 2=CF=80 r=
adians.*


It also explains how arcs and ellipses are drawn using the same coordinates=
:

*The arc() method is equivalent to the ellipse() method in the case where
> the two radii are equal. When the arc() method is invoked, it must act as
> if the ellipse() method had been invoked with the radiusX and radiusY
> arguments set to the value of the radius argument, the rotation argument
> set to zero, and the other arguments set to the same values as their
> identically named arguments on the arc() method.*


Going forward, I *think* I can work this out.

I hope B-spline drawing doesn't turn out to be as difficult. =3D(

Thank you all again!



On 29 April 2017 at 01:38, Ralph Corderoy <ralph@inputplus.co.uk> wrote:

> Hi John,
>
> > <https://cdn.rawgit.com/Alhadis/language-roff/
> a7c07744a9d44adf32a546646f7a8d57d52e6e58/preview-tty.html>
> > <https://cloud.githubusercontent.com/assets/2346707/25514878/732e09ea-
> 2c23-11e7-97ea-9674d3845dd1.png>
>
> Gorgeous.  :-)
>
> > Groff's output gives me these coordinates to go by:
> >
> >    - startX, startY - Coordinates of the arc's starting point
> >    - centreX, centreY - Coordinates of the arc's centre
> >    - endX, endY - Coordinates of the arc's terminal point
>
> I'm assuming centreX and centreY are zero as it's just a simple
> translation to get there.  And for the moment that startX and startY are
> in the x>0, y>0 quadrant.  This gives a right-angled triangle (0, 0),
> (startX, 0), (startX, startY).
>
> > But the canvas arc method I'm working with requires all of these:
> >
> >    - x - The x coordinate of the arc's centre.
> >    - y - The y coordinate of the arc's centre.
>
> 0, 0.
>
> >    - radius - The arc's radius.
>
> sqrt(startX**2, startY**2) as pic's arcs are always circular.
>
> >    - startAngle - The angle at which the arc starts, measured clockwise
> >    from the positive x axis and expressed in radians.
>
> That's the triangle's angle at its origin corner.  That's the arc sine
> of the opposite edge's length, startY.  But this assumes the radius,
> i.e. triangle's hypotenuse, is 1.  When it's not, it's
> asin(startY/radius).
>
> This bit of Python might help.
>
>     >>> from math import *
>     >>> def d(r): return r / pi * 180
>     ...
>     >>> d(asin(0.001))
>     0.05729578906238321
>     >>> d(asin(0.999))
>     87.43744126687686
>     >>>
>     >>> d(asin(1))
>     90.0
>     >>> d(asin(-1))
>     -90.0
>     >>>
>     >>> d(asin(-0.001))
>     -0.05729578906238321
>     >>> d(asin(-0.999))
>     -87.43744126687686
>     >>>
>     >>> d(asin(0.5))
>     30.000000000000004
>     >>> d(asin(sqrt(0.75)))
>     60.0
>
> You can see asin copes with [1, -1], giving [90, -90] in degrees.
> You'll need to check the signs of start{X,Y}, making =CF=80/2 adjustments=
 to
> the radians you obtain to handle the other quadrants.
>
> Hope that helps.  It's been many decades since I needed this.  :-)
>
> --
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy
>
>

From MAILER-DAEMON Sun Apr 30 08:27:46 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4nx4-0000gj-43
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 08:27:46 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57451)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4nx1-0000gd-Iu
	for groff@gnu.org; Sun, 30 Apr 2017 08:27:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4nww-0005rE-J0
	for groff@gnu.org; Sun, 30 Apr 2017 08:27:43 -0400
Received: from relay01.pair.com ([209.68.5.15]:33602)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4nww-0005r2-EH
	for groff@gnu.org; Sun, 30 Apr 2017 08:27:38 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 3A98CD00AFE
	for <groff@gnu.org>; Sun, 30 Apr 2017 08:27:37 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 527DF2128B
	for <groff@gnu.org>; Sun, 30 Apr 2017 13:27:36 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170429164404.GE95205@athene.usta.de>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
	<20170429164404.GE95205@athene.usta.de>
Date: Sun, 30 Apr 2017 13:27:36 +0100
Message-Id: <20170430122736.527DF2128B@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 12:27:44 -0000

Hi Ingo,

> > > .Fl S Ar var Ns Op Pf =3D Ar value
> >
> > This has reminded me of one reason I didn't get on with mdoc.  Only
> > the `Fl' is obviously mdoc's, due to the `.' invocation.  The rest
> > are a mix of command and data, but without any sigil one's left
> > guessing unless the command set has been memoised.
...
> > If, in some made up syntax, it was
> >
> >     .Fl S .Ar var .Ns .Op .Pf =3D .Ar value
> >
> > that might be more grokable,
>
> Remebering the above very simple rule about Xx-style words, it is
> about the same; maybe the shorter version is even easier to read.

No, the `dot-less' version, though shorter, isn't easier since there's
too little to distinguish command and data and the /^[A-Z][a-z]$/ rule
is slower to apply when reading than /^\./.

> > though still long-winded for `-S var[=3Dvalue]'.
>
> It is not long-winded at all.  Even in man(7), which has no sematic
> annotation, it is
>
> .B -S
> .IR var [=3D value ]

But with that -man, I can quickly see that "-S var [=3D value ]" is the
useful information being presented by the page.  If I'm reading for
formatting then I can look back to the start of the line that I've
skipped over, see the .IR, and apply it to the arguments.  But if I
don't, and most of the time when editing a man page I'm not doing a
careful format check, then I want the plain-text content, and it's -man
that gives it.

> That's 33 bytes (long-winded!?) in mdoc(7) vs. 25 bytes in man(7),

It's long winded because one reads words and then has to parse the
non-English ones, and mdoc makes parsing for humans too slow and
awkward.

    10  .Fl S Ar var Ns Op Pf =3D Ar value

     2  .B -S
     5  .IR var [=3D value ]

> The basic concept of mdoc(7) is extremely close to the theoretical
> optimum.

That's not what's wanted; redundancy for a reader would improve mdoc,
e.g. a `.' sigil, or `[]' still being present even though `Op' doesn't
need them.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 08:50:45 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4oJJ-0002tK-F4
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 08:50:45 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59524)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4oJG-0002tC-7i
	for groff@gnu.org; Sun, 30 Apr 2017 08:50:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4oJE-00049k-PO
	for groff@gnu.org; Sun, 30 Apr 2017 08:50:42 -0400
Received: from mail-yw0-x22b.google.com ([2607:f8b0:4002:c05::22b]:34936)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d4oJE-00048L-H3
	for groff@gnu.org; Sun, 30 Apr 2017 08:50:40 -0400
Received: by mail-yw0-x22b.google.com with SMTP id u70so47604650ywe.2
	for <groff@gnu.org>; Sun, 30 Apr 2017 05:50:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=8eE1qj0B4sDUpOVhScfNFDTWVs6Xw1Xhxd8N6u+jv9Q=;
	b=CjsmHRhpJPrr4La6DTZYgHRh8SGCPMtYwtAOC020CtGTBU04nOsrDT/3RAU3c04jQw
	UdU7kuaxIkgsm42Sv5jj8IFeJiT3mR2ovbgkzQAkUBkSmW1KzdX3tiSAhst43/PPrcQM
	zZjDCh8WC/2uwDz6xK6D40C/zBowI/Udu4dUJQ4AA9wWlU7k6/PfgD2zgENjyYJbagS6
	vPDlJDupiqSkhgPGHoygpkAW88DRnx3O2rEBDnfmAsNjy6Wm5JHpeivkfnijmwZowC9E
	H1/hZVSML+5bZv2Z7JEH5J6f5UirgKSKxpCM8OH1IoXAIfx69Xb7ogq7lS4aofmcJQf/
	hFwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=8eE1qj0B4sDUpOVhScfNFDTWVs6Xw1Xhxd8N6u+jv9Q=;
	b=MCf0xurCXbAc+0Y6n0gk/C+UqYgu3T59rLNiFuGtqC5dtWUovTg/x2CBv3lqxYs2tE
	Lf9NS47dzcKdglLseRGlkgkmmxjKe/Bhqf99yfMmJrCla0zwZkWXvnGE125EhvcjDIeW
	bPQukz4h4JpyGtxuir42+hQkWW4E2TXSs652+DI7lQLYcx2JujKYzdyU3OoXDYbmSkq1
	NHMKjjJ40cpzjCAZXtVdcHvxFwyauion/zFYrOloixTrmP2sOqkX8w+WhbGATYsXQGsU
	pi27sozgo9Boa3fSBj+LJZNwn2gTe/ypx4xCLaF7cpsoqrLqu8EacNK2GTJXm8bh78Wb
	HwPg==
X-Gm-Message-State: AN3rC/6cY/C2qo/Gn4gAmpy4O4d87hRMREwteuDDBnjJq0CkrS/a3H2s
	kKFpKcycNLR01ivcee9GgC+r45AWPioFN1o=
X-Received: by 10.129.73.72 with SMTP id w69mr15616118ywa.190.1493556639538;
	Sun, 30 Apr 2017 05:50:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Sun, 30 Apr 2017 05:50:23 -0700 (PDT)
In-Reply-To: <20170430122736.527DF2128B@orac.inputplus.co.uk>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
	<20170429164404.GE95205@athene.usta.de>
	<20170430122736.527DF2128B@orac.inputplus.co.uk>
From: John Gardner <gardnerjohng@gmail.com>
Date: Sun, 30 Apr 2017 22:50:23 +1000
Message-ID: <CAGcdajeAjDAas07Lt1TdYrQ1sORfZg_CKJ08=CFAEvTkM=Tw5Q@mail.gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff <groff@gnu.org>
Content-Type: multipart/related; boundary=001a114d94e6f3d626054e61c0b2
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22b
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 12:50:43 -0000

--001a114d94e6f3d626054e61c0b2
Content-Type: text/plain; charset=UTF-8

Chained commands are easier to follow with syntax highlighting:

[image: Inline images 1]

But I'm still in agreement with Ralph here, at least with regards to
complex formatting. Lines like `.It Ar radius` are fine, but the Ns and No
commands... ugh. Even when formatting with mdoc, I find it beneficial to
include a few wrapper macros to reduce clutter:

Although I *always* keep this one handy:

.de XR
> . Xr \\fB\\$1\\fP \\$2
> ..


Seeing manpage references without *bold*(1) just looks unnatural to me. ;-)

On 30 April 2017 at 22:27, Ralph Corderoy <ralph@inputplus.co.uk> wrote:

> Hi Ingo,
>
> > > > .Fl S Ar var Ns Op Pf = Ar value
> > >
> > > This has reminded me of one reason I didn't get on with mdoc.  Only
> > > the `Fl' is obviously mdoc's, due to the `.' invocation.  The rest
> > > are a mix of command and data, but without any sigil one's left
> > > guessing unless the command set has been memoised.
> ...
> > > If, in some made up syntax, it was
> > >
> > >     .Fl S .Ar var .Ns .Op .Pf = .Ar value
> > >
> > > that might be more grokable,
> >
> > Remebering the above very simple rule about Xx-style words, it is
> > about the same; maybe the shorter version is even easier to read.
>
> No, the `dot-less' version, though shorter, isn't easier since there's
> too little to distinguish command and data and the /^[A-Z][a-z]$/ rule
> is slower to apply when reading than /^\./.
>
> > > though still long-winded for `-S var[=value]'.
> >
> > It is not long-winded at all.  Even in man(7), which has no sematic
> > annotation, it is
> >
> > .B -S
> > .IR var [= value ]
>
> But with that -man, I can quickly see that "-S var [= value ]" is the
> useful information being presented by the page.  If I'm reading for
> formatting then I can look back to the start of the line that I've
> skipped over, see the .IR, and apply it to the arguments.  But if I
> don't, and most of the time when editing a man page I'm not doing a
> careful format check, then I want the plain-text content, and it's -man
> that gives it.
>
> > That's 33 bytes (long-winded!?) in mdoc(7) vs. 25 bytes in man(7),
>
> It's long winded because one reads words and then has to parse the
> non-English ones, and mdoc makes parsing for humans too slow and
> awkward.
>
>     10  .Fl S Ar var Ns Op Pf = Ar value
>
>      2  .B -S
>      5  .IR var [= value ]
>
> > The basic concept of mdoc(7) is extremely close to the theoretical
> > optimum.
>
> That's not what's wanted; redundancy for a reader would improve mdoc,
> e.g. a `.' sigil, or `[]' still being present even though `Op' doesn't
> need them.
>
> --
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy
>
>

--001a114d94e6f3d626054e61c0b2
Content-Type: image/png; name="figure-1.png"
Content-Disposition: inline; filename="figure-1.png"
Content-Transfer-Encoding: base64
Content-ID: <ii_15bbedceedaa4617>
X-Attachment-Id: ii_15bbedceedaa4617

iVBORw0KGgoAAAANSUhEUgAAAw4AAAEJCAMAAAAKBoDuAAACTFBMVEUXFAwAAAAXFAwXFAwXFAwX
FAwXFAwXFAwXFAwXFAwXFAwXFAwXFAwXFAwXFAwXFAz////w8PDb29vd3d3Z2dnm5ubk5OS5ubni
4uLd397h4eHf4eDf39/X19dERESylLvo6OgAAP8AAADR0dHT09PS0tLU1NTV1dUAmP9GRkbNzc39
/P7v7+/39/8uLf9ra2v7+vwXFv/ek1+/v7/+/v+0lryQkJCrq//Ly8vu7v/Pz8+Li4tlZWVKSkrM
zP9MTP+8vLzm3OnDq8r7+/+amv/FxcW1mL0tLS2hoaHy7fTd0OL3+Pj49fjCwsK2mr/KysqHh4d3
d3dwcHDHss6YmJj19f+/psfs7Oxzc3Pc3P+2tv/p6urj2OYVFRW9ocRubv9jY/+vr6+4nMBVVVUi
Iv8AAMzu7u7Hx8ezs7N+fn7Lt9H08Pb19fXr4+7Uw9nQvdVQUFCVlf+6n8JYWFiDg4PX1//Zyd3y
8v/w6fH28vfNudNaWlrt5u/k5P/h1OTQ0P/IyP+xsf9VVf/o3uqUlJReXl7r6/+8vP80NP8qK//J
tM+pqakyMjI7PP+lpaV3d/8cG//y8/LWxdubm5uhof+Ojv/59vrlqX8eHh6lpf9+fv9paf88rfwo
KChaWv/IyPXExP8NDP/OzvUyMtYQnv+enp6Ghv9LtPt4xPiHyvf99/PD4PP24NHqupmnp/+02vS2
trbuxarS0v/y1cE6OjoOnf767+ffmGcNDQ1AQP/h6/H459xBQdkdHdLhnm/W1vdnZ+HnsIu02vP2
4NKH4EkQAAAAEHRSTlMFAAIIEgsOGxYrJSAeFyMo7z5JvAAAIGpJREFUeNrs2F1KxEAQReHxp020
kzSEgE/uxQ24Dve/A/tSoTpBER9kBrrOqQ3My8dNz+WOiPa+cbgnCtMvHFzChShAbuInDkiggDmI
E4eDhQeiEB1EOAfX4BQSUYCMhHtoHBqGpJ6Iui+pBsI5NA1G4ZEoQEbCPTiHpmG3MBJ13i7CPTgH
jYM0CIMozLWBqOPmmkgIhDzYPBgH1yAMkjCpTNRlk5IJgXAPxuGsYZaFvNReiDptqWWJmM8ejINr
EIZcJZRSnom6rZRSTWSBcA9HDilJw0YULHlIqXGwcdCX0rARBWsY5UHz0DhoHMZZHFaOC3Sb3g+a
B+Ng30o2DtN681/Hcde9yebBvpacg8Yh3/y3cdyVL2seThz0dNA4LCtRsBbNgx4PxsGeDvqT9c8c
3j4/3l/pH/tiz+x124ahKLwlsZ0fkLR4SYk2jCqOECNABy2B0YELR8OplxbwlCnt1qGv0Peu6CZK
JVmU2IZJAN/vZGE2nfDLgWW9ephQF3OTA/KC5GZe6lC8XNp9eCh1OLI6jIb9ZDCABMC0C5Fq8CKF
gyT1NCKlBcOR1eGopsPJ2en5BaWsM5c6T8c8mvUnOtj0JuLjZa4vWyo3YNSWIC/KVhkwlNKL89Oz
k/06MNqZFNZS8KiVWfPw5rfyzdKfGRdyDeneznOtiBc35EDxfHCqc9amw7FdB9aVMawTwV2XfM+v
DhYfcbhI1jDeuw0R2hDm0SMwrNDheL8OA9aJzmVsdZi556EE56GvOFzEMteswQQyggQig8mgTYdh
tw5LyJTVAXlprA4qgyWrAyuC4xDs4VcwGO7XYTQcSNYRMDJBG8LARSIN1BtfgiBIMEShw6hVhw4M
jFXMUYcgcB6rMRhZBdY4DiEff+3QQUl3YMESwZ+JeOVQB8WJIltLX4RiC6g2bgDfsAZl61oH5Uyu
qYoF51EZHlUOmEZ8WhGxojqvdA4ZjkPYAlzr4CSDubTj0Hce0I8iEfdAJHIOmXomz7+QJ9CGABX8
hw6wolYHJBRWB7oCVZIBJUhA3DokypElZEzFqENARKxYBsuyczDEBxwH7xLc65A4Ag9UetmA5njX
IGJJH+CpcXzJGhq3DnHSHqMnVocGbNFkLgrQhkd2XYgS18HqMNHmsXNYEB9wHPxrcOrgsIHCLVWJ
/fNVQr9fT5tc3wuOeYr9qZ7/OtUPCaO3QHedG70lO9AGEqoI9zq0A5oy1RyHu+Lu1/njgxBvfg/f
TSx950Gxsc7jAoovWWu8Hx2uYE5lcxzEj+m9qPN5+sv6gJTwWiqH+jxIOocr+w8oJyWel+Dgv7rz
8MGhg4jbAqvmOFim01RUsTrc/5xef/OdB/p1M3n9SUmoEu9pHew80BWIOANF/o2bzYfN832YfLpr
uRzbzUdODp7f7J3Na9tIFMD/Bn0ksmZGj0WJo5Uw+CAwxh/gi1lfjD8I2FByCIXavhnsW67JKSWX
XHJobwnbZQ/tYQtlj/uX7XszUmQrlhrvEm/X7W/azIxm9JSm79cnf9EcHTJtqFqebvCNOtSoYykd
2BKanwrb4TT9tFrMY4WX5ZMPC174lmDc0D2rWvgnT7K+YjQ4vHPvKM+ZRvTc5kjbyOH7M67tKc8t
D/nVIQtrYtL7M7J06M/4ug6FAvpgFbbCbPrHqcwYQ73wovQBYMEKO0S/1B/Ht8GmHUzo5sSqWgfa
tvz01g0pFQbuALuhW9GQwG2+ydj+y/7qEPEyOoT0JCvfsKB0qAMkPigdGNWHFits0VCHo/UjrIw6
sJdr1TkgC4Hjl24x+hCGsQ91WGz0gdOTrds/yUr5TTrENL5rHdbKw+8f3n3+/O7D79oGttdBtwIT
dWAbQB0YuwH0QbAY1IFjLs+guZIPxpEpe+cE1/Qjg3ndbptFq55ltZne9ItyZ9eyqnRUeBcwo/1q
R8tM5Zh3xNnE6tK6Hlot5ZJe1AsUmsfXDSlanP90nSTCJcDDJSw4K+ygKSoA6AON+BKHZbYB1MFs
tUZaBiP+k+wPGH4p8JLmtNumvFXyztzzg0Mc8JE2Omy6M9yS6KC320GcJIVJu6iN9vhmac2H335W
fP5NS5Ovw+HGhplID6SzdEj7MIAYlnAJS+rMJrQYb0D9EpBFjSFcjufW3D/CyYMPyFWVTiHkwToQ
HbYCRWk08DybsWt5zlKwVOh4pXFE496VvM45i6n4XXYKC8F2hz6MfBAzHFzU2CbonRqOlsWt26fu
p/fuRNOu3NnQRYYjGhN/jHBHHX8TZzzWodCg+V1PIx5o/Lb9dp91SPj150d+Ta/l6rDZhmOrmFUc
lA5rPmTocAr9SIcp42WZ8b7KddYHiZrd0MocoGmyDiB4B0X7FZcsIT56JTC2oizSocmMC5oEdGkc
kxE9FjFx2M504KqLfTAG9G0eZ+y1855k7WCyI+rOiJL8C+CXmaYNpAAXb+SOa5q8v4t1KPziSkgh
re5G7LUOpaQ2JDypD9tXB6trkg4bAQhkL33gEYIzbDUA6qOGOlDvoA6ccnY+YaICsGS8h5Me5xWZ
weI1XBUZ7wBZwxvQp3PPAfo2P77CDUlEGaUc2IIFPjRqTJ/ROaL8GG3JWdWX13kAGDB+DX4Lr+ZD
na19Xwub8V20COXDmGqWxzOoWYXn6zB7pRUWMrMP3+OheEfpSu1TOvTdL1Mc39HEwcrgaKXTPdch
4ndZFT7+qX18R/dLqccP+dVhExPLQxtErg5iCQAdHsOoBQAr2YA6UG82Vc76VZoNwD9htzihHQOZ
7b2ug2PRQGtoHznEh1Cm3cdN6CQRaXWh0+gBfF2dMxAcQwdRNA9X1HUqdJ1raOo4DsLiapZSdeC7
8UHQL+UDUfZ4FlZbe7YOzZHM+TOuDiU7GokOtHJDk6775US7cc9Mmgz2XAdVHj4k90jkwwctxbY6
WD3TNATP0SFtgwJ14AlUHRBZHTCRB5yw0AAxjCYt0gExq+3WdEFFhHSgA3MYt8Mw7M5xqi9nxDik
1TpHMECzi8uTMSyMzaEDH0I8Av5tV+frUHXgO0TEPpRNnkXbevV8HSpqkq9D0XU7xSCodV3cMXQH
GtHbcx0SBz6q4Uccvkstb6tD2PIc3RAZoA5C2NIGEfMcHeqcOPKh+zjxmqTDURkUsQ60ABE49XyQ
nMer1McsjM2hTXnVARDl9iYdBHv5XzGm0sERWVie9nwdaFL6mg6B+0gYKbTfL8Ml5eEeHYjmf9Ld
kpZiOx10K3BM3c7VIbah2iOqVS6ooQ7UR+0U6tSTDkKmKc2qvt+zcSJ3FJt+jTtzAL8xnsl8lwkv
SIeLsaR8I8x+negH8Sr1/kCtL+3HaAGGlteJr4p9azlXoq19XwuDi920xAai7InNhK1Rvg6VlA6l
r1aHnus2xpJG7VGHwr7rQD6kdbjXUuToQJ/tTf22QtNcKQ5crMAjHa59VRtA4au/fdRhJRdOoWFj
bzYxzzFnyzYd/QR+TQxwQjumdHvTkmLRjqn82scVfQ6dDdlFq7IfwCDJOAwtomg1XFHXmQC0uXKu
48PVav5TdRC784ELM3kofSISnv+J0I578SZVHb6qg+d+cbSYgdsoUd/9cbOk5VeHg3Q7top5xUHp
IK47grhQXAmbGupAfdQuYW5iPwU4p3/CoYXH7Ab4jv2AE1wxyuRGCFDDlS5uk+tLWhmrc41OpbsS
kXSQow5Am/pp5RyjJNE8WglpZQb+if3pdErjCizwz1OrRVFOcYr9bhqibDB1+UTr0eaPpGu53NJL
C5TMsQ6lWIfD91k6jN6qxwsHndMD7dr9EuC41Nh/HUr/6qH0wROstuOYhp0JQDV1RMStCiCS2TXA
rGie+wAqZ/1zszYGqNgi8MGf0gR1sFt4yDE/NckaYVfADx0biwg0enowA7CSiBSlL0dHGMAyvVuK
Zq+EFnZRhvbwxKVtDzGmIcImlA36bh5UFLpZwn43zbYjG2xbly/DBfTzWqdmHWq5WK47K4xaZ+6T
6lC6cC/Eq1iHS/eu9krpQBO3fzg6ee3eFTR+5p51R2z8nTzRek8+/BU90XqfeqJ1Ox0mLQ+LQ74O
Yl2GR1AHO8GcQ8S5TToo5g4uPUCEH6xuw5UbkI4YM1CMDTvBaKAOCG1TNJ106Ot44tl2V14CqGDY
FRKEkNXB3hmiomxADPkmDfsJVk/LZ/SHK4l1KJEO6mHAwHUp+ZUO09VXpUe+q7jGlevv4mU4SWm7
l+HydWBWz3HQhi2qQ5YOdtCgtJyOlQ71jk/p7djEOY2Hkzlmvl0cyg/TDWBKKdMnR3Agdzdv1xLX
GEAlTqHXgCxP7CehwwtA+vLEbgOQcpdOULpRZGjsSgdDUHUgGxR9eN2z07TpcXQ+/ILeYtEduCEJ
cKqqwx3H7qAsdTh3LykTKjLfPff1G5Ko4iLzUCNadzgeOn/c7b0OW75JI1+HUBYH21ghNUEdjDXs
x4Y6UJ+0WlBT65izS1sPeifRCo6PaazaSbGmr52ndlTpaGYLgsCU+8rQN4ygd5ys1KpOPD4Jqh72
/2HTnYpjxJz2jCc86xOhBcFSLzY9g1e6SG7DxOF38skf+vH8dq9kuN/yLXyp/55AtwLSwcgmrcNq
xqIOWTlBOWu/RFOmGd9u+xphWNK24Mfno79KSb3B+/5++zd4H6z7YHVzbSAAellLPYCMFb0BS+NF
UKH/v3iWrf1gh+RXhzU864h0yGUBdSuDOiyMzej95q3xIqjQ3zR/s3f/qg3DQBjAn8Gyy0GMSsGy
BF69iQxeCllMHqBjhzxQXrgyVaF/4kNHIzkh3+8Go4yHPi7CRFEcXLt3dXyLBHGgV+caFdSrpc7P
jLOqUZIa6KmCgvg4vL18q3myn8OhVozD/n3F/qA23183Wetw7V4GbJOSzw47Ojod4gDFjBPO0Rlw
bUr+skSTdUhDSZo0hgMrZxz46dCQd4hDUTQiDRmwjUp9DUezcDggOf9slacHeTN2W5LiMJBd4hCp
+GQXCpVcl9CpksBwuE6r+N87xKKjsfprj8cHv1Cb77H7qUsfnqiC4tJu0hin3lino0YHKwsQYLqG
c3QmfLP4OEQNed+ZEIh0GgTcH+OENGTBt4uNQ9u2uwWNIQ69SdcZi5JUZ34a8DdwBcjjsPBkfNCl
832HktTv5tJcSWA4MCQNY+NAsBGco7NDHO6HryQwHBiilrFxqAAeDOIAgDgAIA4AiAPAB/t2jNJA
EAVg+Aojw5ossQqKoCksZJBU6UVsAimsbKxyjHSBBfEiHtGIcQuLZIe12cn33eEv3uM9OcB/5RDh
xMgBuuQQephOAwyOHEAO0DeHl9HnUzhODgxTTg7nTUppcxeOkgPDlJHDNn1byoFiZeTwkdJrIwcK
lpFDs12FhRwoWOZmaSQHCiYHkAPIAeQAcgA5wA85QIZeOSzS8jYcJQeGKSeHq/llk9LN/GEdDpMD
w5SRw3v69RwOkwPDlJHDepP2rsNhcmCYfMOBHEAOsCMHaMkBWnKAlhygJQf4Iy8HODFyADlAv5ul
alLX9fgsQKG65zCLe1WAMnXP4S3GelxNYoyrAEXqnsPZxSzsVDGOAxQpe5R+jHFyH6BEX+zbsQnD
QBBE0RYOBoQPJcqVuA8XoMC5+lHHNqgBbbq818OHG9ir5zCzDmipnMPpsURb1Rz2mVwDWqrm8EqW
AT0Vc1gMaRqr5bAl8z2gqVIOW5LPgK4qORzJNKNprJDDqQaae57DlWQ5vn9ulmjqeQ5HbtY0bdUP
vJN1H9CR33AgB5ADyAHkAHIAOYAc+LF3ti9pRWEA/xceGAv2AmfP57tC5Yb0JUklyIVfQod3khJu
H2wrDJxbZGUDXwZhi5pU0GqDPsQKWtAYe2f/2M7jc72569U0cx+2+/vgsboezoPP75zzHC9mY+tg
Y2PrYGNj8C/okJZ8yMD/RD4SifTD3+ZFNBpdfAE27dKRDvf7qt/Rehc6JpLyM6kIQMiJkmWw4vDk
qFI5Oj0EC9Ipfw6uHjXnPv4AxPKx2wctGdouFouplnnNA5W49zLGy3Y54mb0KFplVEhG7RvM2qYT
HR7fuMb0QadsIaHnhK9cjiMOgwWnH13Me2hkGzERgisnlJD9VjWIo3MIWhFxIpEYajNaDZgY4r5n
fwma0ptoHd7wnBATYNMuHehA3zd2s+/6zct8R6sbMR4jdtNA+AYsdfjsYix16B9AxCW4arjfPZDE
LtAhVELcTJcRPb4Lo90uJ5Cc11/nV6EVPYt2TIgA2LRLJzrAKwUkDy7xtWNudIagjpC1Dj9drsoZ
wNnJRwsdPqBkE64YTjxK8It10BD9UJ230xdEu0bR+qUVZAHJn4aW9CzaGSHGwKZtOi+llRuX0MGU
aP3WOlRcrjMgDqkxkcKVFK7q83Lar4G26/H4Q2BmfeIpEGpyIgDgCEzMBYPBeQWqBCZm1PngaPDl
eN1YSjyPGzoUdlY9K5sNGazu8PYli5gC8G358xtFz8pe02hVD1mW929IL3aON/xZaEoPomXCYoqf
jyeT5IU6+3IEiMVwMDg3a5cVXevwuHMdeL40aKoD75KsUVbRH0GMQJUtLMbRsj5V58SkAlCdGGWm
eAXjVfQ/iqAgFuvHsuLBXaWmg7qLBOdiPaESz/a+IqV5KIFMCsywDnp/aayxB430MFrCMVorHQJC
PJHNMyFmZDM2pV8HNt3o4HDclQX1HegQN+67C5qEJWixOlSa+RBBHO4v4UatQ8T9VGHT4rgmLIKU
DM8HxWT1cMW7PjIzSHsG/qUQU7OzQVG/OmB8D3GppoOGGBtOa7tmHehCPxAxXFHoJywOL5fQHImh
g/KJtMloWs6J2zL6IVN37x4a/FCuPlpiwSgdXopRh2yeCrEA8EQIEV6Uz4V9CtuNDrcuebLkRoan
3KY6nLgklaPPYMEWrmUgRgmmd7ial20+A2ZmeX/gFeKZbEYcQI9CjFAbFUKsg2QRGB7Lru8TTfys
g1sfpCl76UJeCQwd6IQpn8ByY7TODIBvE6trDtUOVkVx6OtDgy++XkRbVzqoUyJMrZesUKaEiIK0
wq6zu9OBj1rvQ6e4EYseyWpZBaKJDnDkqvKtUQh1hRJWQ2e21uEwWDNfTYEXQsxDlfGx6ecBzhZI
sg0G+lg8SoE2JjukA2ViFqyIIOug0qxvrBWbmMg0RuvZiTvpaKhVtN/fGkR6Em1d6TDNmyQlKLzV
jVPSMT09vTBo69CVDq8ePeqTPjyAzuD50qC5DnD600U0nizlnahVH3PcYfND+SgliDrFmwPHTFAw
40A7bfqtCdLB5ytiWV8dlhEx7l7KgJlMiXWAHdaBQ9DoReZoGeeeKdqm9CRa69LhKaiTQsdeHbov
pV/d6PSLZdo8WWIOTyu0YwITBcSDgparnV26ab9iTZTe+RkulseoVhgclI+TANUd9jyY4NUBNNzP
lnmUKayigQlz7cAhpC118Ofc7iXFFG1zehKtRekQoNJhfFBexYhnYNOdDiDXh8fQCRY6lFolyHvp
A5iIoc7aEHcoU9gSmgED44O8VQ4LMfscYEw2IInSptoE60CPB7oOkNW2ndj44UKohNvU8gFqv14Q
LJt1aPccrf/Luxpff6g9iLZZ6TBiV9BXqcP1NnU4GCjyjQmWq8MGNOdbw4FrJoEDcYmHzytbJYhM
jugE58ET3jFDkjTgdhxMsA68w6kbZQ7xGP7EtyqLbB5LTKWXaSDZMuvQ3lpoLqV7EC098xpXrXPj
BdJhGmy61cHh4EZulu5BG+ygXgFygpj+tgmNnJwBQTocwh8sc1f6DN0yQV6PiqBeWS5y+i+clw6T
0ADrQD1j6XyUykDjCP28YmiIBT6QUmtLRT3t6gBvzvl+9dESk7XS4RnvpuapdIAR+sGmOx1oVei7
+/je/dvX2vxXibEWOhwgavmseVqtuI5+ARweyVoawHT9Gl8co6qyZYIAVYpcMSfp7VeeivPSYRZM
GDrABhb5oDWW7gffBuW8iQjiWgSG5WOG7+1IqWqqcRWx1qETuo+WmRMisPBEqe4Svcrrl4JKBzqG
Gh0BZWx9NAk2l9ah71qNV3AxrVeHLDbek0M61DiFOvijMhWIHJ9eulvcRjdpfOgcoNJSSFiDRYvS
gaZg7msogfpBK0oxLO8nTSFTANYB952N13VWKTE9iJaYEESAVgeGxQnzhWSPzW/27Z+lYSAMwPhX
eOWwJFUoBYtDFaoo4hh1kbiJSnTQQRwkdRCKCBb/DOImFfFDCArVwa9nr5VItEou1CIvz28qJVAC
eZpL7i53Dva+YBVjyeT2M4dt+3eXEtlVByuS9jTb89aWtOZMeSH16bK8V5UfHCaLD+aWSh3Hdx/P
jkel+TX5Zvqmd/HZi91OIVzsl63da/nuOXl/2p2Us0VcLcpXl+mpCHvoizgYyNla1e43q/aobiWb
vUNrmyVrfv1B4J5DotaaOpgK5e88vrY7u3/ajzIoq0FwJq42mlF0In2dNKJGMrF+vtyImvKP/HK2
9SBYk8RDPaifCr5ir3ROvQcCaEMOeZCDUuSQi13gfSHQhhzyWV64vxZoQw4AOQDkAJADQA4AOQDD
yWHH87YE0Mkxh9g3xhNAJ8ccioYcoJdbDjuGHKCYUw6hMQWfHKCWUw6e8UNygF4uORwYs1VjsAS9
HHKo+qYoMXcH6OWQQ8H4sTBYgmLZc2gZMyrkAM2y5zBm/FYcj/imGIYCaJQ9h3HTxcwD9HK4O5AD
tMueQ9zBYAmquS3S4FEaqjnnwFAJeuXIoSCATuyGA8gBIAeAHAByAMgBIAeAHAByAMihr8lKpTIu
w+V1fnOiJtDknb17+30ZjOM4/i98ZIhTfHU3EnWYpI1DHNJi0lmGlAqqZMRhNWMXw5xNkDkL4hDC
jUsX4sZ/p98+/T3RquiDuKi+bn7dLN0unve679ZZKXI4/bJer79t4A+0r/q+f7WNwoyN9chOVMpE
IYcl8+bG5kDVga3CuWvAlme89ezObfw9O7bX75/aY+APjIi1UNy93Yvr9bWolIlCDgtrwvwG1Bg3
tcTz+DcGhXMG/hLOYT3+TGvoEZEDFYuqHMpGKYf5C9k8A4qeHT78TtOOHH5zIP4F2puPXm+OetiK
v4RzWIs/ZlNXh4rZVQ5lo5TDPPy2/drqvWD8c/0Armvasb34K/5SDo0muVBQ5VBC/zCHdYjI3yc/
x1dkNXpuHyx0eSN8anc7nW4LwsD123az0z2jI6VgDo47fQHmu71o4/LA63Q6QR+Jy3J0aLlPEbGm
Ax2RsBc9CK+PjCqHElLLofHkNH5HTg438nK4SDQG84guQ2+ScGbmH5MrQqQUzMEn8oH4MNBswKHE
BMKZmdHB6FKAiE1mA8CAhAtIq3IoIeVRev4cqMvJ4VFODvIFi080AC6Q6Y6sHlFHF1dGvDNj6v7s
6LDjfl3aoCOjnzz994gsYETdccu3iVwI3sx+Q9Gf3iEbgM05Wh5RgLQqhxJSyGHR7/+3Mukc7qzY
e+V1NFrr+EFALsCHhU4DaPhgPaJ28pcsAG0LKTIH/vxB+tJAxguTWuDI4mUe9pM7DHQwUSJrEfXF
7UbxBZtv4HGTKVUOJaSQw4IFB5/Mmhf1cBCq0jkIN/lyVhA/RQ+IfMRCJ2xPxUo0hkSXkUfmgKXL
pPnIumjGC94jugimh2F4cchtMDk6YEpNTmnEd2d0iZx2GLZ71K1yKD+FHISDtdpCA4rycriCHPGq
c0isUWdKQqAjXs028hSdHYyAc2gRPUVk4pEwBkuNDh4iNldh0Yzq6PA/UM7BWKT+ORzSORxYty4a
pI9twY/GvAY9sTJbFDFNiucIOQnnKJgDArLRaHJwwFTu3EIsf3QYE5kCuUircigh5RywoDZfh7Ls
KL1G017hRyOiUMzR/FK/2XoRV2EBcoTII0fpjdvvJw6tMpBlU0fvibeSJkTDiQ7YYqc/HR0C8vAT
VQ4lpJ5D0aPDx5V3P1yD8GMO+lft2Hn8wCJyuuJ1yRmxLI1ArFhjSAFyFR2lMaahQ2LVe2I+uGgm
O+Wty2DiAMV/6HIy2uercigh5RyW1woeHd5omrYJAufwmFe/zAHvcw8PE6JOcjSYilcvI6IAiNfr
APlkDlh7Ysa2pcjiCb0p23IRsWlmp778NMON7zc04yoCGurIV+VQQsVz2FebM2vH6Tm1Wm0Jijgs
c8D+TZ/XaB/uXLt+BTKHLQ/yztJ4YZKYo3nFUh/tqRwduJJchWcHiyIjIG5r2MYFT44OvHv7Qt8R
92vBN8XD8IimOl5YLoXIqHIooeI5HK8Jxd5YSh0dvjujVeaAA5r2CVkXOYcQjEPgS78cHQqf0eoT
JU/2RjfZudypI989sokl4fQpuWFTR0Z1RmsJFc9heU2Yg2IecQ5yU3gmc4g27mqbtyCDn5ufItbu
UMQek9lGxCMP+eIcHhb4GkZoEvURs4gNbLlTXG0S0RSAY3I1Z5KzMloUC64ia9+8k1UOZaMyO5ye
tfz4LAP/zAXLclDE6bfK34bT+9akgVwvfKufehSTC3m3PFqvVzmUTSm+HLpjw4YNl3YZ+KduHd2w
4ex8VL6xT8c0AAAwEIT8u+7SnIgPeGDJRAfQAXSApwNEB4gOEB0gOkB0gOgA0QGiA0QHiA4QHSA6
QHSA6ADRAa79esluEAaCKEr4WDYSgv2vNqrQtI2Pk2EG9Ltr0DulduQAOHIAHDkAjhwARw6A+7cc
CjkgnsdcPudQyQHhPOpvOawbEMz6OYeFHBBQy2EhB+CPHMYl5XkDgplzWsa3HCblUOoGBFOLcpg8
h74bfn5L5ICAjkt66HrLwY6HlDcgmJzsdDjnoHnYgGA0Di857MfDPg8bEMw+DvvpcOSwzwM5IBwb
h2cOxzyMywYEs4zHOFgONg/qIaWSa53XdX0Al9Ue+FxrLimpBhsHz8F7uCuIVkQzAxdVm1wUw91r
sBzeelAQqUgGLqlIUgznGiyH1x4URJOAC1saxfCswXPQPOw9KAi5Axc3NopBNezj4Dl4DwriNgIB
3BSD12A5nHoYJrkBlzfJcKpBOUh/BCETEMAgFoNq8By8BxmAEDqxGjwH00sHhNJ7DJ7DMwiaQBi9
+XKeg+uBML7klAMA8w1Y5V6yKfitXQAAAABJRU5ErkJggg==
--001a114d94e6f3d626054e61c0b2--


From MAILER-DAEMON Sun Apr 30 10:07:22 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4pVS-0000FF-OV
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 10:07:22 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37344)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4pVQ-0000F9-NS
	for groff@gnu.org; Sun, 30 Apr 2017 10:07:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4pVN-000534-Hc
	for groff@gnu.org; Sun, 30 Apr 2017 10:07:20 -0400
Received: from relay01.pair.com ([209.68.5.15]:39404)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4pVN-000530-Di
	for groff@gnu.org; Sun, 30 Apr 2017 10:07:17 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 44724D00AEC
	for <groff@gnu.org>; Sun, 30 Apr 2017 10:07:16 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 63A3D1FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 15:07:15 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
Date: Sun, 30 Apr 2017 15:07:15 +0100
Message-Id: <20170430140715.63A3D1FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 14:07:21 -0000

Hi Branden,

>     22  .  if '\*[.T]'utf8' \
>     23  .    char - \[hy]
>     24  .
>
> Also, the linitan(1) tool that is a huge part of Debian package QA
> checks man pages for many problems, and I think this is one of them.

I had a look at https://lintian.debian.org/tags-all.html, searching for
`manpage', but didn't spot it?  Lintian does look very useful though.  I
had a browse of a few packages, and some of groff's faults are still in
git.
https://lintian.debian.org/full/cjwatson@debian.org.html#groff_1.22.3-9
http://git.savannah.gnu.org/cgit/groff.git/tree/contrib/hdtbl/groff_hdtbl=
.7.man#n1251

> Debian _is_ trying to bring about the day when that bodge can be
> reversed.

Sounds good.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 10:33:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4pus-0004Iw-B7
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 10:33:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41292)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4puq-0004Ip-He
	for groff@gnu.org; Sun, 30 Apr 2017 10:33:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schwarze@usta.de>) id 1d4pup-0002X1-Df
	for groff@gnu.org; Sun, 30 Apr 2017 10:33:36 -0400
Received: from scc-mailout-kit-02.scc.kit.edu
	([2a00:1398:9:f712::810d:e752]:39963)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <schwarze@usta.de>) id 1d4pup-0002Wt-85
	for groff@gnu.org; Sun, 30 Apr 2017 10:33:35 -0400
Received: from asta-nat.asta.uni-karlsruhe.de ([172.22.63.82]
	helo=hekate.usta.de) by scc-mailout-kit-02.scc.kit.edu with esmtps
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(envelope-from <schwarze@usta.de>)
	id 1d4puj-0001eG-Or; Sun, 30 Apr 2017 16:33:31 +0200
Received: from donnerwolke.usta.de ([172.24.96.3])
	by hekate.usta.de with esmtp (Exim 4.77)
	(envelope-from <schwarze@usta.de>)
	id 1d4puj-00039M-AB; Sun, 30 Apr 2017 16:33:29 +0200
Received: from athene.usta.de ([172.24.96.10])
	by donnerwolke.usta.de with esmtp (Exim 4.84_2)
	(envelope-from <schwarze@usta.de>)
	id 1d4puj-0007ox-6b; Sun, 30 Apr 2017 16:33:29 +0200
Received: from localhost (athene.usta.de [local])
	by athene.usta.de (OpenSMTPD) with ESMTPA id b1e0b378;
	Sun, 30 Apr 2017 16:33:29 +0200 (CEST)
Date: Sun, 30 Apr 2017 16:33:29 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: John Gardner <gardnerjohng@gmail.com>
Cc: groff@gnu.org
Message-ID: <20170430143329.GB71297@athene.usta.de>
References: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
	<20170429164404.GE95205@athene.usta.de>
	<20170430122736.527DF2128B@orac.inputplus.co.uk>
	<CAGcdajeAjDAas07Lt1TdYrQ1sORfZg_CKJ08=CFAEvTkM=Tw5Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGcdajeAjDAas07Lt1TdYrQ1sORfZg_CKJ08=CFAEvTkM=Tw5Q@mail.gmail.com>
User-Agent: Mutt/1.6.2 (2016-07-01)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2a00:1398:9:f712::810d:e752
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 14:33:37 -0000

Hi John,

John Gardner wrote on Sun, Apr 30, 2017 at 10:50:23PM +1000:

> .de XR
> . Xr \\fB\\$1\\fP \\$2
> ..

That's a bad idea for three reasons.

 1. It already stands out by the (N), additional font change is not
    required.  Manuals tend to have so much font jumping anyway
    that they are often not very visually pleasing and look noisy.
    Where that is required to convey semantics, it can't be helped,
    but whereever additional markup is not required, it ought to
    be avoided.  Admittedly, so far, my argumenmt can be considered
    a matter of taste.

 2. The whole point of markup is that readers get used to what gets
    marked up in which way and can easily glean the semantics from
    the markup without thinking about it.  If you invent your own
    presentation for established semantic markup, you defeat the
    whole purpose of the exercise.
    Note that in this respect, mdoc(7) is much better than man(7)
    because it ensures a uniform presentation across all manuals.
    While man-pages(7) usefully suggests standard practices (most
    of which, though not all, conform to preveiously established
    practice), those are unfortunately not enforced by the language,
    so you do see wildly varying markup for the same semantics,
    hindering readers.

 3. By mixing low-level roff(7) syntax into your mdoc(7) document,
    like defining your own macros, you gratuitiously endanger
    portability.  Since nowadays, only groff, Heirloom, and mandoc
    are commonly used for mdoc(7) and those all handle .de, that
    argument has become less compelling, but it is still bad style
    and potentially harmful.  It is also harmful for *authors*
    because they can't edit your manual pages without learning your
    personal idiosyncrasies.
    On the one hand, people say editing mdoc(7) is too hard because
    it contains about three dozen macros and that's too much.  And
    then they go ahead and define their own macros on top of it.
    As if nobody else will ever have to read or edit their pages.

> Seeing manpage references without *bold*(1) just looks unnatural to me. ;-)

You are being selfish.  If you forcefully redefine standard macros,
the result will look unnatural to *everyone else*.  \fR for .Xr is
the standard at least since July 1990 and has been ever since.
It predates the first stable version of groff by more than a year.
Even the first ever public groff version, groff-0.3.1, was only
released in June 1990.  So the established practice you are throwing
overboard was already established at a time when Brian Kernighan's
device independent troff was still the predominant tool for formatting
manual pages.

Oh, and by the way, even when Cynthia made this decision in 1989
or 1990, it was not arbitrary.  The 4.3BSD manuals she was converting
already had the convention of \fR for cross references, and so had
the Version 7 AT&T UNIX manuals before them, and even Version 4
started using bold markup, but not for cross references.  So what
you are calling "unnatural" has been a firmly established UNIX
convention for more than four decades.

See, when developing mandoc, i don't unilaterally change practices
established by groff either, no matter to which degree i like them,
except in very rare cases (like some improvements to .Rs and .Dq
presentation recently) where i first make sure that there is
consensus across the *whole* community and *all* maintainers (groff,
Heirloom, and mandoc) accept the required patches in lock-step.
Examples exist where i delayed committing improvements to mandoc
for more than a year in order to allow sufficient time for consensus
to emerge in the groff community.

Yours,
  Ingo


From MAILER-DAEMON Sun Apr 30 10:42:59 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4q3v-0004yn-G8
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 10:42:59 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4q3t-0004yh-Ix
	for groff@gnu.org; Sun, 30 Apr 2017 10:42:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4q3o-0004fR-Md
	for groff@gnu.org; Sun, 30 Apr 2017 10:42:57 -0400
Received: from relay01.pair.com ([209.68.5.15]:41497)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4q3o-0004fN-Hj
	for groff@gnu.org; Sun, 30 Apr 2017 10:42:52 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 81B6FD00B08
	for <groff@gnu.org>; Sun, 30 Apr 2017 10:42:48 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id D017B1FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 15:42:47 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170426165513.GB50994@athene.usta.de>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426165513.GB50994@athene.usta.de>
Date: Sun, 30 Apr 2017 15:42:47 +0100
Message-Id: <20170430144247.D017B1FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 14:42:58 -0000

Hi Ingo,

> That leads to a natural suggestion solving *both* of these problems:
>
>  - Make sure *all* output devices (even UTF-8) render - as a
>    typographic hyphen (U+2010 HYPHEN) even in manual pages.
>    That solves the second problem brought up in this mail.
>    Yes, it will require fixing lots of manual pages, but if
>    we decide that way, i think i'm willing to try and convince
>    the BSD camp and help fixing OpenBSD manuals, even though
>    i anticipate that will require some work.  That has good
>    chances to work out because quite a few people are already
>    at least half-aware that the input - is not quite the same
>    as an output ASCII HYPHEN-MINUS.
>
>  - Make sure *all* output devices (even PDF) render \- as
>    U+002D HYPHEN-MINUS.  That is admittedly a deviation from current
>    practice, but it thoroughly solves Ralph's original problem for
>    the future, and i think it is close to what \- was originally
>    intended to mean in historical roff implementations, so i don't
>    view it as trampling on roff traditions.  Also, the visual
>    appearance of U+002D HYPHEN-MINUS and U+2212 MINUS SIGN is so
>    similar in most fonts that this change is unlikely to cause
>    much outrage.
>
>  - Educate people to always use \(mi rather than \- if they want a
>    typographic minus sign U+2212 MINUS SIGN (say, in mathematical
>    formula) as opposed to an ASCII minus sign (say, in sample C code).
>
>  - Nothing changes for \(en and \(em.
>
> After the above code changes in groff, Heirloom, mandoc, and the
> related documentation, and until manual pages adapt, people may
> see slighly wrong typography in practice - but none of that will
> harm understanding.  The same goes for people using legacy roff
> implementations other than the three mentioned, or old versions
> of groff.  So incompatibility costs are minor and the transition
> paths are more or less benign.
>
> Thoughts?

Well done, it seems ideal.

    -     =E2=80=90  U+2010 HYPHEN        Long=E2=80=90term usage.
    \-    -  U+002D HYPHEN-MINUS  wc -l
    \(mi  =E2=88=92  U+2212 MINUS SIGN    Maths =E2=88=9242.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 10:58:21 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4qIn-0000Sq-3g
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 10:58:21 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45075)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4qIl-0000Se-Ig
	for groff@gnu.org; Sun, 30 Apr 2017 10:58:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4qIi-00087r-FM
	for groff@gnu.org; Sun, 30 Apr 2017 10:58:19 -0400
Received: from relay01.pair.com ([209.68.5.15]:42341)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4qIi-00087l-BP
	for groff@gnu.org; Sun, 30 Apr 2017 10:58:16 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 082CDD00A91
	for <groff@gnu.org>; Sun, 30 Apr 2017 10:58:12 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 34DDB1FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 15:58:11 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170430143329.GB71297@athene.usta.de>
References: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
	<20170429164404.GE95205@athene.usta.de>
	<20170430122736.527DF2128B@orac.inputplus.co.uk>
	<CAGcdajeAjDAas07Lt1TdYrQ1sORfZg_CKJ08=CFAEvTkM=Tw5Q@mail.gmail.com>
	<20170430143329.GB71297@athene.usta.de>
Date: Sun, 30 Apr 2017 15:58:11 +0100
Message-Id: <20170430145811.34DDB1FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 14:58:20 -0000

Hi,

Ingo wrote:
>     Manuals tend to have so much font jumping anyway
>     that they are often not very visually pleasing and look noisy.

That's true.  And my crude understanding of typography is that =F0=9D=91=96=
=F0=9D=91=A1=F0=9D=91=8E=F0=9D=91=99=F0=9D=91=96=F0=9D=91=90 is
normally used for emphasis, with =F0=9D=90=9B=F0=9D=90=A8=F0=9D=90=A5=F0=9D=
=90=9D being kept in reserve for that odd
time when the reader wants to find, or be attracted to, that term in a
page of otherwise non-bold text.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 12:03:01 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4rJN-0001ny-FU
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 12:03:01 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54116)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4rJK-0001n9-R4
	for groff@gnu.org; Sun, 30 Apr 2017 12:03:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gardnerjohng@gmail.com>) id 1d4rJJ-0001zO-JM
	for groff@gnu.org; Sun, 30 Apr 2017 12:02:58 -0400
Received: from mail-yw0-x229.google.com ([2607:f8b0:4002:c05::229]:34602)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gardnerjohng@gmail.com>)
	id 1d4rJJ-0001zK-DR
	for groff@gnu.org; Sun, 30 Apr 2017 12:02:57 -0400
Received: by mail-yw0-x229.google.com with SMTP id k11so48400914ywb.1
	for <groff@gnu.org>; Sun, 30 Apr 2017 09:02:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=hNYlSF7vWyUHHASj12A3iAYH60EXtcxBdO4hjlyAvrI=;
	b=ExF1YEohw8hEN1+cADN53vKrDE5fm61rxtsFkPxx9aOP+wAzvC7TYHFzCLiwuI/oqw
	xPNTPDAVE96ZuR7vvUPYMIACNW+fUwAzmvwb+ikQUeC+zfPpx1Yn+0sG36CBwFKmnsdv
	Fz4gjscJa+mfuqfbuZKLltFR0UNtCgms8IaylbjEFmG79djOmjAX2C4llAU9KYPTi4HK
	svBr+WMWM76cwVbzASy4ZcsQ7sjmpNc8Tz3yXfO4NdCsk8nz3bRgPopYOc+KMLkAXTwS
	Ulnu1nYmmFlbyxwByv16eQ5k/V0aLVSPjPXF0t+eCOtZAToQk7rnm4wCYvfjNTO59keK
	s2Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=hNYlSF7vWyUHHASj12A3iAYH60EXtcxBdO4hjlyAvrI=;
	b=dNdqDRNpLU4b8Hlh2qtXXcRVGjYkclSX2u7WDf0GrvfkfGqfBpoCEbXb8ILhi/GLFM
	ixgIkMiaq2yGNLSlLfTNYscbB03qQ3Ehvy1GuY5iZViYAj/28HIMVFWqvfQiMa3iSsLf
	vcGGsH28kldvtmHfecq7eA+rgrzrDMnK9Oo4Tqfe3IOVsFPGf9EqSZriv0xJj9gS/bAW
	tQuULUhZZvNgUsXzABnd4ir0J/m9Xb1vLDeT5csFQanwxPW1ejCVylX0F6GF1EGQdRP9
	m77fMkmYTXEuGAb5i1fqZAjaPvVSJ88H4b02iTsmI7ZNBJi0wHcU+ra7V44KvI3OyvTw
	zr2g==
X-Gm-Message-State: AN3rC/6kMDNBMxSqf06hDCXCsepQu8+4MSMnBe9H0+NqpRete74jX3rZ
	Sid/uo1ictqmDYkMWRQZ/8EH0C0Pxx9U
X-Received: by 10.129.73.12 with SMTP id w12mr14956920ywa.219.1493568176603;
	Sun, 30 Apr 2017 09:02:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.171.14 with HTTP; Sun, 30 Apr 2017 09:02:40 -0700 (PDT)
In-Reply-To: <20170430145811.34DDB1FACE@orac.inputplus.co.uk>
References: <20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170427181209.GI37287@athene.usta.de>
	<20170429144753.701BE2112B@orac.inputplus.co.uk>
	<20170429164404.GE95205@athene.usta.de>
	<20170430122736.527DF2128B@orac.inputplus.co.uk>
	<CAGcdajeAjDAas07Lt1TdYrQ1sORfZg_CKJ08=CFAEvTkM=Tw5Q@mail.gmail.com>
	<20170430143329.GB71297@athene.usta.de>
	<20170430145811.34DDB1FACE@orac.inputplus.co.uk>
From: John Gardner <gardnerjohng@gmail.com>
Date: Mon, 1 May 2017 02:02:40 +1000
Message-ID: <CAGcdajfWTCDbZ4fkxcxG6cp+0ZWuCTakDEL42ditfOfmzEOkWA@mail.gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: groff <groff@gnu.org>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::229
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 16:03:00 -0000

>
> *By mixing low-level roff(7) syntax into your mdoc(7) document, like
> defining*

*your own macros, you gratuitiously endanger portability.*

...

*You are being selfish. If you forcefully redefine standard macros, the
> result*

*will look unnatural to *everyone else**


Some documents I write are for personal use, or written recreationally.
E.g., this
<https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/=
arc>
was
made for amusement when I got sick of loading the same slow-loading (and
cluttered) page in a browser. Since I've been referencing that particular
page very frequently lately, it's actually proven quite convenient. Were I
documenting a C library or system documentation in mdoc, well... I know
better than to get carried away scratching personal itches. =3D)

*Manuals tend to have so much font jumping anyway that they*

*are **often* *not very visually pleasing and look noisy.*


True. Unfortunately, these manuals tend to be written by programers with
little to no knowledge of typography or design. Thankfully, I'm not one of
them. =3D)





On 1 May 2017 at 00:58, Ralph Corderoy <ralph@inputplus.co.uk> wrote:

> Hi,
>
> Ingo wrote:
> >     Manuals tend to have so much font jumping anyway
> >     that they are often not very visually pleasing and look noisy.
>
> That's true.  And my crude understanding of typography is that
> =F0=9D=91=96=F0=9D=91=A1=F0=9D=91=8E=F0=9D=91=99=F0=9D=91=96=F0=9D=91=90 =
is
> normally used for emphasis, with =F0=9D=90=9B=F0=9D=90=A8=F0=9D=90=A5=F0=
=9D=90=9D being kept in reserve for that
> odd
> time when the reader wants to find, or be attracted to, that term in a
> page of otherwise non-bold text.
>
> --
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy
>
>

From MAILER-DAEMON Sun Apr 30 12:11:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4rRk-0003O9-AC
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 12:11:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55678)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4rRi-0003Nz-RX
	for groff@gnu.org; Sun, 30 Apr 2017 12:11:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4rRd-0003wb-QF
	for groff@gnu.org; Sun, 30 Apr 2017 12:11:38 -0400
Received: from relay01.pair.com ([209.68.5.15]:45268)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4rRd-0003wA-LJ
	for groff@gnu.org; Sun, 30 Apr 2017 12:11:33 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 18E0CD00AF2
	for <groff@gnu.org>; Sun, 30 Apr 2017 12:11:31 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id 3CAA51FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 17:11:30 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
Date: Sun, 30 Apr 2017 17:11:30 +0100
Message-Id: <20170430161130.3CAA51FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Applications of \c in man pages in the wild [LONG]
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 16:11:39 -0000

Hi Branden,

> The remaining man pages categorize as follows:
>
> mandb(1)                        FONT_MACRO_C
> nmcli(1)                        DOCBOOK_C
> passwd(1)                       DOCBOOK_C
...

Have you a summary combining your two survey-result sets?
For this email, it's

    $ sed '/^mandb/,/^$/! d' `mhpath .` |
    > tr -s ' ,\010' \\012 |
    > grep -v '[[:lower:]]' |
    > sort | uniq -c
          1 COMMENT_C
         58 DOCBOOK_C
         17 FONT_MACRO_C
          4 PRIVATE_FONT_MACRO_C
          1 SMALL_C
          1 SPURIOUS_C_1
          3 SPURIOUS_C_2
          2 SPURIOUS_C_3
          1 SPURIOUS_C_4
          1 SPURIOUS_C_5
         10 TILDE_C
    $

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 12:25:52 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4rfU-0006GK-C9
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 12:25:52 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57601)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4rfR-0006Fz-BH
	for groff@gnu.org; Sun, 30 Apr 2017 12:25:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4rfM-0007cN-U8
	for groff@gnu.org; Sun, 30 Apr 2017 12:25:49 -0400
Received: from relay01.pair.com ([209.68.5.15]:45544)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4rfM-0007av-BQ
	for groff@gnu.org; Sun, 30 Apr 2017 12:25:44 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 8D84DD00B24
	for <groff@gnu.org>; Sun, 30 Apr 2017 12:25:41 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id E99D31FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 17:25:40 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170429112613.uprq652tftye4hvu@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170427123033.GC37287@athene.usta.de>
	<20170427134625.umeev72htdnzqnvj@crack.deadbeast.net>
	<20170427153715.GE37287@athene.usta.de>
	<20170429112613.uprq652tftye4hvu@crack.deadbeast.net>
Date: Sun, 30 Apr 2017 17:25:40 +0100
Message-Id: <20170430162540.E99D31FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] Applications of \c in man pages in the wild
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 16:25:50 -0000

Hi Branden,

> > Besides, i did not even try to list ad-hoc non-roff man(7) parsers.
>
> This may warrant another thread, but how many of _those_ are still
> alive?

There's https://manned.org/
It's useful because it has man pages from many different systems, and
saves having to install a large package just to help someone else.  It's
author, Yoran Heling, responds to emails and implements changes
promptly.  It uses groff(1), but not man(1) IIRC.

> docbook-to-man seems to poison everyone who touches it.  It was cast
> over the wall by Oasis/OPEN in 1996, picked up by David Bolen in 1999,
> and the only people to hack on since then are the Debian folks, and
> even there the package has been orphaned multiple times, the latest
> since 2014.

Well, that's good in a way if programmers can come to recognise the
better quality output from non-Docbook man pages from -man or -mdoc and
ditch Docbook.  :-)

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 14:29:09 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4tal-0007ta-3U
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 14:29:09 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47705)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4tai-0007sQ-Ev
	for groff@gnu.org; Sun, 30 Apr 2017 14:29:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4tae-00062d-Gb
	for groff@gnu.org; Sun, 30 Apr 2017 14:29:04 -0400
Received: from relay01.pair.com ([209.68.5.15]:46886)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4tae-00062V-CT
	for groff@gnu.org; Sun, 30 Apr 2017 14:29:00 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id A97C1D00AF0;
	Sun, 30 Apr 2017 14:28:58 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id C181B1FACE;
	Sun, 30 Apr 2017 19:28:57 +0100 (BST)
To: Doug McIlroy <doug@cs.dartmouth.edu>
cc: groff@gnu.org, esr@snark.thyrsus.com, bwk@cs.princeton.edu
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
References: <201704262136.v3QLauLR026273@coolidge.cs.Dartmouth.EDU>
Date: Sun, 30 Apr 2017 19:28:57 +0100
Message-Id: <20170430182857.C181B1FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] pic syntax blemishes
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 18:29:05 -0000

Hi Doug,

> The convention of dropping irrelevant attributes may have been
> justified during the experimental days of pic's development, but seems
> cheesy now, nearly 40 years on.

I agree a "strict" parsing, considering all attributes relevant, that
disallows `box radius 3' would ease writing pictures with less puzzling
over how something's been parsed.

> The fact that 2d gets tokenized differently from 2nd is also
> disconcerting.

Dropping irrelevancies doesn't help `move 2d' being `move 2 d' because
nothing is irrelevant.  So the lexer would go for the longest match,
making `2d' the token, but then complain when it isn't a NUMBER, because
of the unused `d', nor an ORDINAL?

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 15:21:52 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4uPo-00086S-Cp
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 15:21:52 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4uPm-00085V-OV
	for groff@gnu.org; Sun, 30 Apr 2017 15:21:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4uPj-0005fD-KV
	for groff@gnu.org; Sun, 30 Apr 2017 15:21:50 -0400
Received: from mail-yw0-x243.google.com ([2607:f8b0:4002:c05::243]:33342)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4uPj-0005f7-FS
	for groff@gnu.org; Sun, 30 Apr 2017 15:21:47 -0400
Received: by mail-yw0-x243.google.com with SMTP id 203so8396983ywe.0
	for <groff@gnu.org>; Sun, 30 Apr 2017 12:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=Q8iUKh4jQGqu6qiT3qRLf188eTOPSSz2ualiqeZ3pG0=;
	b=cp7uLpWpBFDU1hbgH+xksNuCjacOjhXM3vgSDNWF9hR3PXKwZgSNjf15eDwQaZMQRJ
	1lKWpsPvWNNEqQRUw2iLP8zseGw0UVo1OhwH+lklOluVE4Tw/feL4hfFZjlSNxQf+4if
	yUD6VqmXhnytkYLxWLqejlXXHqQ6VYWlZmuNPTesQBXkFdNFdIrctyqNlJUsseHpK1oy
	0ITjTU9AhYkiG88xHSqqSVZFxP1p4EcHA08FdlAYQS2TS6z9s8SV7FNQAXUk3b29NDj1
	VPH4zTSAfpQ987RXkNUV/5xui749jVEjMcQ3g18IQQ/AWsz7Np6105bRdAI4SNhDofvw
	RQTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=Q8iUKh4jQGqu6qiT3qRLf188eTOPSSz2ualiqeZ3pG0=;
	b=qNywjRYpOuVVWfEFUO1flMkYf4pdkXHIBIS8FnTF7ewNTjX33k8Uv4OowQBtClYjXy
	1fO963kcOfptM2NnVZBgK+A0ZN5Zo2RnFJC8Uv7EQguNlF60y5jinQ2tbGk1Wypfv2ya
	V9z3Oh9i4FvRQ9KaUIyMjwF4pdjxUvvaNFfafRoe2SSSyXUH2CgHF2ZeodFF91Y+uq3N
	VWoZU/5APx8uhSVblfImpKJwccaUiYxJrMTnJUZbT7GZXB7Ndh3BpoXPT0QcNQTiReRO
	qIEd1CgpSlChd142r+nFTz/oEDxYg6VI14dpZeXDL7zAFBbZCMQI4QBj5id0B/lSjocD
	iwcg==
X-Gm-Message-State: AN3rC/5jbwdSXtzH6cZarDJiaGTN617rOgF2vGGe42nR4NXEdDAGPr4F
	uDso0q+2jQ3Honaq6gY=
X-Received: by 10.129.91.213 with SMTP id p204mr13318314ywb.271.1493580106306; 
	Sun, 30 Apr 2017 12:21:46 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	g65sm6548559ywh.29.2017.04.30.12.21.44 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sun, 30 Apr 2017 12:21:45 -0700 (PDT)
Date: Sun, 30 Apr 2017 15:21:42 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170430192140.r3ucb3vtj3zqrv5w@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170430140715.63A3D1FACE@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="h2ctpw76gow23dml"
Content-Disposition: inline
In-Reply-To: <20170430140715.63A3D1FACE@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::243
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 19:21:51 -0000


--h2ctpw76gow23dml
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-30T15:07:15+0100, Ralph Corderoy wrote:
> Hi Branden,
>=20
> >     22  .  if '\*[.T]'utf8' \
> >     23  .    char - \[hy]
> >     24  .
> >
> > Also, the linitan(1) tool that is a huge part of Debian package QA
> > checks man pages for many problems, and I think this is one of them.
>=20
> I had a look at https://lintian.debian.org/tags-all.html, searching for
> `manpage', but didn't spot it?  Lintian does look very useful though.  I
> had a browse of a few packages, and some of groff's faults are still in
> git.
> https://lintian.debian.org/full/cjwatson@debian.org.html#groff_1.22.3-9
> http://git.savannah.gnu.org/cgit/groff.git/tree/contrib/hdtbl/groff_hdtbl=
=2E7.man#n1251

Here are some manpage-related lintian tags.  Make sure you let that huge
page finish loading before searching.

Apparently the only - lintian cares about (nowadays?) is the one needed
for whatis parsing, which _is_ the most important one.  The number of
people trying to override is rather disheartening, though.  Perl hackers
seem to be responsible for a lot of them.  :-/

manpage-has-bad-whatis-entry (213 packages, 3317 tags, plus 12883 overrides)
manpage-has-errors-from-man (639 packages, 5470 tags, plus 636 overrides)
manpage-has-errors-from-pod2man (58 packages, 460 tags, plus 1 overrides)
manpage-has-useless-whatis-entry (47 packages, 283 tags, plus 84 overrides)
manpage-has-wrong-extension (Not emitted)
manpage-in-wrong-directory (4 packages, 11 tags)
manpage-is-dh_make-template (Not emitted)
manpage-locale-dir-country-specific (2 packages, 18 tags, plus 20 overrides)
manpage-named-after-build-path (4 packages, 31 tags)
manpage-not-compressed (1 packages, 7 tags)
manpage-not-compressed-with-gzip (Not emitted)
manpage-not-compressed-with-max-compression (Not emitted)
manpage-section-mismatch (52 packages, 1244 tags, plus 7 overrides)

It sure is checking for spelling errors in man pages:

https://lintian.debian.org/tags/spelling-error-in-manpage.html

Only 24,000 problems to fix.  ;-)

Regards,
Branden

--h2ctpw76gow23dml
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkGOTwACgkQ0Z6cfXEm
bc6dJA/+II0A+h9KQEECCVuKI+qTuojXdC5qGxyrqLVNXXU2629R86J5xfMeLxDe
XkvBfmOANCjitSs2Ly7e2NbQZ8VHrxDOk0cDC5dP51UaNuZUJ+uR4b3I2aAiRJl5
XJ9Jlg4DwFIGTZk4/chvYd4/mQCJbkMgxecUwOzL0VaEfRE2jtP9WoOa5WeiUG4s
XfkY7pBMREoye12RTSfwL2SD/b+kYM1swmWVrOtFo/eSCoxfyHF0dDQ5peSn+NKO
k5qbAHUAKAcnOexrEcBfgKFTx7mhaYRIeBfuxYY+L6JutEUEjr3DWkEcG4q2mqtm
ScTF5hh3YQyLsRNEcEhI2Pbpgz50r6hIiYoFM97FFn/ESUpwTBu5MDlEghBi85q0
uAfMH/uqROt0sxduW61Vmd+W5K52FjzTO/1s0eSFg1Xmq+PkHctjGcm2ynJM9pp9
LFJ+yYsokh51Jdo07o9ZN0NjFrNB3L1kWcFrkyRBtQGGVOz0Aw5HEpi6b+d3/oZH
DmWlUTtuBlxdVSLIZwkc5/FhObmwwAGXh1eqSQGuTnwbean9C8BN7o4KIBmT5GDY
I8OCfmLqrVd+GNU7GS9MwWFpgM8JaCDP+1MLgJcB95OKWMnKRCt3EvqYqxKPEh8L
SH6jlDc6cjogaB79w0oM95uCtIVTCWsOwNV7vxi1KiTUNi952Zo=
=HK3F
-----END PGP SIGNATURE-----

--h2ctpw76gow23dml--


From MAILER-DAEMON Sun Apr 30 16:31:32 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4vVE-000192-1l
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 16:31:32 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35478)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4vVB-00018w-Ll
	for groff@gnu.org; Sun, 30 Apr 2017 16:31:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ralph@inputplus.co.uk>) id 1d4vV6-0007Sj-Oq
	for groff@gnu.org; Sun, 30 Apr 2017 16:31:29 -0400
Received: from relay01.pair.com ([209.68.5.15]:47953)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ralph@inputplus.co.uk>)
	id 1d4vV6-0007SI-Kd
	for groff@gnu.org; Sun, 30 Apr 2017 16:31:24 -0400
Received: from orac.inputplus.co.uk (unknown [212.159.50.185])
	by relay01.pair.com (Postfix) with ESMTP id 75052D00A70
	for <groff@gnu.org>; Sun, 30 Apr 2017 16:31:23 -0400 (EDT)
Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1])
	by orac.inputplus.co.uk (Postfix) with ESMTP id CEC3B1FACE
	for <groff@gnu.org>; Sun, 30 Apr 2017 21:06:12 +0100 (BST)
To: groff@gnu.org
From: Ralph Corderoy <ralph@inputplus.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-reply-to: <20170430192140.r3ucb3vtj3zqrv5w@crack.deadbeast.net>
References: <201704231610.v3NGA36r010074@coolidge.cs.Dartmouth.EDU>
	<20170424072908.enfnhojgbrh7tc35@crack.deadbeast.net>
	<20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170430140715.63A3D1FACE@orac.inputplus.co.uk>
	<20170430192140.r3ucb3vtj3zqrv5w@crack.deadbeast.net>
Date: Sun, 30 Apr 2017 21:06:12 +0100
Message-Id: <20170430200612.CEC3B1FACE@orac.inputplus.co.uk>
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.68.5.15
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 20:31:30 -0000

Hi Branden,

> > > Also, the linitan(1) tool that is a huge part of Debian package QA
> > > checks man pages for many problems, and I think this is one of
> > > them.
> >
> > I had a look at https://lintian.debian.org/tags-all.html, searching
> > for `manpage', but didn't spot it?
...
> Here are some manpage-related lintian tags.  Make sure you let that
> huge page finish loading before searching.

Yes, I did.  Sorry, I was talking specifically about `-' and `\-' WRT
Debian's bodge and it working towards fixing it.  If Ingo's realignment
goes ahead so we've a clear target then perhaps Lintian can learn some
new transgressions.

--=20
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


From MAILER-DAEMON Sun Apr 30 19:34:24 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4yMB-0002HB-Sr
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 19:34:23 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35693)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d4yM9-0002Fk-8c
	for groff@gnu.org; Sun, 30 Apr 2017 19:34:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d4yM6-0002f4-5W
	for groff@gnu.org; Sun, 30 Apr 2017 19:34:21 -0400
Received: from rrcs-50-74-108-158.nyc.biz.rr.com ([50.74.108.158]:55120
	helo=mail.schemamania.org) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jklowden@schemamania.org>) id 1d4yM5-0002ez-Ul
	for groff@gnu.org; Sun, 30 Apr 2017 19:34:18 -0400
Received: from oak.schemamania.org (localhost [IPv6:::1])
	by mail.schemamania.org (Postfix) with ESMTP id DA1A4256FABA
	for <groff@gnu.org>; Sun, 30 Apr 2017 19:34:20 -0400 (EDT)
Date: Sun, 30 Apr 2017 19:34:20 -0400
From: "James K. Lowden" <jklowden@schemamania.org>
To: groff@gnu.org
Message-Id: <20170430193420.7b7945e61c9b84e5b8820988@schemamania.org>
In-Reply-To: <20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
References: <20170424152237.93942201ED@orac.inputplus.co.uk>
	<20170424154119.c7h6zozyivnoafa7@crack.deadbeast.net>
	<20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
	<20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
Reply-To: groff@gnu.org
X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; x86_64--netbsd)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 50.74.108.158
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 23:34:22 -0000

On Fri, 28 Apr 2017 01:15:05 -0400
"G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:

> the benefit to the user is relatively few keystrokes above those
> > needed for the text.
> 
> Did you write your DocBook-based user guide in ed?
> 
> Nothing has come close to saving me more keystrokes than <TAB> at the
> shell prompt and CTRL-N in Vim.

At the time I used nedit.  Today I would use emacs.  There's no package
for docbook-mode that closes tags for you.  The xml modes I've used are
lame and wouldn't perform well on a large manual.  

DocBook is a complex beast.  It would be great if the editor could do
tab-completion for valid tags for the current parent and valid parents
for a selected region, and jump from beginning to end of a tag.  If
such a tool exists, that would be news to me.  

Meanwhile, what could be simpler than having the editor supply "tool
tip" text to explain .Sx or an "mdoc apropos" feature derived from
keywords in the manual?  The only reason there isn't better editor
facilitation for man and mdoc is ... lack of interest.  The problem is
technically much simpler.  

> We have ludicrously more processor horsepower and memory

Yes, and my contention is that we nevertheless have not developed a
system that is easier to use or learn.  troff macro packages are
simpler and impose less on the author than any alternative of similar
capacity.   The facilitation promised 2 decades ago to deal with the
verbosity and complexity of more recent designs never materialized,
leaving authors with a variety of lousy options. 

> They're programmers.  Some of them are difficult to coerce into
> writing documentation _at all_.

There is no evidence that programmers disinclined to write
documentation do a better job of it if it's made easier to do.  Good
documentation takes effort, and that effort is different from the
programming effort.  

The impetus for Markdown and Doxygen and the like is that good
documentation will emerge by lowering the bar.  It's simply not true.

The problem of writing documentation isn't in opening another file
(Doxygen) or understanding the markup system (Markdown).  It's in
capturing the syntax and semantics from the point of view of the user.
And, as you say, some people have the additional burden of caring
enough to bother.  

I have yet to see good documentation produced by those systems unless
great care was taken.  Having used Doxygen for C library with a 100
functions, I wouldn't use it again.  For equivalent time invested, I
get better results from mdoc, albeit without the pretty diagrams. 

>> when transferring them from the manpage

I was afraid that might not be clear.  What I meant is that as I'm
writing documentation, I'm refering to the mdoc manpage (say).  I've
never done that kind of work for a living.  I'm just another occasional
mdoc hacker, so I quite often have to relearn parts of it.  By
"transfer", I meant putting to use what I'm reading in my writing.  Two
letters aren't hard to remember, and most of the pairs carry some
mnemonic weight.  (That said, better editor facilitation would make the
work less tedious.)  

> C adopted designated initializers, a sop to those who can't recall
> what order a struct's fields come in. 

I guess you're implying that designated initializers, while verbose,
are easier to use, even for aficionados of a terse language like C.
As it happens, my current work is in C, and I adopted C11 as a
baseline, partly so I could use them.  

With today's machines, the compiler can do more than was feasible in
1978.  I'd argue we have bigger structures now, too.  Designated
initializers aren't so much a sop to the lazy as they are a gift of
clarity, because otherwise the programmer has to count structure
elements and supply any zeros preceding the elements to be
initialized.  Designated initializers also support re-initialization of
existing structures, something that otherwise required error-prone
member-by-member assignment.  

All to say that at least one fan of short macro names finds explicit
structure initialization useful.  

--jkl



From MAILER-DAEMON Sun Apr 30 19:36:14 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4yNy-0002ZW-6M
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 19:36:14 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35937)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4yNv-0002Z3-G8
	for groff@gnu.org; Sun, 30 Apr 2017 19:36:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4yNs-0002vS-Dx
	for groff@gnu.org; Sun, 30 Apr 2017 19:36:11 -0400
Received: from mail-yw0-x233.google.com ([2607:f8b0:4002:c05::233]:35331)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4yNs-0002vM-7m
	for groff@gnu.org; Sun, 30 Apr 2017 19:36:08 -0400
Received: by mail-yw0-x233.google.com with SMTP id u70so50682541ywe.2
	for <groff@gnu.org>; Sun, 30 Apr 2017 16:36:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=lTDioSz4LFyME9r6MfEwKmyRgyjhw53pYM7kGvAona0=;
	b=dTPWHMPBi8+RzzuhsA5vlxHY2nux/mx35NKq6944Ba6q7mYz9HHqXe0H0MMgNuNxLy
	I+Ny5piwK40G6v9jCan3lp+gElWaj8H8lAqZzNS2wIXsph+5fzVQKcG3GJGY6u3YMirx
	+SjXKfwnQHgoZOTT74YPnBLeN8/Zbm8X9M7tDVJ7mDexxa3nIYP7S2lt/2ausILaJl3u
	KFVOY63/PJPq97tajRJGE1KwBbVMDfRqBh/7VuJo4bzFCCirw1tW+ygT7kSUjVDfXoRc
	uX715JjbQ9qKieCFAGMh6U5dXVU2fe6HmuhBI+t56oCu43UvUyq56Gv88S2u9dLNFiVH
	CBow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=lTDioSz4LFyME9r6MfEwKmyRgyjhw53pYM7kGvAona0=;
	b=hLjR/9IYD6YgIF9bp4i1tKueVPJYMOlMq43NnZpEi3KQ3c6JY4cM5M5R6+ws9N7H2L
	71EnYqX18OJLVAJbFGy8COo7kHkzM5TmL/WtIuhSSOrgMhx4A8NGh1iNf4+4E9MFCVSb
	SWK6KlHZgWqw86KDu5JNmnlt4S0zAniOGaCH9JFXtb2XS+WCwg7Ib89wzlZFPbflVXwc
	R+EBQXXxr9DcsW0WSTa7QeXUpyf8UUZMfM2IyGBfQVHgOHauQ1bkrNbZEfaCnbfkYTKV
	GeuwZZK94U7TJkCIldn6kapIYWqBTRg54ywDxezUwM+He45P8se3wcxusPcyFteSMS9y
	5utA==
X-Gm-Message-State: AN3rC/7K4G8LzMuzjIVGQMtsGUoAbpg+N/mzE1hby9YcJyyIJhDz3ezt
	geHR8nVsp8TfQvrnXaA=
X-Received: by 10.13.197.131 with SMTP id h125mr3114644ywd.292.1493595367182; 
	Sun, 30 Apr 2017 16:36:07 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	h27sm1005923ywk.63.2017.04.30.16.36.05 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sun, 30 Apr 2017 16:36:05 -0700 (PDT)
Date: Sun, 30 Apr 2017 19:36:03 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170430233601.3iujbjvzoqvup2jn@crack.deadbeast.net>
References: <20170424111639.097A1201ED@orac.inputplus.co.uk>
	<20170424115017.4wb5k6wn2vvedm6h@crack.deadbeast.net>
	<20170424120817.2EF71201ED@orac.inputplus.co.uk>
	<20170424121826.qb734iy72burofyx@crack.deadbeast.net>
	<20170424143915.GA47874@athene.usta.de>
	<20170426145026.E9BD12038D@orac.inputplus.co.uk>
	<20170426155418.u6fm3in46apw6qct@crack.deadbeast.net>
	<20170430140715.63A3D1FACE@orac.inputplus.co.uk>
	<20170430192140.r3ucb3vtj3zqrv5w@crack.deadbeast.net>
	<20170430200612.CEC3B1FACE@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="h6u3wbrpa3eggbfz"
Content-Disposition: inline
In-Reply-To: <20170430200612.CEC3B1FACE@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::233
Subject: Re: [Groff] ASCII Minus Sign in man Pages.
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 23:36:12 -0000


--h6u3wbrpa3eggbfz
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-30T21:06:12+0100, Ralph Corderoy wrote:
> Hi Branden,
>=20
> > > > Also, the linitan(1) tool that is a huge part of Debian package QA
> > > > checks man pages for many problems, and I think this is one of
> > > > them.
> > >
> > > I had a look at https://lintian.debian.org/tags-all.html, searching
> > > for `manpage', but didn't spot it?
> ...
> > Here are some manpage-related lintian tags.  Make sure you let that
> > huge page finish loading before searching.
>=20
> Yes, I did.  Sorry, I was talking specifically about `-' and `\-' WRT
> Debian's bodge and it working towards fixing it.  If Ingo's realignment
> goes ahead so we've a clear target then perhaps Lintian can learn some
> new transgressions.

I'm working up a man(7) style guide that is sure to be completely
uncontroversial.  <beat>

Here is the relevant material from it.

Note that this is related to but independent of Ingo's proposal.  My
preference is not to refer to \- as a minus sign at all, but that bears
on documentation, not his proposed mapping per se.

       Hyphens, dashes, and minus signs
              As noted above, use a simple  hyphen  when  you  mean  a
              hyphen,  as  in  phrases  like =E2=80=9Cbest=E2=80=90known=E2=
=80=9D.  Use an en=E2=80=90
              dash, \[en], to express a range of numbers; for example,
              =E2=80=9Cplease  allow 4=E2=80=936 weeks for delivery=E2=80=
=9D.  Use an em=E2=80=90dash,
              \[em], to express a structural aside=E2=80=94somewhat like th=
is=E2=80=94
              in a sentence.  Use \[mi] to obtain a mathematical minus
              sign.

              Finally,  use  \-  to  represent   the   much=E2=80=90overloa=
ded
              =E2=80=9Chyphen=E2=80=90minus=E2=80=9D  at  code  point decim=
al 45 in the ASCII,
              ISO 8859, and Unicode character sets.   It  is  best  to
              think of \- as a piece of meta=E2=80=90punctuation that has o=
nly
              technical and contextual  meaning,  usually  in  textual
              human/computer  interface  discussions (programming lan=E2=80=
=90
              guages, Unix=E2=80=90style command=E2=80=90line options, and =
so on).

              Two important use cases for \- are (1) to  separate  the
              name  of  a man page from its summary in the =E2=80=9CName=E2=
=80=9D sec=E2=80=90
              tion; and (2) to indicate the hyphen=E2=80=90minus character =
 as
              terminal  input  or output in Unix command names or com=E2=80=
=90
              mand=E2=80=90line options.

Regards,
Branden

--h6u3wbrpa3eggbfz
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkGdNgACgkQ0Z6cfXEm
bc5pPhAAr2x/DBjfmIPbTTG/Gnemnk3wn9bhYXJJAn3527s8F42ZTgfcpW+K2ZfL
CSMynkNzjTctl07Te4VKx9FQ1Yi5AtuyQySlRbPjffnG56FFcjH7KeIdrAVj0TWp
AzHeNiIPpBCjDv0KRA03KGu9t68RC4TNtpfsyD6aP5yMOvXwF9u//kEy8tWdunE4
+zwjkar8spMIBJ9NiJcEPzYdb/6nhx60lrVZUhCFW5lVzmvYNAJI4jSoKZDNhci5
MBj7DTX7FOvA4N2Ra6hAKRNFW934Qi0eJ4hLoPty9IOnnWNG/9zW6i5U7PI8XMJl
6h00xmjPlWxHiKTjGGDSEhVI6FMSuCyBQDcQvBENqQTLwqV8zNJUi10KGtg1673J
ulJSZk2hqUd437Qw42KCprSvdlVXFpprCfF/slrohC6ke5DeH56LAM2RoGqHotwK
qgRPrvCifQyhf5Dp4fEqgGTAzOqk1oULJvlNsRDBBBTBJiyNeVQQNKKiRDi2823Z
IDlWnbbb1VwMTGQgTInuGpQOdMkaH90z3PatyyPsXz83Qk+/iaI6Y0RelCBv0JFU
JX2TFu1s1udroQqVbHQ5JOScXuA281ZuNu33fbC38Et+0cz7vPVOi7CUMQj4frBY
ajOkbcoukd/PwQAgOxRYgnAniLyHSPdi6OIg+RTX2B0QJtIinNw=
=53Vx
-----END PGP SIGNATURE-----

--h6u3wbrpa3eggbfz--


From MAILER-DAEMON Sun Apr 30 19:46:40 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4yY4-0003zw-HQ
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 19:46:40 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37085)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4yY1-0003zd-W6
	for groff@gnu.org; Sun, 30 Apr 2017 19:46:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4yXy-0005CL-VS
	for groff@gnu.org; Sun, 30 Apr 2017 19:46:38 -0400
Received: from mail-yw0-x22b.google.com ([2607:f8b0:4002:c05::22b]:34722)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4yXy-0005Bq-QJ
	for groff@gnu.org; Sun, 30 Apr 2017 19:46:34 -0400
Received: by mail-yw0-x22b.google.com with SMTP id k11so50567073ywb.1
	for <groff@gnu.org>; Sun, 30 Apr 2017 16:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=tCkSEEJ5e4t1TSv7OOZApi5k2KJI17OC41VOU0uxJGg=;
	b=cTb73amMhzIGu26DSomRs/Z+wud5tLp9Z7IgvYntFUX+hByMHCBnD8zg/8TTiusXe7
	R3nvcGaa8R/xQJxrXaRY3iaLljaDsHj4Ky5X6svNI+aERzgNerYlmfvO+LpqWrtrgbv+
	aHH7P3qyLJ60QeeTQ44JP7oIFw3qTK00xj3lHmNT7CFDiPeavGTzmPgKhGmeSa56SVhR
	F1VjXUoetUJr+BBbKNt2eN9Rgh1hYVDzW9Vdyu6i90EeJSvjCPDk3z2jTZlei+d3vCjg
	eDlrrkPFruM2o2nd82EZS0yPwP8HgEBI6Exyb7YB0F33N306Rk0DcQzm2t8+DZhFnI5r
	xDqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=tCkSEEJ5e4t1TSv7OOZApi5k2KJI17OC41VOU0uxJGg=;
	b=oA7d+hh20l7HgPxMqLczZcaneHx4wX2/kTAQXOQ5Iaeeo3CLuSLhfeBiYn9UrouV8x
	GThruFkMt2uQZDqODHacRA835ioyFyZEaLQnVZItTf6l3LwxhFj41CmBOvo81sYm12bf
	yAY1PAvYlgNbkoRDgOD7Sv97Q8kgeP+dMes8njOn9nRBflH6gQjEHd1SZtu10kZNdmGc
	2LIe8qSEj/kHHmRK8FNcHdxdHHopqiwAlIwCrhmrxmBFQz6P8tvF4qq4A1CSMEX6VkX1
	+FQ/kHvWvyqiTTWRreaUoT07cPmNf3FHqaWP/SOkMPX7aCkplSkXlz7NuTKJS7t4xcsj
	N12g==
X-Gm-Message-State: AN3rC/7TfW32P01dPfYiHaYOvJxIyWz8bFEW7Rhi/IcGGPc3WzyC+lZ8
	23u08jTBc5SlBGzT76k=
X-Received: by 10.129.181.83 with SMTP id c19mr18533913ywk.304.1493595993826; 
	Sun, 30 Apr 2017 16:46:33 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100]) by smtp.gmail.com with ESMTPSA id
	w201sm6047867ywg.6.2017.04.30.16.46.32 for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sun, 30 Apr 2017 16:46:32 -0700 (PDT)
Date: Sun, 30 Apr 2017 19:46:30 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170430234628.5f36g2ff4eukh2z7@crack.deadbeast.net>
References: <20170424162957.GC47874@athene.usta.de>
	<20170425012223.6ezbqjhijxuteped@crack.deadbeast.net>
	<20170425050427.GA37231@athene.usta.de>
	<20170425111456.gxwrcdasb2vctlej@crack.deadbeast.net>
	<20170425145219.GB74948@athene.usta.de>
	<20170425181921.kz2kB%steffen@sdaoden.eu>
	<20170426134641.kcrnxrhc7kcjzvlk@crack.deadbeast.net>
	<20170427233823.9abd1fd2752aef3089c85bf1@schemamania.org>
	<20170428051504.4vobz5wyfffju6od@crack.deadbeast.net>
	<20170430193420.7b7945e61c9b84e5b8820988@schemamania.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="qdnb5l5siimhu4qk"
Content-Disposition: inline
In-Reply-To: <20170430193420.7b7945e61c9b84e5b8820988@schemamania.org>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22b
Subject: Re: [Groff] Nesting font macros in man pages
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 23:46:39 -0000


--qdnb5l5siimhu4qk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-30T19:34:20-0400, James K. Lowden wrote:
> On Fri, 28 Apr 2017 01:15:05 -0400
> "G. Branden Robinson" <g.branden.robinson@gmail.com> wrote:
> > C adopted designated initializers, a sop to those who can't recall
> > what order a struct's fields come in.=20
>=20
> I guess you're implying that designated initializers, while verbose,
> are easier to use, even for aficionados of a terse language like C.
> As it happens, my current work is in C, and I adopted C11 as a
> baseline, partly so I could use them. =20
>=20
> With today's machines, the compiler can do more than was feasible in
> 1978.  I'd argue we have bigger structures now, too.  Designated
> initializers aren't so much a sop to the lazy as they are a gift of
> clarity, because otherwise the programmer has to count structure
> elements and supply any zeros preceding the elements to be
> initialized.  Designated initializers also support re-initialization of
> existing structures, something that otherwise required error-prone
> member-by-member assignment. =20
>=20
> All to say that at least one fan of short macro names finds explicit
> structure initialization useful. =20

Lest I be misunderstood, even on a side point, and to assuage fears in
the event I start submitting patches to, say, libgroff, I'm a big fan of
designated initializers.

I was indulging myself in a bit of snark; alas, the price I pay for that
is being sometimes misunderstood.  :-O

Regards,
Branden

--qdnb5l5siimhu4qk
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkGd00ACgkQ0Z6cfXEm
bc5UyQ//T6wxfwIo84UAr8HFSjjxGFdcpNMtQHAlRauzCmFwbLKsNTEDGzOKBCFQ
sToSdbk6eT4b/yYnTiE4b9h7nx4K/XtnqqjEVce81e/YVjf2SAFVDdlDF0R7gV/e
BcZkO5e6fbh6jzsSkTjE8YFzoFAbHkVsOMq60vniQh2vKJ6l8HoQzTNk1Gw62leN
Vb5EFlxlMQpR27w5+1/68BYVkKk8UG/EwyoB+doVRa5cTA5qRDGeOlPXtnjabIec
so5IPmRSgGll7Ow6qmeaOa6GIO5OGt6h/Can4ToisOgNW9bkIIoZihcGI7JPPUAU
N0fXQnGuhu0s+uGo7u/hdD7rAjCMcg+J6xqEnh/VGgVqDcyIRhQ3QhEagPxYcfmp
DOkBMKTytQIAES4ndXEy/N9XdZ86Is4QdsqUqd+ctBjt5e/WdXg6F3XmqScyES0B
Lffb9sHJnGdemnkmToFq/iGo7HzeaeQIg0uvt7pfDyOonVFBnVPFSVJvsDXF4swJ
f7VezJwG1O18s8KdGDYg9o1oK+EsPGN9eWIU3NiS2ZKsPYWsPaiH9MpamGrrI6KM
itQJP1rc9ugfb8gLuJKe61orel2iC6TLBD4y5OzvHWoNFamJvMcBpSpTJuLqlgqb
wVOwwcUcSWRoE3XXYZdGfJmn85ipsy8O67v9IwVlWXKP6g1NtBo=
=aQeP
-----END PGP SIGNATURE-----

--qdnb5l5siimhu4qk--


From MAILER-DAEMON Sun Apr 30 19:51:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4ycs-0004Ji-3E
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 19:51:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37447)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4ycq-0004Jb-CH
	for groff@gnu.org; Sun, 30 Apr 2017 19:51:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4ycl-0006Sp-Ho
	for groff@gnu.org; Sun, 30 Apr 2017 19:51:36 -0400
Received: from mail-yw0-x22f.google.com ([2607:f8b0:4002:c05::22f]:36183)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4ycl-0006Sk-D9
	for groff@gnu.org; Sun, 30 Apr 2017 19:51:31 -0400
Received: by mail-yw0-x22f.google.com with SMTP id l18so50724396ywh.3
	for <groff@gnu.org>; Sun, 30 Apr 2017 16:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:references:mime-version
	:content-disposition:in-reply-to:user-agent;
	bh=sZIJ5E8Uz3nsPn7fe3YuMF9x2wWlXYMoVZWO2ecHh2o=;
	b=CXLpCWBVGcIHzRRhkHxqH58aAePMpNr+ynFB6oKg0EUgR1aJMivz02ZZ6aClId8EH8
	QShnaGxWAL/wCum5yIMJdUwBckcsUdF5SZhHdcum48yLjWPdOg21qhPYHQ64NSUiAcVY
	Hdf1WJOgTYtSa93cIevuHN9x4N5HDmduOAbNj/KnXfAO1C4zw5GVYvUCfna3cvPZVyVO
	9w9y5RSoKx+F3HxTgYCYmWwDJ9wyORWqeeJhOuOuU/LoplMxCKb00LPDnCRXkEuaupIN
	KYQwRHMNMmVYXBNyVvpp0pLsLRK8OrSMAhfSFYh0uHFw7ZpFdkfa7Jj3xkOKI28lI74j
	T8SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=sZIJ5E8Uz3nsPn7fe3YuMF9x2wWlXYMoVZWO2ecHh2o=;
	b=GgMhPJYr8o/uzmZZyQ3viYkfuoNySHyZrTWGI7Q7e5f407pT+T4u/tRMlMCdDxj4oC
	qKh4jJw+LGdzz9zhYT1/rT7XkmEjZ1Pazdo1BLKycXd+PVPqmLZSWVJONsaVFdOy5ED0
	pBeTqNVi2W5YoxTy8D2AKcwtvHTP8gNJZvLE/ncHavRbHWAf3SbaRicKA0E0VRGFDx/h
	EFS1wK+iZy5qSQSY0nGVtQIfMd5oIFpnewFReBvNYqNvT0fvdPOkEdsjFQqWSMhdJna+
	tkmda9F/rc9f0nIegoAFsODeMInyjQGi4xywuyKnH2719zYScIIzVCbiJ78g6a5hRegN
	2gPA==
X-Gm-Message-State: AN3rC/7ddPVy72FZZUlgsuuMApgF3p+Ta2Y7IbTBoxb+/lBUsm9DQVho
	h9rnbCw02VZLbzW63lU=
X-Received: by 10.129.169.8 with SMTP id g8mr20595550ywh.56.1493596290311;
	Sun, 30 Apr 2017 16:51:30 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id k1sm5625994ywi.34.2017.04.30.16.51.28
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sun, 30 Apr 2017 16:51:29 -0700 (PDT)
Date: Sun, 30 Apr 2017 19:51:26 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170430235124.5nk33cmexj6i6lnl@crack.deadbeast.net>
References: <201704252300.v3PN0QCi009878@coolidge.cs.Dartmouth.EDU>
	<20170426124342.3mjnds74yvuu2pcj@crack.deadbeast.net>
	<20170426235742.7bp5elajil34itiw@crack.deadbeast.net>
	<20170430161130.3CAA51FACE@orac.inputplus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="nyycy7jlnkz52i2h"
Content-Disposition: inline
In-Reply-To: <20170430161130.3CAA51FACE@orac.inputplus.co.uk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22f
Subject: Re: [Groff] Applications of \c in man pages in the wild [LONG]
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Apr 2017 23:51:37 -0000


--nyycy7jlnkz52i2h
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

At 2017-04-30T17:11:30+0100, Ralph Corderoy wrote:
> Hi Branden,
>=20
> > The remaining man pages categorize as follows:
> >
> > mandb(1)                        FONT_MACRO_C
> > nmcli(1)                        DOCBOOK_C
> > passwd(1)                       DOCBOOK_C
> ...
>=20
> Have you a summary combining your two survey-result sets?

I do not.  Of what value would it be?  If it's worth measuring this sort
of thing more than once, the analysis should be scripted.  Unfortunately
some of these categories are going to be hard to recognize without a
standalone *roff parser, which I don't think exists.

> For this email, it's
>=20
>     $ sed '/^mandb/,/^$/! d' `mhpath .` |
>     > tr -s ' ,\010' \\012 |
>     > grep -v '[[:lower:]]' |
>     > sort | uniq -c
>           1 COMMENT_C
>          58 DOCBOOK_C
>          17 FONT_MACRO_C
>           4 PRIVATE_FONT_MACRO_C
>           1 SMALL_C
>           1 SPURIOUS_C_1
>           3 SPURIOUS_C_2
>           2 SPURIOUS_C_3
>           1 SPURIOUS_C_4
>           1 SPURIOUS_C_5
>          10 TILDE_C

Nicely done!

Regards,
Branden

--nyycy7jlnkz52i2h
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkGeHwACgkQ0Z6cfXEm
bc705BAAjqRBKITpqRlv3JgcVEF0ETbPOaMh3UIlpItoaBGUFJoraMCJTnJLcQyl
Un3x5deteNZTaAYoHRCnii7p6MoibImpxo0SuLMu6lFdrQiL4ygo0V+SLeJOnMSn
vLtHrzdYfPrbv7P6HqQ0Yjcj/SttDiZDDumgbiwc3F+G0xDtiviZ/GxAnPA8XZ9Z
p3vGsBOlJbcILgqIJgjmznNvgN+moPKThls1B54xB8uVsoQ1+SCzLEzgl/yniZbZ
6Urebut1UsA3QthTZHASdFr9gVRW0OWw//ZtDU/w+3//6TLmO7/JxmS+ShCSLre6
jBuxk9W0RP9qiDyh1BGF1TakEOaRaXjOELHNUaA8y1MObbxMNicn/frpDJDb+6gy
2/wDNOQfWIwH0cdrX5SKLh2duKx73hGhyP1n1Ps6jJLaV/g29v4HEA4X9TDccYQN
95LD81hh7X8/OrlRXKZkePUT5g8+kblNvKAwiuGhgi942cb418DWq89exhl+olHh
YQ1EaXvXS2i+nuZD8ZpSBz3w1zY7dpeC+XdVzKyDn4TIr70zqoWG7+h9vYpw7/MY
tOCCPHLn/qulR3vOpKU6wJ9X/M7fjPHLw3tC8u1bZiO9nF2VFDDLt91oO3xxFpW0
kUoD1227+CXyzLPqA/qLUDVJjnvsmdFkfnPoEvG82S9Ub4zyHJ4=
=p2jz
-----END PGP SIGNATURE-----

--nyycy7jlnkz52i2h--


From MAILER-DAEMON Sun Apr 30 20:37:43 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1d4zLS-0007pW-Vd
	for mharc-groff@gnu.org; Sun, 30 Apr 2017 20:37:42 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42887)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4zLH-0007p0-TV
	for groff@gnu.org; Sun, 30 Apr 2017 20:37:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <g.branden.robinson@gmail.com>) id 1d4zL9-0006ZP-54
	for groff@gnu.org; Sun, 30 Apr 2017 20:37:31 -0400
Received: from mail-yw0-x22a.google.com ([2607:f8b0:4002:c05::22a]:36086)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <g.branden.robinson@gmail.com>)
	id 1d4zL8-0006ZJ-OL
	for groff@gnu.org; Sun, 30 Apr 2017 20:37:23 -0400
Received: by mail-yw0-x22a.google.com with SMTP id l18so50955804ywh.3
	for <groff@gnu.org>; Sun, 30 Apr 2017 17:37:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mime-version:content-disposition
	:user-agent; bh=RQcAuzZo2FueWtOdmJBVuvJ8BUAC4B3pLJZdElUQWTI=;
	b=bx+SsBkNSPfMsJ4N5C2q/yQ66CmmKdjb5hWwJ7Q4C2Bgv0OcJnQHpm22AW5jeaPlOc
	avtQAhzl2ZuwLB4WsBHHNugwTLmHaIMJAsDaZcnumTtI0Ty4y1UwShHJ58u4006YyZ86
	PVbaKGPJ6wC3Ip8muBb41S/1iV2ylN3XczqcIXDLnMha+jZX2S2GB6tybRys/1PNInn+
	qr7mF30mmEaL6e2YjH9dHYcuXlnWcPp8+YfAPTj1qhLeRGI72wkeLrDTpVf3WHwphEQ2
	ZoHm1+EJKDTd7ncw8T62pXSbT7+qpTgGMTNxdn/BzN0ssGAXp6x47cCg3JS1Hn+Yi2GT
	jv8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-disposition:user-agent;
	bh=RQcAuzZo2FueWtOdmJBVuvJ8BUAC4B3pLJZdElUQWTI=;
	b=D5WzfNFBy36k+pukAGVQHsKhfz/gq4E6VCftHDRbiy/qDK0Wri7YcRXnWSyeIeue0+
	GuU87jGEl9+7Depr+0tv4dSivLJReTR269Xm5gyEhBGBF8+bcfUI3IX2Uho1qb1gp47+
	TOwTLuZOVK0fHD+mLIap1/wKkND/ECxRAvkuApYSUAVGP5CXS4U55M1atqCbQADay5WV
	JqAmle1o077l3OxOHlnVLJL/SHNIFOo8oe4VxXN3LgWs4zgv1VSBwM3ek6rnVlY4rw2n
	JrR+R9cYkjGJdXbbcQu5Ttth6jtsN6fi2t8H379yzWyQ7ibTGEntu8sfA6xiAEpXmmZR
	rohw==
X-Gm-Message-State: AN3rC/7ZVNaUnqxikwbdmYrVES14l9fQOPRhv14eP+Y0cndA4iOSN/dX
	BO+F7uZ+BiN74Oh3lbw=
X-Received: by 10.129.70.2 with SMTP id t2mr18087168ywa.275.1493599041739;
	Sun, 30 Apr 2017 17:37:21 -0700 (PDT)
Received: from crack.deadbeast.net (rrcs-24-171-184-100.midsouth.biz.rr.com.
	[24.171.184.100])
	by smtp.gmail.com with ESMTPSA id 202sm2491334yww.4.2017.04.30.17.37.19
	for <groff@gnu.org>
	(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
	Sun, 30 Apr 2017 17:37:20 -0700 (PDT)
Date: Sun, 30 Apr 2017 20:37:17 -0400
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Message-ID: <20170501003715.uos37z4xrxfiy5az@crack.deadbeast.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="35hydig57bfxplve"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:4002:c05::22a
Subject: [Groff] [PATCH] dogfooding the deprecation of \(aq in prose
X-BeenThere: groff@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <groff.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/groff>,
	<mailto:groff-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/groff/>
List-Post: <mailto:groff@gnu.org>
List-Help: <mailto:groff-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/groff>,
	<mailto:groff-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 00:37:40 -0000


--35hydig57bfxplve
Content-Type: multipart/mixed; boundary="q2ox7oclsifbafhj"
Content-Disposition: inline


--q2ox7oclsifbafhj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi folks,

In light of the recent discussion about the aq ("apostrophe quote")
character escape, please review the attached patch.

Please find attached a patch to set a better example for ourselves and
our readers.

N.B. that I did not do blind substitutions; uses of the escape outside
of prose contexts, I left alone, namely:

./contrib/gpinyin/gpinyin.1.man:.B \e[\[aq]u] or
./contrib/gpinyin/gpinyin.1.man:.BR \e[\[aq]U] ,
./contrib/hdtbl/groff_hdtbl.7.man:.CR width=\[aq]1.5i 10%\[aq]
./contrib/hdtbl/groff_hdtbl.7.man:.CRI key=\[aq] "value1 \[lB]value2 \[lB]\[ell]\[rB]\[rB]" \[aq]
./contrib/hdtbl/groff_hdtbl.7.man:.XAA "fsz=\[aq]" "d1 \[lB]d2\[rB]" \[aq]
./contrib/hdtbl/groff_hdtbl.7.man:.XAA "width=\[aq]" "w1 \[lB]w2 \[lB]\[ell]\[rB]\[rB]" \[aq]
./contrib/hdtbl/groff_hdtbl.7.man:.XDEFS "fsz=\[aq]1.0 1.0\[aq]" t*fsz
./contrib/mom/groff_mom.7.man:.B .IB \[rs]w\[aq]margarine\[aq] \[rs]w\[aq]jello\[aq]
./man/groff.7.man:.B \(aq
./man/groff.7.man:.BI !\[aq] s1 \[aq] s2 \[aq]
./man/groff.7.man:.BI \[aq] s1 \[aq] s2 \[aq]
./man/groff.7.man:.dquoted_char \[aq] ,
./man/groff.7.man:.dquoted_char \[aq] ,
./man/groff.7.man:.dquoted_char \[aq] .
./man/groff.7.man:.dquoted_char \[aq] ;
./man/groff.7.man:\&. el \[rs]\[rs]$1\[rs]Z\[aq]\[rs]\[rs]$2\[aq]\[rs]v\[aq].25m\[aq]\
./man/groff.7.man:\&.el \[rs]*(u1\[rs]Z\[aq]\[rs]*(u2\[aq]\[rs]v\[aq].25m'\[rs]D\[aq]l \
./man/groff.7.man:\&.el \[rs]*[u1]\[rs]Z\[aq]\[rs]*[u2]\[aq]\[rs]v\[aq].25m\[aq]\[rs]D\
./man/groff.7.man:\&\f[CB]\[aq]\f[]
./man/groff.7.man:\[aq]\\[rs]\[rs]$3
./man/groff.7.man:\[aq]l \[rs]w\[aq]\[rs]*[u2]\[aq]u 0\[aq]\[rs]v\[aq]-.25m\[aq]\[rs]*[u3]
./man/groff.7.man:\[rs]D\[aq]l \[rs]w\[aq]\[rs]\[rs]$2\[aq]u 0\[aq]\[rs]v\[aq]-.25m\
./man/groff.7.man:\[rs]w\[aq]\[rs]*(u2\[aq]u 0\[aq]\[rs]v\[aq]-.25m\[aq]\[rs]*(u3
./man/groff_char.7.man:.ds aq \(aq
./man/groff_char.7.man:.if !\n(.g .if '\(aq'' .ds aq \'
./man/groff_char.7.man:\[aq]    \e[aq]  quotesingle     u0027   apostrophe quote (ASCII 39)
./src/preproc/eqn/eqn.1.man:.B \[aq]
./tmac/groff_ms.7.man:You can replace the quote (\[aq]) marks with any character not
./tmac/groff_trace.7.man:> \[aq] | groff > /dev/null
./tmac/groff_trace.7.man:> \[aq] | groff \-m trace > /dev/null
./tmac/groff_trace.7.man:> \[aq] | groff \-m trace > /dev/null
./tmac/groff_trace.7.man:\fIsh#\fP echo \[aq].
./tmac/groff_trace.7.man:\fIsh#\fP echo \[aq].
./tmac/groff_trace.7.man:\fIsh#\fP echo \[aq].

Regards,
Branden

--q2ox7oclsifbafhj
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="dogfooding-no-aq-in-prose.diff"

diff --git a/contrib/groff_filenames/groff_filenames.5.man b/contrib/groff_filenames/groff_filenames.5.man
index 0a69c951..126ee965 100644
--- a/contrib/groff_filenames/groff_filenames.5.man
+++ b/contrib/groff_filenames/groff_filenames.5.man
@@ -637,7 +637,7 @@ or in graphical mode (PDF) by
 .
 .P
 .UR https://\:github.com/\:n-t-roff/\:heirloom-doctools
-.I Gunnar Ritter\(aqs Heirloom roff project
+.I Gunnar Ritter's Heirloom roff project
 .UE .
 .
 You can get this package with the shell command:
diff --git a/contrib/hdtbl/groff_hdtbl.7.man b/contrib/hdtbl/groff_hdtbl.7.man
index 3adf1a2c..1798a514 100644
--- a/contrib/hdtbl/groff_hdtbl.7.man
+++ b/contrib/hdtbl/groff_hdtbl.7.man
@@ -195,7 +195,7 @@ An advantage of
 .B hdtbl
 is that the tables are constructed without calling a preprocessor; this
 means that
-.BR groff \[aq]s
+.BR groff 's
 full macro capabilities are available.
 .
 On the other hand, table processing with
@@ -328,7 +328,7 @@ Equivalent to the above is the following notation.
 By default, the formatted table is inserted into the surrounding text
 at the place of its definition.
 .
-If the vertical space isn\[aq]t sufficient, it is placed at the top of
+If the vertical space isn't sufficient, it is placed at the top of
 the next page.
 .
 Tables can also be stored for later insertion.
diff --git a/contrib/mm/groff_mm.7.man b/contrib/mm/groff_mm.7.man
index 3aa0d827..efe6e741 100644
--- a/contrib/mm/groff_mm.7.man
+++ b/contrib/mm/groff_mm.7.man
@@ -222,11 +222,11 @@ respectively.
 .
 Internally, font positions are used for backwards compatibility.
 .
-From a practical point of view it doesn\[aq]t make a big difference
+From a practical point of view it doesn't make a big difference
 \[en] a different font family can still be selected with a call to the
 .B .fam
 request or using
-.BR groff \[aq]s
+.BR groff 's
 .B \-f
 command line option.
 .
@@ -281,7 +281,7 @@ Abstract end, see
 .
 .TP
 .BI AF\ \fR[\fP name-of-firm \fR]\fP
-Author\[aq]s firm, should be called before
+Author's firm, should be called before
 .BR AU ,
 see also
 .BR COVER .
@@ -406,7 +406,7 @@ Sets the text above the abstract text.
 .
 .TP
 .BI AT\  "title1 \fR[\fPtitle2 \fR[.\|.\|.]]\fP"
-Author\[aq]s title.
+Author's title.
 .
 .B AT
 must appear just after each
@@ -1206,11 +1206,11 @@ is added to the header in the text but not in the table of contents.
 .
 This is normally used for footnote marks and similar things.
 .
-Don\[aq]t use
+Don't use
 .B \[rs]*F
 in
 .IR heading-suffix ,
-it doesn\[aq]t work.
+it doesn't work.
 .
 A manual label must be used, see
 .BR FS .
@@ -1623,7 +1623,7 @@ all are concatenated.
 .
 .TP
 .BI IA\  "\fR[\fPaddressee-name \fR[\fPtitle\fR]]\fP"
-Begin specification of the addressee and addressee\[aq]s address in
+Begin specification of the addressee and addressee's address in
 letter style.
 .
 Several names can be specified with empty
@@ -2007,7 +2007,7 @@ l lx.
 Arg@Style
 BL@T{
 Blocked.
-Date line, return address, writer\[aq]s address and closing
+Date line, return address, writer's address and closing
 begins at the center of the line.
 .
 All other lines begin at the left margin.
@@ -2024,7 +2024,7 @@ T}
 SP@T{
 Simplified.
 Almost the same as the full-blocked style.
-Subject and the writer\[aq]s identification are printed in all-capital.
+Subject and the writer's identification are printed in all-capital.
 T}
 .TE
 .RE
@@ -2141,8 +2141,8 @@ tab(@);
 l l.
 0@Normal memorandum, no type printed.
 1@Memorandum with \[oq]MEMORANDUM FOR FILE\[cq] printed.
-2@Memorandum with \[oq]PROGRAMMER\[aq]S NOTES\[cq] printed.
-3@Memorandum with \[oq]ENGINEER\[aq]S NOTES\[cq] printed.
+2@Memorandum with \[oq]PROGRAMMER'S NOTES\[cq] printed.
+3@Memorandum with \[oq]ENGINEER'S NOTES\[cq] printed.
 4@Released paper style.
 5@External letter style.
 .TE
@@ -2210,7 +2210,7 @@ See
 .B NCOL
 Force printing to the next column.
 .
-Don\[aq]t use this together with the
+Don't use this together with the
 .B MUL*
 macros, see
 .BR 2C .
@@ -2224,7 +2224,7 @@ The argument selects between the predefined type of notations.
 If the second argument is available,
 then the argument becomes the entire notation.
 .
-If the argument doesn\[aq]t select a predefined type,
+If the argument doesn't select a predefined type,
 it is printed as \[oq]Copy (\fIarg\/\fP) to\[cq].
 .
 It is possible to add more standard notations,
@@ -2330,7 +2330,7 @@ Using 0 and\~1 is the same as adding that value to
 .BR P .
 .
 A value of\~2 indents all paragraphs, except after headings, lists,
-and displays (this value can\[aq]t be used as an argument to
+and displays (this value can't be used as an argument to
 .B P
 itself).
 .
@@ -2359,7 +2359,7 @@ A line break is done unless the fourth argument is given.
 This can be used to avoid the page number on the first page
 while setting new width and length.
 .
-(It seems as if this macro sometimes doesn\[aq]t work too well.
+(It seems as if this macro sometimes doesn't work too well.
 .
 Use the command line arguments to change
 line length, page length, and page offset instead.)
@@ -2880,7 +2880,7 @@ ends the header of the table.
 .
 This header is printed again if a page break occurs.
 .
-Argument \[oq]N\[cq] isn\[aq]t implemented yet.
+Argument \[oq]N\[cq] isn't implemented yet.
 .
 .TP
 .BI TL\  "\fR[\fPcharging-case-number \fR[\fPfiling-case-number\fR]]\fP"
@@ -3070,7 +3070,7 @@ and setting top and/or bottom margin to less than the default.
 .
 .TP
 .BI WA\  "\fR[\fPwriter-name \fR[\fPtitle\fR]]\fP"
-Begin specification of the writer and writer\[aq]s address.
+Begin specification of the writer and writer's address.
 .
 Several names can be specified with empty
 .BR WA / WE
@@ -3265,7 +3265,7 @@ is an array containing the different strings used in
 It is really a number of string variables prefixed with
 .BR Letns! .
 .
-If the argument doesn\[aq]t exist, it is included between
+If the argument doesn't exist, it is included between
 .B ()
 with
 .B Letns!copy
diff --git a/contrib/mm/mmroff.1.man b/contrib/mm/mmroff.1.man
index 1de1ba9e..4e4256cb 100644
--- a/contrib/mm/mmroff.1.man
+++ b/contrib/mm/mmroff.1.man
@@ -69,7 +69,7 @@ when the cross reference file is up to date.
 .B \-x
 Just create the cross reference file.
 .
-This can be used to refresh the cross reference file, it isn\(aqt
+This can be used to refresh the cross reference file, it isn't
 always needed to have accurate cross references and by using this
 option
 .B groff
diff --git a/contrib/mom/groff_mom.7.man b/contrib/mom/groff_mom.7.man
index 05b7a261..881559a1 100644
--- a/contrib/mom/groff_mom.7.man
+++ b/contrib/mom/groff_mom.7.man
@@ -132,8 +132,8 @@ output.
 provides two categories of macros: macros for typesetting, and
 macros for document processing.
 .
-The typesetting macros provide access to groff\[aq]s typesetting
-capabilities in ways that are simpler to master than groff\[aq]s
+The typesetting macros provide access to groff's typesetting
+capabilities in ways that are simpler to master than groff's
 primitives.
 .
 The document processing macros provide highly customizable markup
@@ -160,7 +160,7 @@ viewers, and may contain clickable internal and external links.
 When
 .RI \-T ps
 is absent,
-.B groff\[aq]s
+.B groff's
 native
 .I PDF
 driver,
@@ -172,7 +172,7 @@ When given, the output is still
 but processing is passed over to
 .BR pdfroff ,
 which uses
-.B groff\[aq]s
+.B groff's
 PostScript driver,
 .BR grops \&.
 Not all
@@ -700,7 +700,7 @@ Once
 is invoked, it remains in effect until turned off.
 .
 .P
-Note: If you\[aq]re using the document processing macros with
+Note: If you're using the document processing macros with
 .BR "\%.PRINTSTYLE \%TYPEWRITE" ,
 .B mom
 ignores
@@ -768,7 +768,7 @@ must be turned off before changing the condense percentage with
 .BR \%.CONDENSE .
 .
 .P
-Note: If you\[aq]re using the document processing macros with
+Note: If you're using the document processing macros with
 .BR "\%.PRINTSTYLE \%TYPEWRITE" ,
 .B mom
 ignores
@@ -948,7 +948,7 @@ embedded in text lines, like this:
 .P
 Alternatively, if you wanted the whole line
 .IR pseudo-italicized ,
-you\[aq]d do
+you'd do
 .RS
 .EX
 .FONT B \[rs]*[SLANT] R "Not everything is as it seems." B \[rs]*[SLANTX]
@@ -961,7 +961,7 @@ Once
 is invoked, it remains in effect until turned off.
 .
 .P
-Note: If you\[aq]re using the document processing macros with
+Note: If you're using the document processing macros with
 .BR "\%.PRINTSTYLE \%TYPEWRITE" ,
 .B mom
 underlines pseudo-italics by default.
@@ -1139,7 +1139,7 @@ you should do:
 .B .TAB 1
 .B .PT_SIZE 24
 .B .ALD 3p
-.B \[rs]*[RULE] \[rs]" Note that you can\[aq]t use \[rs]*[UP] or \[rs]*[DOWN] with \[rs]*[RULE]\""
+.B \[rs]*[RULE] \[rs]" Note that you can't use \[rs]*[UP] or \[rs]*[DOWN] with \[rs]*[RULE]\""
 .B .RLD 3p
 .B .TQ
 .EE
@@ -1209,7 +1209,7 @@ Requires a unit of measure
 .P
 .B .B_MARGIN
 sets a nominal position at the bottom of the page beyond which you
-don\[aq]t want your type to go.
+don't want your type to go.
 .
 When the bottom margin is reached,
 .B mom
@@ -1227,7 +1227,7 @@ To set a nominal bottom margin of 3/4 inch, enter
 .RE
 .
 .P
-Obviously, if you haven\[aq]t spaced the type on your pages so that the
+Obviously, if you haven't spaced the type on your pages so that the
 last lines fall perfectly at the bottom margin, the margin will vary
 from page to page.
 .
@@ -1239,14 +1239,14 @@ Occasionally, owing to a peculiarity in
 .IR groff ,
 an extra line will fall below the nominal bottom margin.
 .
-If you\[aq]re using the document processing macros, this is unlikely to
+If you're using the document processing macros, this is unlikely to
 happen; the document processing macros are very hard-nosed about
 aligning bottom margins.
 .
 .P
 Note: The meaning of
 .B .B_MARGIN
-is slightly different when you\[aq]re using the document processing
+is slightly different when you're using the document processing
 macros.
 .
 .RE
@@ -1274,7 +1274,7 @@ by default, uses the
 in order to continue processing your file.
 .
 .P
-If you\[aq]d prefer another
+If you'd prefer another
 .IR "fallback font" ,
 pass
 .B \%.FALLBACK_FONT
@@ -1282,9 +1282,9 @@ the full
 .I family+font name
 of the
 .I font
-you\[aq]d like.
+you'd like.
 .
-For example, if you\[aq]d rather the
+For example, if you'd rather the
 .I fallback font
 were
 .BR "Times Roman Medium Roman" ,
@@ -1301,7 +1301,7 @@ issues a warning whenever a
 .I font style set
 with
 .B .FT
-does not exist, either because you haven\[aq]t registered the style
+does not exist, either because you haven't registered the style
 or because the
 .I font style
 does not exist in the current
@@ -1314,7 +1314,7 @@ By default,
 then aborts, which allows you to correct the problem.
 .
 .P
-If you\[aq]d prefer that
+If you'd prefer that
 .B \%mom
 not abort on non-existent
 .IR fonts ,
@@ -1519,11 +1519,11 @@ will set all subsequent type in the fallback font (by default,
 .BR Roman )
 until she encounters a
 .B .FT
-request that\[aq]s valid for the
+request that's valid for the
 .IR family .
 .
 .P
-For example, assuming you don\[aq]t have the font
+For example, assuming you don't have the font
 .B Medium Condensed Roman
 .RB  ( mom
 extension
@@ -1546,7 +1546,7 @@ In the above example, you must follow
 .B .FAMILY H
 with a
 .B .FT
-request that\[aq]s valid for
+request that's valid for
 .BR Helvetica .
 .
 .P
@@ -1557,7 +1557,7 @@ for information on adding fonts and families to groff, as well as to
 see a list of the extensions
 .B mom
 provides to
-.IR groff \[aq]s
+.IR groff 's
 basic
 .BR R ,
 .BR I ,
@@ -1665,7 +1665,7 @@ If your
 .I family
 were
 .BR \%Palatino ,
-you\[aq]d get the
+you'd get the
 .I \%Palatino bold
 .IR font .
 .
@@ -1699,13 +1699,13 @@ How
 .B mom
 reacts to an invalid argument to
 .B .FT
-depends on which version of groff you\[aq]re using.
+depends on which version of groff you're using.
 .
 If your
 .I groff version
 is greater than or equal to 1.19.2,
 .B mom
-will issue a warning and, depending on how you\[aq]ve set up the fallback
+will issue a warning and, depending on how you've set up the fallback
 font, either continue processing using the fallback font, or abort
 (allowing you to correct the problem).  If your
 .I groff version
@@ -1832,7 +1832,7 @@ intervening control lines).
 .
 And because
 .I hanging indents
-affect only one line, there\[aq]s no need to turn them off.
+affect only one line, there's no need to turn them off.
 .
 .P
 .I IMPORTANT:
@@ -1876,13 +1876,13 @@ only.
 .B ".HI \[rs]w'\[rs]0\[rs]0.'"
 \fB1.\[rs]0The most important point to be considered is whether the
 answer to the meaning of Life, the Universe, and Everything
-really is 42.  We have no-one\[aq]s word on the subject except
-Mr. Adams\[aq].
+really is 42.  We have no-one's word on the subject except
+Mr. Adams'.
 .B .HI
 2.\[rs]0If the answer to the meaning of Life, the Universe,
 and Everything is indeed 42, what impact does this have on
 the politics of representation?  42 is, after all not a
-prime number.  Are we to infer that prime numbers don\[aq]t
+prime number.  Are we to infer that prime numbers don't
 deserve equal rights and equal access in the universe?
 .B .HI
 3.\[rs]0If 42 is deemed non-exclusionary, how do we present it
@@ -1911,7 +1911,7 @@ starts at exactly the same spot as the indented lines that follow.
 .P
 Notice that subsequent invocations of
 .B .HI
-don\[aq]t require a
+don't require a
 .I measure
 to be given.
 .
@@ -1965,7 +1965,7 @@ and
 instead of
 .BR .IB .
 .
-You\[aq]ll save yourself a lot of grief.
+You'll save yourself a lot of grief.
 .
 .P
 A
@@ -2028,7 +2028,7 @@ Indent left \[em] the optional argument requires a unit of measure
 .
 .P
 .B .IL
-indents text from the left margin of the page, or if you\[aq]re in a
+indents text from the left margin of the page, or if you're in a
 .IR tab ,
 from the left edge of the
 .IR tab
@@ -2147,7 +2147,7 @@ a measure again.
 .
 .P
 .BR ".IQ CLEAR" ,
-as you\[aq]d suspect, quits and clears the values for all indent
+as you'd suspect, quits and clears the values for all indent
 styles at once.
 .
 .RE
@@ -2166,7 +2166,7 @@ Indent right \[em] the optional argument requires a unit of measure
 .B .IR
 indents text from the
 .I right margin
-of the page, or if you\[aq]re in a
+of the page, or if you're in a
 .IR tab ,
 from the end of the
 .IR tab .
@@ -2243,14 +2243,14 @@ It may be used any time, and remains in effect until you enter a new value.
 .P
 Left indents and tabs are calculated from the value you pass to
 .BR .L_MARGIN ,
-hence it\[aq]s always a good idea to invoke it before starting any serious
+hence it's always a good idea to invoke it before starting any serious
 typesetting.
 .
 A unit of measure is required.
 .
 Decimal fractions are allowed.
 .
-Therefore, to set the left margin at 3 picas (1/2 inch), you\[aq]d enter either
+Therefore, to set the left margin at 3 picas (1/2 inch), you'd enter either
 .RS
 .EX
 .B .L_MARGIN 3P
@@ -2281,7 +2281,7 @@ to
 .P
 Note:
 .B .L_MARGIN
-behaves in a special way when you\[aq]re using the document processing
+behaves in a special way when you're using the document processing
 macros.
 .
 .RE
@@ -2327,7 +2327,7 @@ macro in the document processing macros.
 .\" ======================================================================
 .TP
 .B \%.MCR
-Once you\[aq]ve turned
+Once you've turned
 .I multi-columns
 on (with
 .BR \%.MCO ),
@@ -2379,7 +2379,7 @@ the distance specified by the argument.
 The argument requires a unit of measure; therefore, to advance an
 extra 6 points below where
 .B \%.MCX
-would normally place you, you\[aq]d enter
+would normally place you, you'd enter
 .RS
 .EX
 .B .MCX 6p
@@ -2447,16 +2447,16 @@ All arguments require a unit of measure
 .
 .P
 .I IMPORTANT:
-If you\[aq]re using the document processing macros,
+If you're using the document processing macros,
 .B .PAGE
 must come after
 .BR .START .
 .
 Otherwise, it should go at the top of a document, prior to any text.
 .
-And remember, when you\[aq]re using the document processing macros, top
+And remember, when you're using the document processing macros, top
 margin and bottom margin mean something slightly different than when
-you\[aq]re using just the typesetting macros (see Top and bottom margins
+you're using just the typesetting macros (see Top and bottom margins
 in document processing).
 .
 .P
@@ -2467,7 +2467,7 @@ macro.
 The only required argument is page width.
 .
 The rest are
-optional, but they must appear in order and you can\[aq]t skip over
+optional, but they must appear in order and you can't skip over
 any.
 .
 .IR <lm> ,
@@ -2478,7 +2478,7 @@ and
 refer to the left, right, top and bottom margins respectively.
 .
 .P
-Assuming your page dimensions are 11 inches by 17 inches, and that\[aq]s
+Assuming your page dimensions are 11 inches by 17 inches, and that's
 all you want to set, enter
 .RS
 .EX
@@ -2501,7 +2501,7 @@ Now suppose you also want to set the top margin, say, at 1\(en1/2 inches.
 .I <tm>
 comes after
 .I <rm>
-in the optional arguments, but you can\[aq]t skip over any arguments,
+in the optional arguments, but you can't skip over any arguments,
 therefore to set the top margin, you must also give a right margin.
 .
 The
@@ -2547,7 +2547,7 @@ To compensate, do
 .B .RLD 1v
 .EE
 .RE
-immediately before entering any text, or, if it\[aq]s feasible, make
+immediately before entering any text, or, if it's feasible, make
 .B .PAGE
 the last macro you invoke prior to entering text.
 .
@@ -2686,7 +2686,7 @@ of something,
 .B \%.PT_SIZE
 does not require that you supply a
 .I unit of measure
-since it\[aq]s a near universal convention that
+since it's a near universal convention that
 .I type size
 is measured in
 .IR points .
@@ -2755,18 +2755,18 @@ can also be changed inline.
 It is unfortunate that the
 .B \%pic
 preprocessor has already taken the name, PS, and thus
-.IR mom \[aq]s
+.IR mom 's
 macro for setting
 .I point sizes
-can\[aq]t use it.
+can't use it.
 .
-However, if you aren\[aq]t using
+However, if you aren't using
 .BR pic ,
 you might want to alias
 .B \%.PT_SIZE
 as
 .BR .PS ,
-since there\[aq]d be no conflict.
+since there'd be no conflict.
 .
 For example
 .RS
@@ -2803,14 +2803,14 @@ if used, must come after
 .BR .L_MARGIN ,
 and/or
 .B .PAGE
-(if a right margin isn\[aq]t given to PAGE).
+(if a right margin isn't given to PAGE).
 .
 The reason is that
 .B .R_MARGIN
 calculates line length from the overall page dimensions and the left margin.
 .
 .P
-Obviously, it can\[aq]t make the calculation if it doesn\[aq]t know the page
+Obviously, it can't make the calculation if it doesn't know the page
 width and the left margin.
 .
 .P
@@ -2838,7 +2838,7 @@ type as having a right margin.
 In others, giving a line length may make more sense.
 .
 .P
-For example, if you\[aq]re setting a page of type you know should have
+For example, if you're setting a page of type you know should have
 6-pica margins left and right, it makes sense to enter a left and
 right margin, like this:
 .RS
@@ -2849,7 +2849,7 @@ right margin, like this:
 .RE
 .
 .P
-That way, you don\[aq]t have to worry about calculating the line
+That way, you don't have to worry about calculating the line
 length.
 .
 On the other hand, if you know the line length for a patch of type
@@ -2885,7 +2885,7 @@ is, of course, overridden.
 .P
 Note:
 .B .R_MARGIN
-behaves in a special way when you\[aq]re using the document processing
+behaves in a special way when you're using the document processing
 macros.
 .
 .RE
@@ -2914,9 +2914,9 @@ In this respect,
 .B .ST
 is like
 .B \%.TAB_SET
-except that you don\[aq]t have to give
+except that you don't have to give
 .B .ST
-an indent or a line length (that\[aq]s already taken care of, inline,
+an indent or a line length (that's already taken care of, inline,
 by
 .BR \[rs]*[ST]\*[Ellipsis]\[rs]*[STX] ).
 .
@@ -3106,7 +3106,7 @@ A temporary indent is one that applies only to the first line of text
 that comes after it.
 .
 Its chief use is indenting the first line of paragraphs.
-.RB ( Mom\[aq]s
+.RB ( Mom's
 .B .PP
 macro, for example, uses a
 .IR "temporary indent" .)
@@ -3135,7 +3135,7 @@ keeps track of the last measure you gave it.
 .P
 Because
 .I temporary indents
-are temporary, there\[aq]s no need to turn them off.
+are temporary, there's no need to turn them off.
 .
 .P
 .I IMPORTANT:
@@ -3196,9 +3196,9 @@ works.
 .P
 In
 .I \%tabs
-that aren\[aq]t given the
+that aren't given the
 .B QUAD
-argument when they\[aq]re set up with
+argument when they're set up with
 .B \%.TAB_SET
 or
 .BR ST ,
@@ -3232,7 +3232,7 @@ You must put text in the input line immediately after
 .BR .TN .
 .
 Stacking of
-.BR .TN \[aq]s
+.BR .TN 's
 is not allowed.
 .
 In other words, you cannot do
@@ -3316,7 +3316,7 @@ you want your type to start.
 .
 It requires a unit of measure, and decimal fractions are allowed.
 .
-To set a top margin of 2\(12 centimetres, you\[aq]d enter
+To set a top margin of 2\(12 centimetres, you'd enter
 .RS
 .EX
 .B .T_MARGIN 2.5c
@@ -3338,7 +3338,7 @@ top of the page.
 .P
 Note:
 .B .T_MARGIN
-means something slightly different when you\[aq]re using the document
+means something slightly different when you're using the document
 processing macros.
 .
 See Top and bottom margins in document processing for an explanation.
diff --git a/contrib/pdfmark/pdfroff.1.man b/contrib/pdfmark/pdfroff.1.man
index 44dfee2c..5ba2b8f9 100644
--- a/contrib/pdfmark/pdfroff.1.man
+++ b/contrib/pdfmark/pdfroff.1.man
@@ -665,7 +665,7 @@ option is specified, on the command line.
 .
 Input and output files for
 .B pdfroff
-may be named according to any convention of the user\[aq]s choice.
+may be named according to any convention of the user's choice.
 Typically, input files may be named according to the choice of the
 principal formatting macro package, e.g.,
 .IB file .ms
@@ -818,7 +818,7 @@ may also be considered to be the definitive reference to all
 capabilities of
 .BR pdfroff ,
 with this document providing the reference to
-.BR pdfroff \[aq]s
+.BR pdfroff 's
 extended features.
 .
 .
diff --git a/contrib/pic2graph/pic2graph.1.man b/contrib/pic2graph/pic2graph.1.man
index 5b578188..9764920e 100644
--- a/contrib/pic2graph/pic2graph.1.man
+++ b/contrib/pic2graph/pic2graph.1.man
@@ -89,7 +89,7 @@ black-on-transparent graphic.
 By specifying command-line options to be passed to
 .BR \%convert (1)
 you can give it a border, force the background transparent, set the
-image\(aqs pixel density, or perform other useful transformations.
+image's pixel density, or perform other useful transformations.
 .
 .
 .P
diff --git a/man/ditroff.7.man b/man/ditroff.7.man
index 90f80e6b..a8304b7b 100644
--- a/man/ditroff.7.man
+++ b/man/ditroff.7.man
@@ -68,27 +68,27 @@ In 1979, Brian Kernighan rewrote troff to support more devices by
 creating an intermediate output format for troff that can be fed into
 postprocessor programs which actually do the printout on the device.
 .
-Kernighan\(aqs version marks what is known as
+Kernighan's version marks what is known as
 .I classical troff
 today.
 .
-In order to distinguish it from Ossanna\(aqs original mono-device
+In order to distinguish it from Ossanna's original mono-device
 version, it was called
 .I ditroff
 .RI ( d "evice " i "ndependent " troff )
-on some systems, though this naming isn\(aqt mentioned in the
+on some systems, though this naming isn't mentioned in the
 classical documentation.
 .
 .
 .P
-Today, any existing roff system is based on Kernighan\(aqs
+Today, any existing roff system is based on Kernighan's
 multi-device troff.
 .
 The distinction between
 .I troff
 and
 .I ditroff
-isn\(aqt necessary any longer, for each modern
+isn't necessary any longer, for each modern
 .I troff
 provides already the complete functionality of
 .IR ditroff .
@@ -116,7 +116,7 @@ that automatically handles postprocessing.
 .TP
 .I [CSTR\~#54]
 The 1992 revision of the
-.I Nroff/Troff User\(aqs Manual
+.I Nroff/Troff User's Manual
 by
 .I J.\& F.\& Ossanna
 and
diff --git a/man/groff.7.man b/man/groff.7.man
index ed53ca1a..08558fb2 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -433,7 +433,7 @@ but they are used exactly like requests.
 Macro packages are pre-defined sets of macros written in the groff
 language.
 .
-A user\[aq]s possibilities to create escape sequences herself is very
+A user's possibilities to create escape sequences herself is very
 limited, only special characters can be mapped.
 .
 .
@@ -523,7 +523,7 @@ In groff, the distinction between those two elements is not always
 obvious (and a full discussion is beyond the scope of this man page).
 .
 A first approximation is that glyphs have a specific size and
-colour and are taken from a specific font; they can\[aq]t be modified any
+colour and are taken from a specific font; they can't be modified any
 more \[en] characters are the input, and glyphs are the output.
 .
 As soon as an output line has been generated, it no longer contains
@@ -593,7 +593,7 @@ At the beginning of a line and in the conditional requests it is the
 non-breaking control character.
 .
 That means that it introduces a request like the dot, but with the
-additional property that this request doesn\[aq]t cause a linebreak.
+additional property that this request doesn't cause a linebreak.
 .
 By using the
 .request c2
@@ -676,7 +676,7 @@ Space characters are only functional characters.
 They separate the arguments in requests, macros, and strings, and the words
 in text lines.
 .
-They are subject to groff\[aq]s horizontal spacing calculations.
+They are subject to groff's horizontal spacing calculations.
 .
 To get a defined space width, escape sequences like
 .squoted_char "\[rs]\ "
@@ -1479,7 +1479,7 @@ or as a string of four-digit hexadecimal components with two leading
 .BR # .
 The color
 .B default
-can\[aq]t be redefined.
+can't be redefined.
 .
 .TPx
 .REQ .dei "macro"
@@ -1729,7 +1729,7 @@ to
 .
 .TPx
 .REQ .fzoom "font"
-Don\[aq]t magnify
+Don't magnify
 .IR font .
 .
 .TPx
@@ -4577,7 +4577,7 @@ pointers to further documentation.
 .TP
 .I [CSTR\~#54]
 .UR http://\:cm.bell-labs.com/\:cm/\:cs/\:cstr/\:54.ps.gz
-Nroff/\:Troff User\[aq]s Manual by Ossanna & Kernighan
+Nroff/\:Troff User's Manual by Ossanna & Kernighan
 .UE
 \[em] the bible for classical troff.
 .
diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index e38c70b9..5508eecd 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -770,7 +770,7 @@ We map it rather arbitrarily to u23AA.
 .P
 Note that not all devices contain extensible bracket pieces which can
 be piled up with \[oq]\f(CW\eb\fP\[cq] due to the restrictions of the
-escape\[aq]s piling algorithm.
+escape's piling algorithm.
 .
 A general solution to build brackets out of pieces is the following
 macro:
@@ -815,7 +815,7 @@ bracket pieces in original troff can be used for other mathematical
 symbols also, for example \[oq]lf\[cq] and \[oq]rf\[cq] which provide
 the \[oq]floor\[cq] operator.
 .
-Other devices (most notably for DVI output) don\[aq]t unify such
+Other devices (most notably for DVI output) don't unify such
 glyphs.
 .
 For this reason, the four glyphs \[oq]lf\[cq], \[oq]rf\[cq],
@@ -1233,7 +1233,7 @@ Starting with Unicode\ 3.0, the reference glyphs have been exchanged and
 described verbally also: In mathematical context, U+03D5 is the stroked
 variant and U+03C6 the curly glyph.
 .
-Unfortunately, most font vendors didn\[aq]t update their fonts to
+Unfortunately, most font vendors didn't update their fonts to
 this (incompatible) change in Unicode.
 .
 At the time of this writing (January 2006), it is not clear yet
diff --git a/man/groff_diff.7.man b/man/groff_diff.7.man
index e84d7f63..cc2a4935 100644
--- a/man/groff_diff.7.man
+++ b/man/groff_diff.7.man
@@ -81,7 +81,7 @@ text processing system, and the classical
 .I roff
 formatter of the freely available Unix\~7 of the 1970s, documented in
 the
-.I Troff User\[aq]s Manual
+.I Troff User's Manual
 by
 .I Ossanna
 and
@@ -400,7 +400,7 @@ request.
 .B \[rs]F[]
 switches back to the previous font family (note that
 .B \[rs]FP
-won\[aq]t work; it selects font family \[oq]P\[cq] instead).
+won't work; it selects font family \[oq]P\[cq] instead).
 .
 .TP
 .BI \[rs]m x
@@ -1074,8 +1074,8 @@ pairwise.
 If, for example, the left character has value 512, and the right
 character 128, no line break gets inserted.  If we use value\~6
 instead for the left character, a line break after the character
-can\[aq]t be suppressed since the right neighbour character
-doesn\[aq]t get examined.
+can't be suppressed since the right neighbour character
+doesn't get examined.
 .
 .TP
 .BI .char\  c\ string
@@ -1132,7 +1132,7 @@ request is used to give the object a hyphenation code.
 .
 .IP
 There is a special anti-recursion feature: Use of glyph within the
-glyph\[aq]s definition is handled like normal glyphs not defined with
+glyph's definition is handled like normal glyphs not defined with
 .BR char .
 .IP
 A glyph definition can be removed with the
@@ -1275,7 +1275,7 @@ request, thus the above statement is equivalent to
 .IP
 The color named
 .B default
-(which is device-specific) can\[aq]t be redefined.
+(which is device-specific) can't be redefined.
 .
 It is possible that the default color for
 .B \[rs]M
@@ -1433,7 +1433,7 @@ request; the only difference is that a glyph defined with
 hides the glyph with the same name in the current font, whereas a
 glyph defined with
 .B fchar
-is checked only if the particular glyph isn\[aq]t found in the current
+is checked only if the particular glyph isn't found in the current
 font.
 .
 This test happens before checking special fonts.
@@ -1673,7 +1673,7 @@ character as the start of a comment).
 Use the
 .B hpfcode
 request to map the encoding used in hyphenation patterns files to
-.BR groff \[aq]s
+.BR groff 's
 input encoding.
 .
 By default, everything maps to itself except letters \[oq]A\[cq] to
@@ -1755,7 +1755,7 @@ to\~\c
 .IR n :
 When the current adjustment mode is\~\c
 .B b
-don\[aq]t hyphenate the line if the line can be justified by adding no
+don't hyphenate the line if the line can be justified by adding no
 more than
 .I n
 extra space to each word space.
@@ -1871,7 +1871,7 @@ command line option.
 .
 If the file name to be included has the form
 .IB name .tmac
-and it isn\[aq]t found,
+and it isn't found,
 .B mso
 tries to include
 .BI tmac. name
@@ -1881,7 +1881,7 @@ A warning of type
 .B file
 is generated if
 .I file
-can\[aq]t be loaded, and the request is ignored.
+can't be loaded, and the request is ignored.
 .
 .TP
 .BI .nop \ anything
@@ -1951,7 +1951,7 @@ on stderr.
 Get the bounding box of a PostScript image
 .IR filename .
 .
-This file must conform to Adobe\[aq]s Document Structuring
+This file must conform to Adobe's Document Structuring
 Conventions; the command looks for a
 .B \%%%BoundingBox
 comment to extract the bounding box values.
@@ -2138,7 +2138,7 @@ Each
 can also be a range of sizes
 .IR m \(en n .
 .
-Contrary to the font file command, the list can\[aq]t extend over more
+Contrary to the font file command, the list can't extend over more
 than a single line.
 .
 .TP
@@ -2241,7 +2241,7 @@ The first character in the string has index\~0.
 .
 If
 .I n2
-is omitted, it is taken to be equal to the string\[aq]s length.
+is omitted, it is taken to be equal to the string's length.
 .
 If the index value
 .I n1
@@ -2554,7 +2554,7 @@ is read in copy mode.
 .
 .TP
 .BR \[rs]D' \*[ellipsis] '
-All drawing commands of groff\[aq]s intermediate output are accepted.
+All drawing commands of groff's intermediate output are accepted.
 .
 See subsection
 .B "Drawing Commands"
@@ -3299,7 +3299,7 @@ If there is a glyph named
 or
 .BR \[rs]^ ,
 respectively (note the leading backslash), defined in the current font file,
-use this glyph\[aq]s width instead of the default value.
+use this glyph's width instead of the default value.
 .
 .P
 It is now possible to have whitespace between the first and second dot
@@ -3312,7 +3312,7 @@ Example:
 .EX
 \&.if t \[rs]{\[rs]
 \&.  de bar
-\&.    nop Hello, I\[aq]m \[oq]bar\[cq].
+\&.    nop Hello, I'm \[oq]bar\[cq].
 \&.  .
 \&.\[rs]}
 .EE
@@ -3484,7 +3484,7 @@ changing this.
 .IP
 The corresponding
 .BI \[rs]D'f \*[ellipsis] '
-command shouldn\[aq]t be used since its argument is always rounded to an
+command shouldn't be used since its argument is always rounded to an
 integer multiple of the horizontal resolution which can lead to
 surprising results.
 .
@@ -3617,7 +3617,7 @@ Set the color components of the filling color similar to the
 commands above.
 .
 .P
-The current position isn\[aq]t changed by those colour commands
+The current position isn't changed by those colour commands
 (contrary to
 .BR Df ).
 .
@@ -3947,7 +3947,7 @@ systems, including pointers to further historical documentation.
 .TP
 .RI [ CSTR\~#54\/ ]
 The
-.I Nroff/\:Troff User\[aq]s Manual
+.I Nroff/\:Troff User's Manual
 by
 .I J.\& F.\& Ossanna
 of 1976 in the revision of
diff --git a/man/groff_font.5.man b/man/groff_font.5.man
index 58da9cdc..0b000fa9 100644
--- a/man/groff_font.5.man
+++ b/man/groff_font.5.man
@@ -126,7 +126,7 @@ but under other systems (notably cygwin) it might be set to another name.
 .BI "paperlength " n
 The physical vertical dimension of the output medium in machine units.
 .
-This isn\[aq]t used by
+This isn't used by
 .B troff
 itself but by output devices.
 .
@@ -196,7 +196,7 @@ Use
 .B papersize
 instead.
 .
-This isn\[aq]t used by
+This isn't used by
 .BR troff
 itself but by output devices.
 .
@@ -497,7 +497,7 @@ If it is exactly two characters
 it can be entered as
 .BI \[rs]( xx\fR.
 .
-Note that single-letter special characters can\[aq]t be accessed as
+Note that single-letter special characters can't be accessed as
 .BI \[rs] c\fR;
 the only exception is \[oq]\[rs]\-\[cq] which is identical to
 \[oq]\[rs][\-]\[cq].
@@ -564,7 +564,7 @@ to build sub-encoding arrays for PS fonts containing more than 256
 glyphs.
 .
 (It has also been used for
-.BR \%grohtml \[aq]s
+.BR \%grohtml 's
 entity names but for efficiency reasons this data is now compiled
 directly into
 .BR \%grohtml .)
diff --git a/man/groff_tmac.5.man b/man/groff_tmac.5.man
index e4e6408c..75687dab 100644
--- a/man/groff_tmac.5.man
+++ b/man/groff_tmac.5.man
@@ -57,7 +57,7 @@ type-setting system provides a set of macro packages suitable for
 special kinds of documents.
 .
 Each macro package stores its macros and definitions in a file called
-the package\[aq]s
+the package's
 .BR "tmac file" .
 .
 The name is deduced from
@@ -139,7 +139,7 @@ man\~pages; see
 .B andoc
 .TQ
 .B mandoc
-Use this file in case you don\[aq]t know whether the
+Use this file in case you don't know whether the
 .B man
 macros or the
 .B mdoc
@@ -280,7 +280,7 @@ specified as the first macro argument on the command line.
 .B @g@roff
 loads latin1 by default at start-up.
 .
-Note that these macro packages don\[aq]t work on EBCDIC hosts.
+Note that these macro packages don't work on EBCDIC hosts.
 .
 .
 .TP
@@ -291,7 +291,7 @@ On those platforms it is loaded automatically at start-up.
 .
 Due to different character ranges used in
 .B @g@roff
-it doesn\[aq]t work on architectures which are based on ASCII.
+it doesn't work on architectures which are based on ASCII.
 .
 .
 .P
@@ -344,7 +344,7 @@ To be used with
 .B papersize
 This macro file is already loaded at start-up by
 .B @g@troff
-so it isn\[aq]t necessary to call it explicitly.
+so it isn't necessary to call it explicitly.
 .
 It provides an interface to set the paper size on the command line with
 the option \f[B]\%\-dpaper=\f[]\,\f[I]size\f[].
@@ -426,7 +426,7 @@ preprocessor.
 .
 They center each picture.
 .
-Use it only if your macro package doesn\[aq]t provide proper
+Use it only if your macro package doesn't provide proper
 definitions for those two macros (actually, most of them already do).
 .
 .
@@ -447,7 +447,7 @@ of the same size.
 .
 This macro file is already loaded at start-up by
 .B @g@troff
-so it isn\[aq]t necessary to call it explicitly.
+so it isn't necessary to call it explicitly.
 .
 .IP
 Syntax:
@@ -473,8 +473,8 @@ If neither a
 .I width
 nor a
 .I height
-argument is specified, the image\[aq]s natural width (as given in the
-file\[aq]s bounding box) or the current line length is used as the
+argument is specified, the image's natural width (as given in the
+file's bounding box) or the current line length is used as the
 width, whatever is smaller.
 .
 The
@@ -515,8 +515,8 @@ option causes the graphic to be indented by\~\c
 For use of
 .B .PSPIC
 within a diversion it is recommended to extend it with the following
-code, assuring that the diversion\[aq]s width completely covers the
-image\[aq]s width.
+code, assuring that the diversion's width completely covers the
+image's width.
 .
 .RS
 .IP
@@ -979,7 +979,7 @@ arg1 arg2
 .
 .
 .P
-Let\[aq]s analyze each backslash in the macro definition.
+Let's analyze each backslash in the macro definition.
 .
 As the positional parameters and the number of arguments change
 with each call of the macro their leading backslash must be doubled,
@@ -1102,7 +1102,7 @@ almost-empty lines (this is, lines which have a leading dot
 and nothing else) for a better structuring.
 .
 .IP \(bu
-To increase readability, use groff\[aq]s indentation facility for
+To increase readability, use groff's indentation facility for
 requests and macro calls (arbitrary whitespace after the leading dot).
 .
 .
@@ -1185,7 +1185,7 @@ a colon separated list of these constitutes the
 The search sequence for macro files is (in that order):
 .
 .IP \(bu
-the directories specified with troff/groff\[aq]s
+the directories specified with troff/groff's
 .B \-M
 command line option
 .
diff --git a/man/roff.7.man b/man/roff.7.man
index 7840d980..ef101c91 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -163,7 +163,7 @@ roots go back to the earlier operating systems CTSS and Multics.
 .SS "The Predecessor RUNOFF"
 .\" --------------------------------------------------------------------
 .
-.BR roff \[aq]s
+.BR roff 's
 ancestor
 .B RUNOFF
 was written in the MAD language by
@@ -174,7 +174,7 @@ a project of the Massachusetts Institute of Technology (MIT), in 1963 and
 1964 \[en] note that CTSS commands were all uppercase.
 .
 .P
-In 1965, MIT\[aq]s Project MAC teamed with Bell Telephone Laboratories
+In 1965, MIT's Project MAC teamed with Bell Telephone Laboratories
 (BTL) and General Electric to begin the
 .UR http://\:www.multicians.org
 .I Multics
@@ -260,7 +260,7 @@ The name
 was shortened to
 .IR roff .
 .
-The greatly enlarged language of Ossanna\[aq]s version already
+The greatly enlarged language of Ossanna's version already
 included all elements of a full
 .IR "roff system" .
 .
@@ -304,7 +304,7 @@ system as a whole.
 .
 .
 .P
-Ossanna\[aq]s first version was written in the PDP-11 assembly
+Ossanna's first version was written in the PDP-11 assembly
 language and released in 1973.
 .
 .I Brian Kernighan
@@ -319,7 +319,7 @@ The C\~version was released in 1975.
 The syntax of the formatting language of the
 .BR nroff /\: troff
 programs was documented in the famous
-.IR "Troff User\[aq]s Manual [CSTR\~#54]" ,
+.IR "Troff User's Manual [CSTR\~#54]" ,
 first published in 1976, with further revisions up to 1992 by Brian
 Kernighan.
 .
@@ -332,7 +332,7 @@ systems tried to establish compatibility with this specification.
 .
 .
 .P
-After Ossanna\[aq]s death in 1977, Kernighan went on with developing
+After Ossanna's death in 1977, Kernighan went on with developing
 .IR troff .
 .
 In the late 1970s, Kernighan equipped
@@ -371,7 +371,7 @@ capabilities automatically.
 .
 The source code of both the ancient Unix and classical
 .I troff
-weren\[aq]t available for two decades.
+weren't available for two decades.
 .
 Meanwhile, it is accessible again (on-line) for non-commercial use,
 cf.\& section
@@ -430,7 +430,7 @@ standard today.
 .
 An alternative is
 .UR https://\:github.com/\:n-t-roff/\:heirloom-doctools
-.I Gunnar Ritter\[aq]s Heirloom roff project
+.I Gunnar Ritter's Heirloom roff project
 .UE
 project, started in 2005, which provides enhanced versions of the various
 roff tools found in the OpenSolaris and Plan\~9 operating systems, now
@@ -447,7 +447,7 @@ You can get this package with the shell command:
 .P
 Moreover, one finds there the
 .UR https://github.com/n-t-roff/DWB3.3
-.I Original Documenter\[aq]s Workbench Release 3.3
+.I Original Documenter's Workbench Release 3.3
 .UE .
 .
 .
@@ -455,7 +455,7 @@ Moreover, one finds there the
 .SH "USING ROFF"
 .\" --------------------------------------------------------------------
 .
-Most people won\[aq]t even notice that they are actually using
+Most people won't even notice that they are actually using
 .IR roff .
 .
 When you read a system manual page (man page)
@@ -470,7 +470,7 @@ a standard program of the X window distribution, see
 .
 But using
 .I roff
-explicitly isn\[aq]t difficult either.
+explicitly isn't difficult either.
 .
 .
 .P
@@ -601,7 +601,7 @@ There are a lot of free and commercial
 .I roff
 preprocessors.
 .
-Some of them aren\[aq]t available on each system, but there is a small
+Some of them aren't available on each system, but there is a small
 set of preprocessors that are considered as an integral part of each
 .I roff
 system.
@@ -739,7 +739,7 @@ For example, the classical devices mentioned in
 .I [CSTR\~#54]
 have greatly changed since the classical times.
 .
-The old hardware doesn\[aq]t exist any longer and the old graphical
+The old hardware doesn't exist any longer and the old graphical
 conversions were quite imprecise when compared to their modern
 counterparts.
 .
@@ -750,14 +750,14 @@ For example, the Postscript device
 in classical
 .I troff
 had a resolution of 720 units per inch, while
-.IR groff \[aq]s
+.IR groff 's
 .I ps
 device has 72000, a refinement of factor 100.
 .
 .
 .P
 Today the operating systems provide device drivers for most
-printer-like hardware, so it isn\[aq]t necessary to write a special
+printer-like hardware, so it isn't necessary to write a special
 hardware postprocessor for each printer.
 .
 .
@@ -852,7 +852,7 @@ and
 The classical
 .I roff
 formatting language is documented in the
-.I Troff User\[aq]s Manual
+.I Troff User's Manual
 .IR "[CSTR\~#54]" .
 .
 The
@@ -1225,7 +1225,7 @@ by AT&T Bell Labs.
 .TP
 runoff
 .UR http://\:web.mit.edu/\:Saltzer/\:www/\:publications/\:pubs.html
-Jerry Saltzer\[aq]s home page
+Jerry Saltzer's home page
 .UE
 .
 stores some documents using the ancient RUNOFF formatting language.
@@ -1270,7 +1270,7 @@ language are
 [CSTR\~#54]
 J.\& F.\& Ossanna,
 .UR http://\:www.troff.org/\:54.pdf
-.I "Nroff/\:Troff User\[aq]s Manual"
+.I "Nroff/\:Troff User's Manual"
 .UE ;
 .
 Bell Labs, 1976; revised by Brian Kernighan, 1992.
diff --git a/src/devices/grodvi/grodvi.1.man b/src/devices/grodvi/grodvi.1.man
index fd093bff..8fd0a356 100644
--- a/src/devices/grodvi/grodvi.1.man
+++ b/src/devices/grodvi/grodvi.1.man
@@ -190,12 +190,12 @@ in the corresponding tfm file;
 all characters in the tfm file can be accessed this way.
 .
 .LP
-By design, the DVI format doesn\[aq]t care about physical dimensions of the
+By design, the DVI format doesn't care about physical dimensions of the
 output medium.
 .
 Instead,
 .B grodvi
-emits the equivalent to \*[tx]\[aq]s
+emits the equivalent to \*[tx]'s
 .BI \[rs]special{papersize= width , length }
 on the first page;
 .B dvips
@@ -257,7 +257,7 @@ Set the default line thickness to
 .I n
 thousandths of an em.
 .
-If this option isn\[aq]t specified, the line thickness defaults to
+If this option isn't specified, the line thickness defaults to
 0.04\~em.
 .
 .
@@ -390,7 +390,7 @@ additionally, they give a much better coverage of groff symbols.
 .
 Note that
 .B ec.tmac
-must be called before any language-specific files; it doesn\[aq]t take
+must be called before any language-specific files; it doesn't take
 care of hcode values.
 .
 .
diff --git a/src/devices/grohtml/grohtml.1.man b/src/devices/grohtml/grohtml.1.man
index f8c45dd1..14abf9de 100644
--- a/src/devices/grohtml/grohtml.1.man
+++ b/src/devices/grohtml/grohtml.1.man
@@ -102,7 +102,7 @@ is run by
 options can be passed to
 .B grohtml
 using
-.BR groff \(aqs
+.BR groff 's
 .B \-P
 option.
 .
@@ -126,7 +126,7 @@ always writes output in \%UTF-8 encoding and has built-in entities for
 all non-composite unicode characters.
 .
 In spite of this, groff may issue warnings about unknown special
-characters if they can\(aqt be found during the first pass.
+characters if they can't be found during the first pass.
 .
 Such warnings can be safely ignored unless the special characters
 appear inside a table or equation.
diff --git a/src/devices/grolbp/grolbp.1.man b/src/devices/grolbp/grolbp.1.man
index eacede35..34eaba86 100644
--- a/src/devices/grolbp/grolbp.1.man
+++ b/src/devices/grolbp/grolbp.1.man
@@ -153,7 +153,7 @@ Set the default line thickness to
 .I width
 thousandths of an em.
 .
-If this option isn\(aqt specified, the line thickness defaults to 0.04\~em.
+If this option isn't specified, the line thickness defaults to 0.04\~em.
 .
 .TP
 .B \-v
@@ -348,7 +348,7 @@ or
 indicating the font styles Roman, Italic and Bold respectively.
 .
 .IP
-For instance, if the printer\(aqs
+For instance, if the printer's
 .I font listing A
 shows font \(oqNelite12I.ISO_USA\(cq, the corresponding entry in the
 font description file is
@@ -367,12 +367,12 @@ program.
 .IP \(bu
 For scalable fonts,
 .I printer_font_name
-is identical to the font name as it appears in the printer\(aqs
+is identical to the font name as it appears in the printer's
 .IR "font listing A" .
 .
 .IP
 For instance, to select the \(oqSwiss\(cq font in bold style, which
-appears in the printer\(aqs
+appears in the printer's
 .I font listing A
 as \(oqSwiss-Bold\(cq, the required
 .B lbpname
diff --git a/src/devices/grolj4/grolj4.1.man b/src/devices/grolj4/grolj4.1.man
index 3c898684..eaf7be65 100644
--- a/src/devices/grolj4/grolj4.1.man
+++ b/src/devices/grolj4/grolj4.1.man
@@ -127,7 +127,7 @@ Set the default line thickness to
 .I n
 thousandths of an em.
 .
-If this option isn\(aqt specified, the line thickness defaults to
+If this option isn't specified, the line thickness defaults to
 0.04\~em.
 .
 .TP
diff --git a/src/devices/gropdf/gropdf.1.man b/src/devices/gropdf/gropdf.1.man
index cb5fe268..5a6e05a4 100644
--- a/src/devices/gropdf/gropdf.1.man
+++ b/src/devices/gropdf/gropdf.1.man
@@ -97,7 +97,7 @@ is run by
 options can be passed to
 .B gropdf
 using
-.BR groff \[aq]s
+.BR groff 's
 .B \-P
 option.
 .
@@ -194,7 +194,7 @@ to embed ALL fonts (even the 14 base PDF fonts).
 Append a comment line to end of PDF showing statistics,
 i.e.\& number of pages in document.
 .
-Ghostscript\[aq]s
+Ghostscript's
 .B ps2pdf
 complains about this line if it is included, but works anyway.
 .
@@ -256,7 +256,7 @@ Fewer Type\~1 fonts are supported natively in PDF documents than the
 standard 35 fonts supported by
 .B grops
 and all postscript printers, but all the fonts are available since any
-which aren\[aq]t supported natively are automatically embedded in the
+which aren't supported natively are automatically embedded in the
 PDF.
 .
 .
@@ -935,10 +935,10 @@ bold italic faces, it is recommended to use the letters
 .BR I ,
 and
 .BR BI ,
-respectively, as postfixes in the groff font names to make groff\[aq]s
+respectively, as postfixes in the groff font names to make groff's
 \[oq].fam\[cq] request work.
 .
-An example is groff\[aq]s built-in Times-Roman font: The font family
+An example is groff's built-in Times-Roman font: The font family
 name is
 .BR T ,
 and the groff font names are
@@ -958,7 +958,7 @@ section in the
 .BR troff (@MAN1EXT@)
 man page which lists the actual value of the font path.
 .
-Note that groff doesn\[aq]t use the AFM files (but it is a good idea to
+Note that groff doesn't use the AFM files (but it is a good idea to
 store them anyway).
 .
 .LI
diff --git a/src/devices/gropdf/pdfmom.1.man b/src/devices/gropdf/pdfmom.1.man
index 44b2d2a1..007dad0c 100644
--- a/src/devices/gropdf/pdfmom.1.man
+++ b/src/devices/gropdf/pdfmom.1.man
@@ -1,4 +1,4 @@
-.TH PDFMOM @MAN1EXT@ "@MDATE@" "Groff Version @VERSION@"
+].TH PDFMOM @MAN1EXT@ "@MDATE@" "Groff Version @VERSION@"
 .SH NAME
 pdfmom \- Produce PDF documents using the mom macro set
 .
@@ -77,7 +77,7 @@ If called with the
 .B \-Tpdf
 option (which is the default),
 .B pdfmom
-processes files using groff\(aqs native PDF driver,
+processes files using groff's native PDF driver,
 .BR gropdf .
 .
 If
@@ -85,7 +85,7 @@ If
 is given, processing is passed over to
 .BR pdfroff ,
 which uses
-.BR groff \(aqs
+.BR groff 's
 PostScript driver.
 .
 In either case, multiple runs of the source file are peformed in
@@ -144,7 +144,7 @@ sometimes issues warnings of the type
 .P
 .RS 2
 \&.\|.\|.:
-.B can\(aqt transparently output node at top level
+.B can't transparently output node at top level
 .RE
 .
 .P
diff --git a/src/devices/grops/grops.1.man b/src/devices/grops/grops.1.man
index 55b26f74..e31185d9 100644
--- a/src/devices/grops/grops.1.man
+++ b/src/devices/grops/grops.1.man
@@ -94,7 +94,7 @@ is run by
 options can be passed to
 .B grops
 using
-.BR groff \[aq]s
+.BR groff 's
 .B \-P
 option.
 .
@@ -102,7 +102,7 @@ option.
 .LP
 Note that
 .B grops
-doesn\[aq]t produce a valid document structure (conforming to the
+doesn't produce a valid document structure (conforming to the
 Document Structuring Convention) if called with multiple file
 arguments.
 .
@@ -132,7 +132,7 @@ Normally
 produces output at PostScript LanguageLevel\~2 that conforms to the
 Document Structuring Conventions version 3.0.
 .
-Some older printers, spoolers, and previewers can\[aq]t handle such
+Some older printers, spoolers, and previewers can't handle such
 output.
 .
 The value of\~\c
@@ -159,7 +159,7 @@ comment.
 .IP
 Add\~2 if lines in included files beginning with
 .B %!\&
-should be stripped out; this is needed for Sun\[aq]s pageview
+should be stripped out; this is needed for Sun's pageview
 previewer.
 .
 .IP
@@ -170,7 +170,7 @@ and
 .B %%End\%Prolog
 comments should be
 stripped out of included files; this is needed for spoolers that
-don\[aq]t understand the
+don't understand the
 .B %%Begin\%Document
 and
 .B %%End\%Document
@@ -181,7 +181,7 @@ Add\~8 if the first line of the PostScript output should be
 .B %!PS-Adobe-2.0
 rather than
 .BR %!PS-Adobe-3.0 ;
-this is needed when using Sun\[aq]s Newsprint with a printer that
+this is needed when using Sun's Newsprint with a printer that
 requires page reversal.
 .
 .IP
@@ -193,7 +193,7 @@ nor the
 PostScript command).
 .
 This was the behaviour of groff version 1.18.1 and earlier; it is
-needed for older printers which don\[aq]t understand PostScript
+needed for older printers which don't understand PostScript
 LanguageLevel\~2.
 .
 It is also necessary if the output is further processed to get an
@@ -469,7 +469,7 @@ It is also able to handle inter-resource dependencies.
 For example, suppose that you have a downloadable font called
 Garamond, and also a downloadable font called Garamond-Outline which
 depends on Garamond (typically it would be defined to copy
-Garamond\[aq]s font dictionary, and change the PaintType), then it is
+Garamond's font dictionary, and change the PaintType), then it is
 necessary for Garamond to appear before Garamond-Outline in the
 PostScript document.
 .
@@ -818,7 +818,7 @@ and y\~coordinates increase down the page.
 A procedure\~\c
 .B u
 is defined that converts groff units to the coordinate system in
-effect (provided the user doesn\[aq]t change the scale).
+effect (provided the user doesn't change the scale).
 .
 For example,
 .
@@ -888,7 +888,7 @@ procedure.
 .B grops
 wraps user-specified PostScript code into a dictionary, nothing more.
 .
-In particular, it doesn\[aq]t start and end the inserted code with
+In particular, it doesn't start and end the inserted code with
 .B save
 and
 .BR restore ,
@@ -1136,7 +1136,7 @@ drawn unconnected).
 .\" --------------------------------------------------------------------
 .
 .B grops
-itself doesn\[aq]t emit bounding box information.
+itself doesn't emit bounding box information.
 .
 With the help of Ghostscript the following simple script,
 .BR groff2eps ,
@@ -1263,12 +1263,12 @@ The very first characters in a Type\~42 font file look like this:
 .IP
 This is a wrapper format for TrueType fonts.
 .
-Old PS printers might not support it (this is, they don\[aq]t have a
+Old PS printers might not support it (this is, they don't have a
 built-in TrueType font interpreter).
 .
 .IP
 If your font is in PFB format (such fonts normally have \[oq].pfb\[cq]
-as the file extension), you might use groff\[aq]s
+as the file extension), you might use groff's
 .BR \%pfbtops (@MAN1EXT@)
 program to convert it to PFA.
 .
@@ -1303,10 +1303,10 @@ and bold italic faces, it is recommended to use the letters
 .BR I ,
 and
 .BR BI ,
-respectively, as postfixes in the groff font names to make groff\[aq]s
+respectively, as postfixes in the groff font names to make groff's
 \[oq].fam\[cq] request work.
 .
-An example is groff\[aq]s built-in Times-Roman font: The font family
+An example is groff's built-in Times-Roman font: The font family
 name is
 .BR T ,
 and the groff font names are
@@ -1326,7 +1326,7 @@ section in the
 .BR troff (@MAN1EXT@)
 man page which lists the actual value of the font path.
 .
-Note that groff doesn\[aq]t use the AFM files (but it is a good idea
+Note that groff doesn't use the AFM files (but it is a good idea
 to store them anyway).
 .
 .LI
@@ -1382,7 +1382,7 @@ to
 .B groff \-Tps \-P\-F \-P@OLDFONTDIR@ .\|.\|.
 .
 .LP
-or add the directory to groff\[aq]s font path environment variable
+or add the directory to groff's font path environment variable
 .
 .IP
 .B GROFF_FONT_PATH=@OLDFONTDIR@
diff --git a/src/devices/grotty/grotty.1.man b/src/devices/grotty/grotty.1.man
index 0c7ed8d4..568b82ca 100644
--- a/src/devices/grotty/grotty.1.man
+++ b/src/devices/grotty/grotty.1.man
@@ -133,7 +133,7 @@ For SGR support, it is necessary to use the
 option of
 .BR less (1)
 to disable the interpretation of
-.BR grotty \[aq]s
+.BR grotty 's
 old output format.
 .
 Consequently, all programs which use
@@ -173,7 +173,7 @@ environment variable instead.
 .
 .
 .LP
-.BR grotty \[aq]s
+.BR grotty 's
 old output format can be displayed on a terminal
 by piping through
 .BR ul (1).
@@ -252,19 +252,19 @@ Suppress the use of overstriking for bold characters.
 .
 Ignored if
 .B \-c
-isn\[aq]t used.
+isn't used.
 .
 .TP
 .B \-B
 Use only overstriking for bold-italic characters.
 Ignored if
 .B \-c
-isn\[aq]t used.
+isn't used.
 .
 .TP
 .B \-c
 Use
-.BR grotty \[aq]s
+.BR grotty 's
 old output format (see above).
 This also disables color output.
 .
@@ -325,7 +325,7 @@ Tabs are assumed to be set every 8 columns.
 Use escape sequences to set the italic text attribute instead of the
 underline attribute for italic fonts (\[oq]I\[cq] and \[oq]BI\[cq]).
 .
-Note that most terminals (including xterm) don\[aq]t support this.
+Note that most terminals (including xterm) don't support this.
 .
 Ignored if
 .B \-c
@@ -352,7 +352,7 @@ Suppress the use of underlining for italic characters.
 .
 Ignored if
 .B \-c
-isn\[aq]t used.
+isn't used.
 .
 .TP
 .B \-U
@@ -360,7 +360,7 @@ Use only underlining for bold-italic characters.
 .
 Ignored if
 .B \-c
-isn\[aq]t used.
+isn't used.
 .
 .TP
 .B \-v
@@ -515,9 +515,9 @@ of\~0) cannot be printed.
 Color handling is different compared to
 .BR grops (@MAN1EXT@).
 .B \[rs]M
-doesn\[aq]t set the fill color for closed graphic objects (which
+doesn't set the fill color for closed graphic objects (which
 .B grotty
-doesn\[aq]t support anyway) but changes the background color of the
+doesn't support anyway) but changes the background color of the
 character cell, affecting all subsequent operations.
 .
 .
diff --git a/src/preproc/eqn/eqn.1.man b/src/preproc/eqn/eqn.1.man
index 5901dbe3..3242203c 100644
--- a/src/preproc/eqn/eqn.1.man
+++ b/src/preproc/eqn/eqn.1.man
@@ -154,7 +154,7 @@ is not handled specially.
 .
 .TP
 .B \-N
-Don\[aq]t allow newlines within delimiters.
+Don't allow newlines within delimiters.
 .
 This option allows
 .B eqn
@@ -208,7 +208,7 @@ before the default directories.
 .
 .TP
 .B \-R
-Don\[aq]t load
+Don't load
 .BR eqnrc .
 .
 .TP
@@ -298,7 +298,7 @@ to restore the delimiters which have been previously disabled
 with a call to
 .RB \[oq] "delim off" \[cq].
 .
-If delimiters haven\[aq]t been specified, the call has no effect.
+If delimiters haven't been specified, the call has no effect.
 .
 .
 .\" --------------------------------------------------------------------
@@ -377,7 +377,7 @@ type "binary" \e(mu
 .RE
 .
 .IP
-The name of the type doesn\[aq]t have to be quoted, but quoting protects
+The name of the type doesn't have to be quoted, but quoting protects
 from macro expansion.
 .
 .TP
@@ -687,7 +687,7 @@ with
 .BI \%cancel\ {\  e\  }
 .
 .IP
-Here\[aq]s a more complicated construct that draws a box round an
+Here's a more complicated construct that draws a box round an
 expression:
 .
 .RS
@@ -741,7 +741,7 @@ equation, a negative value sets the spacing after the equation,
 replacing the default values.
 .
 This primitive provides an interface to
-.BR groff \[aq]s
+.BR groff 's
 .B \ex
 escape (but with opposite sign).
 .
@@ -775,7 +775,7 @@ The integer value\~\c
 .I n
 (in hundredths of an em) increases the vertical spacing between rows,
 using
-.BR groff \[aq]s
+.BR groff 's
 .B \ex
 escape (the value has no effect in MathML mode).
 Negative values are possible but have no effect.
@@ -837,7 +837,7 @@ definitive.
 .  TP
 .B minimum_size
 .B eqn
-doesn\[aq]t set anything at a smaller point-size than this.
+doesn't set anything at a smaller point-size than this.
 .
 The value is in points.
 .
@@ -1368,7 +1368,7 @@ In MathML mode, the
 .B mark
 and
 .B lineup
-features don\[aq]t work.
+features don't work.
 .
 These could, in theory, be implemented with \[oq]<maligngroup>\[cq]
 elements.
diff --git a/src/preproc/grn/grn.1.man b/src/preproc/grn/grn.1.man
index e767b80f..48024289 100644
--- a/src/preproc/grn/grn.1.man
+++ b/src/preproc/grn/grn.1.man
@@ -231,7 +231,7 @@ Commands may be upper or lower case and abbreviated down to one character.
 .
 .
 .PP
-Commands that affect a picture\[aq]s environment (those listed before
+Commands that affect a picture's environment (those listed before
 .BR default ,
 see below) are only in effect for the current picture:
 .
@@ -249,7 +249,7 @@ The commands are as follows:
 .BI 4\  N
 .
 Set
-.IR gremlin \[aq]s
+.IR gremlin 's
 text size number 1 (2, 3, or 4) to
 .I N
 points.
@@ -265,7 +265,7 @@ The default is 12 (16, 24, and 36, respectively).
 .TQ
 .BI special\  f
 Set the roman (italics, bold, or special) font to
-.IR @g@troff \[aq]s
+.IR @g@troff 's
 font
 .I f
 (either a name or number).
@@ -277,7 +277,7 @@ The default is R (I, B, and S, respectively).
 .TQ
 .BI stipple\  f
 Set the stipple font to
-.IR @g@troff \[aq]s
+.IR @g@troff 's
 stipple font
 .I f
 (name or number).
@@ -316,7 +316,7 @@ may be abbreviated down to \[oq]sc\[cq].
 .BI thick\  N
 .
 Set the thickness of
-.IR gremlin \[aq]s
+.IR gremlin 's
 narrow (medium and thick, respectively) lines to
 .I N
 times 0.15pt (this value can be changed at compile time).
@@ -344,7 +344,7 @@ regardless of any scaling factors in the picture.
 Setting
 .B pointscale
 will cause the point sizes to scale with the picture (within
-.IR @g@troff \[aq]s
+.IR @g@troff 's
 limitations, of course).
 .
 An operand of anything but
@@ -406,7 +406,7 @@ commands are given, the second one overrides the first.
 .
 If
 .I name
-doesn\[aq]t exist, an error message is reported and processing
+doesn't exist, an error message is reported and processing
 continues from the
 .B .GE
 line.
@@ -418,7 +418,7 @@ line.
 .
 Since
 .I @g@grn
-is a preprocessor, it doesn\[aq]t know about current indents, point
+is a preprocessor, it doesn't know about current indents, point
 sizes, margins, number registers, etc.  Consequently, no
 .I @g@troff
 input can be placed between the
@@ -465,7 +465,7 @@ should always be run last.
 .
 .
 .PP
-A picture is considered an entity, but that doesn\[aq]t stop
+A picture is considered an entity, but that doesn't stop
 .I @g@troff
 from trying to break it up if it falls off the end of a page.
 .
@@ -476,7 +476,7 @@ proper placement.
 .PP
 .I @g@grn
 uses
-.IR @g@troff \[aq]s
+.IR @g@troff 's
 number registers
 .B g1
 through
@@ -597,7 +597,7 @@ and
 are floating point values giving a positioning point to be used when
 this file is read into another file.
 .
-The stuff on this line really isn\[aq]t all that important; a value of
+The stuff on this line really isn't all that important; a value of
 \[lq]1 0.00 0.00\[rq] is suggested.
 .
 .IP \(bu
@@ -698,7 +698,7 @@ ncw(0.1i)l.
 4 \(mi@@special (S font in groff)
 .TE
 .sp
-If you\[aq]re using
+If you're using
 .I @g@grn
 to run your pictures through
 .IR groff ,
@@ -751,14 +751,14 @@ to 483.
 For horizontal pictures, x-values range from 0 to 511 and y-values
 range from 0 to 367.
 .
-Although you needn\[aq]t absolutely stick to this range, you\[aq]ll
+Although you needn't absolutely stick to this range, you'll
 get best results if you at least stay in this vicinity.
 .
 Also, point lists are terminated by a point of (\-1, \-1), so you
 shouldn't ever use negative coordinates.
 .
 .I gremlin
-writes out coordinates using format \[lq]%f1.2\[rq]; it\[aq]s probably
+writes out coordinates using format \[lq]%f1.2\[rq]; it's probably
 a good idea to use the same format if you want to modify the
 .I @g@grn
 code.
diff --git a/src/preproc/pic/pic.1.man b/src/preproc/pic/pic.1.man
index cc272790..d6e7fbba 100644
--- a/src/preproc/pic/pic.1.man
+++ b/src/preproc/pic/pic.1.man
@@ -109,7 +109,7 @@ is passed through without change.
 .
 .
 .LP
-It is the user\[aq]s responsibility to provide appropriate definitions
+It is the user's responsibility to provide appropriate definitions
 of the
 .B PS
 and
@@ -163,9 +163,9 @@ Unsafe mode; revert the default option
 .
 .TP
 .B \-n
-Don\[aq]t use the groff extensions to the troff drawing commands.
+Don't use the groff extensions to the troff drawing commands.
 .
-You should use this if you are using a postprocessor that doesn\[aq]t
+You should use this if you are using a postprocessor that doesn't
 support these extensions.
 .
 The extensions are described in
@@ -312,7 +312,7 @@ would avoid this.
 .
 .LP
 To make the vbox having a positive height and a depth of zero
-(as used e.g.\& by \*[lx]\[aq]s
+(as used e.g.\& by \*[lx]'s
 .BR \%graphics.sty ),
 define the following macro in your document:
 .RS
@@ -397,7 +397,7 @@ For the multiplicative case,
 .I expr3
 must be greater than zero.
 .
-If the constraints aren\[aq]t met, the loop isn\[aq]t executed.
+If the constraints aren't met, the loop isn't executed.
 .
 .I X
 can be any character not occurring in
@@ -859,7 +859,7 @@ The
 .B xslanted
 and
 .B yslanted
-attributes specify the x and y\~offset of the box\[aq]s upper right
+attributes specify the x and y\~offset of the box's upper right
 corner from its default position.
 .
 .
@@ -1010,7 +1010,7 @@ All three keywords expect a suffix specifying the color, for example
 .
 .
 .LP
-Currently, color support isn\[aq]t available in \*(tx mode.
+Currently, color support isn't available in \*(tx mode.
 .
 Predefined color names for
 .B groff
@@ -1227,7 +1227,7 @@ papersize to groff.
 .LP
 As the Encapsulated PostScript File Format
 .B EPS
-is getting more and more important, and the conversion wasn\[aq]t
+is getting more and more important, and the conversion wasn't
 regarded trivial in the past you might be interested to know that
 there is a conversion tool named
 .B ps2eps
diff --git a/src/preproc/preconv/preconv.1.man b/src/preproc/preconv/preconv.1.man
index e106ea23..ce93d93b 100644
--- a/src/preproc/preconv/preconv.1.man
+++ b/src/preproc/preconv/preconv.1.man
@@ -97,7 +97,7 @@ Specify default encoding if everything fails (see below).
 Specify input encoding explicitly, overriding all other methods.
 .
 This corresponds to
-.BR groff \[aq]s
+.BR groff 's
 .BI \-K encoding
 option.
 .
@@ -184,8 +184,8 @@ with a BOM (to ease the conversion from and to \%UTF-16 and \%UTF-32).
 In all cases, the byte order mark is
 .I not
 part of the data but part of the encoding protocol; in other words,
-.BR preconv \[aq]s
-output doesn\[aq]t contain it.
+.BR preconv 's
+output doesn't contain it.
 .
 .
 .PP
@@ -200,14 +200,14 @@ space\[cq] character \[en] something not needed normally in
 .\" --------------------------------------------------------------------
 .
 Editors which support more than a single character encoding need tags
-within the input files to mark the file\[aq]s encoding.
+within the input files to mark the file's encoding.
 .
 While it is possible to guess the right input encoding with the help of
 heuristic algorithms for data which represents a greater amount of a natural
 language, it is still just a guess.
 .
 Additionally, all algorithms fail easily for input which is either too short
-or doesn\[aq]t represent a natural language.
+or doesn't represent a natural language.
 .
 .
 .PP
@@ -332,7 +332,7 @@ is used.
 .\" --------------------------------------------------------------------
 .
 .B preconv
-doesn\[aq]t support
+doesn't support
 .I "local variable lists"
 yet.
 .
diff --git a/src/preproc/soelim/soelim.1.man b/src/preproc/soelim/soelim.1.man
index 6ed62789..c5ec64cd 100644
--- a/src/preproc/soelim/soelim.1.man
+++ b/src/preproc/soelim/soelim.1.man
@@ -137,7 +137,7 @@ requests (for general use, with non-groff files).
 .
 .TP
 .B \-t
-Don\[aq]t emit
+Don't emit
 .B .lf
 requests but TeX comment lines (starting with \[oq]%\[cq]) giving the
 current file and line number.
diff --git a/src/preproc/tbl/tbl.1.man b/src/preproc/tbl/tbl.1.man
index 336bcc63..ebfb9a29 100644
--- a/src/preproc/tbl/tbl.1.man
+++ b/src/preproc/tbl/tbl.1.man
@@ -141,7 +141,7 @@ at the end of the last line.
 .
 After each cell definition,
 .I column specifiers
-can be appended, but that\[aq]s optional.
+can be appended, but that's optional.
 .
 .
 .P
@@ -327,7 +327,7 @@ type.
 .
 .TP
 .B nokeep
-Don\[aq]t use diversions to prevent page breaks (GNU tbl only).
+Don't use diversions to prevent page breaks (GNU tbl only).
 .
 Normally
 .B tbl
@@ -528,7 +528,7 @@ Using equations (to be processed with
 within columns which use the
 .BR N \~specifier
 is problematic in most cases due to
-.BR tbl \[aq]s
+.BR tbl 's
 algorithm for finding the vertical alignment, as described above.
 .
 Using the global
@@ -704,7 +704,7 @@ whatever follows.
 The macro which name can be specified here must be defined before
 creating the table.
 .
-It is called just before the table\[aq]s cell text is output.
+It is called just before the table's cell text is output.
 .
 As implemented currently, this macro is only called if block input is
 used, that is, text between \[oq]T{\[cq] and \[oq]T}\[cq].
@@ -756,7 +756,7 @@ tbl extension).
 A vertical line spacing specifier followed by a column separation
 number must be separated by one or more blanks.
 .
-No effect if the corresponding table entry isn\[aq]t a text block.
+No effect if the corresponding table entry isn't a text block.
 .
 .TP
 .BR w , W
@@ -789,7 +789,7 @@ This feature has the same effect as specifying a minimum column width.
 .TP
 .BR z , Z
 Ignore the corresponding column for width-calculation purposes, this
-is, don\[aq]t use the fields but only the specifiers of this column to
+is, don't use the fields but only the specifiers of this column to
 compute its width.
 .
 .
@@ -847,7 +847,7 @@ concatenation).
 Note that
 .B @g@tbl
 computes the column widths line by line, applying \[rs]w on each entry
-which isn\[aq]t a text block.
+which isn't a text block.
 .
 As a consequence, constructions like
 .IP
@@ -972,7 +972,7 @@ request right after \[oq]T{\[cq].
 .
 The number register
 .B \[rs]n[TW]
-holds the table width; it can\[aq]t be used within the table itself
+holds the table width; it can't be used within the table itself
 but is defined right before calling
 .B .TE
 so that this macro can make use of it.
@@ -1086,7 +1086,7 @@ fails if those numbers are passed on as macro parameters because
 decimal point alignment is handled by
 .B @g@tbl
 itself: It only sees \[oq]\[rs]$1\[cq], \[oq]\[rs]$2\[cq], etc., and
-therefore can\[aq]t recognize the decimal point.
+therefore can't recognize the decimal point.
 .
 .
 .\" --------------------------------------------------------------------
@@ -1201,7 +1201,7 @@ as in
 .
 .LP
 The resulting \[lq]dummy\[rq] columns are invisible and have zero width;
-note that such columns usually don\[aq]t work with TTY devices.
+note that such columns usually don't work with TTY devices.
 .
 .
 .\" --------------------------------------------------------------------
diff --git a/src/roff/groff/groff.1.man b/src/roff/groff/groff.1.man
index fde40e87..192e7325 100644
--- a/src/roff/groff/groff.1.man
+++ b/src/roff/groff/groff.1.man
@@ -276,7 +276,7 @@ Preprocess with
 This is run before any other preprocessor.
 .
 Please refer to
-.BR preconv \[aq]s
+.BR preconv 's
 manual page for its behaviour if no
 .B \-K
 (or
@@ -335,7 +335,7 @@ before passing it to the spooler program.
 .
 .TP
 .B \-N
-Don\[aq]t allow newlines within
+Don't allow newlines within
 .I eqn
 delimiters.
 .
@@ -459,7 +459,7 @@ see
 Then
 .B groff
 calls a postprocessor to convert
-.BR @g@troff \[aq]s
+.BR @g@troff 's
 .I intermediate output
 to its final format.
 .
@@ -949,7 +949,7 @@ It is always run first before any other preprocessor.
 Besides these, there are some internal preprocessors that are
 automatically run with some devices.
 .
-These aren\[aq]t visible to the user.
+These aren't visible to the user.
 .
 .
 .\" --------------------------------------------------------------------
@@ -1259,7 +1259,7 @@ Today, most printing or drawing hardware is handled by the operating
 system, by device drivers, or by software interfaces, usually
 accepting PostScript.
 .
-Consequently, there isn\[aq]t an urgent need for more hardware device
+Consequently, there isn't an urgent need for more hardware device
 postprocessors.
 .
 .
@@ -1431,7 +1431,7 @@ but it can be anything.
 For example,
 .BR gtroff
 stood for
-.IR groff \[aq]s
+.IR groff 's
 .BR troff ,
 .BR gtbl
 for the
@@ -1481,7 +1481,7 @@ The value of this environment value is passed to the
 preprocessor to select the encoding of input files.
 .
 Setting this option implies
-.BR groff \[aq]s
+.BR groff 's
 command line option
 .B \-k
 (this is,
@@ -1643,7 +1643,7 @@ devices
 .B ascii
 and
 .B latin1
-aren\[aq]t available.
+aren't available.
 .
 Similarly, output for \f[CR]EBCDIC\f[] code page
 .B cp1047
diff --git a/src/roff/nroff/nroff.1.man b/src/roff/nroff/nroff.1.man
index 46104e58..fb4fb5c5 100644
--- a/src/roff/nroff/nroff.1.man
+++ b/src/roff/nroff/nroff.1.man
@@ -78,7 +78,7 @@ are devices accepted by
 .BR nroff
 to select the output encoding emitted by
 .BR grotty ,
-groff\(aqs TTY output device.
+groff's TTY output device.
 .
 If neither the
 .B GROFF_TYPESETTER
@@ -108,7 +108,7 @@ and
 .B \-c
 options
 are equivalent to
-.BR grotty \(aqs
+.BR grotty 's
 options
 .B \-h
 (using tabs in the output) and
diff --git a/src/roff/troff/troff.1.man b/src/roff/troff/troff.1.man
index 0414440e..4f9d52cd 100644
--- a/src/roff/troff/troff.1.man
+++ b/src/roff/troff/troff.1.man
@@ -98,7 +98,7 @@ Print a backtrace with each warning or error message.
 This backtrace should help track down the cause of the error.
 .
 The line numbers given in the backtrace may not always be correct, for
-.BR @g@troff \(aqs
+.BR @g@troff 's
 idea of line numbers gets confused by
 .B as
 or
@@ -131,7 +131,7 @@ must be a one letter name.
 Inhibit all error messages of
 .BR @g@troff .
 .
-Note that this doesn\(aqt affect messages output to standard error by
+Note that this doesn't affect messages output to standard error by
 macro packages using the
 .B tm
 or
@@ -188,7 +188,7 @@ No directory search is performed for files with an absolute file name.
 Read in the file
 .IB name .tmac\fR.
 .
-If it isn\(aqt found, try
+If it isn't found, try
 .BI tmac. name
 instead.
 .
@@ -253,7 +253,7 @@ can be any troff numeric expression.
 .
 .TP
 .B \-R
-Don\(aqt load
+Don't load
 .B troffrc
 and
 .BR troffrc-end .
diff --git a/src/utils/afmtodit/afmtodit.1.man b/src/utils/afmtodit/afmtodit.1.man
index 518381e1..6df5fc71 100644
--- a/src/utils/afmtodit/afmtodit.1.man
+++ b/src/utils/afmtodit/afmtodit.1.man
@@ -115,7 +115,7 @@ Lines starting with
 .B #
 and blank lines are ignored.
 .
-If the file isn\(aqt found in the current directory, it is searched
+If the file isn't found in the current directory, it is searched
 in the \(oqdevps/generate\(cq subdirectory of the default font
 directory.
 .
@@ -154,7 +154,7 @@ index values greater than 255 (or greater than the biggest character
 code used in the AFM file in the unlikely case that it is greater than
 255) in the groff font file.
 .
-Glyph indices of unencoded characters don\(aqt have a specific order;
+Glyph indices of unencoded characters don't have a specific order;
 it is best to access them with glyph names only.
 .
 .
@@ -270,7 +270,7 @@ character's width plus the character's italic correction is equal to
 .I n
 thousandths of an em
 plus the amount by which the right edge of the character's bounding box
-is to the right of the character\(aqs origin.
+is to the right of the character's origin.
 .
 If this would result in a negative italic correction, use a zero
 italic correction instead.
@@ -290,7 +290,7 @@ equal to
 .I n
 thousandths of an em
 plus the amount by which the left edge of the character's bounding box
-is to the left of the character\(aqs origin.
+is to the left of the character's origin.
 .
 The left italic correction may be negative unless option
 .B \-m
diff --git a/src/utils/hpftodit/hpftodit.1.man b/src/utils/hpftodit/hpftodit.1.man
index 98a3d001..6ba9fd96 100644
--- a/src/utils/hpftodit/hpftodit.1.man
+++ b/src/utils/hpftodit/hpftodit.1.man
@@ -184,7 +184,7 @@ it should be listed in the
 command in the DESC file;
 if it is not special, there is no need to list it, since
 .B troff
-can automatically mount it when it\[aq]s first used.
+can automatically mount it when it's first used.
 .
 .
 .LP
@@ -232,7 +232,7 @@ glyphs; with the
 option, only the \(lqmathematical\(rq symbol sets
 are searched.
 .
-Nonetheless, restricting the symbol sets searched isn\[aq]t very
+Nonetheless, restricting the symbol sets searched isn't very
 selective\(emmany glyphs are placed in both regular and special fonts.
 .
 Normally, the
@@ -318,11 +318,11 @@ option, the search order is reversed.
 .TP
 .BI \-i n
 Generate an italic correction for each character so that the
-character\[aq]s width plus the character\[aq]s italic correction is
+character's width plus the character's italic correction is
 equal to
 .I n
 thousandths of an em plus the amount by which the right edge of the
-character\[aq]s bounding is to the right of the character\[aq]s
+character's bounding is to the right of the character's
 origin.
 .
 If this would result in a negative italic correction, use a zero italic
@@ -341,7 +341,7 @@ instead.
 Also generate a left italic correction for each character equal to
 .I n
 thousandths of an em plus the amount by which the left edge of the
-character\[aq]s bounding box is to the left of the character\[aq]s
+character's bounding box is to the left of the character's
 origin.
 .
 The left italic correction may be negative.
diff --git a/src/utils/indxbib/indxbib.1.man b/src/utils/indxbib/indxbib.1.man
index 5d319dc8..f764aa11 100644
--- a/src/utils/indxbib/indxbib.1.man
+++ b/src/utils/indxbib/indxbib.1.man
@@ -167,7 +167,7 @@ option can be given at most once.
 .
 .TP
 .BI \-i string
-Don\(aqt index the contents of fields whose names are in
+Don't index the contents of fields whose names are in
 .IR string .
 .
 Initially
diff --git a/src/utils/tfmtodit/tfmtodit.1.man b/src/utils/tfmtodit/tfmtodit.1.man
index 81994ccb..620c4a67 100644
--- a/src/utils/tfmtodit/tfmtodit.1.man
+++ b/src/utils/tfmtodit/tfmtodit.1.man
@@ -120,7 +120,7 @@ it should be listed in the
 command in the DESC file;
 if it is not special, there is no need to list it, since
 .B troff
-can automatically mount it when it\(aqs first used.
+can automatically mount it when it's first used.
 .
 .
 .LP
diff --git a/tmac/groff_man.7.man b/tmac/groff_man.7.man
index f207ef6d..2007bbbf 100644
--- a/tmac/groff_man.7.man
+++ b/tmac/groff_man.7.man
@@ -973,7 +973,7 @@ which ignores indentation.
 .BI .AT " \fR[\fPsystem \fR[\fPrelease\fR]]\fP"
 Alter the footer for use with \f[CR]AT&T\f[]
 .IR \%man\~pages .
-This command exists only for compatibility; don\[aq]t use it.
+This command exists only for compatibility; don't use it.
 .
 See the
 .I groff
@@ -1057,7 +1057,7 @@ Redefine this macro to get control of the header.
 .BI .UC " \fR[\fPversion\fR]\fP"
 Alter the footer for use with \f[CR]BSD\f[]
 .IR man\~pages .
-This command exists only for compatibility; don\[aq]t use it.
+This command exists only for compatibility; don't use it.
 .
 See the
 .I groff
@@ -1157,7 +1157,7 @@ render it to HTML.
 .
 Troff requests make implicit assumptions about things like character
 and page sizes that may break in an HTML environment; also, many of
-these viewers don\[aq]t interpret the full troff vocabulary, a problem
+these viewers don't interpret the full troff vocabulary, a problem
 that can lead to portions of your text being silently dropped.
 .
 .
@@ -1200,7 +1200,7 @@ These are wrapper files to call
 .
 .TP
 .B andoc.tmac
-Use this file in case you don\[aq]t know whether the
+Use this file in case you don't know whether the
 .B man
 macros or the
 .B mdoc
diff --git a/tmac/groff_ms.7.man b/tmac/groff_ms.7.man
index 53d868a7..9b15c871 100644
--- a/tmac/groff_ms.7.man
+++ b/tmac/groff_ms.7.man
@@ -117,7 +117,7 @@ are specific to AT&T or Berkeley, and are not supported in
 .TP
 .B "Format and layout"
 By setting number registers,
-you can change your document\[aq]s type (font and size),
+you can change your document's type (font and size),
 margins, spacing, headers and footers, and footnotes.
 .
 See
@@ -127,7 +127,7 @@ below for more details.
 .TP
 .B "Cover page"
 A cover page consists of a title,
-and optionally the author\[aq]s name and institution,
+and optionally the author's name and institution,
 an abstract, and the date.
 .
 See
@@ -342,7 +342,7 @@ macro into the title, until reaching the author name or abstract.
 .
 .TP
 .B .AU
-Specifies the author\[aq]s name.
+Specifies the author's name.
 .
 You can specify multiple authors by using an
 .B AU
@@ -350,7 +350,7 @@ macro for each author.
 .
 .TP
 .B .AI
-Specifies the author\[aq]s institution.
+Specifies the author's institution.
 .
 You can specify multiple institutions.
 .
@@ -1420,7 +1420,7 @@ string.
 .
 Traditionally, the
 .I ms
-macros only support integer values for the document\[aq]s font size
+macros only support integer values for the document's font size
 and vertical spacing.
 .
 To overcome this restriction, values larger than or equal to 1000 are
@@ -1503,7 +1503,7 @@ macros both collide with different macros in the Berkeley version of
 .IP
 These emulations are sufficient to give back the 1976 Kernighan\~&
 Cherry paper
-.I "Typesetting Mathematics \(en User\[aq]s Guide"
+.I "Typesetting Mathematics \(en User's Guide"
 its section headings, and restore some text that had gone missing as
 arguments of undefined macros.
 .
@@ -1645,7 +1645,7 @@ Use
 .B \[rs]*Q
 and
 .B \[rs]*U
-to get a left and right typographer\[aq]s quote,
+to get a left and right typographer's quote,
 respectively, in
 .I troff
 (and plain quotes in
@@ -1693,7 +1693,7 @@ the default is\~14.
 .
 .PP
 Improved accent marks
-(as originally defined in Berkeley\[aq]s
+(as originally defined in Berkeley's
 .I ms
 version)
 are available by specifying the
diff --git a/tmac/groff_trace.7.man b/tmac/groff_trace.7.man
index b31a60c0..6b75e594 100644
--- a/tmac/groff_trace.7.man
+++ b/tmac/groff_trace.7.man
@@ -247,7 +247,7 @@ request it passes \[oq]\en[bar]\[cq] instead.
 .
 .
 .P
-The solution to this problem is to use groff\[aq]s
+The solution to this problem is to use groff's
 .B \eE
 escape which is an escape character not interpreted in copy mode, for
 example
diff --git a/tmac/groff_www.7.man b/tmac/groff_www.7.man
index c4d57619..f3a7f3f0 100644
--- a/tmac/groff_www.7.man
+++ b/tmac/groff_www.7.man
@@ -151,7 +151,7 @@ A file is split whenever a \&.SH or \&.NH\ 1 is encountered.
 Its argument is the file stem name for future output files.
 .
 This option is equivalent to
-.BR \%grohtml \[aq]s
+.BR \%grohtml 's
 .B \-j
 option.
 .
@@ -238,11 +238,11 @@ foo \[la]\f[C]http://foo.org\f[]\[ra]:
 .
 .IP
 The URL macro can be of any type; for example we can reference
-.URL pic.html "Eric Raymond\[aq]s pic guide"
+.URL pic.html "Eric Raymond's pic guide"
 by:
 .RS
 .IP
-.B .URL pic.html \[dq]Eric Raymond\[aq]s pic guide\[dq]
+.B .URL pic.html \[dq]Eric Raymond's pic guide\[dq]
 .RE
 .
 .TP
@@ -375,7 +375,7 @@ package:
 and
 .BR pnmtops .
 .
-If the document isn\[aq]t processed with
+If the document isn't processed with
 .B \-Thtml
 or
 .B \-Txhtml

--q2ox7oclsifbafhj--

--35hydig57bfxplve
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAlkGgzMACgkQ0Z6cfXEm
bc7QQw/8DHpiFo4VhIfXFlL9ziDWp28VnJOjLOXtY6NzZC20vkN3k545VNLtZmEm
l+dXvnRzg6ZzHXa0RlfaHldX1+MiHekHdZswPMykvzAiPqnAGhZwfZSjmeMSUc6F
VkggpJPCIoW3CHf2DcfOPYkzTBrh0Rn2tDvQmFbfcC8k/Ska3NII/lzyPgNmfJrB
AYgxuroKZBZo7Q3X66Qdg+SpRRzN39TwvMDA8oD3x2FWUG37uO2lGXW6OzPz/W/O
e8LDSUmNDUoNWguTXXNENJRR9pZtgjTbxztopRAP53lq5oBn+1mbR2W9U9Lv/dgG
O9Au9w+SVSQKauD1eFNfdChGZEp0uOYuooTa1nB8Nrll/UIyM2bVAwAOhTLpUBg6
sq1hrYVs1e2pjxnRx8LKkS9pPbRkfp+MxwALSny1qqPY9xBuOQgsf91k47iudSFr
4NsQJAxEyR0fU6roTXy/2wXqbW/eb+nKgLOR+rFGhafSjwquhzXtfQQ7SaXOj9bS
U3lZp21OQDDtY0wk651KbN5w2xa8EPdHlDiJq3WIrgj2TlsUUuL7gGbXn72KC4z5
nK52x8h+oW7K5prLmN1TC0PMkrNkKMBsHM02kEcfBClbKzZy513bOwDgPR3DIXnv
t5UCUtvidk/p298o04Ntco+gtcIJOFzDmOUzfpnW1nIpWDBIzS4=
=0j7N
-----END PGP SIGNATURE-----

--35hydig57bfxplve--


