From groff-admin  Sun Jul  2 05:08:18 2000
Received: from mescaline.gnu.org (we-refuse-to-spy-on-our-users@mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id FAA09760
	for <groff@ffii.org>; Sun, 2 Jul 2000 05:08:15 +0200
Received: from harpy.servcom.net.au (IDENT:root@harpy.servcom.net.au [202.61.205.10])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id XAA19171
	for <groff@gnu.org>; Sat, 1 Jul 2000 23:22:18 -0400
Received: from main-computer (dup188.servcom.net.au [202.61.195.188])
	by harpy.servcom.net.au (8.9.3/8.9.3) with SMTP id LAA06876
	for <groff@gnu.org>; Sun, 2 Jul 2000 11:45:37 +0800
Message-Id: <200007020345.LAA06876@harpy.servcom.net.au>
To: groff@gnu.org
From: "rgordon" <robert@ezpeakperform.com>
Date: Sun, 02 Jul 2000 11:19:22
Subject: [Groff] How To Earn An Alternative Income
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 281
Lines: 12

Feel free to check out the new web site below:

www.ezpeakperform.com

--------------------

E-Mail sent using the Free Trial Version of WorldMerge, the fastest
and easiest way to send personalized e-mail messages. More
information at http://www.coloradosoft.com/worldmrg

660448


From groff-admin  Mon Jul  3 15:33:59 2000
Received: from mescaline.gnu.org (we-refuse-to-spy-on-our-users@mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id PAA24321
	for <groff@ffii.org>; Mon, 3 Jul 2000 15:33:58 +0200
Received: from dns-01.emailwise.net ([203.46.218.131])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id JAA11699
	for <groff@gnu.org>; Mon, 3 Jul 2000 09:48:10 -0400
Received: (from nobody@localhost)
	by dns-01.emailwise.net (8.9.3/8.8.7) id XAA16026;
	Mon, 3 Jul 2000 23:48:25 +1000
Date: Mon, 3 Jul 2000 23:48:25 +1000
Message-Id: <200007031348.XAA16026@dns-01.emailwise.net>
To: groff@gnu.org
From: info@ausbizlinks.com
Reply-to: info@ausbizlinks.com
Subject: [Groff] Free 8 Page Business Web Site
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 890
Lines: 23

Dear Business Owner,
Ausbizlinks.com would like to offer all Australian Businesses a FREE and Easy way
to showcase your business online. Build up to 8 pages,  No Html, Ftp
or Web Design Knowledge needed .  And best of all, it's as easy as 1.2.3 !

To Build your free Web Site today please visit: 
http://www.ausbizlinks.com

---------------------------------------------------------
EASY ONE STEP REMOVAL INSTRUCTIONS..
====================================
To be removed from further mailings
simply click the link below this line

   http://www.emailwise.net/cgi-bin/email/removeme.cgi?REMOVE_FOR=00000005_groff@gnu.org

{ if your browser does not launch the above removal URL
  simply cut and paste the above link into your browser }
---------------------------------------------------------
Date/Timestamp: 03/07/2000 14:05:03
---------------------------------------------------------



From groff-admin  Tue Jul  4 08:06:29 2000
Received: from mescaline.gnu.org (we-refuse-to-spy-on-our-users@mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA12932
	for <groff@ffii.org>; Tue, 4 Jul 2000 08:06:27 +0200
Received: from dns-01.emailwise.net ([203.46.218.131])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id CAA13431
	for <groff@gnu.org>; Tue, 4 Jul 2000 02:20:47 -0400
Received: (from nobody@localhost)
	by dns-01.emailwise.net (8.9.3/8.8.7) id QAA06194;
	Tue, 4 Jul 2000 16:21:11 +1000
Date: Tue, 4 Jul 2000 16:21:11 +1000
Message-Id: <200007040621.QAA06194@dns-01.emailwise.net>
To: groff@gnu.org
From: info@ausbizlinks.com
Reply-to: info@ausbizlinks.com
Subject: [Groff] Free 8 Page Business Web Site
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 890
Lines: 23

Dear Business Owner,
Ausbizlinks.com would like to offer all Australian Businesses a FREE and Easy way
to showcase your business online. Build up to 8 pages,  No Html, Ftp
or Web Design Knowledge needed .  And best of all, it's as easy as 1.2.3 !

To Build your free Web Site today please visit: 
http://www.ausbizlinks.com

---------------------------------------------------------
EASY ONE STEP REMOVAL INSTRUCTIONS..
====================================
To be removed from further mailings
simply click the link below this line

   http://www.emailwise.net/cgi-bin/email/removeme.cgi?REMOVE_FOR=00000005_groff@gnu.org

{ if your browser does not launch the above removal URL
  simply cut and paste the above link into your browser }
---------------------------------------------------------
Date/Timestamp: 03/07/2000 14:05:03
---------------------------------------------------------



From groff-admin  Tue Jul 11 16:22:00 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id QAA11834
	for <Groff@ffii.org>; Tue, 11 Jul 2000 16:21:56 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA26404 for Groff@ffii.org; Tue, 11 Jul 2000 16:36:22 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Tue, 11 Jul 2000 16:35:39 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Groff@ffii.org
Message-Id: <Pine.LNX.4.10.10007111633230.278-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] refer macros
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 529
Lines: 18

Hi,

I need to use the refer preprocessor for a paper I'm writing and
using the mm macros. The mm macros I have (from the groff CVS dist)
have no support for refer, while the ms do. I'm thinking of rebuilding
a separate set of refer macros to be used with any package.

Has something like this already been done? Is there any counter-indication
in doing it? (I would send them to the maintainers afterwards of
course).

Nicola

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+


From groff-admin  Tue Jul 11 18:35:38 2000
Received: from maxwell.phys.lafayette.edu (maxwell.phys.lafayette.edu [139.147.200.41])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA17993
	for <Groff@ffii.org>; Tue, 11 Jul 2000 18:35:37 +0200
Received: from localhost (doughera@localhost)
	by maxwell.phys.lafayette.edu (8.9.3+Sun/8.9.3) with ESMTP id MAA21113;
	Tue, 11 Jul 2000 12:50:46 -0400 (EDT)
X-Authentication-Warning: maxwell.phys.lafayette.edu: doughera owned process doing -bs
Date: Tue, 11 Jul 2000 12:50:46 -0400 (EDT)
From: Andy Dougherty <doughera@lafayette.edu>
X-Sender: doughera@maxwell.phys.lafayette.edu
To: Nicola Bernardini <nicb@axnet.it>
cc: Groff@ffii.org
Subject: Re: [Groff] refer macros
In-Reply-To: <Pine.LNX.4.10.10007111633230.278-100000@ax-nicb.axnet.it>
Message-ID: <Pine.SOL.4.10.10007111235460.21092-100000@maxwell.phys.lafayette.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3765
Lines: 136

On Tue, 11 Jul 2000, Nicola Bernardini wrote:

> 
> Hi,
> 
> I need to use the refer preprocessor for a paper I'm writing and
> using the mm macros. The mm macros I have (from the groff CVS dist)
> have no support for refer, while the ms do. I'm thinking of rebuilding
> a separate set of refer macros to be used with any package.
> 
> Has something like this already been done? Is there any counter-indication
> in doing it? (I would send them to the maintainers afterwards of
> course).

Some time ago, I did something along these lines as follows:

1.  Extract the Refer support module from groff's tmac.s and put it in a
separate file.

2.  Modify that file to use -mm commands rather than -ms commands to
format the various lists.  (e.g. I used a .VL list instead of individual
indented .IP paragraphs).

3.  Customize the output to match the requirements of the journal I was
submitting to

4.  Save the result in a separate file and  .so it as part of my document.

Here's the result.  My originals were based on an older version of the
groff -ms macros; I have patched my macros against the oldest version I
have lying around to try to avoid confusing matters due to version skew.
Even so, I don't recognize what I was doing with the par@sup-start stuff.

My main observations on the whole procedure are:

    1.  There wasn't too much to change, so it wasn't too hard.
    2.  The package builds extensively on existing macros in the larger
	macro package (either -ms or -mm).  I think it would be a mistake
	to try to reimplement the refer macros in a package-independent
	way.  That's likely to lead to too much duplication of effort
	(e.g. a package-independent way to get indented paragraphs using
	the prevailing indent, etc.)
    3.  Making a duplicate -mm version also duplicates a lot of work, but,
	as my patch shows, not all *that* much has to be changed, so it's
	probably not that big a deal to maintain duplicate "flavors"
	of the refer support.
    4.  Specific requirements of specific journals (or other target
	audiences) may require customization of the macros anyway.

Hope this helps.

--- ms.refer	Tue Jul 11 12:46:06 2000
+++ mm.refer	Sat Feb 21 13:50:39 1998
@@ -58,9 +57,11 @@
 .rm [F [T1 [T2
 ..
 .\" start of reference number
-.ds [. \\*[par@sup-start]
+.\" .ds [. \v'-.4m'\s-4[
+.ds [. \0[
 .\" end of reference number
-.ds .] \\*[par@sup-end]
+.\" .ds .] ]\s0\v'.4m'
+.ds .] ]
 .\" period before reference
 .ds <. .
 .\" period after reference
@@ -70,16 +71,13 @@
 .\" comma after reference
 .ds >, \" empty
 .\" start collected references
-.de ]<
+.de ]<   \" start to display collected references
 .als ref*print ref*end-print
-.SH
-\&\\*[REFERENCES]
-.par@reset
-..
-.\" end collected references
-.de ]>
-.par@finish
+.VL 4 0 1
+..
+.de ]>   \" end display of collected references
 .als ref*print ref*normal-print
+.LE
 ..
 .de ref*normal-print
 .ie d [F .FS "\\*([.\\*([F\\*(.]"
@@ -88,7 +86,7 @@
 .FE
 ..
 .de ref*end-print
-.ie d [F .IP "\\*([F."
+.ie d [F .LI "\\*([F."
 .el .XP
 \\*[ref*string]
 ..
@@ -118,21 +116,24 @@
 .if r [T .nr ref*suppress-period \\n([T
 ..
 .de ref*add-T2
-.ref*field T , "\\*Q" "" "\\*U"
+.ref*field T , "\\(lq" "" "\\(rq"
 .if r [T .nr ref*suppress-period \\n([T
 ..
-.de ref*add-P
-.ie \\n([P>0 .ref*field P , "pp. "
-.el .ref*field P , "p. "
-..
+.\" .de ref*add-P
+.\" .ie \\n([P>0 .ref*field P , "pp. "
+.\" .el .ref*field P , "p. "
+.\" ..
 .de ref*add-J
 .ref*field J , \fI "" \fP
 ..
+.de ref*add-V
+.ref*field V , \fB "" \fP
+..
 .de ref*add-D
 .ref*field D "" ( )
 ..
 .de ref*add-E
-.ref*field E , "ed. "
+.ref*field E , "" " eds."
 ..
 .de ref*add-G
 .ref*field G "" ( )


-- 
    Andy Dougherty		doughera@lafayette.edu
    Dept. of Physics
    Lafayette College, Easton PA 18042


From groff-admin  Tue Jul 11 20:06:55 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA21795
	for <Groff@ffii.org>; Tue, 11 Jul 2000 20:06:55 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13C4fB-0003uI-00; Tue, 11 Jul 2000 19:21:46 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id TAA13498;
	Tue, 11 Jul 2000 19:09:18 +0100
Message-ID: <XFMail.000711190918.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.10.10007111633230.278-100000@ax-nicb.axnet.it>
Date: Tue, 11 Jul 2000 19:09:18 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Nicola Bernardini <nicb@axnet.it>
Subject: RE: [Groff] refer macros
Cc: Groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3216
Lines: 96

Hi Nicola,

On 11-Jul-00 Nicola Bernardini wrote:
> I need to use the refer preprocessor for a paper I'm writing and
> using the mm macros. The mm macros I have (from the groff CVS dist)
> have no support for refer, while the ms do. I'm thinking of rebuilding
> a separate set of refer macros to be used with any package.
> 
> Has something like this already been done? Is there any
> counter-indication
> in doing it? (I would send them to the maintainers afterwards of
> course).
> 
> Nicola

I don't know of it's having been done so if anyone else knows, or has done
it, it would be good to hear.

It shouldn't be too difficult to do it, so long as you take care to avoid
treading on anything already defined in mm, and correctly implement
the calls to ms macros and registers.

Of the latter, I think there are only

In .de ]<
.SH
.par@reset

In .de ]>
.par@finish

In .de ref*normal-print
.FS
.FE

In .de ref*end-print
.IP
.XP

.ds [. \\*[par@sup-start]
.ds .] \\*[par@sup-end]
.ref*field T , "\\*Q" "" "\\*U"

Of these, .SH, .FS, .FE, .IP, .XP, \\*Q and \\*U
are "user" macros/strings defined in ms macros; the remainder
are "internal" to the ms macros (the latter may cause you more
trouble since the former have their mm equivalents).


However, you may also like to have a look at 'bib' (a fairly
old program written 1985-87 by Timothy Budd) and avoid using
'refer' altogether. ('bib' is descended from 'refer' and can, I think,
do anything that troff 'refer' can; I'm not too sure how it compares
with groff 'refer').

I find that 'refer' and its ms implementation are a bit limited,
and difficult to customise. 'bib' gives you a bit more scope;
it is another pre-processor like 'refer'. It can be found at

   ftp ftp.cs.orst.edu  pub/budd/bib.tar.Z

(it's still there!). There is also a brief man-page in the O'Reilly
"4.4BSD User's Reference Manual", and an extended user's manual
in "4.4BSD User's Supplementary Documents" (more extended than
the one which is "bibdoc.ps" which can be constructed -- using
'bib' itself -- from the sources in the tar file).

'bib' uses the same bibliographic database format as 'refer.
Output format is specified in format files containing style macros.
This is more flexible than the 'refer' mechanism, where customising
requires re-writing the (somewhat obscure) macros in the "ref"
module of the ms macros. One advantage of doing it the 'bib' way
is that you can have different format files for, say, different
journals.

However, 'bib' still does a less than comprehensive job.

'bib' is closely related to the TeX-oriented package 'tib' with similar
functionality (and descended, like 'bib' from 'refer'), allowing
a degree of exchange between troff and TeX bibliographies.

You can find 'tib' at CTAN, e.g.

  ftp://sunsite.org.uk/packages/tex/uk-tex/biblio/tib

but it's all in separate files, and I don't know of a place to
find a tar-ball.

I hope this helps!
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 11-Jul-00                                       Time: 19:09:18
------------------------------ XFMail ------------------------------

From groff-admin  Wed Jul 12 14:23:17 2000
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id OAA01785
	for <groff@ffii.org>; Wed, 12 Jul 2000 14:23:15 +0200
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA18944
	for <groff@ffii.org>; Wed, 12 Jul 2000 08:37:54 -0400 (EDT)
Received: from sol.eng.fore.com (sol.pit.comms.marconi.com [169.144.155.73])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA19215
	for <groff@ffii.org>; Wed, 12 Jul 2000 08:37:54 -0400 (EDT)
Received: from pss-pc.eng.fore.com (root@pss-pc [169.144.32.90])
	by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id IAA12019
	for <groff@ffii.org>; Wed, 12 Jul 2000 08:37:54 -0400 (EDT)
Received: from pss-pc.eng.fore.com (IDENT:pss@localhost [127.0.0.1])
	by pss-pc.eng.fore.com (8.9.3/8.8.7) with ESMTP id IAA06365
	for <groff@ffii.org>; Wed, 12 Jul 2000 08:41:14 -0400
Message-Id: <200007121241.IAA06365@pss-pc.eng.fore.com>
To: groff@ffii.org
Reply-to: pragnesh.sampat@marconi.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 12 Jul 2000 08:41:14 -0400
From: Pragnesh Sampat <pss@fore.com>
Subject: [Groff] .TC in the groff mm macros
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 292
Lines: 6

Has anyone used the .TC command and used to 2 groff passes to get the Table Of
Contents in the right place in the postscript output?  The groff_mm man mage
mentions this, but I have not tried it yet.  I am using a .TC at the end and
get a decent contents page at the end.  Thanks,

-Pragnesh

From groff-admin  Wed Jul 12 18:45:32 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id SAA15317
	for <Groff@ffii.org>; Wed, 12 Jul 2000 18:45:30 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA00531 for Groff@ffii.org; Wed, 12 Jul 2000 19:00:33 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Wed, 12 Jul 2000 18:59:31 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Andy Dougherty <doughera@lafayette.edu>, Ted.Harding@nessie.mcc.ac.uk
Cc: Groff@ffii.org
Subject: Re: [Groff] refer macros
In-Reply-To: <XFMail.000711190918.Ted.Harding@nessie.mcc.ac.uk>
Message-Id: <Pine.LNX.4.10.10007121851460.10205-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1255
Lines: 29

I'd like to thank very much Andy Dougherty and Ted Harding for their
reply in the refer macros related to the mm package question.

I have looked at bib. I have pulled it down from the net, compiled it
and tried to play with it. While it looks much better than refer, it
requires (from what I can see) a complete re-organization of the
bibliographic database and I do not have the time to do it right now.
I have, however, done a number of minimal modifications to the bib package
in order to be able to compile it and use it and I am ready to provide
a patch file for them if somebody wants it. I think that bib is definitely
worth taking back in business and keep maintaining (although I cannot
do anything like that right now).

I have also followed the instructions by Andy Dougherty, and by miracle
I now have a perfect (or at least it looks like that) mm.refer file
which I can .mso in my paper file and use it right away. I had to make
minor modifications to his patch file and everything worked like charm.

Please let me know if anybody wants the mm.refer file I produced.

Thanks again Andy and Ted. Your comments have been very useful.

nicb

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+


From groff-admin  Thu Jul 13 01:34:31 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id BAA30190
	for <Groff@ffii.org>; Thu, 13 Jul 2000 01:34:31 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13CWFz-0008Fu-00; Thu, 13 Jul 2000 00:49:36 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id XAA14471;
	Wed, 12 Jul 2000 23:48:25 +0100
Message-ID: <XFMail.000712234825.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.10.10007121851460.10205-100000@ax-nicb.axnet.it>
Date: Wed, 12 Jul 2000 23:48:25 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Nicola Bernardini <nicb@axnet.it>
Subject: Re: [Groff] refer macros
Cc: Groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2179
Lines: 53

Hi again Nicola,

I'm pleased you got going with Andy Dougherty's suggestion.
I have just one comment on your mail.

On 12-Jul-00 Nicola Bernardini wrote:
> I have looked at bib. I have pulled it down from the net, compiled it
> and tried to play with it. While it looks much better than refer, it
> requires (from what I can see) a complete re-organization of the
> bibliographic database and I do not have the time to do it right now.

Mainly, the database format of 'bib' matches that of 'refer',
the main differences being:

- 'bib' has a %F field which can be used to over-ride whatever formatted
  reference string 'bib' would have used;

- 'refer' has a %L field ("label") to specify labels used to
  designate references instead of numbers;

- 'refer' has a %Q field ("Author if not person") while /bib' does not;

- 'bib' has a %W field for "local finding information" which 'refer' has
   not.

- UNIX 'refer' does not honour multiple %E fields ("editor"), while
  'bib' allows multiple editors like multiple authors. I'm not sure
  about how groff 'refer' behaves in this respect: the man page hints
  that it might allow multiple %Es, but I never tried it.

Most of these differences are quite minor, and the only cases which
could cause trouble in moving from 'refer' to 'bib' are %L and %Q,

However, the manner of planting citations in the text is quite different.

So I'm a bit puzzled by "it requires (from what I can see) a complete
re-organization of the bibliographic database" (unless, of course,
you are referring to the citations).

> I have also followed the instructions by Andy Dougherty, and by miracle
> I now have a perfect (or at least it looks like that) mm.refer file
> which I can .mso in my paper file and use it right away. I had to make
> minor modifications to his patch file and everything worked like charm.

That's excellent!
Best wishes,
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 12-Jul-00                                       Time: 23:48:25
------------------------------ XFMail ------------------------------

From groff-admin  Thu Jul 13 22:32:18 2000
Received: from RSMTP.mycity.at (cybertron035.cybertron.at [212.236.73.35] (may be forged))
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA10465
	for <groff@ffii.org>; Thu, 13 Jul 2000 22:32:18 +0200
X-Authentication-Warning: genba.ffii.org: Host cybertron035.cybertron.at [212.236.73.35] (may be forged) claimed to be RSMTP.mycity.at
Received: from schleppo.sun.universe (baden-remote30.mycity.at [212.236.73.222])
	by RSMTP.mycity.at (8.9.3/8.9.3) with ESMTP id WAA01166;
	Thu, 13 Jul 2000 22:46:47 +0200
Received: (from salb@localhost)
	by schleppo.sun.universe (8.8.8/8.8.8) id WAA00321;
	Thu, 13 Jul 2000 22:34:45 +0200 (CEST)
Date: Thu, 13 Jul 2000 22:34:45 +0200 (CEST)
From: Bernd Salbrechter <bernd@mycity.at>
Message-Id: <200007132034.WAA00321@schleppo.sun.universe>
To: groff@ffii.org
Subject: Re: [Groff] .TC in the groff mm macros
Cc: pragnesh.sampat@marconi.com
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1484
Lines: 32

On Wed, 12 Jul 2000 08:41:14 -0400 Pragnesh Sampat <pss@fore.com> wrote:

> Has anyone used the .TC command and used to 2 groff passes to get the Table Of
> Contents in the right place in the postscript output?  The groff_mm man mage
> mentions this, but I have not tried it yet.  I am using a .TC at the end and
> get a decent contents page at the end.  Thanks,
> 
> -Pragnesh

Sorry I didn't have used the mm macros, but have looked at the manpage
and the code. From what I read there the two passes only used for
cross-references and not for reordering the table of content pages.

Dose taking the table of content pages from the end of the printout and
insert it after the cover page not working for you? Or do you imposition
for printing on better devices than a Hp-Laserjet (i.e. a Linotronic :-)?
If the later, you will have PostScript output, where you can use pstools
to reorder the pages, but that require a separate page numbering of the
front matter (Table of Content).

I saw an instruction for something in "The Groff and Friends HOWTODO"
(sorry didn't have an exact reference, but I think I saw it on the
"groff-maillist"). If you want (must, because of page numbering) to go
this line you will have a happy time hacking the macros ;-).

Hope that helps
Bernd

PS.: Thanks for that question, it points me to some problems, with
imposition. I work on some tools for that.  If you are interest in
details using the the pstools I can send you a more detailed
description.

From groff-admin  Fri Jul 14 02:03:54 2000
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id CAA19054
	for <groff@ffii.org>; Fri, 14 Jul 2000 02:03:53 +0200
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id UAA07911;
	Thu, 13 Jul 2000 20:19:04 -0400 (EDT)
Received: from sol.eng.fore.com (sol.pit.comms.marconi.com [169.144.155.73])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id UAA16735;
	Thu, 13 Jul 2000 20:19:05 -0400 (EDT)
Received: from pss-pc.eng.fore.com (root@pss-pc [169.144.32.90])
	by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id UAA22422;
	Thu, 13 Jul 2000 20:19:04 -0400 (EDT)
Received: from pss-pc.eng.fore.com (IDENT:pss@localhost [127.0.0.1])
	by pss-pc.eng.fore.com (8.9.3/8.8.7) with ESMTP id UAA19215;
	Thu, 13 Jul 2000 20:22:16 -0400
Message-Id: <200007140022.UAA19215@pss-pc.eng.fore.com>
To: Bernd Salbrechter <bernd@mycity.at>
cc: groff@ffii.org, pragnesh.sampat@marconi.com
Subject: Re: [Groff] .TC in the groff mm macros 
In-Reply-To: Message from Bernd Salbrechter <bernd@mycity.at> 
   of "Thu, 13 Jul 2000 22:34:45 +0200."
	<200007132034.WAA00321@schleppo.sun.universe>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 13 Jul 2000 20:22:16 -0400
From: Pragnesh Sampat <pss@fore.com>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 997
Lines: 24

> Sorry I didn't have used the mm macros, but have looked at the manpage
> and the code. From what I read there the two passes only used for
> cross-references and not for reordering the table of content pages.
> 
> Dose taking the table of content pages from the end of the printout and
> insert it after the cover page not working for you? Or do you imposition
> for printing on better devices than a Hp-Laserjet (i.e. a Linotronic :-)?
> If the later, you will have PostScript output, where you can use pstools
> to reorder the pages, but that require a separate page numbering of the
> front matter (Table of Content).

Thanks for your response.

Yes, when I print it, I put the TOC in the right place.  But this file will be
used by others internally, converted to pdf etc., so it would be nice if I
don't have to tell people that they should remember to take the TOC from back
and put it in the right place.

I will look around some more and try to find your reference.

Thanks,

-Pragnesh


From groff-admin  Fri Jul 14 16:23:19 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id QAA26532
	for <Groff@ffii.org>; Fri, 14 Jul 2000 16:23:14 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AB23706 for Groff@ffii.org; Fri, 14 Jul 2000 16:37:57 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Fri, 14 Jul 2000 10:20:29 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Ted.Harding@nessie.mcc.ac.uk
Cc: Groff@ffii.org
Subject: Re: [Groff] refer macros
In-Reply-To: <XFMail.000712234825.Ted.Harding@nessie.mcc.ac.uk>
Message-Id: <Pine.LNX.4.10.10007132050030.365-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1351
Lines: 37

Hello Ted, hello all,

Yesterday, Ted.Harding@nessie.mcc.ac.uk schrieb:

[snip]
> - UNIX 'refer' does not honour multiple %E fields ("editor"), while
>   'bib' allows multiple editors like multiple authors. I'm not sure
>   about how groff 'refer' behaves in this respect: the man page hints
>   that it might allow multiple %Es, but I never tried it.

It does. I tried it.

> Most of these differences are quite minor, and the only cases which
> could cause trouble in moving from 'refer' to 'bib' are %L and %Q,
> 
> However, the manner of planting citations in the text is quite different.
> 
> So I'm a bit puzzled by "it requires (from what I can see) a complete
> re-organization of the bibliographic database" (unless, of course,
> you are referring to the citations).

Maybe I was unclear. The format is the same, but from what I can
see the way the database is different (and more rational): basically,
the database is built upon multiple data tables (publications, journals,
etc. etc.); I might be wrong - but it requires some re-organization.
In the end, you use less re-writing, which is better, but in the beginning
it requres more work. I will look bib in more depth, but now I have to
finish my paper... :) Thanks again Ted!

Nicola

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+



From groff-admin  Thu Jul 20 22:10:03 2000
Received: from RSMTP.mycity.at (cybertron035.cybertron.at [212.236.73.35] (may be forged))
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA24889
	for <groff@ffii.org>; Thu, 20 Jul 2000 22:10:03 +0200
X-Authentication-Warning: genba.ffii.org: Host cybertron035.cybertron.at [212.236.73.35] (may be forged) claimed to be RSMTP.mycity.at
Received: from schleppo.sun.universe (baden-remote18.mycity.at [212.236.73.210])
	by RSMTP.mycity.at (8.9.3/8.9.3) with ESMTP id WAA27595
	for <groff@ffii.org>; Thu, 20 Jul 2000 22:25:17 +0200
Received: (from salb@localhost)
	by schleppo.sun.universe (8.8.8/8.8.8) id WAA00506
	for groff@ffii.org; Thu, 20 Jul 2000 22:21:40 +0200 (CEST)
Date: Thu, 20 Jul 2000 22:21:40 +0200 (CEST)
From: Bernd Salbrechter <bernd@mycity.at>
Message-Id: <200007202021.WAA00506@schleppo.sun.universe>
To: groff@ffii.org
Subject: [Groff] Page classes in groff output to support reordering of the pages.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2634
Lines: 65

Hi all!

I am playing around with imposition of groff generated pages (PostScript).

In more detail the idea is to use groff to format a document into
well layouted pages (groff do this job quite well) and use the
pstools to put may of that pages onto one sheet of paper, which
get folded, stitched and trimmed to get nice booklets. The "pstools"
need some improvement at least for no so common impositions like
gate fold, concertina fold or 8 pages on one sheet of paper and a
64 page signature.

Pragnesh Sampat <pss@fore.com> question from Wed, 12 Jul 2000
08:41:14 -0400 pointed me to an groff related problem with that
idea.

> Has anyone used the .TC command and used to 2 groff passes to get the Table Of
> Contents in the right place in the postscript output?  The groff_mm man mage
> mentions this, but I have not tried it yet.  I am using a .TC at the end and
> get a decent contents page at the end.  Thanks,
> 
> -Pragnesh

Wouldn't it be a nice feature to include a page class into the
output. This could be put in the %%Page: comment of the PostScript output
for example. Where it can be used to reorder the pages before printing it
(The pstools didn't have such a tool yet, but it would be easy to add).

A short example for what groff should produce as PostScript (prolog,
trailer and content striped):
  %%Page: Cover.1 1
  %%Page: Body.1 2
  %%Page: Body.2 3
  %%Page: Body.3 4
  %%Page: Body.4 5
  %%Page: TableOfContence.1 6
  %%Page: TableOfContence.2 7
  %%Page: ListOfFigures.1 8
  %%Page: Index.1 9
  %%Page: Index.2 10

If the policity is to print the Cover, TableOfContence, ListOfFigures,
Body and Index in that order and start each on a odd Page. The pages
can be easy reordered with that information as well as filler pages can
be included.

Yes this needs a new interface from the macros to the groff backend.
But couldn't it be done with a additional variable handled like the
page number (not directly set!), which content groff passes to the
backend.

It wouldn't work if the parts are not numbered independent, but in
that case only a two pass solution would work.

Any thought
Bernd

PS.: I have noticed that you have switched to libpaper to get the
paper format, but thats not really solution of the problem.  The user
have to recompile it or worse all tools that use it, if he wants
to add his very private strange format.  I would suggest to use a
full featured paper capability database (like termcap and in the
same format). I started one, but use the BSD access routines. If
you are interest in it (A, B, C and D formats from 0 to 10 and
several US formats already collected) I can upload it.

From groff-admin  Fri Jul 21 10:41:23 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id KAA19549
	for <Groff@ffii.org>; Fri, 21 Jul 2000 10:41:14 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA21130 for Groff@ffii.org; Fri, 21 Jul 2000 10:55:40 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Fri, 21 Jul 2000 10:50:25 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Groff@ffii.org
Message-Id: <Pine.LNX.4.10.10007211043180.443-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] pic does not work any longer
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1878
Lines: 75

Dear Friends,

I use a lot pic as an algorithmic drawing language.
I am having problems with the latest CVS version of pic (tagged 1.16).
A very (very) simple pic script like this one:

	.PS
	scale=2.54
	.PE

does not get groked any longer by the pic preprocessor. It says:

./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: parse error before `='
./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: giving up on this picture
.lf 1 /usr/local/user/nicb/tr/tmp/test.pic
.lf 1
.lf 4

The version right before this one is groff-20000311 and it works as usual.
A diff -BbNu between the two versions gives:

--- pic.h	Sun Feb  6 10:38:22 2000
+++ ../pic-new-and-broken/pic.h	Sun Jul  9 08:38:05 2000
@@ -24,11 +24,11 @@
 #include <stdlib.h>
 #include <errno.h>
 
-#ifndef MATH_H_DECLARES_HYPOT
+#ifdef NEED_DECLARATION_HYPOT
 extern "C" {
   double hypot(double, double);
 }
-#endif
+#endif /* NEED_DECLARATION_HYPOT */
 
 #include "assert.h"
 #include "cset.h"
--- pic.y	Sun Feb  6 10:38:27 2000
+++ ../pic-new-and-broken/pic.y	Fri Jun  9 06:35:17 2000
@@ -40,7 +40,11 @@
 #undef srand
 extern "C" {
   int rand();
+#ifdef RET_TYPE_SRAND_IS_VOID
   void srand(unsigned int);
+#else
+  int srand(unsigned int);
+#endif
 }
 
 /* Maximum number of characters produced by printf("%g") */
--- lex.cc	Sun Feb  6 10:38:10 2000
+++ ../pic-new-and-broken/lex.cc	Sun Jul  9 08:38:04 2000
@@ -21,7 +21,7 @@
 #include "pic.h"
 #include "ptable.h"
 #include "object.h"
-#include "pic.tab.h"
+#include "pic_tab.h"
 
 declare_ptable(char)
 implement_ptable(char)
-8<---------------------------------------------------------------------

I cannot make head of tails out of this, so I restored the old version
of pic (thanks god we have CVS!) - but I want to submit this to the list...

Thanks a lot

Nicola
+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+


From groff-admin  Fri Jul 21 11:08:17 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id LAA21407
	for <groff@ffii.org>; Fri, 21 Jul 2000 11:08:17 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13FZ2V-0004qn-00; Fri, 21 Jul 2000 10:24:16 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id KAA02675;
	Fri, 21 Jul 2000 10:22:45 +0100
Message-ID: <XFMail.000721102245.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200007202021.WAA00506@schleppo.sun.universe>
Date: Fri, 21 Jul 2000 10:22:45 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Bernd Salbrechter <bernd@mycity.at>
Subject: RE: [Groff] Page classes in groff output to support reordering o
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3372
Lines: 71

On 20-Jul-00 Bernd Salbrechter wrote:
> 
> I am playing around with imposition of groff generated pages
> (PostScript).
> 
> In more detail the idea is to use groff to format a document into
> well layouted pages (groff do this job quite well) and use the
> pstools to put may of that pages onto one sheet of paper, which
> get folded, stitched and trimmed to get nice booklets. The "pstools"
> need some improvement at least for no so common impositions like
> gate fold, concertina fold or 8 pages on one sheet of paper and a
> 64 page signature.

In my view it is probably not a good idea to try to incorporate this
kind of thing into groff itself. The way the main engine (gtroff) works
is strictly sequential and pages get formatted as they are encountered,
so it would need to take place either as a modification of the grops
post-processor, or in an extra post-processor placed between gtroff
and grops or following grops. The last case is, in effect, what you
are trying to do with pstools.

[By the way, is what you mean by "pstools" the same as "psutils",
which is a package I have. Below I shall refer to "psutils".]

Putting an extra post-processor between gtroff and grops would probably
not work, for all sorts of reasons, and similarly for a modification
of grops which was not equivalent to a post-processor following grops.

Furthermore, once you contemplate re-ordering pages for special purposes
there is no limit to the possible variations you may need to consider.

So my considered view is that this kind of thing is best done using
a psutils-like utility which operates directly on the PS output
from grops, whether this is a new program or an extension of pstools
itself.

One feature of groff which could be useful for this is the possibility of
selecting which pages get output by groff: the -o option does this.
For instance, -o1,3,5,7,9 would output these odd-numbered pages,
-o2,4,6,8 these even-numbered pages, etc. If anything, I would agree
that an extension to this option which gave ALL odd, or ALL even
pages without explicit listing, could be useful. However, this is already
possible in psutils [psselect] so I don't see its necessity as pressing.

Psutils has the following main programs:

psbook          rearranges pages into signatures
psselect        selects pages and page ranges
pstops          performs general page rearrangement and selection
psnup           put multiple pages per physical sheet of paper
psresize        alter document paper size
epsffit         fits an EPSF file to a given bounding box

and several perl scripts to perform various useful/necessary minor
tasks.

Another option you could consider might be (e.g. using "psselect" and
a script) to pull out each page of the final groff output as a separate
PostScript file. Each of these, since it will have a %%BoundingBox
for the whole page, should be a valid EPS file which you can then import
(even using groff!) into a document where the layout of the original
pages on the final pages is exactly what you want, for whatever purpose.

I hope this helps.
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 21-Jul-00                                       Time: 10:22:45
------------------------------ XFMail ------------------------------

From groff-admin  Fri Jul 21 12:23:49 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA27254
	for <Groff@ffii.org>; Fri, 21 Jul 2000 12:23:48 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 21 Jul 2000 12:39:30 +0200
Received: from rigel.univie.ac.at (dial-143166.HRZ.Uni-Dortmund.DE [129.217.143.166])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id MAA24883;
	Fri, 21 Jul 2000 12:39:28 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id MAA11671;
	Fri, 21 Jul 2000 12:39:17 +0200
Date: Fri, 21 Jul 2000 12:39:16 +0200 (CEST)
Message-Id: <20000721.123916.21382283.sx0005@gnu.org>
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] pic does not work any longer
From: Werner LEMBERG <sx0005@studserver.uni-dortmund.de>
In-Reply-To: <Pine.LNX.4.10.10007211043180.443-100000@ax-nicb.axnet.it>
References: <Pine.LNX.4.10.10007211043180.443-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.95b43 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 293
Lines: 11

> ./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: parse error before `='
> ./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: giving up on this picture
> .lf 1 /usr/local/user/nicb/tr/tmp/test.pic
> .lf 1
> .lf 4

I can't repeat this problem on my Linux box.  Which platform do you
use?


    Werner

From groff-admin  Fri Jul 21 15:12:44 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id PAA06659
	for <Groff@ffii.org>; Fri, 21 Jul 2000 15:12:40 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA00237 for Groff@ffii.org; Fri, 21 Jul 2000 15:28:42 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Fri, 21 Jul 2000 15:27:52 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Werner LEMBERG <wl@gnu.org>
Cc: Groff@ffii.org
Subject: Re: [Groff] pic does not work any longer
In-Reply-To: <20000721.123916.21382283.sx0005@gnu.org>
Message-Id: <Pine.LNX.4.10.10007211524160.443-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 808
Lines: 32

Today, Werner LEMBERG schrieb:

> 
> > ./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: parse error before `='
> > ./pic:/usr/local/user/nicb/tr/tmp/test.pic:2: giving up on this picture
> > .lf 1 /usr/local/user/nicb/tr/tmp/test.pic
> > .lf 1
> > .lf 4
> 
> I can't repeat this problem on my Linux box.  Which platform do you
> use?

I use linux 2.2.14 (a Slackware descendant), and the following tools:

gcc version pgcc-2.95.2 19991024 (release)
flex version 2.5.4
GNU Bison version 1.25
glibc-2.1.1

This problem happens with the current groff sitting in the CVS repository.
Reverting to the version tagged 20000311 of the pic directory eliminates
the problem - using the same tools...

Thank you

Nicola

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+


From groff-admin  Fri Jul 21 18:38:45 2000
Received: from bitmover.com (IDENT:root@bitmover.com [207.181.251.162])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA09645
	for <groff@ffii.org>; Fri, 21 Jul 2000 18:38:44 +0200
Received: from work.bitmover.com (root@work.bitmover.com [10.3.9.4])
	by bitmover.com (8.8.7/8.8.7) with ESMTP id JAA17575
	for <groff@ffii.org>; Fri, 21 Jul 2000 09:54:47 -0700
Received: (from lm@localhost)
	by work.bitmover.com (8.9.3/8.9.3) id JAA04758
	for groff@ffii.org; Fri, 21 Jul 2000 09:54:47 -0700
Date: Fri, 21 Jul 2000 09:54:47 -0700
From: Larry McVoy <lm@bitmover.com>
To: groff@ffii.org
Message-ID: <20000721095447.B4742@work.bitmover.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
Subject: [Groff] I'm building groff docs
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 593
Lines: 14

Hi, I'm a long time *roff user and recently got revved up about this again,
my company is doing their docs in groff.  

I tracked down the v7 docs and ask Dennis Ritchie if it would be OK to
update them for groff and he said he thought it would be fine as long as
we attributed them to the original authors (which is of course OK by me).

So I'm working through them all one at a time and I'll be making them 
available for redistribution with future versions of groff.

Just thought you'd like to know.
-- 
---
Larry McVoy            	   lm@bitmover.com           http://www.bitmover.com/lm 

From groff-admin  Fri Jul 21 20:36:50 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA10791
	for <groff@ffii.org>; Fri, 21 Jul 2000 20:36:50 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13Fhul-000M0C-00; Fri, 21 Jul 2000 19:52:52 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id TAA02711;
	Fri, 21 Jul 2000 19:50:50 +0100
Message-ID: <XFMail.000721195050.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000721095447.B4742@work.bitmover.com>
Date: Fri, 21 Jul 2000 19:50:50 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Larry McVoy <lm@bitmover.com>
Subject: RE: [Groff] I'm building groff docs
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2962
Lines: 69

Hi again Larry,

On 21-Jul-00 Larry McVoy wrote:
> Hi, I'm a long time *roff user and recently got revved up about this
> again,my company is doing their docs in groff.

Good to hear!

> I tracked down the v7 docs and ask Dennis Ritchie if it would be OK to
> update them for groff and he said he thought it would be fine as long
> as we attributed them to the original authors (which is of course OK by
> me).
> 
> So I'm working through them all one at a time and I'll be making them 
> available for redistribution with future versions of groff.

I should let you know that this is a project I have been working on for
quite a while, though perhaps not on identical lines. My strategy is:

1. Re-write the Ossanna & Ritchie "Troff User's Manual" for gtroff
     (1982 "ditroff" edition)
2. Write complete man-pages for all the components of groff
3. Write/rewrite user's manuals for tbl, pic, eqn, maybe refer etc.

The above would be build on the traditional UNIX manuals (mainly because
these were so well written in the first place, and are excellent
references for experienced users).

4. Write additional users' manuals (e.g. tips, tricks, methods, ...,
     especially with usable information for advanced macro writing, etc).

5. Documentation for the use of non-groff programs in conjunction
     with groff (e.g. "makeindex" for indexing and TOC, "bib" for
     bibliographies, etc).

(1) above is quite far advanced. (2) has made some progress.
(3) has made patchy progress. (4) exists in the shape of a somewhat
random assortment of pieces. (5) exists in the shape of well-arranged
but not-written-up material.

Apart from (1) (which is well advanced) I'm not envisaging that I
would do all the work myself! Input from well-informed good writers
on any of it would be most welcome. However, I have pretty clear
ideas as to how I would like it all to appear at the end of the day:
this mainly aspires to achieve the clarity and conciseness of the
traditional UNIX documentation, but with more comprehensive coverage
and with more in the way of well-posed user examples.

This is why I started with (1): it structures everything you may ever
want to say about gtroff in a form which is excellent to refer to,
and I would like to get the rest done in a form which is compatible
with how (1) will turn out.

You have (correctly) got Ritchie's blessing for proceeding subject
to due acknowledgement, which is what I planned to do too before
releasing any of this stuff. I'd be grateful, therefore, if you could
let me know how to get in touch with him.

> Just thought you'd like to know.

Yes indeed! Many thanks, and let's all keep in touch on this.
Ted.


--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 21-Jul-00                                       Time: 19:50:50
------------------------------ XFMail ------------------------------

From groff-admin  Fri Jul 21 20:45:14 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA10895
	for <Groff@ffii.org>; Fri, 21 Jul 2000 20:45:13 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 21 Jul 2000 21:01:14 +0200
Received: from rigel.univie.ac.at (dial-143180.HRZ.Uni-Dortmund.DE [129.217.143.180])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id VAA12763;
	Fri, 21 Jul 2000 21:01:13 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id UAA19401;
	Fri, 21 Jul 2000 20:40:50 +0200
Date: Fri, 21 Jul 2000 20:40:49 +0200 (CEST)
Message-Id: <20000721.204049.118971130.sx0005@gnu.org>
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] pic does not work any longer
From: Werner LEMBERG <sx0005@studserver.uni-dortmund.de>
In-Reply-To: <Pine.LNX.4.10.10007211524160.443-100000@ax-nicb.axnet.it>
References: <20000721.123916.21382283.sx0005@gnu.org>
	<Pine.LNX.4.10.10007211524160.443-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.95b43 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 982
Lines: 30

> > I can't repeat this problem on my Linux box.  Which platform do you
> > use?
> 
> I use linux 2.2.14 (a Slackware descendant), and the following tools:
> 
> gcc version pgcc-2.95.2 19991024 (release)
> flex version 2.5.4
> GNU Bison version 1.25
> glibc-2.1.1

Except glibc (I have version 2.1.3) I have the same versions.  Very
strange.

> This problem happens with the current groff sitting in the CVS
> repository.  Reverting to the version tagged 20000311 of the pic
> directory eliminates the problem - using the same tools...

Due to my limited internet bandwidth (I'm sitting behind a 28.8k
modem) I don't have enough resources to do a complete check out
starting from scratch.  Using `cvs -z9 update -dP' shows that
everything is up to date in my local copy of the CVS.

I even did a `make realclean' to force the use of bison etc., and
everything is OK.

Maybe you have some other version of pic somewhere in the path which
probably doesn't fit your DLLs?


    Werner

From groff-admin  Fri Jul 21 21:42:38 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA11369
	for <groff@ffii.org>; Fri, 21 Jul 2000 21:42:37 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 21 Jul 2000 21:58:33 +0200
Received: from rigel.univie.ac.at (dial-143197.HRZ.Uni-Dortmund.DE [129.217.143.197])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id VAA13491;
	Fri, 21 Jul 2000 21:58:31 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id VAA19512;
	Fri, 21 Jul 2000 21:42:17 +0200
Date: Fri, 21 Jul 2000 21:42:17 +0200 (CEST)
Message-Id: <20000721.214217.17851667.sx0005@gnu.org>
To: lm@bitmover.com
Cc: groff@ffii.org
Subject: Re: [Groff] I'm building groff docs
From: Werner LEMBERG <sx0005@studserver.uni-dortmund.de>
In-Reply-To: <20000721095447.B4742@work.bitmover.com>
References: <20000721095447.B4742@work.bitmover.com>
X-Mailer: Mew version 1.95b43 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 361
Lines: 10

> I tracked down the v7 docs and ask Dennis Ritchie if it would be OK
> to update them for groff and he said he thought it would be fine as
> long as we attributed them to the original authors (which is of
> course OK by me).

Everything which is contributed to groff is fine!  But please excuse
my ignorance -- what exactly are you talking about?


    Werner

From groff-admin  Fri Jul 21 21:45:00 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id VAA11389
	for <Groff@ffii.org>; Fri, 21 Jul 2000 21:44:59 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA09520 for Groff@ffii.org; Fri, 21 Jul 2000 22:01:03 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Fri, 21 Jul 2000 22:04:40 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Werner LEMBERG <wl@gnu.org>
Cc: Groff@ffii.org
Subject: Re: [Groff] pic does not work any longer
In-Reply-To: <20000721.204049.118971130.sx0005@gnu.org>
Message-Id: <Pine.LNX.4.10.10007212200100.443-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 955
Lines: 31

Today, Werner LEMBERG schrieb:

[snip]
> Due to my limited internet bandwidth (I'm sitting behind a 28.8k
> modem) I don't have enough resources to do a complete check out
> starting from scratch.  Using `cvs -z9 update -dP' shows that
> everything is up to date in my local copy of the CVS.

I'm sitting on a 9600 line over a cellular phone right now! :)
But I moved the newer pic distribution to another name, and then
pulled out again the old distribution using cvs -z9 co groff/src/preproc/pic.
So I have both right now (that's how I compared them).

[snip]
> Maybe you have some other version of pic somewhere in the path which
> probably doesn't fit your DLLs?

no. I'm currently tried with the compiled versions (uninstalled) running
./pic <file> etc.

ah well, I'll search into this: I'll try with gdb (little hope, though).

Thanks again

nicb

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+


From groff-admin  Fri Jul 21 23:22:48 2000
Received: from bitmover.com (IDENT:root@bitmover.com [207.181.251.162])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA12459
	for <groff@ffii.org>; Fri, 21 Jul 2000 23:22:47 +0200
Received: from work.bitmover.com (root@work.bitmover.com [10.3.9.4])
	by bitmover.com (8.8.7/8.8.7) with ESMTP id OAA21500;
	Fri, 21 Jul 2000 14:38:50 -0700
Received: (from lm@localhost)
	by work.bitmover.com (8.9.3/8.9.3) id OAA12605;
	Fri, 21 Jul 2000 14:38:50 -0700
Date: Fri, 21 Jul 2000 14:38:50 -0700
From: Larry McVoy <lm@bitmover.com>
To: Werner LEMBERG <wl@gnu.org>
Cc: groff@ffii.org
Subject: Re: [Groff] I'm building groff docs
Message-ID: <20000721143850.A12591@work.bitmover.com>
References: <20000721095447.B4742@work.bitmover.com> <20000721.214217.17851667.sx0005@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <20000721.214217.17851667.sx0005@gnu.org>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1311
Lines: 34

On Fri, Jul 21, 2000 at 09:42:17PM +0200, Werner LEMBERG wrote:
> 
> > I tracked down the v7 docs and ask Dennis Ritchie if it would be OK
> > to update them for groff and he said he thought it would be fine as
> > long as we attributed them to the original authors (which is of
> > course OK by me).
> 
> Everything which is contributed to groff is fine!  But please excuse
> my ignorance -- what exactly are you talking about?

Taking the original V7 troff documentation, i.e.,
	Troff Users Manual
	Troff tutorial
	Tbl manual
	Eqn manual
	ESR's version of the PIC manual
	Refer manual
	Bib manual
Putting them under revision control (BitKeeper), 
making changes so that they format under groff,
add information about what groff does that the originals didn't do,
add in a collection of ``stupid groff tricks'' (which aren't so
stupid, examples of color support, how to escape to postscript,
examples of image inclusion, etc),
ideally, add in Rich Steven's scripts for writing books in troff,
and print the whole mess and make it available in source and .ps form.

Should be done tomorrow :-)

So far, I have everything under version control and printing under groff.
I can make that repository available if people like.
-- 
---
Larry McVoy            	   lm@bitmover.com           http://www.bitmover.com/lm 

From groff-admin  Sat Jul 22 10:56:26 2000
Received: from RSMTP.mycity.at (cybertron035.cybertron.at [212.236.73.35] (may be forged))
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA22193
	for <groff@ffii.org>; Sat, 22 Jul 2000 10:56:25 +0200
X-Authentication-Warning: genba.ffii.org: Host cybertron035.cybertron.at [212.236.73.35] (may be forged) claimed to be RSMTP.mycity.at
Received: from schleppo.sun.universe (baden-remote08.mycity.at [212.236.73.200])
	by RSMTP.mycity.at (8.9.3/8.9.3) with ESMTP id LAA29364;
	Sat, 22 Jul 2000 11:11:21 +0200
Received: (from salb@localhost)
	by schleppo.sun.universe (8.8.8/8.8.8) id LAA01492;
	Sat, 22 Jul 2000 11:12:20 +0200 (CEST)
Date: Sat, 22 Jul 2000 11:12:20 +0200 (CEST)
From: Bernd Salbrechter <bernd@mycity.at>
Message-Id: <200007220912.LAA01492@schleppo.sun.universe>
To: Ted.Harding@nessie.mcc.ac.uk
Subject: RE: [Groff] Page classes in groff output to support reordering o
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3153
Lines: 66

On 21 Jul 2000 Ted Harding wrote:

> On 20-Jul-00 Bernd Salbrechter wrote:
> > 
> > I am playing around with imposition of groff generated pages
> > (PostScript).
> > 
> > In more detail the idea is to use groff to format a document into
> > well layouted pages (groff do this job quite well) and use the
> > pstools to put may of that pages onto one sheet of paper, which
> > get folded, stitched and trimmed to get nice booklets. The "pstools"
> > need some improvement at least for no so common impositions like
> > gate fold, concertina fold or 8 pages on one sheet of paper and a
> > 64 page signature.
> 
> In my view it is probably not a good idea to try to incorporate this
> kind of thing into groff itself. The way the main engine (gtroff) works
> is strictly sequential and pages get formatted as they are encountered,
> so it would need to take place either as a modification of the grops
> post-processor, or in an extra post-processor placed between gtroff
> and grops or following grops. The last case is, in effect, what you
> are trying to do with pstools.

Maybe I was no clear her. I want to write a new program (using
parts of the psutils) with better support for fancier impositions
than the existing parts of pstools have. groff should only produce
a sequence of nice formated pages, which it do very well. I want
to use on the the PostScript output.

> [By the way, is what you mean by "pstools" the same as "psutils",
> which is a package I have. Below I shall refer to "psutils".]

Yes, you are right the correct name of the package is "psutils".

> Putting an extra post-processor between gtroff and grops would probably
> not work, for all sorts of reasons, and similarly for a modification
> of grops which was not equivalent to a post-processor following grops.
> 
> Furthermore, once you contemplate re-ordering pages for special purposes
> there is no limit to the possible variations you may need to consider.

Yes, thats the reason, why I want to put the description of the
reordering in an external database (ASCII ala termcap). And thats
the area were the psutils are week.

> So my considered view is that this kind of thing is best done using
> a psutils-like utility which operates directly on the PS output
> from grops, whether this is a new program or an extension of pstools
> itself.

I want to go this way, but the essence of my question was to improve
the "%%Page:" comment grops leave for this tools in it's output.
The DSC (Document Structuring Conventions) describe the "%%Page:"
entry as "%%Page: <label> <sequence>". Where the <label> is a free
formatted page description and the <sequence> is a strict sequential
numbering of the pages. grops actually use the same value for <label>
and <sequence>. A psutils-like utility could be much more powerful,
if it can identify several classes of pages (i.e. Cover, Body, Table
of Contence, ...), thats was what I ask for. For an example look
in my original message.

Bernd

PS.: I have already running some step and repeat impositions and
some 3*2 concertina fold impositions for loose leave binding. All
with "pstops" and hand calculated order and position.

From groff-admin  Sat Jul 22 11:59:07 2000
Received: from TK212017118241.teleweb.at (IDENT:postfix@TK212017118241.teleweb.at [212.17.118.241])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id LAA22594
	for <groff@ffii.org>; Sat, 22 Jul 2000 11:59:07 +0200
Received: by TK212017118241.teleweb.at (Postfix, from userid 501)
	id 1CDE044B2; Sat, 22 Jul 2000 12:15:11 +0200 (CEST)
Date: Sat, 22 Jul 2000 12:15:11 +0200
From: Leonard Stiles <ljs@uk2.net>
To: groff@ffii.org
Message-ID: <20000722121511.A1148@TK212017118241.teleweb.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
Subject: [Groff] pic solid attribute
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 416
Lines: 16

Is it just me or does gpic not support the "solid" attribute?
For example, this code produces an error (using groff 1.16):

.PS
circle solid
.PE

Eric Raymond's paper about gpic says something about solid not being 
supported yet, but it isn't mentioned in the TODO of groff 1.16 - has 
it just been forgotten?

-- 
+------------------------------+
| Leonard Stiles <ljs@uk2.net> |
+------------------------------+


From groff-admin  Sat Jul 22 13:27:20 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id NAA23228
	for <groff@ffii.org>; Sat, 22 Jul 2000 13:27:20 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13Fxgk-0007Eg-00; Sat, 22 Jul 2000 12:43:27 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id MAA06452;
	Sat, 22 Jul 2000 12:39:44 +0100
Message-ID: <XFMail.000722123944.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200007220912.LAA01492@schleppo.sun.universe>
Date: Sat, 22 Jul 2000 12:39:44 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Bernd Salbrechter <bernd@mycity.at>
Subject: RE: [Groff] Page classes in groff output to support reordering o
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 4589
Lines: 113

Thanks, Bernd, it is much clearer now.

On 22-Jul-00 Bernd Salbrechter wrote:
> I want to go this way, but the essence of my question was to improve
> the "%%Page:" comment grops leave for this tools in it's output.
> The DSC (Document Structuring Conventions) describe the "%%Page:"
> entry as "%%Page: <label> <sequence>". Where the <label> is a free
> formatted page description and the <sequence> is a strict sequential
> numbering of the pages. grops actually use the same value for <label>
> and <sequence>. A psutils-like utility could be much more powerful,
> if it can identify several classes of pages (i.e. Cover, Body, Table
> of Contence, ...), thats was what I ask for. For an example look
> in my original message.

In fact, grops in certain cases will have a different <label> and
<sequence>. For instance, you can very straightforwardly create
a source file which starts with "front matter", with page numbers
formatted as i, ii, iii, , ... beginning the document with the command

.af PN i

(for ms macros) and then later continue with main text pages formatted
as 1, 2, 3, ... beginning this section with the commands

.af PN 1
.bp 1

In that case, the %%Page: comments would be like

%%Page: 1 1
%%Page: 2 2
...
%%Page: 9 9
%%Page: 1 10
%%Page: 2 11
...

and this, for instance, is how the page numbers would show in
the "gv" page-panel (i.e. as 1 2 ... 9 1 2 ... ).

If you look at the source code in grops.cc, you will find

void ps_printer::begin_page(int n)
{
  out.begin_comment("Page:").comment_arg(itoa(n));
  out.comment_arg(itoa(++pages_output)).end_comment();

showing that the first comment_arg is "n" (the value of \n%, the
logical page number), i.e. the <label>, while the second is
++pages_output, i.e. a count of the number of physical pages output,
the <sequence>.

Nevertheless, as can be seen from the code in /libgroff/itoa.c,
the <label> is still formatted by groff as "arabic" (1, 2, 3, ... ),
and not (as one would probably wish) as i, ii, iii, ... .

So this is a shortcoming of grops to start with, independently of
your wish to use <label> to distinguish page classes.

Therefore there would seems to be a case for extending the functionality
of the way grops creates the %%Page: <label> <sequence> comment.
However, at present there is no specific mechanism for gtroff to
communicate its "%%Page:" wishes to grops. The gtroff output language
(see man groff_out) does not describe any extension to ditroff output in
this respect, so that the only relevant output is ditroff's "pn", meaning
"new page n begins" where n is the ASCII decimal representation of
the next page number (i.e. "arabic"). So <label> is computed as the
ASCII decimal representation of n, while <sequence> is computed as the
ASCII decimal representation of the physical page count.

Possibly the most straightforward mechanism would be to extend the
\X'ps: ...' mechanism (with corresponding implementation code in grops).

In that case, the following suggestions seem to me to be feasible:

1. A new \X'ps: ...' command like
   \X'ps: pagenumformat F' where F may be as in troff .af, namely
   1 001 i I a A

   This would at least require the void ps_printer::begin_page(int n)
   function (above) to be re-written so that the formatting of n
   is done by a different routing (capable of achieving format F)
   instead of itoa(n).

2. A new X'ps: ...' command like
   \X'ps: pagelabel F text' where F is as above and "text" is
   whatever the user wants (e.g. TOC, Author Index, Bibliography ... ).
   This could presumably be used instead of or in addition to the
   suggestion in (1).

   This would require an additional re-writing of the function
   ps_printer::begin_page(int n) to be something like
   ps_printer::begin_page(int n, char *F, char *text)
   with appropriate support code.

Meanwhile, I think for practical purposes it should not be too
difficult to simply do what you are now doing, namely determining
independently what page-numbers correspond to the different classes,
and using say pstops to extract these when the page-list is submitted
via an argument to pstops.

However, you have raised an interesting and by no means entirely
cosmetic issue about groff. It would be good to see other users'
comments on these questions.

Best wishes to all,
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 22-Jul-00                                       Time: 12:39:44
------------------------------ XFMail ------------------------------

From groff-admin  Sat Jul 22 14:08:41 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id OAA23504
	for <groff@ffii.org>; Sat, 22 Jul 2000 14:08:41 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13FyKm-0007WO-00; Sat, 22 Jul 2000 13:24:49 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id NAA07465;
	Sat, 22 Jul 2000 13:23:22 +0100
Message-ID: <XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000722121511.A1148@TK212017118241.teleweb.at>
Date: Sat, 22 Jul 2000 13:23:22 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Leonard Stiles <ljs@uk2.net>
Subject: RE: [Groff] pic solid attribute
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1331
Lines: 35

On 22-Jul-00 Leonard Stiles wrote:
> Is it just me or does gpic not support the "solid" attribute?
> For example, this code produces an error (using groff 1.16):
> 
> .PS
> circle solid
> .PE
> 
> Eric Raymond's paper about gpic says something about solid not being 
> supported yet, but it isn't mentioned in the TODO of groff 1.16 - has 
> it just been forgotten?

Can we have some backgrouns on this? I.e. what is "solid" supposed
to do? The 1991 PIC User Manual (Kernighan, Bell docs #116) gives
"solid" as an attribute in its "Reference Manual" Appendix, but it
is not mentioned anywhere else.

Maybe there is more info in something like the DWB documentation
(which I don't have).

Meanwhile, the source code of groff pic indicates that (internally)
"solid" is used for "solid lines" (as opposed to dashed or dotted)
which is the default for lines anyway unless explcitily given the
"dashed" or "dotted" attribute.

However, lex.cc for groff pic does not have "solid" in its list of
keywords, so it would not be recognised.

Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 22-Jul-00                                       Time: 13:23:22
------------------------------ XFMail ------------------------------

From groff-admin  Sat Jul 22 17:00:36 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA24407
	for <groff@ffii.org>; Sat, 22 Jul 2000 17:00:35 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13G119-0009VW-00
	for groff@ffii.org; Sat, 22 Jul 2000 16:16:44 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA12474;
	Sat, 22 Jul 2000 16:16:40 +0100
Message-ID: <XFMail.000722161640.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sat, 22 Jul 2000 16:16:40 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: groff@ffii.org
Subject: [Groff] "mkdoc" at Edinburgh University
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 506
Lines: 14

Groffers may be interested to look at the

  http://www.ee.ed.ac.uk/~memos/mkdoc

page (at the Dept of Electronics & Electrical Engineering,
University of Edinburgh) entitled "Document Preparation: mkdoc"

Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 22-Jul-00                                       Time: 16:16:40
------------------------------ XFMail ------------------------------

From groff-admin  Sat Jul 22 20:54:51 2000
Received: from tkb.mpl.com (IDENT:root@tkb.mpl.com [198.77.4.83])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA25763
	for <groff@ffii.org>; Sat, 22 Jul 2000 20:54:50 +0200
Received: from tkb.mpl.com (IDENT:tkb@tkb.mpl.com [198.77.4.83])
	by tkb.mpl.com (8.9.3/8.9.3) with ESMTP id PAA02453;
	Sat, 22 Jul 2000 15:09:23 -0400
From: "T. Kurt Bond" <tkb@tkb.mpl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14713.61795.723987.509617@tkb.mpl.com>
Date: Sat, 22 Jul 2000 15:09:23 -0400 (EDT)
To: Ted.Harding@nessie.mcc.ac.uk
Cc: Bernd Salbrechter <bernd@mycity.at>, groff@ffii.org
Subject: RE: [Groff] Page classes in groff output to support reordering o
In-Reply-To: <XFMail.000721102245.Ted.Harding@nessie.mcc.ac.uk>
References: <200007202021.WAA00506@schleppo.sun.universe>
	<XFMail.000721102245.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: VM 6.75 under Emacs 20.4.1
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3174
Lines: 72

On 20-Jul-00 Bernd Salbrechter wrote:
> In more detail the idea is to use groff to format a document into
> well layouted pages (groff do this job quite well) and use the
> pstools [he meant psutils] to put may of that pages onto one sheet
> of paper, which get folded, stitched and trimmed to get nice
> booklets. The "pstools" need some improvement at least for no so
> common impositions like gate fold, concertina fold or 8 pages on one
> sheet of paper and a 64 page signature.

(Ted Harding) writes:
> In my view it is probably not a good idea to try to incorporate this
> kind of thing into groff itself. 

I agree that the re-ordering itself should not be done in the gtroff
engine. 

> The way the main engine (gtroff) works is strictly sequential and
> pages get formatted as they are encountered, so it would need to
> take place either as a modification of the grops post-processor, or
> in an extra post-processor placed between gtroff and grops or
> following grops. The last case is, in effect, what you are trying to
> do with pstools.

[...]
> Putting an extra post-processor between gtroff and grops would probably
> not work, for all sorts of reasons, 

Could you expound on these reasons?  I've actually used a
simple-minded version of this to re-order pages in troff output.

While it might not work in the completely general case (multiple
resized logical pages per physical sheet), I can't see why it wouldn't
work for moving the table of contents and such around.  It looks like
in gtroff output the "p" command that starts a new page is always
followed with an "f" command to set the current font, so the pages
should be fairly independent.  And doing this in a filter between
gtroff and the device-specific post-processor would allow this
reordering to be done independently of the type of final output
device, so it would be useful not only for grops, but also grodvi,
grotty, grolj4, and grolbj.

Groff's output, with one command per line, is well suited for this;
some ditroff descendants (Unixware's, I think), on the other hand, put
multiple commands on one line, delimited only with whitespace, which
makes it harder.

For those who haven't looked at gtroff's output format before, it is
documented in the revised version of the Nroff/Troff manual

    CSTR #54, J. F. Ossanna, Nroff/Troff User's Manual, Bell Labs,
    1976. Revised by Brian Kernighan, 1992. 
    http://plan9.bell-labs.com/cm/cs/cstr/54.ps.gz

in section 22, with groff's additions documented in groff_out(5).

> and similarly for a modification
> of grops which was not equivalent to a post-processor following grops.
> 
> Furthermore, once you contemplate re-ordering pages for special purposes
> there is no limit to the possible variations you may need to consider.

True, but the common, indeed very common, desire to put the table of
contents, etc., into the proper place  in the document, seems to me to 
be very practical and useful.

The user would still have to indicate in some manner how where the
table of contents starts and ends, but this could be done
automatically by the (suitable modified) macro package, or manually.

-- 
T. Kurt Bond, tkb@tkb.mpl.com


From groff-admin  Sat Jul 22 21:38:48 2000
Received: from tkb.mpl.com (IDENT:root@tkb.mpl.com [198.77.4.83])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA26042
	for <groff@ffii.org>; Sat, 22 Jul 2000 21:38:47 +0200
Received: from tkb.mpl.com (IDENT:tkb@tkb.mpl.com [198.77.4.83])
	by tkb.mpl.com (8.9.3/8.9.3) with ESMTP id PAA02522;
	Sat, 22 Jul 2000 15:53:20 -0400
From: "T. Kurt Bond" <tkb@tkb.mpl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14713.64432.801768.960562@tkb.mpl.com>
Date: Sat, 22 Jul 2000 15:53:20 -0400 (EDT)
To: Ted.Harding@nessie.mcc.ac.uk
Cc: Bernd Salbrechter <bernd@mycity.at>, groff@ffii.org
Subject: RE: [Groff] Page classes in groff output to support reordering o
In-Reply-To: <XFMail.000722123944.Ted.Harding@nessie.mcc.ac.uk>
References: <200007220912.LAA01492@schleppo.sun.universe>
	<XFMail.000722123944.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: VM 6.75 under Emacs 20.4.1
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 4346
Lines: 114

(Ted Harding) writes:

[a very interesting and thorough discussion of the way DSC page labels
are created in postscript output by gtroff and grops.]

> Possibly the most straightforward mechanism would be to extend the
> \X'ps: ...' mechanism (with corresponding implementation code in
> grops).

Actually, I think something like this could be useful for all the
output backends for reordering.

> In that case, the following suggestions seem to me to be feasible:
> 
> 1. A new \X'ps: ...' command like
>    \X'ps: pagenumformat F' where F may be as in troff .af, namely
>    1 001 i I a A
> 
>    This would at least require the void ps_printer::begin_page(int n)
>    function (above) to be re-written so that the formatting of n
>    is done by a different routing (capable of achieving format F)
>    instead of itoa(n).
> 
> 2. A new X'ps: ...' command like
>    \X'ps: pagelabel F text' where F is as above and "text" is
>    whatever the user wants (e.g. TOC, Author Index, Bibliography ... ).
>    This could presumably be used instead of or in addition to the
>    suggestion in (1).
> 
>    This would require an additional re-writing of the function
>    ps_printer::begin_page(int n) to be something like
>    ps_printer::begin_page(int n, char *F, char *text)
>    with appropriate support code.
> 
> Meanwhile, I think for practical purposes it should not be too
> difficult to simply do what you are now doing, namely determining
> independently what page-numbers correspond to the different classes,
> and using say pstops to extract these when the page-list is submitted
> via an argument to pstops.
> 
> However, you have raised an interesting and by no means entirely
> cosmetic issue about groff. It would be good to see other users'
> comments on these questions.

The difficult thing to do automatically is to figure out where things
like the table of contents start and stop, so you can move them to the
beginning.  Since the user can do things like

    .bp 1
    Some random text here.
    .bp 10
    Some other random text here.
    .bp 1
    Yet more random text here.

you can't just have the macro package record the pages where the table
of contents started and ended, since other pages might have the same
page number.

It might be useful if gtroff had a predefined read-only number
register, say \n[.pp] (for physical page), that recorded the physical
page number independent of what \n% had.  This number would start at 1
and be increased by 1 at the start of each new page, regardless of
what the user has requested with .bp or .pn.  The "p" command in
gtroff output could be followed by something like

    x X page: 1 i 3

where "1" is the page number from \n%, "i" is the page number
according to the current current format for % requested by .af, and 
"3" is the physical page of the document.  (In this case, there was a
cover page and a copyright page before the table of contents started
on logical page "i", physical page "3".)

The macro packages could use this physical page number to uniquely
identify where a section starts and stops and reordering packages
could depend on it.

Reordering filters could operating on these 'x X page:' commands,
while grops could generate DSC comments from them for the postscript
otuput.  Other postprocessors could ignore them.

If macro packages were to output at the start of a new document part
something like

    x X part: cover
    x X part: body
    x X part: appendix
    x X part: TOC
    x X part: LOF
    x X part: LOI

a reordering filter could automatically reorder the output into a
user-specified order, perhaps like this:

    $ gtroff -ms input.ms | 
         reorder --order=cover,TOC,LOI,LOF,body,appendix |
         grops >output.ps

The grops postprocessor could use that to make DSC comments like
"%%Page: TOC-i 3" or "%%Page: BODY-1".

If gtroff had a writable predefined string, perhaps \*[.sect], 
that started out blank and was always output after the "p" command for
each page as the end of a "x X part:" command, the macro packages
could just set this and each page would be labeled, which would make 
reordering and labeling simpler for the postprocessors, at the expense
of more complication in gtroff.

I don't know if others would find these useful, but it's certainly
interesting to think about.
-- 
T. Kurt Bond, tkb@tkb.mpl.com


From groff-admin  Sat Jul 22 22:39:05 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA26371
	for <groff@ffii.org>; Sat, 22 Jul 2000 22:39:05 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 22 Jul 2000 22:55:14 +0200
Received: from rigel.univie.ac.at (dial-143131.HRZ.Uni-Dortmund.DE [129.217.143.131])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id WAA03773;
	Sat, 22 Jul 2000 22:55:11 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA01888;
	Sat, 22 Jul 2000 10:55:05 +0200
Date: Sat, 22 Jul 2000 10:55:04 +0200 (CEST)
Message-Id: <20000722.105504.52182672.sx0005@gnu.org>
To: lm@bitmover.com
Cc: groff@ffii.org
Subject: Re: [Groff] I'm building groff docs
From: Werner LEMBERG <sx0005@studserver.uni-dortmund.de>
In-Reply-To: <20000721143850.A12591@work.bitmover.com>
References: <20000721095447.B4742@work.bitmover.com>
	<20000721.214217.17851667.sx0005@gnu.org>
	<20000721143850.A12591@work.bitmover.com>
X-Mailer: Mew version 1.95b43 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 876
Lines: 24

> making changes so that they format under groff, add information
> about what groff does that the originals didn't do,

BTW, I'm working on a groff texinfo manual which tries to cover every
aspect of groff...

> add in a collection of ``stupid groff tricks'' (which aren't so
> stupid, examples of color support, how to escape to postscript,
> examples of image inclusion, etc),

Someone has posted a FAQ here which could be extended with your ideas.

> So far, I have everything under version control and printing under
> groff.  I can make that repository available if people like.

Is BitKeeper free software and does it allow anonymous access?  If
not, would it be possible to use CVS instead?  In any case, please
make snapshots of the repository available via FTP so that I can add
the address to groff's `MORE.STUFF' file.

Thanks a lot for your efforts!


    Werner

From groff-admin  Sun Jul 23 00:18:30 2000
Received: from bitmover.com (IDENT:root@bitmover.com [207.181.251.162])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA26972
	for <groff@ffii.org>; Sun, 23 Jul 2000 00:18:29 +0200
Received: from work.bitmover.com (root@work.bitmover.com [10.3.9.4])
	by bitmover.com (8.8.7/8.8.7) with ESMTP id PAA27974;
	Sat, 22 Jul 2000 15:34:37 -0700
Received: (from lm@localhost)
	by work.bitmover.com (8.9.3/8.9.3) id PAA21270;
	Sat, 22 Jul 2000 15:34:37 -0700
Date: Sat, 22 Jul 2000 15:34:37 -0700
From: Larry McVoy <lm@bitmover.com>
To: Werner LEMBERG <wl@gnu.org>
Cc: lm@bitmover.com, groff@ffii.org
Subject: Re: [Groff] I'm building groff docs
Message-ID: <20000722153437.A21265@work.bitmover.com>
References: <20000721095447.B4742@work.bitmover.com> <20000721.214217.17851667.sx0005@gnu.org> <20000721143850.A12591@work.bitmover.com> <20000722.105504.52182672.sx0005@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <20000722.105504.52182672.sx0005@gnu.org>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2263
Lines: 51

On Sat, Jul 22, 2000 at 10:55:04AM +0200, Werner LEMBERG wrote:
> > making changes so that they format under groff, add information
> > about what groff does that the originals didn't do,
> 
> BTW, I'm working on a groff texinfo manual which tries to cover every
> aspect of groff...

That seems sort of weird to me - why wouldn't you do groff docs in groff?
I don't get it.  But whatever, to each their own.

> > add in a collection of ``stupid groff tricks'' (which aren't so
> > stupid, examples of color support, how to escape to postscript,
> > examples of image inclusion, etc),
> 
> Someone has posted a FAQ here which could be extended with your ideas.

Cool.  I don't care who does it as long as there is a collection of useful
tips sitting around.  I'll maintain it unless someone else steps forward.
If you have tricks you think are cool, send them to me in the form of
groff source and a Makefile.

> > So far, I have everything under version control and printing under
> > groff.  I can make that repository available if people like.
> 
> Is BitKeeper free software and does it allow anonymous access?  

Yes and yes.  It has more restrictions than typical free software - you have
to publicly log your changelog messages (see http://www.openlogging.org
for examples) and you can't break the logging feature, but other than
that it is basically the same as GPLed software.  You get the source,
you can hack it, and you can redistribute it.  Whoops, I forgot, you
also have to pass the regression tests - we have 12,000 lines of shell
scripts that we have built up over the last 2-3 years to test it and we
aren't really interested in having those bugs come back.

As to anonymous access, sure.  Suppose I stuck the groff stuff on port 10000.
Then all you do to get it, assuming you have BitKeeper, is

	bk clone bk://bitmover.com:10000 troff-docs

> If not, would it be possible to use CVS instead?  

Sorry, I'd rather not.  What I do for a day job is BitKeeper, it's a much
better answer than CVS.  I wouldn't go back to CVS for love or money.

> Thanks a lot for your efforts!

My pleasure!  It really is.  I love this stuff (sick, I know, but there it is).
-- 
---
Larry McVoy            	   lm@bitmover.com           http://www.bitmover.com/lm 

From groff-admin  Sun Jul 23 12:40:36 2000
Received: from partagas.dragonet.es (IDENT:root@dragonet.es [194.179.92.130])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA22727
	for <groff@ffii.org>; Sun, 23 Jul 2000 12:40:35 +0200
X-Authentication-Warning: genba.ffii.org: Host IDENT:root@dragonet.es [194.179.92.130] claimed to be partagas.dragonet.es
Received: from Trantor.Trnet.org (root@[193.153.177.5])
	by partagas.dragonet.es (Switch-2.0.0/Switch-2.0.0/VirtualServers2.2) with ESMTP id e6NCxMx20457
	for <groff@ffii.org>; Sun, 23 Jul 2000 12:59:23 GMT
Received: from Trantor.dragonet.es (6676 bytes) by Trantor.Trnet.org
	via smail with P:bsmtp/R:smart_host/T:smtp
	(sender: <pandres@dragonet.es>) 
	id <m13GJR0-000XziC@Trantor.Trnet.org>
	for <groff@ffii.org>; Sun, 23 Jul 2000 12:56:38 +0200 (CEST)
	(Smail-3.2.0.102 1998-Aug-2 #2 built 1998-Oct-13)
Received: from localhost (really [127.0.0.1]) by Trantor.Trnet.org
	via in.smtpd with esmtp
	id <m13GJPj-0008V0C@Trantor.Trnet.org> (Debian Smail3.2.0.102)
	for <groff@ffii.org>; Sun, 23 Jul 2000 12:55:19 +0200 (CEST) 
Date: Sun, 23 Jul 2000 12:55:19 +0200 (CEST)
From: Paco Andres Verdu <pandres@dragonet.es>
Reply-To: =?iso-8859-1?Q?Paco_Andr=E9s_Verd=FA?= <pandres@dragonet.es>
To: Ted.Harding@nessie.mcc.ac.uk
cc: Bernd Salbrechter <bernd@mycity.at>, groff@ffii.org
Subject: RE: [Groff] Page classes in groff output to support reordering o
In-Reply-To: <XFMail.000721102245.Ted.Harding@nessie.mcc.ac.uk>
Message-ID: <Pine.LNX.3.96.1000723122544.3499A-200000@Trantor.Trnet.org>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-252569276-964349719=:3499"
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 5774
Lines: 113

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--8323328-252569276-964349719=:3499
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT

On Fri, 21 Jul 2000 Ted.Harding@nessie.mcc.ac.uk wrote:

> One feature of groff which could be useful for this is the possibility of
> selecting which pages get output by groff: the -o option does this.
> For instance, -o1,3,5,7,9 would output these odd-numbered pages,
> -o2,4,6,8 these even-numbered pages, etc. If anything, I would agree
> that an extension to this option which gave ALL odd, or ALL even
> pages without explicit listing, could be useful. However, this is already
> possible in psutils [psselect] so I don't see its necessity as pressing.

	Some time ago I added a step extension to the -o option, the format 
of the -o option with this extension is -o page_list[:step], that way you
could put -o 1-:2 to get all the odd pages in the document, and -o 2-:2 to
get all the even pages. Of course you can use any positive number for this
parameter, but 2 is the most useful one.

	Since I'm not using the -Tps output device I can't use psutils to
accomplish the same result, that's why I added this extension.

	Unfortunately I never modified the groff man page to reflect this
extension, not being a fluent english writer, documenting things is usually
harder than writing the code, and releasing this change was a low priority
task, I'm now too busy to devote any significant time to this. Maybe
somebody could add the necessary explanation to the man page if you find the
extension useful enough to be included in groff.

	I've attached a patch with my changes to this message, feel free to
contact me if you have any problem with it.


Greetings

Paco


 
--
                              Saludos
-----------------------------------------------------------------------------
Paco Andrés Verdú                                     pandres@dragonet.es
Alicante (Spain)                                              


--8323328-252569276-964349719=:3499
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="step-parameter.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.3.96.1000723125519.3499B@Trantor.Trnet.org>
Content-Description: Patch file

LS0tIGdyb2ZmLWN2cy9ncm9mZi9zcmMvcm9mZi90cm9mZi9pbnB1dC5jYwlT
dW4gSnVuIDE4IDIxOjA0OjQwIDIwMDANCisrKyBncm9mZi1jdXJyZW50L3Ny
Yy9yb2ZmL3Ryb2ZmL2lucHV0LmNjCVNhdCBNYXIgMjUgMTQ6MzE6MTQgMjAw
MA0KQEAgLTU0MjUsMjAgKzUzODYsMjEgQEANCiBjbGFzcyBwYWdlX3Jhbmdl
IHsNCiAgIGludCBmaXJzdDsNCiAgIGludCBsYXN0Ow0KKyAgaW50IHN0ZXA7
DQogcHVibGljOg0KICAgcGFnZV9yYW5nZSAqbmV4dDsNCi0gIHBhZ2VfcmFu
Z2UoaW50LCBpbnQsIHBhZ2VfcmFuZ2UgKik7DQorICBwYWdlX3JhbmdlKGlu
dCwgaW50LCBpbnQsIHBhZ2VfcmFuZ2UgKik7DQogICBpbnQgY29udGFpbnMo
aW50IG4pOw0KIH07DQogDQotcGFnZV9yYW5nZTo6cGFnZV9yYW5nZShpbnQg
aSwgaW50IGosIHBhZ2VfcmFuZ2UgKnApDQotOiBmaXJzdChpKSwgbGFzdChq
KSwgbmV4dChwKQ0KK3BhZ2VfcmFuZ2U6OnBhZ2VfcmFuZ2UoaW50IGksIGlu
dCBqLCBpbnQgcywgcGFnZV9yYW5nZSAqcCkNCis6IGZpcnN0KGkpLCBsYXN0
KGopLCBzdGVwKHMpLCBuZXh0KHApDQogew0KIH0NCiANCiBpbnQgcGFnZV9y
YW5nZTo6Y29udGFpbnMoaW50IG4pDQogew0KLSAgcmV0dXJuIG4gPj0gZmly
c3QgJiYgKGxhc3QgPD0gMCB8fCBuIDw9IGxhc3QpOw0KKyAgcmV0dXJuIG4g
Pj0gZmlyc3QgJiYgKGxhc3QgPD0gMCB8fCBuIDw9IGxhc3QpICYmICgoKG4t
Zmlyc3QpJXN0ZXApID09IDApOw0KIH0NCiANCiBwYWdlX3JhbmdlICpvdXRw
dXRfcGFnZV9saXN0ID0gMDsNCkBAIC01NDUzLDM3ICs1NDE1LDU3IEBADQog
ICByZXR1cm4gMDsNCiB9DQogDQorLy8gIE1vZGlmeWVkIGJ5IFBhY28gQW5k
cmVzIDxwYW5kcmVzQGRyYWdvbmV0LmVzPiB0byBhZGQgdGhlIHN0ZXAgcGFy
YW1ldGVyLA0KKy8vICByZWZvcm1hdHRpbmcgYW5kIHNvbWUgY29tbWVudHMN
CiBzdGF0aWMgdm9pZCBwYXJzZV9vdXRwdXRfcGFnZV9saXN0KGNoYXIgKnAp
DQogew0KICAgZm9yICg7Oykgew0KLSAgICBpbnQgaTsNCisgICAgaW50IGk7
IC8vIFN0YXJ0IHBhZ2UNCiAgICAgaWYgKCpwID09ICctJykNCi0gICAgICBp
ID0gMTsNCi0gICAgZWxzZSBpZiAoY3NkaWdpdCgqcCkpIHsNCi0gICAgICBp
ID0gMDsNCi0gICAgICBkbw0KLQlpID0gaSoxMCArICpwKysgLSAnMCc7DQot
ICAgICAgd2hpbGUgKGNzZGlnaXQoKnApKTsNCi0gICAgfQ0KKyAgICAgIGkg
PSAxOyAvLyBzdGFydCBhdCAxIGlmIG9ubHkgdGhlIGVuZGluZyBwYWdlIGlz
IHNwZWNpZmllZA0KICAgICBlbHNlDQotICAgICAgYnJlYWs7DQotICAgIGlu
dCBqOw0KKyAgICAJaWYgKGNzZGlnaXQoKnApKSB7DQorICAgICAgCSAgIGkg
PSAwOw0KKyAgICAgIAkgICBkbw0KKwkJCWkgPSBpKjEwICsgKCpwKysgLSAn
MCcpOw0KKyAgICAgIAkJd2hpbGUgKGNzZGlnaXQoKnApKTsNCisgICAgCX0g
Ly8gaWYgKGNzZGlnaXQoKnApKQ0KKyAgICAJZWxzZQ0KKyAgICAgIAkJYnJl
YWs7DQorCQkJDQorICAgIGludCBqOyAvLyBFbmRpbmcgcGFnZQ0KICAgICBp
ZiAoKnAgPT0gJy0nKSB7DQogICAgICAgcCsrOw0KICAgICAgIGogPSAwOw0K
ICAgICAgIGlmIChjc2RpZ2l0KCpwKSkgew0KLQlkbw0KLQkgIGogPSBqKjEw
ICsgKnArKyAtICcwJzsNCi0Jd2hpbGUgKGNzZGlnaXQoKnApKTsNCi0gICAg
ICB9DQotICAgIH0NCisJCQlkbw0KKwkgIAkJaiA9IGoqMTAgKyAoICpwKysg
LSAnMCcpOw0KKwkJCXdoaWxlIChjc2RpZ2l0KCpwKSk7DQorICAgICAgfSAv
LyBpZiAoY3NkaWdpdCgqcCkpDQorICAgIH0gLy8gaWYgKCpwID09ICctJykN
CiAgICAgZWxzZQ0KICAgICAgIGogPSBpOw0KKw0KKw0KKyAgICBpbnQgc3Rl
cDsgLy8gU3RlcHBpbmcNCisgICAgaWYgKCpwID09ICc6Jykgew0KKyAgICAg
IHArKzsNCisgICAgICBzdGVwID0gMDsNCisgICAgICBpZiAoY3NkaWdpdCgq
cCkpIHsNCisJCQlkbw0KKwkgIAkJc3RlcCA9IHN0ZXAqMTAgKyAoKnArKyAt
ICcwJyk7DQorCQkJd2hpbGUgKGNzZGlnaXQoKnApKTsNCisgICAgICB9IC8v
IGlmIChjc2RpZ2l0KCpwKSkNCisgICAgfSAvLyBpZiAoKnAgPT0gJzonKQ0K
KyAgICBlbHNlDQorICAgICAgc3RlcCA9IDE7DQorCWlmIChzdGVwID09IDAp
IHN0ZXAgPSAxOw0KKwkgIA0KICAgICBpZiAoaiA9PSAwKQ0KICAgICAgIGxh
c3RfcGFnZV9udW1iZXIgPSAtMTsNCiAgICAgZWxzZSBpZiAobGFzdF9wYWdl
X251bWJlciA+PSAwICYmIGogPiBsYXN0X3BhZ2VfbnVtYmVyKQ0KICAgICAg
IGxhc3RfcGFnZV9udW1iZXIgPSBqOw0KLSAgICBvdXRwdXRfcGFnZV9saXN0
ID0gbmV3IHBhZ2VfcmFuZ2UoaSwgaiwgb3V0cHV0X3BhZ2VfbGlzdCk7DQor
ICAgIG91dHB1dF9wYWdlX2xpc3QgPSBuZXcgcGFnZV9yYW5nZShpLCBqLCBz
dGVwLCBvdXRwdXRfcGFnZV9saXN0KTsNCiAgICAgaWYgKCpwICE9ICcsJykN
CiAgICAgICBicmVhazsNCiAgICAgKytwOw0K
--8323328-252569276-964349719=:3499--

From groff-admin  Sun Jul 23 12:57:31 2000
Received: from TK212017118241.teleweb.at (IDENT:postfix@TK212017118241.teleweb.at [212.17.118.241])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA22921
	for <groff@ffii.org>; Sun, 23 Jul 2000 12:57:30 +0200
Received: by TK212017118241.teleweb.at (Postfix, from userid 501)
	id 5CDE244B2; Sun, 23 Jul 2000 13:13:44 +0200 (CEST)
Date: Sun, 23 Jul 2000 13:13:44 +0200
From: Leonard Stiles <ljs@uk2.net>
To: groff@ffii.org
Subject: Re: [Groff] pic solid attribute
Message-ID: <20000723131344.A758@TK212017118241.teleweb.at>
References: <20000722121511.A1148@TK212017118241.teleweb.at> <XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>; from Ted.Harding@nessie.mcc.ac.uk on Sat, Jul 22, 2000 at 01:23:22PM +0100
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1776
Lines: 44

On Sat, Jul 22, 2000 at 01:23:22PM +0100, Ted Harding wrote:
> Can we have some backgrouns on this? I.e. what is "solid" supposed
> to do? The 1991 PIC User Manual (Kernighan, Bell docs #116) gives
> "solid" as an attribute in its "Reference Manual" Appendix, but it
> is not mentioned anywhere else.

> Maybe there is more info in something like the DWB documentation
> (which I don't have).

Neither do I
 
> Meanwhile, the source code of groff pic indicates that (internally)
> "solid" is used for "solid lines" (as opposed to dashed or dotted)
> which is the default for lines anyway unless explcitily given the
> "dashed" or "dotted" attribute.
> 
> However, lex.cc for groff pic does not have "solid" in its list of
> keywords, so it would not be recognised.

To be honest, I'm not entirely sure myself, as I've never used non-GNU
pic.

As far as I know, the solid attribute is merely the explicit specification 
of the line type which is assumed implicitly unless the dotted or dashed 
attributes are used.

In the paper by Eric Raymond, it is said to "make [a] closed figure solid",
which makes it sound like it does something like "fill". However, my guess 
is that this is misleading/wrong. (Raymond goes on to say that 
"the solid primitive [sic] is not yet supported in GNU gpic").

Presuming that solid does indeed mean non-dotted/dashed lines, it isn't all 
that useful except possibly to override previously specified dashed or 
dotted. However, it would still be good if gpic were to recognize the 
attribute, if only to support old code which uses it. Due to the rather 
redundant nature of the attribute, adding support for it would not be 
difficult.

-- 
+------------------------------+
| Leonard Stiles <ljs@uk2.net> |
+------------------------------+



From groff-admin  Sun Jul 23 18:21:59 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA25200
	for <groff@ffii.org>; Sun, 23 Jul 2000 18:21:59 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13GOla-000Pr7-00; Sun, 23 Jul 2000 17:38:15 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id RAA09683;
	Sun, 23 Jul 2000 17:34:43 +0100
Message-ID: <XFMail.000723173443.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000723131344.A758@TK212017118241.teleweb.at>
Date: Sun, 23 Jul 2000 17:34:43 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Leonard Stiles <ljs@uk2.net>
Subject: Re: [Groff] pic solid attribute
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1134
Lines: 25

On 23-Jul-00 Leonard Stiles wrote:
> As far as I know, the solid attribute is merely the explicit
> specification of the line type which is assumed implicitly unless the
> dotted or dashed  attributes are used.
> 
> In the paper by Eric Raymond, it is said to "make [a] closed figure
> solid", which makes it sound like it does something like "fill".
> However, my guess is that this is misleading/wrong. (Raymond goes on
> to say that "the solid primitive [sic] is not yet supported in GNU
> gpic").

Well, this would agree with my own suspicion. Eric Raymond's paper
is a very valuable general guide to use of pic, being more readily
understandable (and more comprehensive with examples) that the UNIX
PIC User's Manual. However, it is not error-free, and should not be
regarded as a definitive reference.

Thanks for the comments!
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 23-Jul-00                                       Time: 17:34:43
------------------------------ XFMail ------------------------------

From groff-admin  Mon Jul 24 16:36:43 2000
Received: from heimdall.sdrc.com (heimdall.sdrc.com [146.122.132.195])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA11631
	for <groff@ffii.org>; Mon, 24 Jul 2000 16:36:42 +0200
Received: from tyr.sdrc.com (mailhub-cvg.sdrc.com [146.122.142.31])
	by heimdall.sdrc.com (8.9.1/8.9.1) with ESMTP id KAA18890;
	Mon, 24 Jul 2000 10:51:54 -0400 (EDT)
Received: from thor.sdrc.com (scjones@thor [146.122.62.108])
	by tyr.sdrc.com (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id KAA20554;
	Mon, 24 Jul 2000 10:51:18 -0400 (EDT)
Received: (from scjones@localhost)
	by thor.sdrc.com (8.9.0/8.9.0) id KAA00695;
	Mon, 24 Jul 2000 10:51:06 -0400 (EDT)
Message-Id: <200007241451.KAA00695@thor.sdrc.com>
Subject: Re: [Groff] Page classes in groff output to support reordering o
To: tkb@tkb.mpl.com (T. Kurt Bond)
Date: Mon, 24 Jul 2000 10:51:06 -0400 (EDT)
Cc: Ted.Harding@nessie.mcc.ac.uk, bernd@mycity.at, groff@ffii.org
In-Reply-To: <14713.64432.801768.960562@tkb.mpl.com> from "T. Kurt Bond" at Jul 22, 0 03:53:20 pm
From: larry.jones@sdrc.com (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1095
Lines: 25

T. Kurt Bond writes:
> 
> It might be useful if gtroff had a predefined read-only number
> register, say \n[.pp] (for physical page), that recorded the physical
> page number independent of what \n% had.  This number would start at 1
> and be increased by 1 at the start of each new page, regardless of
> what the user has requested with .bp or .pn.  The "p" command in
> gtroff output could be followed by something like
> 
>     x X page: 1 i 3
> 
> where "1" is the page number from \n%, "i" is the page number
> according to the current current format for % requested by .af, and 
> "3" is the physical page of the document.

I think something along these lines is definitely needed, but I want to
caution against tying it to \n% too strongly -- many macro packages use
their own register(s) and/or string(s) for the page number and
completely ignore \n%, so you need a mechanism that the macro package
can use to communicate the information rather than building something in
to groff that isn't modifiable.

-Larry Jones

I don't think math is a science, I think it's a religion. -- Calvin

From groff-admin  Mon Jul 24 16:48:50 2000
Received: from tkb.mpl.com (IDENT:root@tkb.mpl.com [198.77.4.83])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA11846
	for <groff@ffii.org>; Mon, 24 Jul 2000 16:48:48 +0200
Received: from tkb.mpl.com (IDENT:tkb@tkb.mpl.com [198.77.4.83])
	by tkb.mpl.com (8.9.3/8.9.3) with ESMTP id LAA06700;
	Mon, 24 Jul 2000 11:03:15 -0400
From: "T. Kurt Bond" <tkb@tkb.mpl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14716.23219.374868.310309@tkb.mpl.com>
Date: Mon, 24 Jul 2000 11:03:15 -0400 (EDT)
To: groff@ffii.org
Subject: Re: [Groff] Page classes in groff output to support reordering o
In-Reply-To: <200007241451.KAA00695@thor.sdrc.com>
References: <14713.64432.801768.960562@tkb.mpl.com>
	<200007241451.KAA00695@thor.sdrc.com>
X-Mailer: VM 6.75 under Emacs 20.4.1
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1745
Lines: 37

Larry Jones writes:
> T. Kurt Bond writes:
> > 
> > It might be useful if gtroff had a predefined read-only number
> > register, say \n[.pp] (for physical page), that recorded the physical
> > page number independent of what \n% had.  This number would start at 1
> > and be increased by 1 at the start of each new page, regardless of
> > what the user has requested with .bp or .pn.  The "p" command in
> > gtroff output could be followed by something like
> > 
> >     x X page: 1 i 3
> > 
> > where "1" is the page number from \n%, "i" is the page number
> > according to the current current format for % requested by .af, and 
> > "3" is the physical page of the document.
> 
> I think something along these lines is definitely needed, but I want to
> caution against tying it to \n% too strongly -- many macro packages use
> their own register(s) and/or string(s) for the page number and
> completely ignore \n%, so you need a mechanism that the macro package
> can use to communicate the information rather than building something in
> to groff that isn't modifiable.

That's a very good point.  I guess the actually output of 
"x X page: 1 i 3" could be done by each individual macro package using
some variation on "\X'page: x y z'"; the physical page register would
still need to be part of groff, I think.

The orignal message was about reordering pages; is the 
"a page-makeup postprocessor and associated macro package (like pm and
-mpm)" mentioned in the PROJECTS file in groff's source distribution
something to do page reordering?  Does anyone have any more details on
this?  I seem to remember reading somewhere that there was a Usenix
paper on something like this; does anyone remember that? 
-- 
T. Kurt Bond, tkb@tkb.mpl.com


From groff-admin  Mon Jul 24 16:55:21 2000
Received: from heimdall.sdrc.com (heimdall.sdrc.com [146.122.132.195])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA11952
	for <groff@ffii.org>; Mon, 24 Jul 2000 16:55:20 +0200
Received: from tyr.sdrc.com (mailhub-cvg.sdrc.com [146.122.142.31])
	by heimdall.sdrc.com (8.9.1/8.9.1) with ESMTP id LAA21372;
	Mon, 24 Jul 2000 11:11:37 -0400 (EDT)
Received: from thor.sdrc.com (scjones@thor [146.122.62.108])
	by tyr.sdrc.com (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id LAA09320;
	Mon, 24 Jul 2000 11:11:35 -0400 (EDT)
Received: (from scjones@localhost)
	by thor.sdrc.com (8.9.0/8.9.0) id LAA00829;
	Mon, 24 Jul 2000 11:11:36 -0400 (EDT)
Message-Id: <200007241511.LAA00829@thor.sdrc.com>
Subject: Re: [Groff] Page classes in groff output to support reordering o
To: Ted.Harding@nessie.mcc.ac.uk
Date: Mon, 24 Jul 2000 11:11:36 -0400 (EDT)
Cc: bernd@mycity.at, groff@ffii.org
In-Reply-To: <XFMail.000722123944.Ted.Harding@nessie.mcc.ac.uk> from "Ted.Harding@nessie.mcc.ac.uk" at Jul 22, 0 12:39:44 pm
From: larry.jones@sdrc.com (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 677
Lines: 17

Ted.Harding@nessie.mcc.ac.uk writes:
> 
> 1. A new \X'ps: ...' command like
>    \X'ps: pagenumformat F' where F may be as in troff .af, namely
>    1 001 i I a A

I think this is too restricted in scope to be useful.  What you really
want is a way to communicate the user-visible page number to any back
end, not just grops.  And the user-visible page number can be quite
complex: "2-1", "Index 2", "2.3", etc., so I think it needs to be a
string, it needs to be something that a macro package can do (since each
macro package formats page numbers differently), and it needs to be
device-independent.

-Larry Jones

I can feel my brain beginning to atrophy already. -- Calvin

From groff-admin  Fri Jul 28 20:22:35 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA23091
	for <groff@ffii.org>; Fri, 28 Jul 2000 20:22:35 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13IF2K-0006NW-00
	for groff@ffii.org; Fri, 28 Jul 2000 19:39:09 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA12754;
	Fri, 28 Jul 2000 16:46:08 +0100
Message-ID: <XFMail.000728164608.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Resent-Date: Fri, 28 Jul 2000 15:53:45 +0100 (BST)
Resent-Message-Id: <XFMail.000728155345.Ted.Harding@nessie.mcc.ac.uk>
Resent-From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Resent-To: linux-users@mcc.ac.uk
Date: Fri, 28 Jul 2000 16:46:08 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: groff@ffii.org
Subject: [Groff] Weird variety of troff/nroff
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 676
Lines: 26

Hi Folks,

Does anyone out there have any idea of which variant of UNIX
troff/nroff uses the folllowing decidedly non-standard syntax
in 'tbl'? (We're talking early-mid 80s).

.TS
.center box;
l l l.
...

Note the '.' in '.center' -- definitely non-kosher!

I've never seen this before, but have encountered a job where this
occurs.

I'd be obliged for any pointers.

Thanks,
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 28-Jul-00                                       Time: 16:46:08
------------------------------ XFMail ------------------------------

From groff-admin  Fri Jul 28 21:46:12 2000
Received: from heimdall.sdrc.com (heimdall.sdrc.com [146.122.132.195])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA24201
	for <groff@ffii.org>; Fri, 28 Jul 2000 21:46:11 +0200
Received: from tyr.sdrc.com (mailhub-cvg.sdrc.com [146.122.142.31])
	by heimdall.sdrc.com (8.9.1/8.9.1) with ESMTP id QAA14234;
	Fri, 28 Jul 2000 16:02:59 -0400 (EDT)
Received: from thor.sdrc.com (scjones@thor.sdrc.com [146.122.62.108])
	by tyr.sdrc.com (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id QAA27249;
	Fri, 28 Jul 2000 16:02:58 -0400 (EDT)
Received: (from scjones@localhost)
	by thor.sdrc.com (8.9.0/8.9.0) id QAA03064;
	Fri, 28 Jul 2000 16:02:57 -0400 (EDT)
Message-Id: <200007282002.QAA03064@thor.sdrc.com>
Subject: Re: [Groff] Weird variety of troff/nroff
To: Ted.Harding@nessie.mcc.ac.uk
Date: Fri, 28 Jul 2000 16:02:57 -0400 (EDT)
Cc: groff@ffii.org
In-Reply-To: <XFMail.000728164608.Ted.Harding@nessie.mcc.ac.uk> from "Ted.Harding@nessie.mcc.ac.uk" at Jul 28, 0 04:46:08 pm
From: larry.jones@sdrc.com (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 490
Lines: 17

Ted.Harding@nessie.mcc.ac.uk writes:
> 
> Does anyone out there have any idea of which variant of UNIX
> troff/nroff uses the folllowing decidedly non-standard syntax
> in 'tbl'? (We're talking early-mid 80s).
> 
> .TS
> .center box;
> l l l.

I think all versions of AT&T tbl ignore miscellaneous punctuation
characters in the options.  I submitted a patch to groff's tbl to do the
same thing long ago -- doesn't it handle this case?

-Larry Jones

It's going to be a long year. -- Calvin

From groff-admin  Sun Jul 30 08:30:29 2000
Received: from bitmover.com (IDENT:root@bitmover.com [207.181.251.162])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA19723
	for <groff@ffii.org>; Sun, 30 Jul 2000 08:30:28 +0200
Received: from work.bitmover.com (root@work.bitmover.com [10.3.9.4])
	by bitmover.com (8.8.7/8.8.7) with ESMTP id XAA17798
	for <groff@ffii.org>; Sat, 29 Jul 2000 23:47:26 -0700
From: Larry McVoy <lm@bitmover.com>
Received: (from lm@localhost)
	by work.bitmover.com (8.9.3/8.9.3) id XAA22336
	for groff@ffii.org; Sat, 29 Jul 2000 23:47:26 -0700
Date: Sat, 29 Jul 2000 23:47:26 -0700
Message-Id: <200007300647.XAA22336@work.bitmover.com>
To: groff@ffii.org
Subject: [Groff] drawing without moving?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 496
Lines: 13

Is there some way that I can say

	when you get to the end of the page, go back to the middle, draw
	some PIC stuff, and then break to the next page?

I'm having a tough time with this.  I can get text to work but PIC is not
cooperating.  Has anyone done such a thing?

While we're on the topic, how about this?  Suppose I'm in the middle of
my doc and I want to stash a little note in the margin and then come back.
Sort of like a foot note.  Does anyone have a package that does this?

Thanks.

From groff-admin  Sun Jul 30 09:51:56 2000
Received: from bitmover.com (IDENT:root@bitmover.com [207.181.251.162])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA20155
	for <groff@ffii.org>; Sun, 30 Jul 2000 09:51:55 +0200
Received: from work.bitmover.com (root@work.bitmover.com [10.3.9.4])
	by bitmover.com (8.8.7/8.8.7) with ESMTP id BAA18168
	for <groff@ffii.org>; Sun, 30 Jul 2000 01:08:54 -0700
From: Larry McVoy <lm@bitmover.com>
Received: (from lm@localhost)
	by work.bitmover.com (8.9.3/8.9.3) id BAA23611
	for groff@ffii.org; Sun, 30 Jul 2000 01:08:54 -0700
Date: Sun, 30 Jul 2000 01:08:54 -0700
Message-Id: <200007300808.BAA23611@work.bitmover.com>
To: groff@ffii.org
Subject: [Groff] margin macros
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 664
Lines: 31

Hi, I have a partial answer to my earlier question about margin notes.
Here's what I came up with, these seem to work OK if you have left yourself
a 1.5 inch page offset.  They even complain when the margin note will cause
a page break.

.ev margin-ev
.       ps 8
.       vs 9
.       ft R
.ev
.de MS
.       ev margin-ev
.       di margin-di
.       sp .25
.       po .4i
.       ll .6i
..
.de ME
.       br
.       di 
.       ie (\\n[dn]+\\n[nl])>=(\\n[.p]-\\n[FM]) \{\
.               tm Margin message is too big at line \\n[.c]
.       \} 
.       el \{\
.               margin-di
.               sp -\\n[dn]u
.       \}
.       po
.       ll
.       ev
..

From groff-admin  Mon Jul 31 12:19:06 2000
Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA13822
	for <groff@ffii.org>; Mon, 31 Jul 2000 12:19:06 +0200
Received: from bsd.jcs.com (user-38lc05p.dialup.mindspring.com [209.86.0.185])
	by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id GAA11806;
	Mon, 31 Jul 2000 06:36:05 -0400 (EDT)
Received: (from jcs@localhost)
	by bsd.jcs.com (8.9.2/8.8.8) id GAA00447;
	Mon, 31 Jul 2000 06:37:19 -0400 (EDT)
	(envelope-from jsnader@ix.netcom.com)
X-Authentication-Warning: bsd.jcs.com: jcs set sender to jsnader@ix.netcom.com using -f
Date: Mon, 31 Jul 2000 06:37:19 -0400
From: Jon Snader <jsnader@ix.netcom.com>
To: Ted Harding <Ted.Harding@nessie.mcc.ac.uk>
Cc: Leonard Stiles <ljs@uk2.net>, groff@ffii.org
Subject: Re: [Groff] pic solid attribute
Message-ID: <20000731063719.B348@ix.netcom.com>
References: <20000722121511.A1148@TK212017118241.teleweb.at> <XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>; from Ted Harding on Sat, Jul 22, 2000 at 01:23:22PM +0100
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1525
Lines: 38

On Sat, Jul 22, 2000 at 01:23:22PM +0100, Ted Harding wrote:
> On 22-Jul-00 Leonard Stiles wrote:
> > Is it just me or does gpic not support the "solid" attribute?
> > For example, this code produces an error (using groff 1.16):
> > 
> > .PS
> > circle solid
> > .PE
> > 
> > Eric Raymond's paper about gpic says something about solid not being 
> > supported yet, but it isn't mentioned in the TODO of groff 1.16 - has 
> > it just been forgotten?
> 
> Can we have some backgrouns on this? I.e. what is "solid" supposed
> to do? The 1991 PIC User Manual (Kernighan, Bell docs #116) gives
> "solid" as an attribute in its "Reference Manual" Appendix, but it
> is not mentioned anywhere else.
> 
> Maybe there is more info in something like the DWB documentation
> (which I don't have).
> 
> Meanwhile, the source code of groff pic indicates that (internally)
> "solid" is used for "solid lines" (as opposed to dashed or dotted)
> which is the default for lines anyway unless explcitily given the
> "dashed" or "dotted" attribute.
> 
> However, lex.cc for groff pic does not have "solid" in its list of
> keywords, so it would not be recognised.
> 

I checked the picl.l file in the AT&T version of pic from the CSRG
4.4BSD release and it just accepts but ignores the attribute ``solid.''
A comment in the UNDOC file (a sort of CHANGES log) dated May 85 says
that ``solid'' is now a valid (but uninteresting) attribute.  It appears
that it was added to complete the list of valid line attributes (dashed,
dotted).

Jon Snader

From groff-admin  Mon Jul 31 20:21:08 2000
Received: from RSMTP.mycity.at (rsmtp.mycity.at [212.236.73.35])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA23226
	for <groff@ffii.org>; Mon, 31 Jul 2000 20:21:08 +0200
Received: from schleppo.sun.universe (baden-remote07.mycity.at [212.236.73.199])
	by RSMTP.mycity.at (8.9.3/8.9.3) with ESMTP id UAA06166;
	Mon, 31 Jul 2000 20:36:19 +0200
Received: (from salb@localhost)
	by schleppo.sun.universe (8.8.8/8.8.8) id UAA03870;
	Mon, 31 Jul 2000 20:36:02 +0200 (CEST)
Date: Mon, 31 Jul 2000 20:36:02 +0200 (CEST)
From: Bernd Salbrechter <bernd@mycity.at>
Message-Id: <200007311836.UAA03870@schleppo.sun.universe>
To: groff@ffii.org
Subject: RE: [Groff] Page classes in groff output to support reordering o
Cc: larry.jones@sdrc.com, Ted.Harding@nessie.mcc.ac.uk, tkb@tkb.mpl.com
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 5999
Lines: 130

Hi all!

Thanks for the interesting replies and sorry for my late answer,
but I was really busy last week. It looks like I have start an
interesting discussion for groff. I will post a summery of the
answers I got and clarify some points.

1. It looks like it will be a good idea to put a reordering of
pages (based on the logical parts) between groff and the post-processors
(i.e. grops). Because this can be useful for all output formats.

larry.jones@sdrc.com (Larry Jones) (24 Jul 2000):
> Ted.Harding@nessie.mcc.ac.uk writes:
> > 
> > 1. A new \X'ps: ...' command like
> >    \X'ps: pagenumformat F' where F may be as in troff .af, namely
> >    1 001 i I a A
> 
> I think this is too restricted in scope to be useful.  What you really
> want is a way to communicate the user-visible page number to any back
> end, not just grops.  And the user-visible page number can be quite
> complex: "2-1", "Index 2", "2.3", etc., so I think it needs to be a
> string, it needs to be something that a macro package can do (since each
> macro package formats page numbers differently), and it needs to be
> device-independent.

T. Kurt Bond <tkb@tkb.mpl.com> (22 Jul 2000):
> While it might not work in the completely general case (multiple
> resized logical pages per physical sheet), I can't see why it wouldn't
> work for moving the table of contents and such around.  It looks like
> in gtroff output the "p" command that starts a new page is always
> followed with an "f" command to set the current font, so the pages
> should be fairly independent.  And doing this in a filter between
> gtroff and the device-specific post-processor would allow this
> reordering to be done independently of the type of final output
> device, so it would be useful not only for grops, but also grodvi,
> grotty, grolj4, and grolbj.

Yes thats the real point her, it can be done easily for all
output formats, which support comments (i.e. PostScript) but would
be quite difficult, if not impossible for less powerful output formats
like ASCII. And it wast of resources to implement it for each output
format.

> Geoff's output, with one command per line, is well suited for this;
> some di troff descendants (Unixware's, I think), on the other hand, put
> multiple commands on one line, delimited only with whitespace, which
> makes it harder.
> 
> True, but the common, indeed very common, desire to put the table of
> contents, etc., into the proper place  in the document, seems to me to 
> be very practical and useful.
>
> The user would still have to indicate in some manner how where the
> table of contents starts and ends, but this could be done
> automatically by the (suitable modified) macro package, or manually.
>
> Actually, I think something like this could be useful for all the
> output backends for reordering.

2. groff need a clear and well defined interface from the macro
package to the post-processor to pass the information to which
logical part a page belongs.

larry.jones@sdrc.com (Larry Jones) (24 Jul 2000):
> T. Kurt Bond writes:
> > 
> > It might be useful if gtroff had a predefined read-only number
> > register, say \n[.pp] (for physical page), that recorded the physical
> > page number independent of what \n% had.  This number would start at 1
> > and be increased by 1 at the start of each new page, regardless of
> > what the user has requested with .bp or .pn.  The "p" command in
> > gtroff output could be followed by something like
> > 
> >     x X page: 1 i 3
> > 
> > where "1" is the page number from \n%, "i" is the page number
> > according to the current current format for % requested by .af, and 
> > "3" is the physical page of the document.
> 
> I think something along these lines is definitely needed, but I want to
> caution against tying it to \n% too strongly -- many macro packages use
> their own register(s) and/or string(s) for the page number and
> completely ignore \n%, so you need a mechanism that the macro package
> can use to communicate the information rather than building something in
> to groff that isn't modifiable.

The interface must work with macros that relay on the \n% and such
that maintain there own registers for page numbering. If I am right
the user (macro package) sets the number of the next page with
".pn" with the page number as parameter. Wouldn't it be nice to have
an additional optional parameter to identify the logical part (I
would vote for a string). Is \s% free for that purpose? If the
macro package maintain there own registers for page numbering, it
must set a defined string variable (\s% ?) to pass the information
to the post-processor. Or should there be a total new request for
that?

Now a short overview on the processing I plan to do.

  groff --page-format=A6 doc.roff | \
  new-reorder | \
  grops | \
  new-ps-imposition --imposition=A6-A3-perfect-bound doc.ps | \
  lpr

I have marked tools not existing now with "new-". If reorder doesn't
exist I can use pstops on the PostScript output. A full imposition
will only work on reasonable powerful output formats like PostScript
(my be dvi, there are dviutils!) and should never be mixed with
the reordering we discuss here.

As you can see groff and new-ps-imposition need a common understanding
on the dimension of paper formats. I have noticed that groff now uses
libpaper to get that information. I looked into libpaper (thanks
for that pointer to it a year ago) and I say it's not a solution
to that problem, but it's better than before. A real solution, will
be to pull the information on the dimension of the paper formats
out of the programs into a database. I have started paper capability
database (like termcap and in the same format) with micrometer as unit
and a maximum paper size of about 4 km in square (range of a 32 bit
number).

Bernd

PS.: I will be on vacation for 3 weeks. But will try to get time
for this after that.

PPS.: If you think the TeX people can contribute or benefit from
this discussion, feel free to forward it there.

