From groff-admin  Wed Mar  1 14:49:15 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/GNU) with ESMTP id OAA00457
	for <groff@ffii.org>; Wed, 1 Mar 2000 14:49:14 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 1 Mar 2000 14:49:52 +0100
Received: from rigel.univie.ac.at (dial-143137.HRZ.Uni-Dortmund.DE [129.217.143.137])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id OAA04021;
	Wed, 1 Mar 2000 14:49:50 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id MAA19130;
	Wed, 1 Mar 2000 12:04:02 GMT
To: groff@ffii.org, 56702@bugs.debian.org, crp22@cam.ac.uk, fab@prosa.it
Cc: 56702-forwarded@bugs.debian.org
Subject: Re: [Groff] Bug#56702: [PATCH] /tmp race in gxditview, suspected
 poor temp file handling in grohtml, etc
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000131114907.A513@none>
References: <20000131114907.A513@none>
X-Mailer: Mew version 1.94 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
Message-Id: <20000301120401F.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 01 Mar 2000 12:04:01 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 539
Lines: 16

> 2) xditview creates a temporary file in /tmp, with mktemp and fopen,
> which is again insecure because a file could be placed there between
> the two calls (as documented in the libc docs for mktemp).
> 
> 3) indxbib creates temporary files; it uses mktemp and creat to open
> these files, which is not safe since a file could be placed there
> between the two calls.
> 
> 4) xtotroff (seems to be a helper program for xditview) has a minor
> race in opening output files.

I've finally applied the patches.  Thanks again.


    Werner


From groff-admin  Wed Mar  1 20:14:12 2000
Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA17653
	for <groff@ffii.org>; Wed, 1 Mar 2000 20:13:53 +0100
Received: from laposte.ilog.fr (laposte [172.17.1.6])
	by sceaux.ilog.fr (8.9.3/8.9.3) with ESMTP id UAA11643;
	Wed, 1 Mar 2000 20:11:25 +0100 (MET)
Received: from oberkampf.ilog.fr ([172.17.4.41])
	by laposte.ilog.fr (8.9.3/8.9.3) with ESMTP id UAA18071;
	Wed, 1 Mar 2000 20:13:50 +0100 (MET)
From: Bruno Haible <haible@ilog.fr>
Received: (from haible@localhost)
	by oberkampf.ilog.fr (8.9.2/8.9.2) id UAA22158;
	Wed, 1 Mar 2000 20:13:47 +0100 (MET)
Date: Wed, 1 Mar 2000 20:13:47 +0100 (MET)
Message-Id: <200003011913.UAA22158@oberkampf.ilog.fr>
To: Eric Fischer <enf@pobox.com>
Cc: groff@ffii.org
In-Reply-To: <200002291920.NAA66959@216-80-13-65.d.enteract.com>
References: <200002291920.NAA66959@216-80-13-65.d.enteract.com>
Subject: [Groff] Re: UTF-8/Unicode for groff
Status: O
Content-Length: 2102
Lines: 51

Eric Fischer writes:

>   (2) For Unicode characters that do not appear in the current font,
>       I have set it up to automatically substitute bitmap versions
>       of the characters.  These are created spontaneously from Roman
>       Czyborra's "unifont" font whenever troff finds it cannot
>       locate a U+xxxx character, and are accomplished through the
>       equivalent of .char with a series of \h, \v, and \D to draw
>       the bitmapped image.  I'm not terribly happy with this, but it
>       seems better than not being able to do anything at all with
>       the characters.

Bitmap as a fallback is a nice solution. But before going into details,
here are more ideas for work.

* Higher Unicode support

  Unicode plain text may have combining characters, right-to-left writing
  (hebrew, arabic), and text which needs special rendering rules: When
  rendering Arabic, one needs to classify the letters at medial/initial/final/
  isolated, and choose the appropriate shapes. When rendering some Indic
  scripts, one needs to rearrange the letters in the words (vowels come
  first, etc.).

  You can ignore these problems, or you can decide to deal with them in
  libgroff.

* Unicode support in devps

  Why would you use Roman Czyborra's low-resolution font, when there are
  a lot of high-quality high-resolution TeX fonts available (some on dante.de,
  some elsewhere)? Render these fonts at 600 dpi, and include them into the
  .ps output. This is also what dvips does.

* Unicode support in devutf8

  Here you don't need any bitmap fonts, because the UTF-8 output device is
  supposed to have them. Currently the treatment of combining characters is
  not correct: instead of "LETTER C then COMBINING HACEK" it outputs "LETTER C,
  backspace, HACEK".

* Breaking the limits

  Some pieces of libgroff assume that the fonts are small enough that its
  feasible to load all fonts into memory, and use one C object per character.
  When a font has 40000 characters, this just becomes too slow.

Don't count on me for doing that soon; I'm currently on other projects.

Bruno


From groff-admin  Thu Mar  2 07:18:12 2000
Received: from ax-nicb.axnet.it (root@ax-nicb.axnet.it [194.184.60.149] (may be forged))
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id HAA02313
	for <Groff@ffii.org>; Thu, 2 Mar 2000 07:16:27 +0100
Received: (from nicb@localhost)
	by ax-nicb.axnet.it (8.8.7/8.8.7) id GAA17028;
	Thu, 2 Mar 2000 06:59:28 +0100
Date: Thu, 2 Mar 2000 06:59:28 +0100 (CET)
From: Nicola Bernardini <nicb@axnet.it>
To: Groff@ffii.org
Message-ID: <Pine.LNX.4.10.10003011115440.2117-100000@ax-nicb.axnet.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] how to access the CVS server
Status: O
Content-Length: 303
Lines: 17

Dear all,

sorry if this has been asked before: I can't find any info anywhere
on where is the groff cvs server and what are the CVSROOT login
and passwd to check out latest snapshots.

thanks

nicb

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




From groff-admin  Thu Mar  2 08:45:41 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id IAA02817
	for <groff@ffii.org>; Thu, 2 Mar 2000 08:45:40 +0100
Received: from zabriskie.EECS.Berkeley.EDU (zabriskie.EECS.Berkeley.EDU [128.32.139.25])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id CAA22186
	for <groff@gnu.org>; Thu, 2 Mar 2000 02:46:26 -0500
Received: (from adm@localhost)
	by zabriskie.EECS.Berkeley.EDU (8.8.5/8.8.5) id XAA21872
	for groff@gnu.org; Wed, 1 Mar 2000 23:46:25 -0800 (PST)
Date: Wed, 1 Mar 2000 23:46:25 -0800 (PST)
X-Authentication-Warning: zabriskie.EECS.Berkeley.EDU: adm set sender to daniel@synchrods.synchrods.COM using -f
>Date: Wed, 1 Mar 00 23:30:33 PST
From: daniel@synchrods.synchrods.COM (Daniel Senderowicz)
Message-Id: <10003020730.AA05275@synchrods.synchrods.COM>
To: groff@gnu.org
Cc: sx0005@sx2.hrz.uni-dortmund.de
Content-Type: text
Subject: [Groff] plot2dev
Status: O
Content-Length: 592
Lines: 17

Werner,

After I took a look at grnplot and plot2fig I decided to add the
gremlin driver to plot2fig making it "plot2dev", which I think
was the original intention. plot2dev is a MUCH better program
than grnplot -- it has auto-scaling, binary file multi-format,
etc. And also it doesn't have any licensing problem since it IS
already a GNU program. It would be good if you could also add in
the "SEE ALSO" section of the grn man page the reference
"plot2dev".

Did you ever get xgremlin fixed for Linux? That way we have
pretty much everything we need for the graphics stuff. Regards,

Dan



From groff-admin  Thu Mar  2 11:54:42 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/GNU) with ESMTP id LAA04182
	for <Groff@ffii.org>; Thu, 2 Mar 2000 11:54:42 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 2 Mar 2000 11:55:24 +0100
Received: from rigel.univie.ac.at (dial-143198.HRZ.Uni-Dortmund.DE [129.217.143.198])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id LAA20055;
	Thu, 2 Mar 2000 11:55:23 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA20254;
	Thu, 2 Mar 2000 10:43:24 GMT
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] how to access the CVS server
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.4.10.10003011115440.2117-100000@ax-nicb.axnet.it>
References: <Pine.LNX.4.10.10003011115440.2117-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.94 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
Message-Id: <20000302104324K.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 02 Mar 2000 10:43:24 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 750
Lines: 25

> sorry if this has been asked before: I can't find any info anywhere
> on where is the groff cvs server and what are the CVSROOT login and
> passwd to check out latest snapshots.

Here the relevant portion of groff's README file (as can be found on
ftp.gnu.org) for groff 1.15:


  A CVS repository is now available, containing the current
  development version of groff.  You can access it with the commands

    export CVSROOT=:pserver:anoncvs@anoncvs.ffii.org:/var/cvs
    cvs login  
    cvs -z9 co groff

  (if the prompt for the password appears, just press the enter key).
  After a successful login you no longer need the first two commands;
  an update of a checked out repository should be done with

    cvs -z9 update -dP



    Werner


From groff-admin  Thu Mar  2 11:54:46 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA04222
	for <groff@ffii.org>; Thu, 2 Mar 2000 11:54:45 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id FAA07205
	for <groff@gnu.org>; Thu, 2 Mar 2000 05:55:32 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 2 Mar 2000 11:55:26 +0100
Received: from rigel.univie.ac.at (dial-143198.HRZ.Uni-Dortmund.DE [129.217.143.198])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id LAA20061;
	Thu, 2 Mar 2000 11:55:25 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA20269;
	Thu, 2 Mar 2000 10:52:25 GMT
To: daniel@synchrods.synchrods.COM
Cc: groff@gnu.org
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <10003020730.AA05275@synchrods.synchrods.COM>
References: <10003020730.AA05275@synchrods.synchrods.COM>
X-Mailer: Mew version 1.94 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
Message-Id: <20000302105225I.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 02 Mar 2000 10:52:25 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] Re: plot2dev
Status: O
Content-Length: 1044
Lines: 26

> After I took a look at grnplot and plot2fig I decided to add the
> gremlin driver to plot2fig making it "plot2dev", which I think was
> the original intention. plot2dev is a MUCH better program than
> grnplot -- it has auto-scaling, binary file multi-format, etc.

Nice!

>  And also it doesn't have any licensing problem since it IS already
> a GNU program.  It would be good if you could also add in the "SEE
> ALSO" section of the grn man page the reference "plot2dev".

I will do that -- where is the home site of plot2dev?  I would like to
add the URL to the MORE.STUFF file in the groff package.

> Did you ever get xgremlin fixed for Linux?  That way we have pretty
> much everything we need for the graphics stuff. Regards,

xgremlin works, but xgremlin2 not (yet) -- the graphics are displayed
OK, but I only get black boxes instead of letters if I type in some
text.  I believe that a fix is simple, but unfortunately, I'm not a X
expert, and I don't have the knowledge (and the interest, I must
admit) to correct it.


    Werner


From groff-admin  Thu Mar  2 18:28:51 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA08135
	for <groff@ffii.org>; Thu, 2 Mar 2000 18:28:49 +0100
Received: from zabriskie.EECS.Berkeley.EDU (zabriskie.EECS.Berkeley.EDU [128.32.139.25])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id MAA05340
	for <groff@gnu.org>; Thu, 2 Mar 2000 12:29:29 -0500
Received: (from adm@localhost)
	by zabriskie.EECS.Berkeley.EDU (8.8.5/8.8.5) id JAA00842
	for groff@gnu.org; Thu, 2 Mar 2000 09:29:28 -0800 (PST)
Date: Thu, 2 Mar 2000 09:29:28 -0800 (PST)
X-Authentication-Warning: zabriskie.EECS.Berkeley.EDU: adm set sender to daniel@synchrods.synchrods.COM using -f
>Date: Thu, 2 Mar 00 09:15:36 PST
From: daniel@synchrods.synchrods.COM (Daniel Senderowicz)
Message-Id: <10003021715.AA05997@synchrods.synchrods.COM>
To: sx0005@sx2.hrz.uni-dortmund.de
Subject: Re:  [Groff] Re: plot2dev
Cc: groff@gnu.org
Content-Type: text
Status: O
Content-Length: 1357
Lines: 37

Werner,

	I will do that -- where is the home site of plot2dev?  I would like to
	add the URL to the MORE.STUFF file in the groff package.

The old version (without the gremlin driver) can be found in:

    Location: /pub/TeX/Tools/transfig
      FILE    -rw-rw-r--         28288  05:00  4 May 1991  plot2fig.tar.Z

I don't have write access to any public URL, so that's why I'm
sending it to you so you can post it somewhere in your gnu
site. I'm resending you the tarball because I fixed a little
thing.

	> Did you ever get xgremlin fixed for Linux?  That way we have pretty
	> much everything we need for the graphics stuff. Regards,
	
	xgremlin works, but xgremlin2 not (yet) -- the graphics are displayed
	OK, but I only get black boxes instead of letters if I type in some
	text.  I believe that a fix is simple, but unfortunately, I'm not a X
	expert, and I don't have the knowledge (and the interest, I must
	admit) to correct it.

I don't either have expertise in X otherwise I would fix it (any
volunteers out there?).

I was thinking that the next interesting addition to the groff
package would be a `fig' preprocessor. But before doing that, it
would be best if we would have some color processing
capabilities in groff (do we?) to better exploit the xfig
features. Since I'm already "warmed up" with grn, I could
volunteer to do that.

Dan



From groff-admin  Fri Mar  3 00:36:45 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id AAA10429
	for <groff@ffii.org>; Fri, 3 Mar 2000 00:36:44 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id SAA31725
	for <groff@gnu.org>; Thu, 2 Mar 2000 18:37:34 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 3 Mar 2000 00:37:09 +0100
Received: from rigel.univie.ac.at (dial-143147.HRZ.Uni-Dortmund.DE [129.217.143.147])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id AAA24186;
	Fri, 3 Mar 2000 00:37:08 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id XAA29297;
	Thu, 2 Mar 2000 23:09:53 GMT
To: daniel@synchrods.synchrods.COM
Cc: groff@gnu.org
Subject: Re:  [Groff] Re: plot2dev
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <10003021715.AA05997@synchrods.synchrods.COM>
References: <10003021715.AA05997@synchrods.synchrods.COM>
X-Mailer: Mew version 1.94 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
Message-Id: <20000302230953J.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 02 Mar 2000 23:09:53 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 689
Lines: 21

> I don't have write access to any public URL, so that's why I'm
> sending it to you so you can post it somewhere in your gnu
> site. I'm resending you the tarball because I fixed a little
> thing.

OK, I'll put it in

  ftp://ftp.ffii.org/pub/groff/plot2dev.tar.gz

> I was thinking that the next interesting addition to the groff
> package would be a `fig' preprocessor.  But before doing that, it
> would be best if we would have some color processing capabilities in
> groff (do we?) to better exploit the xfig features.  Since I'm
> already "warmed up" with grn, I could volunteer to do that.

Do you already have an idea how a color interface to groff could look
like?


    Werner


From groff-admin  Fri Mar  3 01:28:42 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA10873
	for <groff@ffii.org>; Fri, 3 Mar 2000 01:28:41 +0100
Received: from zabriskie.EECS.Berkeley.EDU (zabriskie.EECS.Berkeley.EDU [128.32.139.25])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id TAA01262
	for <groff@gnu.org>; Thu, 2 Mar 2000 19:29:30 -0500
Received: (from adm@localhost)
	by zabriskie.EECS.Berkeley.EDU (8.8.5/8.8.5) id QAA08554
	for groff@gnu.org; Thu, 2 Mar 2000 16:29:28 -0800 (PST)
Date: Thu, 2 Mar 2000 16:29:28 -0800 (PST)
X-Authentication-Warning: zabriskie.EECS.Berkeley.EDU: adm set sender to daniel@synchrods.synchrods.COM using -f
>Date: Thu, 2 Mar 00 16:12:39 PST
From: daniel@synchrods.synchrods.COM (Daniel Senderowicz)
Message-Id: <10003030012.AA06931@synchrods.synchrods.COM>
To: sx0005@sx2.hrz.uni-dortmund.de
Subject: Re:  [Groff] Re: plot2dev
Cc: groff@gnu.org
Content-Type: text
Status: O
Content-Length: 1192
Lines: 35

Werner,

>> I don't have write access to any public URL, so that's why I'm
>> sending it to you so you can post it somewhere in your gnu
>> site. I'm resending you the tarball because I fixed a little
>> thing.
>
>OK, I'll put it in
>
>  ftp://ftp.ffii.org/pub/groff/plot2dev.tar.gz

Thanks.

>
>> I was thinking that the next interesting addition to the groff
>> package would be a `fig' preprocessor.  But before doing that, it
>> would be best if we would have some color processing capabilities in
>> groff (do we?) to better exploit the xfig features.  Since I'm
>> already "warmed up" with grn, I could volunteer to do that.
>
>Do you already have an idea how a color interface to groff could look
>like?

I didn't look at the `fig' file format yet. But I suppose that we
would need something like what we currently have: \D'f ...' but
with additional color commands. Similar things for the lines. It
would also help if we would have color filled patterns like
closed splines and ellipses in addition to the filled polygons
that we already have. Don't ask me how to define the colors but
I imagine that it will have to be a composite similar to the way
that the X11 stuff works.

Dan



From groff-admin  Fri Mar  3 14:03:24 2000
Received: from ns1.greenbush.com (mngovsci@ns1.greenbush.com [209.90.218.2])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA28779
	for <groff@ffii.org>; Fri, 3 Mar 2000 14:03:23 +0100
Received: from localhost (mngovsci@localhost)
	by ns1.greenbush.com (8.9.3/8.8.7) with SMTP id IAA28432
	for <groff@ffii.org>; Fri, 3 Mar 2000 08:04:11 -0500
Date: Fri, 3 Mar 2000 08:04:11 -0500 (EST)
From: Eddie Maddox <eddie@mngovsci.com>
X-Sender: mngovsci@ns1.greenbush.com
To: Groff Mailing List <groff@ffii.org>
In-Reply-To: <m1243Oo-000ivaC@merlin.freeserve.net>
Message-ID: <Pine.LNX.3.96.1000303073726.28319B-100000@ns1.greenbush.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] Groff CD?
Status: O
Content-Length: 905
Lines: 25

Groff CD?

It was suggested to me, since I am now a Proud Owner of a new HP CD
writer, and wondering if it can make me rich^H^H^H^H money, that I put
together a Groff CD. 

Does this make sense to anybody here? Would anyone buy it? For how much?
What should be on it? Should extra stuff be added to fill up any leftover
empty space?  (600+ MB of elbow room)

Anyone have experience burning and shipping these things? The burning I
got mostly figured out from the HOWTOs. Any tips on anything, though, like
international commerce, non-English speaking customers, etc?

I just started a Micro-entrepreneur Training Program in my St. Paul,
Minnesota, USA neighborhood.  The main theme is writing up a Business
Plan, to use when begging for money! Of ~8 in our class I'm the only one
with an Internet based business idea: selling specialty software CDs.

------------------
Eddie Maddox
eddie@mngovsci.com




From groff-admin  Sat Mar  4 07:25:21 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/GNU) with ESMTP id HAA15789
	for <groff@ffii.org>; Sat, 4 Mar 2000 07:25:21 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 4 Mar 2000 07:26:15 +0100
Received: from rigel.univie.ac.at (dial-143181.HRZ.Uni-Dortmund.DE [129.217.143.181])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id HAA19653;
	Sat, 4 Mar 2000 07:26:12 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id WAA32619;
	Fri, 3 Mar 2000 22:32:17 GMT
To: eddie@mngovsci.com
Cc: groff@ffii.org
Subject: Re: [Groff] Groff CD?
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.3.96.1000303073726.28319B-100000@ns1.greenbush.com>
References: <m1243Oo-000ivaC@merlin.freeserve.net>
	<Pine.LNX.3.96.1000303073726.28319B-100000@ns1.greenbush.com>
X-Mailer: Mew version 1.94 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
Message-Id: <20000303223216A.sx0005@sx2.hrz.uni-dortmund.de>
Date: Fri, 03 Mar 2000 22:32:16 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 693
Lines: 18

> It was suggested to me, since I am now a Proud Owner of a new HP CD
> writer, and wondering if it can make me rich^H^H^H^H money, that I
> put together a Groff CD.
> 
> Does this make sense to anybody here?  Would anyone buy it?  For how
> much?  What should be on it?  Should extra stuff be added to fill up
> any leftover empty space?  (600+ MB of elbow room)

I doubt that it makes sense.  Since groff is part of every Linux
system, everybody has it.  And the size of the developement archive
isn't large enough to justify a CD with only groff on it.

And there aren't many troff macros packages (besides the ones which
already come with groff) available (unfortunately)...


    Werner


From groff-admin  Mon Mar  6 11:13:03 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/GNU) with ESMTP id LAA12553
	for <groff@ffii.org>; Mon, 6 Mar 2000 11:13:03 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 6 Mar 2000 11:14:14 +0100
Received: from rigel.univie.ac.at (dial-143139.HRZ.Uni-Dortmund.DE [129.217.143.139])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id LAA19924
	for <groff@ffii.org>; Mon, 6 Mar 2000 11:14:11 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA10899
	for <groff@ffii.org>; Mon, 6 Mar 2000 10:11:31 GMT
To: groff@ffii.org
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
X-Mailer: Mew version 1.94 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Mon_Mar__6_10:11:28_2000_597)--"
Content-Transfer-Encoding: 7bit
Message-Id: <20000306101130N.sx0005@sx2.hrz.uni-dortmund.de>
Date: Mon, 06 Mar 2000 10:11:30 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] groff_man.man revised
Status: O
Content-Length: 9673
Lines: 336

----Next_Part(Mon_Mar__6_10:11:28_2000_597)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Dear friends,


I've completely revised groff_man.man; it now covers *everything* of
the tmac.an macros -- some things may surprise you...

Please check!  I'm especially interested whether there are differences
to the original Unix troff tmac.an.

For you reference, I've attached it.


    Werner

----Next_Part(Mon_Mar__6_10:11:28_2000_597)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="groff_man.man"

.de TQ
.br
.ns
.TP \\$1
..
.TH GROFF_MAN @MAN7EXT@ "@MDATE@" "Groff Version @VERSION@"
.
.SH NAME
.
groff_man \- groff `an' macros to support generation of man pages
.
.SH SYNOPSIS
.
.B groff
.B \-m@TMAC_AN_PREFIX@an
[
.IR options .\|.\|.
]
[
.IR files .\|.\|.
]
.
.SH DESCRIPTION
.
The 
.B tmac.an 
macros used to generate man pages with 
.I groff
were written by James Clark.  
This document provides a brief summary of the use of each macro in that
package.
.
.SH OPTIONS
.
The
.B man
macros understand the following command line options (which define various
registers).
.TP
.B \-rC1
If more than one manual page is given on the command line, number the
pages continuously, rather than starting each at\ 1.
.TP
.B \-rD1
Double-sided printing.
Footers for even and odd pages look different.
.TP
.BI \-rP nnn
Enumeration of pages will start with
.I nnn
rather than with\ 1.
.TP
.BI \-rX nnn
After page
.IR nnn ,
number pages as
.IR nnn a,
.IR nnn b,
.IR nnn c,
etc.
For example, the option `\-rX2' will produce the following page numbers:
1, 2, 2a, 2b, 2c, etc.
.
.SH USAGE
.
This section describes the available macros for manual pages.
For further customization, put additional macros and requests into the file
.B man.local
which will be loaded immediately after
.BR tmac.an .
.TP
.BI .TH " title section " [ extra1 "] [" extra2 "] [" extra3 ]
Sets the title of the man page to 
.I title
and the section to
.IR section ,
which must take on a value between 1 and\ 8.
The value
.I section
may also have a string appended, e.g. `.pm', to indicate a specific
subsection of the man pages.
.TP
.BI ".SH [" "text for a heading" ]
Sets up an unnumbered section heading sticking out to the left.
Prints out all the text following `.SH' up to the end of the line (resp. the
text in the next line if there is no argument to `.SH') in bold face, at a
default size of 9\ point.
Additionally, the left margin for the following text is reset to its default
value.
.TP
.BI ".SS [" "text for a heading" ]
Sets up an unnumbered section heading.
Prints out all the text following `.SS' up to the end of the line (resp. the
text in the next line if there is no argument to `.SS') in bold face, at a
default size of 10\ point.
Additionally, the left margin for the following text is reset to its default
value.
.TP
.BI ".TP [" nnn ]
Sets up an indented paragraph with label.
The indentation is set to 
.I nnn
if that argument is supplied (the default unit is `n' if omitted), otherwise
it is set to the default indentation value.
The first line of text following this macro is interpreted as a string to be
printed flush-left, as it is appropriate for a label.
It is not interpreted as part of a paragraph, so there is no attempt to fill
the first line with text from the following input lines.
Nevertheless, if the label is not as wide as the indentation, then the
paragraph starts at the same line (but indented), continuing on the
following lines.
If the label is wider than the indentation, then the descriptive part of the
paragraph begins on the line following the label, entirely indented.
Note that neither font shape nor font size of the label is set to a default
value; on the other hand, the rest of the text will have default font
settings.
The `.TP' macro is the macro used for the explanations you are just reading.
.TP
.B .LP
.TQ
.B .PP
.TQ
.B .P
These macros are mutual aliases.
Any of them causes a line break at the current position, followed by a
vertical space downwards by the amount specified by the `PD' macro.
The font size and shape are reset to the default value (10pt resp. Roman).
Finally, the current left margin is restored.
.TP
.BI ".IP [" designator "] [" nnn ]
Sets up an indented paragraph, using 
.I designator 
as a tag to mark its beginning.
The indentation is set to
.I nnn
if that argument is supplied (default unit is `n'), otherwise the default
indentation value is used.
Font size and face of the paragraph (but not the designator) are reset to
its default values.
To start an indented paragraph with a particular indentation but without a
designator, use `""' (two doublequotes) as the second argument.
.IP
For example, the following paragraphs were all set up with bullets as the
designator, using `.IP\ \\(bu\ 4':
.RS
.IP \(bu 4
`IP' is one of the three macros used in 
.B tmac.an
to format lists.
.IP \(bu 4
`HP' is another.
This macro produces a paragraph with a left hanging indentation.
.IP \(bu 4
`TP' is another.
This macro produces an unindented label followed by an indented paragraph.
.RE
.TP
.BI ".HP [" nnn ]
Sets up a paragraph with hanging left indentation.
The indentation is set to
.I nnn
if that argument is supplied (default unit is `n'), otherwise the default
indentation value is used.
Font size and face are reset to its default values.
The following paragraph illustrates the effect of this macro with hanging
indentation set to\ 4:
.RS
.HP 4
This is a paragraph following an invocation of the `.HP' macro.
As you can see, it produces a paragraph where all lines but the first are
flushed right and are shorter than the preceding lines.
.RE
.TP
.BI ".RS [" nnn ]
This macro moves the left margin to the right by the value
.I nnn
if specified (default unit is `n'); otherwise the default indentation value
is used.
Calls to the `RS' macro can be nested.
.TP
.BI ".RE [" nnn ]
This macro moves the left margin back to level
.IR nnn ;
if no argument is given, it moves one level back.
The first level (i.e., no call to `RS' yet) has number\ 1, and each call to
`RS' increases the level by\ 1.
.
.SH "MACROS TO SET FONTS"
.
The standard font is Roman; the default text size is 10 point.
.TP
.BI ".SM [" text ]
Causes the text on the same line or the text on the next line to appear in a
font that is one point size smaller than the default font.
.TP
.BI ".SB [" text ]
Causes the text on the same line or the text on the next line to appear in
boldface font, one point size smaller than the default font.
.TP
.BI ".BI " text
Causes text on the same line to appear alternately in bold face and italic.
The text must be on the same line as the macro call.
Thus `.BI this "word and" that' would cause `this' and `that' to appear in
bold face, while `word and' appears in italics.
.TP
.BI ".IB " text
Causes text to appear alternately in italic and bold face.
The text must be on the same line as the macro call.
.TP
.BI ".RI " text
Causes text on the same line to appear alternately in roman and italic.
The text must be on the same line as the macro call.
.TP
.BI ".IR " text
Causes text on the same line to appear alternately in italic and roman.
The text must be on the same line as the macro call.
.TP
.BI ".BR " text
Causes text on the same line to appear alternately in bold face and roman.
The text must be on the same line as the macro call.
.TP
.BI ".RB " text
Causes text on the same line to appear alternately in roman and bold face.
The text must be on the same line as the macro call.
.TP
.BI ".R " text
Causes text to appear in roman font.
If no text is present on the line where the macro is called, then the text
of the next line appears in roman.
This is the default font to which text is returned at the end of processing
of the other macros.
.TP
.BI ".B [" text ]
Causes text to appear in bold face.
If no text is present on the line where the macro is called, then the text
of the next line appears in bold face.
.TP
.BI ".I [" text ]
Causes text to appear in italic.
If no text is present on the line where the macro is called, then the text
of the next line appears in italic.
.
.SH "MISCELLANEOUS"
.
The default indentation is 7.2n for all output devices except for
.B grohtml
which uses 1.2i instead.
.TP
.B .DT
Sets tabs every 0.5 inches.
Since this macro is always called during a
.B TH
request, it makes sense to call it only if the tab positions have been
changed.
.TP
.BI ".PD [" nnn ]
Adjusts the empty space before a new paragraph (resp. section).
The optional argument gives the amount of space (default units are `v');
without parameter, the value is reset to its default value (1 line for tty
devices, 0.4v otherwise).
This affects the macros
.BR SH ,
.BR SS ,
.BR TP ,
.B LP
(resp.\&
.B PP
and
.BR P ),
.BR IP ,
and
.BR HP .
.PP
The following strings are defined:
.TP
.B \e*S
Switch back to the default font size.
.TP
.B \e*R
The `registered' sign.
.TP
.B \e*(Tm
The `trademark' sign.
.TP
.B \e*(lq
.TQ
.B \e*(rq
Left and right quote.
This is equal to `\e(lq' and `\e(rq', respectively.
.
.SH "SEE ALSO"
.
Since the 
.B tmac.an
macros consist of groups of 
.I groff 
requests, one can, in principle, supplement the functionality of the
.B tmac.an
macros with individual 
.I groff
requests where necessary.
A complete list of these requests is available on the WWW at
.ce 1
http://www.cs.pdx.edu/~trent/gnu/groff/groff_toc.html
.
.SH AUTHOR
.
This manual page was originally written for the Debian GNU/Linux system by
Susan G. Kleinmann <sgk@debian.org>, corrected by Werner Lemberg
<wl@gnu.org>, and is now part of the GNU troff distribution.

----Next_Part(Mon_Mar__6_10:11:28_2000_597)----


From groff-admin  Tue Mar  7 10:24:17 2000
Received: from atlantis.erlm.siemens.de (atlantis.erlm.siemens.de [212.114.202.14])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id KAA02510
	for <groff@ffii.org>; Tue, 7 Mar 2000 10:24:17 +0100
Received: from tcenter.erlm.siemens.de (tcenter.erlm.siemens.de [193.98.99.20])
	by atlantis.erlm.siemens.de (8.9.3/8.9.3) with ESMTP id KAA28370
	for <groff@ffii.org>; Tue, 7 Mar 2000 10:03:23 +0100 (MET)
Received: from nbgv101a.nbg9.siemens.de (nbgv101a.nbg9.siemens.de [130.170.148.248])
	by tcenter.erlm.siemens.de (8.9.0/8.9.0) with ESMTP id KAA20517
	for <groff@ffii.org>; Tue, 7 Mar 2000 10:00:58 +0100 (MET)
Received: by NBGV101A with Internet Mail Service (5.5.2650.21)
	id <GG0WDKGL>; Tue, 7 Mar 2000 10:04:39 +0100
Message-ID: <11DD9734B036D311947400805F0DD60703641A@NBGV101A>
From: Freudenberger Joerg <Joerg.Freudenberger@nbg9.siemens.de>
To: "'groff@ffii.org'" <groff@ffii.org>
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
Date: Tue, 7 Mar 2000 10:04:37 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id KAA02511
Status: O
Content-Length: 2048
Lines: 67

Dear Werner,
dear friends,

I compare with man(5) of SunOS 5.4 aka Solaris 2.4.

( Remark: the differences are taken of the man page,
the are not tested. And I don't imply any recommandation. 
It's just that commercial UNIX of that I got a man page
about the man pages. The printed docs of the dead versions
(You may prefer to read: the ancient versions of UNIX)
I got doesn't provide this )


1. That implementation doesn't provide OPTIONS. 
	{ I've ever missed double-sided printing }

2. All macros which having text arguments
accept zero to six (troff-)words. 
If one of the following 
( .B .BI .BR .I .IB .IR. .RB .RI .SM .SS [.R isn't listed ])
has no arg it uses the next text line.

3. "prevailing indent" is remembered as long as not a new 
indent value is set.  indent macros are ( .HP .IP .RS .TP ).
.RE has no argument.

4. The "Text Header" macro ( .TH ) is defined with 5 arguments
	$1 Title
	$2 Section
	$3 (optional) Date of the most recent change
	$4 (optional) left page footer
	$5 (optional) main page header (center of headline)

5. The following requests cause a break:
.HP .IP .LP .P .PP .RE .RS .SH .SS .TH .TP 

6. It predefines only \*R and \*S.

7. It contains a very short tbl example for the man(1) preprocessing
This is excerpted from man(1):
If the first line is 
	'\" <word>
the input is processed by the corresponding preprocessor. 
Mind the single Space. <word> contains e for eqn, r for refer
t for tbl and v for vgrind.

8. Two Macros ( .IX .TX ) are additionaly defined. The first ist 
an index macro mark as for SunSoft internal use. The later 
is explained as resolving title abbreviation. IMHO only
for internal interest 

//
The Sun Man Page give only shorthand technical discription, but
much more semantic and formal advise.

Comparing the both macro packets on source code level needs more 
troff expirience than I have. 

//
May we get Trent's request list into the distribution ?

Yours
	Jörg

P.S: I have not yet restarted working on the white paper.
	My Computer at home had an installation chrash. 


From groff-admin  Tue Mar  7 14:43:38 2000
Received: from mailgw1.be.to (mailgw1.be.to [210.235.212.5])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA04189
	for <groff@ffii.org>; Tue, 7 Mar 2000 14:43:35 +0100
Received: from mail1.be.to (point1.be.to [210.235.212.29])
	by mailgw1.be.to (8.9.3+3.2W/BETO.2.1-2000021722000035) with ESMTP id WAA11554
	for <groff@ffii.org>; Tue, 7 Mar 2000 22:44:53 +0900
Received: from acidrain (ppp11-Mobara1.mtci.ne.jp [210.172.1.213])
	by mail1.be.to (8.8.8+3.0Wbeta13/BETO.2.0-1999110714000000) with SMTP id WAA08210
	for <groff@ffii.org>; Tue, 7 Mar 2000 22:44:48 +0900
Received: (qmail 2516 invoked from network); 7 Mar 2000 13:44:13 -0000
Received: from localhost (HELO acidrain.localnet) (127.0.0.1)
  by localhost with SMTP; 7 Mar 2000 13:44:13 -0000
Date: Tue, 07 Mar 2000 22:44:11 +0900
Message-ID: <86hfeic2tw.wl@dolphin.be.to>
From: OKAZAKI Tetsurou <okazaki@be.to>
To: groff@ffii.org
User-Agent: Wanderlust/1.1.0 (Overjoyed-pre3) REMI/1.14.1
 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) Chao/1.14.0 (Momoyama) APEL/10.2
 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN)
Organization: Unknown
MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?=
 =?ISO-8859-4?Q?sugi=22?=)
Content-Type: multipart/mixed;
 boundary="Multipart_Tue_Mar__7_22:44:11_2000-1"
Subject: [Groff] [patch] script installation
Status: O
Content-Length: 3240
Lines: 98

--Multipart_Tue_Mar__7_22:44:11_2000-1
Content-Type: text/plain; charset=US-ASCII

Hi,

Would you commit the patch below to the groff development tree?
I want to use INSTALL_SCRIPT for script installations. :-)


Tetsurou



--Multipart_Tue_Mar__7_22:44:11_2000-1
Content-Type: text/plain; charset=US-ASCII

diff -urN groff-cvs/Makefile.in groff/Makefile.in
--- groff-cvs/Makefile.in	Mon Mar  6 03:05:34 2000
+++ groff/Makefile.in	Tue Mar  7 21:56:00 2000
@@ -199,6 +199,7 @@
 RANLIB=@RANLIB@
 INSTALL=@INSTALL@
 INSTALL_PROGRAM=@INSTALL_PROGRAM@
+INSTALL_SCRIPT=@INSTALL_SCRIPT@
 INSTALL_DATA=@INSTALL_DATA@
 LN_S=@LN_S@
 AR=ar
@@ -278,6 +279,7 @@
   "RANLIB=$(RANLIB)" \
   "AR=$(AR)" \
   "INSTALL_PROGRAM=$(INSTALL_PROGRAM)" \
+  "INSTALL_SCRIPT=$(INSTALL_SCRIPT)" \
   "INSTALL_DATA=$(INSTALL_DATA)" \
   "ETAGS=$(ETAGS)" \
   "ETAGSFLAGS=$(ETAGSFLAGS)" \
diff -urN groff-cvs/contrib/mm/Makefile.sub groff/contrib/mm/Makefile.sub
--- groff-cvs/contrib/mm/Makefile.sub	Tue Feb 22 05:32:58 2000
+++ groff/contrib/mm/Makefile.sub	Tue Mar  7 22:03:03 2000
@@ -31,7 +31,7 @@
 install_mmroff : mmroff
 	-test -d $(bindir) || $(mkinstalldirs) $(bindir)
 	-rm -f $(bindir)/mmroff
-	$(INSTALL_PROGRAM) mmroff $(bindir)/mmroff
+	$(INSTALL_SCRIPT) mmroff $(bindir)/mmroff
 
 mmroff: mmroff.pl
 	-rm -f $@
diff -urN groff-cvs/src/preproc/eqn/Makefile.sub groff/src/preproc/eqn/Makefile.sub
--- groff-cvs/src/preproc/eqn/Makefile.sub	Sun Feb  6 18:37:56 2000
+++ groff/src/preproc/eqn/Makefile.sub	Tue Mar  7 22:00:43 2000
@@ -51,7 +51,7 @@
 
 install_data: neqn
 	-rm -f $(bindir)/$(NAMEPREFIX)neqn
-	$(INSTALL_PROGRAM) neqn $(bindir)/$(NAMEPREFIX)neqn
+	$(INSTALL_SCRIPT) neqn $(bindir)/$(NAMEPREFIX)neqn
 
 uninstall_sub:
 	-rm -f $(bindir)/$(NAMEPREFIX)neqn
diff -urN groff-cvs/src/roff/grog/Makefile.sub groff/src/roff/grog/Makefile.sub
--- groff-cvs/src/roff/grog/Makefile.sub	Sun Feb  6 18:36:30 2000
+++ groff/src/roff/grog/Makefile.sub	Tue Mar  7 21:59:06 2000
@@ -16,7 +16,7 @@
 install_data: grog
 	-test -d $(bindir) || $(mkinstalldirs) $(bindir)
 	-rm -f $(bindir)/grog
-	$(INSTALL_PROGRAM) grog $(bindir)/grog
+	$(INSTALL_SCRIPT) grog $(bindir)/grog
 
 uninstall_sub:
 	-rm -f $(bindir)/grog
diff -urN groff-cvs/src/roff/nroff/Makefile.sub groff/src/roff/nroff/Makefile.sub
--- groff-cvs/src/roff/nroff/Makefile.sub	Sun Feb  6 18:36:30 2000
+++ groff/src/roff/nroff/Makefile.sub	Tue Mar  7 22:02:06 2000
@@ -12,7 +12,7 @@
 install_data: nroff
 	-test -d $(bindir) || $(mkinstalldirs) $(bindir)
 	-rm -f $(bindir)/$(NAMEPREFIX)nroff
-	$(INSTALL_PROGRAM) nroff $(bindir)/$(NAMEPREFIX)nroff
+	$(INSTALL_SCRIPT) nroff $(bindir)/$(NAMEPREFIX)nroff
 
 uninstall_sub:
 	-rm -f $(bindir)/$(NAMEPREFIX)nroff
diff -urN groff-cvs/src/utils/afmtodit/Makefile.sub groff/src/utils/afmtodit/Makefile.sub
--- groff-cvs/src/utils/afmtodit/Makefile.sub	Sun Feb  6 18:37:18 2000
+++ groff/src/utils/afmtodit/Makefile.sub	Tue Mar  7 21:57:47 2000
@@ -15,7 +15,7 @@
 install_data: afmtodit
 	-test -d $(bindir) || $(mkinstalldirs) $(bindir)
 	-rm -f $(bindir)/afmtodit
-	$(INSTALL_PROGRAM) afmtodit $(bindir)/afmtodit
+	$(INSTALL_SCRIPT) afmtodit $(bindir)/afmtodit
 
 uninstall_sub:
 	-rm -f $(bindir)/afmtodit

--Multipart_Tue_Mar__7_22:44:11_2000-1--


From groff-admin  Tue Mar  7 22:23:29 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/GNU) with ESMTP id WAA07562
	for <groff@ffii.org>; Tue, 7 Mar 2000 22:23:28 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 7 Mar 2000 22:24:30 +0100
Received: from rigel.univie.ac.at (dial-143157.HRZ.Uni-Dortmund.DE [129.217.143.157])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id WAA04053;
	Tue, 7 Mar 2000 22:24:29 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id QAA14655;
	Tue, 7 Mar 2000 16:23:27 GMT
To: okazaki@be.to
Cc: groff@ffii.org
Subject: Re: [Groff] [patch] script installation
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <86hfeic2tw.wl@dolphin.be.to>
References: <86hfeic2tw.wl@dolphin.be.to>
X-Mailer: Mew version 1.94 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
Message-Id: <20000307162327B.sx0005@sx2.hrz.uni-dortmund.de>
Date: Tue, 07 Mar 2000 16:23:27 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 209
Lines: 9

> Would you commit the patch below to the groff development tree?
> I want to use INSTALL_SCRIPT for script installations. :-)

Rather undocumented, isn't it? :-)

I'll apply your fixes, thanks.


    Werner


From groff-admin  Tue Mar  7 23:05:28 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA07857
	for <groff@ffii.org>; Tue, 7 Mar 2000 23:05:27 +0100
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by mescaline.gnu.org (8.9.1a/8.9.1) with SMTP id RAA08515
	for <groff@gnu.org>; Tue, 7 Mar 2000 17:06:49 -0500
Received: (qmail 13724 invoked from network); 7 Mar 2000 22:06:42 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 7 Mar 2000 22:06:42 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id XAA00245
	for groff@gnu.org; Tue, 7 Mar 2000 23:06:17 +0100
Message-ID: <20000307230617.C184@mayn.de>
Date: Tue, 7 Mar 2000 23:06:17 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] addition for pic.man
Status: O
Content-Length: 2709
Lines: 110

Stand-alone pic graphics are not trivial, Stevens wrote a paper on this
subject.  So I provide the following section intended for pic.man.  It
would fit at the end of the DESCRIPTION section or after the USAGE
section.  Feel free to taylor it to your needs.

>>>>>>
.SH CONVERSION
.LP
To obtain a stand-alone picture from a pic file enclose your pic code
with the
.BR .PS " and " .PE
requests; roff configuration commands may be added at the beginning of
the file, but no roff text.
.LP
It is necessary to feed this file into groff without adding any page
information, so you must check which .PS and .PE requests are actually
called.  For example, the mm macro package adds a page number, which is
very annoying.  At the moment, calling standard groff without any macro
package works.  Alternatively, you can define your own requests, eg. to
do nothing.
.LP
.nf
.ft B
.RS
.de PS
..
.de PE
..
.RE
.ft
.fi
.LP
.B groff
itself does not provide direct conversion into other graphics file
formats.  But there are lots of possibilities if you first transform
your picture into PostScript(R) format using the groff option
.B -T
.IR ps .
Since this
.IR ps -file
lacks BoundingBox information it is not very useful by itself, but it
may be fed into other conversion programs, usually named
.BI ps2 other
or
.BI psto other
or the like.  Moreover the ghostscript interpreter
.B gs
has built-in graphics conversion devices that are called with the option
.LP
.RS
.BI "gs -sDEVICE=" <devname>
.RE
.LP
Call
.RS
.B gs --help
.RE
.LP
for a list of the available devices.
.LP
As the Encapsulated PostScript File Format EPS is getting more and more
important and the conversion wasn't regarded trivial in the past you
might be interested to know that there is a conversion tool named
.B ps2eps
which does the right job.  It is much better than the tool
.B ps2epsi
packaged with
.BR gs .
<<<<<<<

##################

I propose to add the following entries to the SEE ALSO section

>>>>>
...
.BR gs (@MAN1EXT@),  ps2epsi (@MAN1EXT@),  pstogif (@MAN1EXT@),
.BR pstopnm (@MAN1EXT@), 
...
.B ps2eps
is available from CTAN mirrors, e.g.
.br
<ftp://ftp.shsu.edu/tex-archive/support/ps2eps/>
.LP
W. Richard Stevens - Turning PIC Into HTML
.br
<http://www.kohala.com/start/troff/pic2html.html>
.LP
W. Richard Stevens - Examples of picMacros
.br
<http://www.kohala.com/start/troff/pic.examples.ps>
.LP
<<<<<<

(BTW, should ".BR tex (1)" be ".BR tex (@MAN1EXT@)" and how about
preceding the Kernighan entry by a .LP?).

##################

Moreover I propose to add the following entry to the BUGS section:

>>>>>>>>
.LP
PostScript(R) is a registered trademark of Adobe Systems Incorporation.
<<<<<<<<


Bernd Warken <bwarken@mayn.de>



From groff-admin  Wed Mar  8 08:41:46 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id IAA24581
	for <groff@ffii.org>; Wed, 8 Mar 2000 08:41:45 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id CAA05732
	for <groff@gnu.org>; Wed, 8 Mar 2000 02:43:11 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 8 Mar 2000 08:43:07 +0100
Received: from rigel.univie.ac.at (dial-143186.HRZ.Uni-Dortmund.DE [129.217.143.186])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id IAA24292;
	Wed, 8 Mar 2000 08:43:07 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id HAA19364;
	Wed, 8 Mar 2000 07:34:53 GMT
To: bwarken@mayn.de
Cc: groff@gnu.org
Subject: Re: [Groff] addition for pic.man
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <20000307230617.C184@mayn.de>
References: <20000307230617.C184@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000308073453A.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 08 Mar 2000 07:34:53 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 658
Lines: 20

> Stand-alone pic graphics are not trivial, Stevens wrote a paper on
> this subject.  So I provide the following section intended for
> pic.man.  It would fit at the end of the DESCRIPTION section or
> after the USAGE section.  Feel free to taylor it to your needs.

Thanks a lot!  I've applied it (slightly modified).

> (BTW, should ".BR tex (1)" be ".BR tex (@MAN1EXT@)" and how about
> preceding the Kernighan entry by a .LP?).

I use @MAN...@ only for packages which are installed by the groff
install scripts.

> Moreover I propose to add the following entry to the BUGS section:

:-)  To have a TM remark in the BUGS section is optimal.


    Werner


From groff-admin  Wed Mar  8 09:49:32 2000
Received: from atlantis.erlm.siemens.de (atlantis.erlm.siemens.de [212.114.202.14])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA25092
	for <groff@ffii.org>; Wed, 8 Mar 2000 09:49:32 +0100
Received: from tcenter.erlm.siemens.de (tcenter.erlm.siemens.de [193.98.99.20])
	by atlantis.erlm.siemens.de (8.9.3/8.9.3) with ESMTP id JAA03009;
	Wed, 8 Mar 2000 09:36:30 +0100 (MET)
Received: from nbgv101a.nbg9.siemens.de (nbgv101a.nbg9.siemens.de [130.170.148.248])
	by tcenter.erlm.siemens.de (8.9.0/8.9.0) with ESMTP id JAA12513;
	Wed, 8 Mar 2000 09:33:51 +0100 (MET)
Received: by NBGV101A with Internet Mail Service (5.5.2650.21)
	id <GG0WDLLM>; Wed, 8 Mar 2000 09:37:46 +0100
Message-ID: <11DD9734B036D311947400805F0DD60703641D@NBGV101A>
From: Freudenberger Joerg <Joerg.Freudenberger@nbg9.siemens.de>
To: "'Werner LEMBERG'" <wl@gnu.org>
Cc: "'groff Mailinglist'" <groff@ffii.org>
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
Date: Wed, 8 Mar 2000 09:37:44 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id JAA25093
Status: O
Content-Length: 2570
Lines: 74

> > I compare with man(5) of SunOS 5.4 aka Solaris 2.4.
> 
> Thanks a lot!
> 
> > 1. That implementation doesn't provide OPTIONS. 
> > 	{ I've ever missed double-sided printing }
> 
> I suppose this is a typo: You probably mean `I've never missed...' :-)
> 
> > 2. All macros which having text arguments
> > accept zero to six (troff-)words. 
> > If one of the following 
> > ( .B .BI .BR .I .IB .IR. .RB .RI .SM .SS [.R isn't listed ])
> > has no arg it uses the next text line.
> 
> This is exactly the same behaviour (well, groff accepts an unlimited
> number of arguments).
 
> > 3. "prevailing indent" is remembered as long as not a new 
> > indent value is set.  indent macros are ( .HP .IP .RS .TP ).
> > .RE has no argument.
> 
> I think that groff's tmac.an is thus backwards compatible.
> 
> > 4. The "Text Header" macro ( .TH ) is defined with 5 arguments
> > 	$1 Title
> > 	$2 Section
> > 	$3 (optional) Date of the most recent change
> > 	$4 (optional) left page footer
> > 	$5 (optional) main page header (center of headline)
> 
> Identical.
> 
> > 5. The following requests cause a break:
> > .HP .IP .LP .P .PP .RE .RS .SH .SS .TH .TP 
> 
> Identical -- shall I mention this in groff_man?
I doubt a man pages newbie will honour this. And the advanced will 
get this detail of there look on the printed peaces of paper.
 
> > 7. It contains a very short tbl example for the man(1) preprocessing
> > This is excerpted from man(1):
> > If the first line is 
> > 	'\" <word>
> > the input is processed by the corresponding preprocessor. 
> > Mind the single Space. <word> contains e for eqn, r for refer
> > t for tbl and v for vgrind.
> 
> Hmm.  Not all man implementation honour this, but I'll add some infos
> about this convention.
> 
> > 8. Two Macros ( .IX .TX ) are additionaly defined. The first ist 
> > an index macro mark as for SunSoft internal use. The later 
> > is explained as resolving title abbreviation. IMHO only
> > for internal interest 
> 
> Has someone infos about other tmac.an implemetations?  Shall I define
> this as no-ops?

I think this is not nessessary, because that who try to format vendor
specific man pages also have the "original" tmac.an.
I will quote this information in the compatibility section 
of the white paper.


> > May we get Trent's request list into the distribution ?
> 
> I'll look at it -- is it complete?  Or has it been extracted from
> groff.texinfo (which I'm currently trying to improve)?
I don't know. I hope I get my machine to format texi in the next week
to look at the documentation ...

	Jörg


From groff-admin  Wed Mar  8 12:02:55 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id MAA26149
	for <groff@ffii.org>; Wed, 8 Mar 2000 12:02:54 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id GAA15754
	for <groff@gnu.org>; Wed, 8 Mar 2000 06:04:21 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 8 Mar 2000 12:04:08 +0100
Received: from rigel.univie.ac.at (dial-143161.HRZ.Uni-Dortmund.DE [129.217.143.161])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id MAA01411
	for <groff@gnu.org>; Wed, 8 Mar 2000 12:04:04 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id LAA20259
	for <groff@gnu.org>; Wed, 8 Mar 2000 11:01:57 GMT
To: groff@gnu.org
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000308110156X.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 08 Mar 2000 11:01:56 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] delimiters for escapes
Status: O
Content-Length: 358
Lines: 15

Dear friends,


I've just added some info to groff.texinfo which characters are
alllowed to delimit escape sequences.  The results are *very*
surprising...

Please look at it (type `makeinfo groff.texinfo' to produce info files
or type `texi2dvi groff.texinfo' to produce a DVI version).

Again, I'm interested in a comparison to UNIX troff...


    Werner


From groff-admin  Wed Mar  8 19:48:48 2000
Received: from enf403-2.ensu.ucalgary.ca (root@enf403-2.geomatics.ucalgary.ca [136.159.122.26])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA28955
	for <groff@ffii.org>; Wed, 8 Mar 2000 19:48:43 +0100
Received: by enf403-2.ensu.ucalgary.ca
	via sendmail from stdin
	id <m12SlWm-00004SC@enf403-2.ensu.ucalgary.ca> (Debian Smail3.2.0.102)
	for groff@ffii.org; Wed, 8 Mar 2000 11:49:48 -0700 (MST) 
Message-Id: <m12SlWm-00004SC@enf403-2.ensu.ucalgary.ca>
From: provinsd@enf403-2.ensu.ucalgary.ca (Dean Allen Provins)
Subject: Re: [Groff] groff HOWTO:  need feedback
In-Reply-To: <20000305205535M.sx0005@sx2.hrz.uni-dortmund.de> from Werner LEMBERG
 at "Mar 5, 2000 08:55:35 pm"
To: Werner LEMBERG <wl@gnu.org>
Date: Wed, 8 Mar 2000 11:49:48 -0700 (MST)
CC: groff mail list <groff@ffii.org>
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 1107
Lines: 35

Werner:

> A longer time ago you wrote:
> 
> > I append the latest incarnation of the groff HOWTO for your comment.
> > As you can see, there is lots remaining; nevertheless, I'd like some
> > feedback on the work to date.
> 
> Have you a home site to maintain the HOWTO?  This would be optimal.
> If not, I can upload it to ftp.ffii.org.
> 
> And have you had some time meanwhile to work on it?
> 
> 
>     Werner

For the past several weeks, nothing has happened on the HOWTO.  I was
working on it each weekend (a chapter per), but my candidacy exam is
fast approaching, and it makes me nervous to spend time on things
other than preparing for it.

There remain several more chapters (2 or 3), and will finish the draft
after the middle of April, at which time I'll get it out for another
review (I hope that someone was able to look at what I had produced
before temporarily stopping).

I don't have a web site, but will approach someone in the department
that does have one.  Perhaps I can post what I have done in the near future.
I'll be in touch if that is possible.

Regards,

Dean Provins
Calgary


From groff-admin  Wed Mar  8 23:01:17 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA30052
	for <groff@ffii.org>; Wed, 8 Mar 2000 23:01:16 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id RAA24531
	for <groff@gnu.org>; Wed, 8 Mar 2000 17:02:45 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 8 Mar 2000 23:02:34 +0100
Received: from rigel.univie.ac.at (dial-143130.HRZ.Uni-Dortmund.DE [129.217.143.130])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id XAA02483
	for <groff@gnu.org>; Wed, 8 Mar 2000 23:02:34 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id QAA20518
	for <groff@gnu.org>; Wed, 8 Mar 2000 16:24:18 GMT
To: groff@gnu.org
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000308162417Q.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 08 Mar 2000 16:24:17 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] funny behaviour of \{
Status: O
Content-Length: 208
Lines: 10

Try the following and look at stderr:

  .ab\{This causes a funny error message!

Is this just pathological behaviour or does it make any sense?
What happens with UNIX troff while calling this?


    Werner


From groff-admin  Wed Mar  8 23:01:18 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA30054
	for <groff@ffii.org>; Wed, 8 Mar 2000 23:01:17 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id RAA24533
	for <groff@gnu.org>; Wed, 8 Mar 2000 17:02:46 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 8 Mar 2000 23:02:36 +0100
Received: from rigel.univie.ac.at (dial-143130.HRZ.Uni-Dortmund.DE [129.217.143.130])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id XAA02486
	for <groff@gnu.org>; Wed, 8 Mar 2000 23:02:36 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id VAA20593
	for <groff@gnu.org>; Wed, 8 Mar 2000 21:59:55 GMT
To: groff@gnu.org
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000308215955P.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 08 Mar 2000 21:59:55 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] illegal input characters in troff
Status: O
Content-Length: 442
Lines: 16


The following input characters are illegal and will be ignored,
causing a warning message: 0x00, 0x0B, 0x0D-0x1F, 0x80-0x9F.

Does this make sense at all?  At least for some Asian encodings (like
SJIS for Japanese or Big 5 for Chinese), and of course for UTF-8, we
need the full 0x80-0xFF range.

Which characters are allowed in UNIX troff?

I suggest to change this and make all characters legal if not in
compatibility mode.


    Werner


From groff-admin  Wed Mar  8 23:16:24 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id XAA30242
	for <groff@ffii.org>; Wed, 8 Mar 2000 23:16:24 +0100
Received: (qmail 30054 invoked from network); 8 Mar 2000 22:17:54 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 8 Mar 2000 22:17:54 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id XAA28762
	for groff@ffii.org; Wed, 8 Mar 2000 23:16:49 +0100
Message-ID: <20000308231648.A28512@mayn.de>
Date: Wed, 8 Mar 2000 23:16:48 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff Mailinglist <groff@ffii.org>
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Status: O
Content-Length: 918
Lines: 22

>>> 5. The following requests cause a break:
>>> .HP .IP .LP .P .PP .RE .RS .SH .SS .TH .TP

>> Identical -- shall I mention this in groff_man?                               

> I doubt a man pages newbie will honour this. And the advanced will
> get this detail of there look on the printed peaces of paper.

As long as everything runs alright you do not need a documentation, but
as soon as problems arise you are happy to have a concise documentation
telling you if you are wrong or if this is a bug.  Moreover you know if
your fix is using a feature or a dirty hack.

I propose to include as many details as possible into the official
documentation and to write separate O'Reilly books for pedestrians.
Good documentation is the base for concise documents and happy users.
Badly documented software tends to vanish - except you have enough
criminal power to impress the industry.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Wed Mar  8 23:16:59 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id XAA30286
	for <groff@ffii.org>; Wed, 8 Mar 2000 23:16:59 +0100
Received: (qmail 30087 invoked from network); 8 Mar 2000 22:18:29 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 8 Mar 2000 22:18:29 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id XAA28800
	for groff@ffii.org; Wed, 8 Mar 2000 23:17:24 +0100
Message-ID: <20000308231723.B28512@mayn.de>
Date: Wed, 8 Mar 2000 23:17:23 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff Mailinglist <groff@ffii.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] mm directory placement
Status: O
Content-Length: 403
Lines: 11

Why is mm kept in the contrib "exile"?  In Debian, "contrib" means
unfree to a certain degree, so is there a problem with the mm license?

When I mailed the author Joergen Haegg <jh@axis.se> he replied:
> I don't know, the license is supposed to be compatible.
> (I wondered about it myself.)
> Though the groff maintainers may have other ideas, feel free to ask them.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Thu Mar  9 00:06:45 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id AAA30645
	for <groff@ffii.org>; Thu, 9 Mar 2000 00:06:44 +0100
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id SAA02912;
	Wed, 8 Mar 2000 18:08:13 -0500
Received: from tedistan.annex.umist.ac.uk ([194.66.22.200] ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12SpYo-0003hM-00; Wed, 8 Mar 2000 23:08:11 +0000
Received: (from efh@localhost)
	by tedistan.annex.umist.ac.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id XAA04842;
	Wed, 8 Mar 2000 23:08:01 GMT
Message-ID: <XFMail.000308230755.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: <20000308162417Q.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 08 Mar 2000 23:07:55 -0000 (GMT)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Werner LEMBERG <wl@gnu.org>
Subject: RE: [Groff] funny behaviour of \{
Cc: groff@gnu.org
Status: O
Content-Length: 2196
Lines: 81

On 08-Mar-00 Werner LEMBERG wrote:
> 
> Try the following and look at stderr:
> 
>   .ab\{This causes a funny error message!
> 
> Is this just pathological behaviour or does it make any sense?
> What happens with UNIX troff while calling this?

If (groff 1.11) I do it as you give it above:

  .ab\{This causes a funny error message!

then I get

  This causes a funny error message!


If I do it with a space after .ab:

  .ab \{This causes a funny error message!

then I get

  \{This causes a funny error message!

In either case I'm not seeing anything that looks pathological:
The error message is clean, and in the first case (since I'm not
using compatibility mode) I guess the "\{" is treated as a separator
or an "opening quote".

In the second case, I get exactly what I expected a priori.

Is the first case the behaviour you got? If so, what seems to be
worrying about it? Or (if different) what did you get?

Interestingly, though, when I do this on a Solaris troff (very ancient,
1987 release) I get the first form of output (without the "\{" ) in
each case.

I expected the second in the second case because, as far as I know,
the use of "\{" and "\}" is mentioned in connection with beginning
and ending conditional input (according to both the 1992 ditroff
manual and the 1976 troff manual), and in no other context; and in
groff also in connection with the ".while" request (which shares
the troff ".if" syntax). So I would not expect it to be treated as a
"grouping" operator outside that context.

However, I tested the latter hypothesis using the code:

  .de temp
  .while \\n[.$] \{ .br
  \\$1
  .shift 1 \}
  ..
  .LP
  .temp \{This causes a funny error message!\}

and got:

  This
  causes
  a
  funny
  error
  message!

(i.e. the \{...\} did NOT group the words into a single argument;
yet both \{ and \} disappeared). This is more like the Solaris
behaviour.

So now I'm feeling a bit confused ...

Ted.


--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Date: 08-Mar-00                                       Time: 23:07:53
------------------------------ XFMail ------------------------------


From groff-admin  Thu Mar  9 00:17:26 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id AAA30752
	for <groff@ffii.org>; Thu, 9 Mar 2000 00:17:26 +0100
Received: (qmail 514 invoked from network); 8 Mar 2000 23:18:57 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 8 Mar 2000 23:18:57 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id AAA30509
	for groff@ffii.org; Thu, 9 Mar 2000 00:17:51 +0100
Message-ID: <20000309001751.A30411@mayn.de>
Date: Thu, 9 Mar 2000 00:17:51 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] make groff.info
Status: O
Content-Length: 278
Lines: 9

The groff info file is not generated by the Makefile.
This is easily done by adding groff.info to the DOCS variable.

Do the following in doc/Makefile:

-DOCS=meref.ps meintro.ps pic.ps pic.html homepage.html
+DOCS=meref.ps meintro.ps pic.ps pic.html homepage.html groff.info



From groff-admin  Thu Mar  9 01:19:10 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA31132
	for <groff@ffii.org>; Thu, 9 Mar 2000 01:19:09 +0100
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id TAA10442;
	Wed, 8 Mar 2000 19:20:39 -0500
Received: from tedistan.annex.umist.ac.uk ([194.66.22.200] ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12Sqgv-00055z-00; Thu, 9 Mar 2000 00:20:38 +0000
Received: (from efh@localhost)
	by tedistan.annex.umist.ac.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA06424;
	Thu, 9 Mar 2000 00:12:52 GMT
Message-ID: <XFMail.000309001252.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: <20000308215955P.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 00:12:52 -0000 (GMT)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Werner LEMBERG <wl@gnu.org>
Subject: RE: [Groff] illegal input characters in troff
Cc: groff@gnu.org
Status: O
Content-Length: 3012
Lines: 70

On 08-Mar-00 Werner LEMBERG wrote:
> 
> The following input characters are illegal and will be ignored,
> causing a warning message: 0x00, 0x0B, 0x0D-0x1F, 0x80-0x9F.
> 
> Does this make sense at all?  At least for some Asian encodings (like
> SJIS for Japanese or Big 5 for Chinese), and of course for UTF-8, we
> need the full 0x80-0xFF range.
> 
> Which characters are allowed in UNIX troff?
> 
> I suggest to change this and make all characters legal if not in
> compatibility mode.

In my view there could be a few slightly delicate issues here.

I'm in favour of allowing everything, as a general principle
(much for the reasons Werner gives).

As far as I know, UNIX troff has always excluded 0x80-0xFF;
and has always documented the range 0x00-0x1F as follows:

  The ASCII control characters horizontal tab [0x09] and SOH [0x01]
  [tabs and leaders] and backspace [0x08] are discussed elsewhere.
  The newline [0x0A] delimits imput lines. In addition, STX [0x02],
  ETX [0x03], ENQ [0x05], ACK [0x06] and BEL [0x07] are accepted,
  and may be used as delimiters or translated into a graphic with
  'tr'. All other are ignored.

The first delicate point is what (if anything) to do with \r [0x0D].
At present, in groff, eqn generates the error message

  illegal input character code `13'

but troff seems to ignore it (I think all components of groff should
treat it the same way). NOW: Should it be ignored (so that \n, \r\n
and \n\r produce the same result, as at present); should it (perhaps
as an option) be treatable as equivalent to \n (as in the Mac, for
instance, and in some other software) which could facilitate file
interchange? Should (as in PostScript), \n, \r\n, \n\r, \r all
be equivalent (and all internally translated to \n)?

Next: should ALL the currently ignored characters be translatable?
I.e., by default they would be "seen" by troff, but have null effect;
however, if translated by ".tr", or defined by ".char", or present at
the appropriate numbered position in the device font files, they could
be assigned to a graphic? I could be in favour of this option.

However, I think that the characters not currently ignored
(STX [0x02], ETX [0x03], ENQ [0x05], ACK [0x06] and BEL [0x07])
should retain their current status (i.e. usable as delimiters
-- "tbl" uses them, for instanace, and I think that "refer"
may do so as well -- or translatable), to avoid breaking
software which depends on this status.

In any case, I'm definitely in favour of ALL input in the range
0x80-0x9F being available to troff, on the same basis as just
described (i.e. wth null efect unless defined by ".char" or
translated by ".tr", or present in the device font files with
the appropriate numerical code).

For what it's worth ...

Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Date: 09-Mar-00                                       Time: 00:12:51
------------------------------ XFMail ------------------------------


From groff-admin  Thu Mar  9 09:02:26 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA14382
	for <groff@ffii.org>; Thu, 9 Mar 2000 09:02:25 +0100
Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id DAA01429
	for <groff@gnu.org>; Thu, 9 Mar 2000 03:03:57 -0500
Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220])
	by smtp1.powertech.no (Postfix) with ESMTP id 1DFE775022
	for <groff@gnu.org>; Thu,  9 Mar 2000 09:03:55 +0100 (CET)
Received: from draugen.kvaleberg.no (root@s01i32-0079.no.powertech.net [195.159.80.79])
	by mail.powertech.no (8.9.3/8.9.3) with ESMTP id JAA26158
	for <groff@gnu.org>; Thu, 9 Mar 2000 09:03:50 +0100
Received: (from egil@localhost) by draugen.kvaleberg.no (8.6.12/8.6.12) id HAA27908; Thu, 9 Mar 2000 07:48:48 +0100
Date: Thu, 9 Mar 2000 07:48:46 +0100 (MET)
From: Egil Kvaleberg <egil@kvaleberg.no>
To: groff@gnu.org
Subject: RE: [Groff] illegal input characters in troff
In-Reply-To: <XFMail.000309001252.Ted.Harding@nessie.mcc.ac.uk>
Message-ID: <%8Z0x4c+Np@draugen.kvaleberg.no>
X-Mailer: Mana 4.0beta (Linux)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 1876
Lines: 52

On Thu, 9 Mar 2000, you wrote:

> At present, in groff, eqn generates the error message
> 
>   illegal input character code `13'
> 
> but troff seems to ignore it (I think all components of groff should
> treat it the same way). NOW: Should it be ignored

Yes.

The present error message is a real nuisance, at least for people like me
who occasionally dump into *roff-like material that originated from Dos. 

> Should (as in PostScript), \n, \r\n, \n\r, \r all
> be equivalent (and all internally translated to \n)?

If that can be implemented absolutely painlessly, then yes, why not? If it
is done, it should be like that in all preprocessors too. I would not give
such a feature high priority, though. (But then, I'm never using Macs).
 
> Next: should ALL the currently ignored characters be translatable?
> I.e., by default they would be "seen" by troff, but have null effect;
> however, if translated by ".tr", or defined by ".char", or present at
> the appropriate numbered position in the device font files, they could
> be assigned to a graphic? I could be in favour of this option.

Fair enough, although I feel that such use shouldn't exactly be
encouraged. 

> However, I think that the characters not currently ignored
> (STX [0x02], ETX [0x03], ENQ [0x05], ACK [0x06] and BEL [0x07])
> should retain their current status (i.e. usable as delimiters
> -- "tbl" uses them, for instanace, and I think that "refer"
> may do so as well -- or translatable), to avoid breaking
> software which depends on this status.

See above.

> In any case, I'm definitely in favour of ALL input in the range
> 0x80-0x9F being available to troff, on the same basis as just
> described

See above, too.

Egil
-- 
Email: egil@kvaleberg.no  Voice: +47 22523641, 92022780 Fax: +47 22525899
Mail:  Egil Kvaleberg, Husebybakken 14A, 0379 Oslo, Norway
Home:  http://www.kvaleberg.com/



From groff-admin  Thu Mar  9 16:09:29 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/GNU) with ESMTP id QAA16974
	for <groff@ffii.org>; Thu, 9 Mar 2000 16:09:29 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 9 Mar 2000 16:10:39 +0100
Received: from rigel.univie.ac.at (dial-143135.HRZ.Uni-Dortmund.DE [129.217.143.135])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id QAA12111;
	Thu, 9 Mar 2000 16:10:39 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id MAA21163;
	Thu, 9 Mar 2000 12:31:42 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] make groff.info
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000309001751.A30411@mayn.de>
References: <20000309001751.A30411@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000309123141T.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 12:31:41 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 303
Lines: 10

> The groff info file is not generated by the Makefile.
> This is easily done by adding groff.info to the DOCS variable.

I know, but the real problem is that doc/Makefile should be converted
to a Makefile.sub file...  Since groff.texinfo is still very
incomplete, it doesn't matter IMHO.


    Werner


From groff-admin  Thu Mar  9 16:09:31 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA16980
	for <groff@ffii.org>; Thu, 9 Mar 2000 16:09:29 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id KAA24939
	for <groff@gnu.org>; Thu, 9 Mar 2000 10:11:03 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 9 Mar 2000 16:10:42 +0100
Received: from rigel.univie.ac.at (dial-143135.HRZ.Uni-Dortmund.DE [129.217.143.135])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id QAA12115;
	Thu, 9 Mar 2000 16:10:41 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id MAA21158;
	Thu, 9 Mar 2000 12:28:30 GMT
To: S.Barany@infosys.tuwien.ac.at
Cc: Ted.Harding@nessie.mcc.ac.uk, groff@gnu.org
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <38C6794F.168759DB@infosys.tuwien.ac.at>
References: <38C6794F.168759DB@infosys.tuwien.ac.at>
X-Mailer: Mew version 1.94 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-2
Message-Id: <20000309122829R.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 12:28:29 GMT
X-Dispatcher: imput version 990905(IM130)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id QAA17002
Subject: [Groff] Re: groff ported to OS/390
Status: O
Content-Length: 1689
Lines: 55

> I want to let you know I have ported groff in the last days to
> OS/390.

This is good news!

> The main problem in porting is that the IBM Mainframe machine uses
> EBCDIC internally, which is a real 8bit character set.
>
> [...]

Sándor,


your mail arrives exactly at the right time.  I'm going to abandon the
input encoding restrictions completely.

Please subscribe to groff@ffii.org and download the current
development snapshot

  ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz

Some comments to your patches -- which I won't apply immediately since
I believe that we need more discussion how to solve the whole issue
gracefully (not to mention support for CJK encodings and Unicode which
is a different pair of shoes, so to say).

> ! DEFS=`sed -f conftest.defs confdefs.h | tr '\n' ' '`

Do all UNIX versions of `tr' support the `\n' notation?

>   char illegal_char_table[256]= {

My idea is to activate illegal characters only incompatibility mode --
BTW, does a UNIX troff exist on the OS-390?

> ! const int ESCAPE_CIRCUMFLEX = 010;
> ! const int ESCAPE_LEFT_BRACE = 011;

Again, I think this should be moved to values larger than 0xFF...

> !     fputc(had_prompt ? ':' : '\057', stderr);

For such situations I would like to have a config file, say,
groff/arch/i390/config.h -- I'll check how other packages manage this.

> I deleted the changes to the font description files - they must be
> completely replaced due to EBCDIC coding.  It would be a nice
> excercise for the autoconf step (if host=i390-ibm-mvs), include an
> other set of PROTO files and define the IS_EBCDIC_HOST macro.

If you provide PROTO files this should not be too difficult.


    Werner


From groff-admin  Thu Mar  9 16:09:29 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/GNU) with ESMTP id QAA16976
	for <groff@ffii.org>; Thu, 9 Mar 2000 16:09:29 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 9 Mar 2000 16:10:38 +0100
Received: from rigel.univie.ac.at (dial-143135.HRZ.Uni-Dortmund.DE [129.217.143.135])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id QAA12108;
	Thu, 9 Mar 2000 16:10:37 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id PAA21288;
	Thu, 9 Mar 2000 15:07:26 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] mm directory placement
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000308231723.B28512@mayn.de>
References: <20000308231723.B28512@mayn.de>
X-Mailer: Mew version 1.94 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Message-Id: <20000309150726Q.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 15:07:26 GMT
X-Dispatcher: imput version 990905(IM130)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id QAA16978
Status: O
Content-Length: 970
Lines: 30

> Why is mm kept in the contrib "exile"?  In Debian, "contrib" means
> unfree to a certain degree, so is there a problem with the mm
> license?

Not at all.

> When I mailed the author Joergen Haegg <jh@axis.se> he replied:
> > I don't know, the license is supposed to be compatible.
> > (I wondered about it myself.)
> > Though the groff maintainers may have other ideas, feel free to
> > ask them.

Maybe my decision was a bit unfortunate (and if you prefer, Jörgen, I
can move the files back to tmac/mm).

The reason for putting the mm files into contrib/mm was done in the
hope that probably other people will start to populate the contrib dir
with other macro packages.  Compare this to

  <CTAN>/pub/tex/macros/latex/base/...
  <CTAN>/pub/tex/macros/latex/contrib/...

Whether this hope will be fulfilled, I don't know...

It has no other meaning than it is contributed software, written and
maintained by a person not identical with the groff team.


    Werner


From groff-admin  Thu Mar  9 16:09:33 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA17001
	for <groff@ffii.org>; Thu, 9 Mar 2000 16:09:31 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id KAA24937
	for <groff@gnu.org>; Thu, 9 Mar 2000 10:11:01 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 9 Mar 2000 16:10:36 +0100
Received: from rigel.univie.ac.at (dial-143135.HRZ.Uni-Dortmund.DE [129.217.143.135])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id QAA12101;
	Thu, 9 Mar 2000 16:10:35 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id PAA21282;
	Thu, 9 Mar 2000 15:02:03 GMT
To: Ted.Harding@nessie.mcc.ac.uk
Cc: groff@gnu.org
Subject: RE: [Groff] funny behaviour of \{
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <XFMail.000308230755.Ted.Harding@nessie.mcc.ac.uk>
References: <20000308162417Q.sx0005@sx2.hrz.uni-dortmund.de>
	<XFMail.000308230755.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: Mew version 1.94 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
Message-Id: <20000309150202J.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 15:02:02 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 734
Lines: 34

> > Try the following and look at stderr:
> > 
> >   .ab\{This causes a funny error message!
> > 
> > Is this just pathological behaviour or does it make any sense?
> 
> [...] I'm not seeing anything that looks pathological:

You probably haven't looked closely enough.

If you, for example, do the following

  .ab\{foo
  Test

with

  groff -Tps -ww ... > xxx.ps

you will see `foo' sent to stderr, and `xxx.ps' is empty!  With other
words, there is no error message at all, but groff silently aborts
after the .ab request.

This *is* pathological IMHO.  The correct error message should be

  `\{' not allowed in a name

and then groff should abort (if aborting at all).

`\}', BTW, shows the same strange behaviour.


    Werner


From groff-admin  Thu Mar  9 16:50:00 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA17523
	for <groff@ffii.org>; Thu, 9 Mar 2000 16:49:59 +0100
Received: from heimdall.sdrc.com (heimdall.sdrc.com [146.122.132.195])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id KAA29086;
	Thu, 9 Mar 2000 10:51:34 -0500
Received: from mailhub-cvg.sdrc.com (mailhub-cvg.sdrc.com [146.122.142.31])
	by heimdall.sdrc.com (8.9.1/8.9.1) with ESMTP id KAA04029;
	Thu, 9 Mar 2000 10:51:32 -0500 (EST)
Received: from thor.sdrc.com (scjones@thor [146.122.62.108])
	by mailhub-cvg.sdrc.com (8.8.8/8.8.5) with ESMTP id KAA05416;
	Thu, 9 Mar 2000 10:51:30 -0500 (EST)
Received: (from scjones@localhost)
	by thor.sdrc.com (8.9.0/8.9.0) id KAA15858;
	Thu, 9 Mar 2000 10:51:30 -0500 (EST)
Message-Id: <200003091551.KAA15858@thor.sdrc.com>
Subject: Re: [Groff] Re: groff ported to OS/390
To: wl@gnu.org
Date: Thu, 9 Mar 2000 10:51:30 -0500 (EST)
Cc: S.Barany@infosys.tuwien.ac.at, Ted.Harding@nessie.mcc.ac.uk, groff@gnu.org
In-Reply-To: <20000309122829R.sx0005@sx2.hrz.uni-dortmund.de> from "Werner LEMBERG" at Mar 9, 0 12:28:29 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
Status: O
Content-Length: 179
Lines: 10

Werner LEMBERG writes:
> 
> Do all UNIX versions of `tr' support the `\n' notation?

No.

-Larry Jones

You don't get to be Mom if you can't fix everything just right. -- Calvin


From groff-admin  Fri Mar 10 00:59:13 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/GNU) with ESMTP id AAA20612
	for <groff@ffii.org>; Fri, 10 Mar 2000 00:59:13 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 10 Mar 2000 01:00:42 +0100
Received: from rigel.univie.ac.at (dial-143194.HRZ.Uni-Dortmund.DE [129.217.143.194])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id BAA06060;
	Fri, 10 Mar 2000 01:00:41 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id XAA23127;
	Thu, 9 Mar 2000 23:43:20 GMT
In-Reply-To: <11DD9734B036D311947400805F0DD607036418@NBGV101A>
References: <11DD9734B036D311947400805F0DD607036418@NBGV101A>
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
To: Joerg.Freudenberger@nbg9.siemens.de
Cc: groff@ffii.org
Reply-To: Werner LEMBERG <wl@gnu.org>
X-Mailer: Mew version 1.94 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000309234320I.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 09 Mar 2000 23:43:20 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 309
Lines: 12

> This is excerpted from man(1):
> If the first line is 
> 	'\" <word>
> the input is processed by the corresponding preprocessor. 
> Mind the single Space. <word> contains e for eqn, r for refer
> t for tbl and v for vgrind.

I forgot to ask: What is `vgrind'?  Is there a free implementation?


    Werner


From groff-admin  Fri Mar 10 01:36:48 2000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA21138
	for <groff@ffii.org>; Fri, 10 Mar 2000 01:36:47 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e3.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id TAA74712
	for <groff@ffii.org>; Thu, 9 Mar 2000 19:37:04 -0500
Received: from D51MTA08.pok.ibm.com (d51mta08.pok.ibm.com [9.117.200.36])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with SMTP id TAA44386
	for <groff@ffii.org>; Thu, 9 Mar 2000 19:38:23 -0500
Received: from infosys.tuwien.ac.at ([9.14.3.70]) by D51MTA08.pok.ibm.com (Lotus SMTP MTA v4.6.5  (863.2 5-20-1999)) with SMTP id 8525689E.000380A0; Thu, 9 Mar 2000 19:38:15 -0500
Message-ID: <38C84400.EBFDAB64@infosys.tuwien.ac.at>
Date: Thu, 09 Mar 2000 19:38:24 -0500
From: =?iso-8859-1?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "groff@ffii.org" <groff@ffii.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: [Groff] OS/390 port - an introduction, patches
Status: O
Content-Length: 6992
Lines: 206

Hi all,

I copy here some parts of my previous letter to Werner. 

I want to let you know I have ported groff in the last days to OS/390.
This sytem has a bit old-fashioned, but very robust, fully
POSIX-compliant UNIX subsystem (USS). There are a lot of commercial
products available on that, from IBM (Domino, WebSphere) and others
(SAP, Peoplesoft etc.). I am a member of a small, time limited  project
titled "Using Open Source Software on OS/390 UNIX". The goal is making
OS/390 more attractive to developers through porting essential programs.
The project is fully IBM-sponsored and uses only IBM resources. However,
the results will be made available for free download (the book itself,
in pdf, and all the distribution materials, sources and binaries). 

The main problem in porting is that the IBM Mainframe machine uses
EBCDIC internally, which is a real 8bit character set. All programs
depending on hard-coded constants from the not-visible ascii ranges make
difficulities. An other problem is the really strict typecasting in the
IBM (commercial) C compiler.

My changes to the groff code are small, and concentrate on the inherent
differences mentioned above. The final version will be soon available in
form of patches. I am not an IBM employee and therefore it is unsure if
I will have access to this environment. Therefore I can not promise to
maintain this platform.

Attached you will find an raw patch file. The EBCDIC dependencies will
be done in the following way:
#ifdef IS_EBCDIC_HOST
      fputc(had_prompt ? ':' : '\057', stderr);
#else
      fputc(had_prompt ? ':' : '\007', stderr);
#endif

I deleted the changes to the font description files - they must be
completely replaced due to EBCDIC coding. It would be a nice excercise
for the autoconf step (if host=i390-ibm-mvs), include an other set of
PROTO files and define the IS_EBCDIC_HOST macro.

Regards,

Sándor Bárány, Co-Author of the RedBook 
                 "Using Open Source Software on OS/390 UNIX"
IBM Resident  in Poughkeepsie, NY by 
International Technical Support Organization (ITSO)
(http://www.redbooks.ibm.com/resindex.html)
E-mail:  itsore24@us.ibm.com
IBM Notes:  ITSO Resident 24/Poughkeepsie/IBM@IBMUS
Tel: (1-914) 433-1481 Fax: (1-914) 432-8264

diff -rbwC groff-1.15/configure s390-groff-1.15/configure
*** groff-1.15/configure Tue Dec 14 08:18:56 1999
--- s390-groff-1.15/configure Fri Mar  3 14:39:34 2000
***************
*** 2750,2754 ****
  s%\$%$$%g
  EOF
! DEFS=`sed -f conftest.defs confdefs.h | tr '\012' ' '`
  rm -f conftest.defs
  
--- 2711,2715 ----
  s%\$%$$%g
  EOF
! DEFS=`sed -f conftest.defs confdefs.h | tr '\n' ' '`
  rm -f conftest.defs
diff -rbwC groff-1.15/libgroff/illegal.cc
s390-groff-1.15/libgroff/illegal.cc
*** groff-1.15/libgroff/illegal.cc Fri May 21 00:50:38 1999
--- s390-groff-1.15/libgroff/illegal.cc Fri Mar  3 18:24:22 2000
***************
*** 4,8 ****
  
  char illegal_char_table[256]= {
!   1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 1, 1, 1,
    1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
--- 4,10 ----
  
  char illegal_char_table[256]= {
!   1, 0, 0, 0, 0, 0, 0, 0, 1, 1, 0, 1, 0, 1, 1, 1,
!   1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1,
!   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
***************
*** 12,17 ****
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
-   1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
--- 14,17 ----
diff -rbwC groff-1.15/refer/refer.cc s390-groff-1.15/refer/refer.cc
*** groff-1.15/refer/refer.cc Fri Dec 24 17:18:13 1999
--- s390-groff-1.15/refer/refer.cc Fri Mar  3 18:22:34 2000
***************
*** 514,518 ****
            pending_line += PRE_LABEL_MARKER;
          pending_line += pre;
!         char lm = LABEL_MARKER + lt;
          pending_line += lm;
          pending_line += post;
--- 514,518 ----
            pending_line += PRE_LABEL_MARKER;
          pending_line += pre;
!         char lm = LABEL_MARKER + (char) lt;
          pending_line += lm;
          pending_line += post;
***************
*** 922,926 ****
  extern "C" {
  
! static int rcompare(const void *p1, const void *p2)
  {
    return compare_reference(**(reference **)p1, **(reference **)p2);
--- 922,929 ----
  extern "C" {
  
! #ifndef __MVS__
! static
! #endif
!  int rcompare(const void *p1, const void *p2)
  {
    return compare_reference(**(reference **)p1, **(reference **)p2);
diff -rbwC groff-1.15/troff/env.cc s390-groff-1.15/troff/env.cc
*** groff-1.15/troff/env.cc Fri May 21 00:50:38 1999
--- s390-groff-1.15/troff/env.cc Fri Mar  3 18:22:58 2000
***************
*** 196,200 ****
  extern "C" {
  
! static int compare_ranges(const void *p1, const void *p2)
  {
    return ((size_range *)p1)->min - ((size_range *)p2)->min;
--- 196,203 ----
  extern "C" {
  
! #ifndef __MVS__
! static
! #endif
!  int compare_ranges(const void *p1, const void *p2)
  {
    return ((size_range *)p1)->min - ((size_range *)p2)->min;
diff -rbwC groff-1.15/troff/input.cc s390-groff-1.15/troff/input.cc
*** groff-1.15/troff/input.cc Tue Dec 28 03:27:27 1999
--- s390-groff-1.15/troff/input.cc Fri Mar  3 21:09:13 2000
***************
*** 136,141 ****
  const int ESCAPE_UNDERSCORE = 023;
  const int ESCAPE_BAR = 024;
! const int ESCAPE_CIRCUMFLEX = 025;
! const int ESCAPE_LEFT_BRACE = 026;
  const int ESCAPE_RIGHT_BRACE = 027;
  const int ESCAPE_LEFT_QUOTE = 030;
--- 136,141 ----
  const int ESCAPE_UNDERSCORE = 023;
  const int ESCAPE_BAR = 024;
! const int ESCAPE_CIRCUMFLEX = 010;
! const int ESCAPE_LEFT_BRACE = 011;
  const int ESCAPE_RIGHT_BRACE = 027;
  const int ESCAPE_LEFT_QUOTE = 030;
***************
*** 148,160 ****
  const int ESCAPE_SPACE = 037;
  
! const int TITLE_REQUEST = 0200;
! const int COPY_FILE_REQUEST = 0201;
! const int TRANSPARENT_FILE_REQUEST = 0202;
  #ifdef COLUMN
! const int VJUSTIFY_REQUEST = 0203;
  #endif /* COLUMN */
! const int ESCAPE_E = 0204;
! const int LAST_PAGE_EJECTOR = 0205;
! const int ESCAPE_RIGHT_PARENTHESIS = 0206;
  
  void set_escape_char()
--- 148,160 ----
  const int ESCAPE_SPACE = 037;
  
! const int TITLE_REQUEST = 060;
! const int COPY_FILE_REQUEST = 061;
! const int TRANSPARENT_FILE_REQUEST = 062;
  #ifdef COLUMN
! const int VJUSTIFY_REQUEST = 063;
  #endif /* COLUMN */
! const int ESCAPE_E = 064;
! const int LAST_PAGE_EJECTOR = 065;
! const int ESCAPE_RIGHT_PARENTHESIS = 066;
  
  void set_escape_char()
***************
*** 3016,3020 ****
    }
    if (reading_from_terminal) {
!     fputc(had_prompt ? ':' : '\007', stderr);
      fflush(stderr);
    }
--- 3016,3020 ----
    }
    if (reading_from_terminal) {
!     fputc(had_prompt ? ':' : '\057', stderr);
      fflush(stderr);
    }


From groff-admin  Fri Mar 10 01:42:52 2000
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA21325
	for <groff@ffii.org>; Fri, 10 Mar 2000 01:42:51 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id TAA83860
	for <groff@ffii.org>; Thu, 9 Mar 2000 19:42:38 -0500
Received: from D51MTA08.pok.ibm.com (d51mta08.pok.ibm.com [9.117.200.36])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with SMTP id TAA74216
	for <groff@ffii.org>; Thu, 9 Mar 2000 19:43:57 -0500
Received: from infosys.tuwien.ac.at ([9.14.3.70]) by D51MTA08.pok.ibm.com (Lotus SMTP MTA v4.6.5  (863.2 5-20-1999)) with SMTP id 8525689E.00040489; Thu, 9 Mar 2000 19:43:53 -0500
Message-ID: <38C84552.3CE9F528@infosys.tuwien.ac.at>
Date: Thu, 09 Mar 2000 19:44:02 -0500
From: =?iso-8859-2?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "groff@ffii.org" <groff@ffii.org>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
Subject: [Groff] how to modify configure.in to test EBCDIC
Status: O
Content-Length: 1226
Lines: 51

It would be great to automagically find out, which character set is used
by groff.

Here is a possible way to do that:

config.in.h   should be modified to include
#undef EBCDIC

and a new test in config.in:

AC_TRY_COMPILE([ ],
[ /* TryCompile function for CharSet.
   Treat any failure as ASCII for compatibility with existing art.
   Use compile-time rather than run-time tests for cross-compiler
   tolerance.  */
#if '0'!=240
make an error "Character set is not EBCDIC"
#endif ],
[ # TryCompile action if true
cf_cv_ebcdic=yes ],
[ # TryCompile action if false
cf_cv_ebcdic=no])
# end of TryCompile ])
# end of CacheVal CvEbcdic
AC_MSG_RESULT($cf_cv_ebcdic)
case "$cf_cv_ebcdic" in  #(vi
    yes) AC_DEFINE(EBCDIC)
         ;;
    *)   ;;
esac

if test "$cf_cv_ebcdic" = "yes"; then
dnl If we have EBCDIC we most likley have OS390 Unix, let's test it!
AC_MSG_CHECKING(for OS/390 Unix)
case `uname` in
    OS/390) OS390Unix="yes";
            CFLAGS="$CFLAGS -D_ALL_SOURCE"; AC_MSG_RESULT(yes)
            ;;
    *)      OS390Unix="no";
            AC_MSG_RESULT(no)
            ;;
esac
fi

Analog to that on BS2000 !?

Sándor
---
Teacher: "Calvin, do you know what state you live in?"
Calvin:  "Denial." - Bill Waterson


From groff-admin  Fri Mar 10 15:01:38 2000
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA09871
	for <groff@ffii.org>; Fri, 10 Mar 2000 15:01:35 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e4.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id JAA215934
	for <groff@ffii.org>; Fri, 10 Mar 2000 09:01:54 -0500
Received: from D51MTA08.pok.ibm.com (d51mta08.pok.ibm.com [9.117.200.36])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with SMTP id JAA130872
	for <groff@ffii.org>; Fri, 10 Mar 2000 09:03:13 -0500
Received: from infosys.tuwien.ac.at ([9.14.3.70]) by D51MTA08.pok.ibm.com (Lotus SMTP MTA v4.6.5  (863.2 5-20-1999)) with SMTP id 8525689E.004D314D; Fri, 10 Mar 2000 09:03:08 -0500
Message-ID: <38C900A6.FADCF033@infosys.tuwien.ac.at>
Date: Fri, 10 Mar 2000 09:03:18 -0500
From: =?iso-8859-1?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "groff@ffii.org" <groff@ffii.org>
Subject: Re: [Groff] how to modify configure.in to test EBCDIC
References: <38C84552.3CE9F528@infosys.tuwien.ac.at>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Status: O
Content-Length: 1348
Lines: 51

Sorry, some lines at the beginning are missing from my previous post,
here is the whole file once more:

dnl Check for EBCDIC stolen from the LYNX port to OS390 Unix
AC_MSG_CHECKING(if character set is EBCDIC)
AC_TRY_COMPILE([ ],
[ /* TryCompile function for CharSet.
   Treat any failure as ASCII for compatibility with existing art.
   Use compile-time rather than run-time tests for cross-compiler
   tolerance.  */
#if '0'!=240
make an error "Character set is not EBCDIC"
#endif ],
[ # TryCompile action if true
cf_cv_ebcdic=yes ],
[ # TryCompile action if false
cf_cv_ebcdic=no])
# end of TryCompile ])
# end of CacheVal CvEbcdic
AC_MSG_RESULT($cf_cv_ebcdic)
case "$cf_cv_ebcdic" in  #(vi
    yes) AC_DEFINE(EBCDIC)
         ;;
    *)   ;;
esac

if test "$cf_cv_ebcdic" = "yes"; then
dnl If we have EBCDIC we most likley have OS390 Unix, let's test it!
AC_MSG_CHECKING(for OS/390 Unix)
case `uname` in
    OS/390) OS390Unix="yes";
            CFLAGS="$CFLAGS -D_ALL_SOURCE"; AC_MSG_RESULT(yes)
            ;;
    *)      OS390Unix="no";
            AC_MSG_RESULT(no)
            ;;
esac
fi
Sándor Bárány wrote:
> 
> It would be great to automagically find out, which character set is used
> by groff.
> 
> Here is a possible way to do that:
> 
> config.in.h   should be modified to include
> #undef EBCDIC
> 
> and a new test in config.in:
>


From groff-admin  Fri Mar 10 19:40:17 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/GNU) with ESMTP id TAA11505
	for <groff@ffii.org>; Fri, 10 Mar 2000 19:40:17 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 10 Mar 2000 19:41:39 +0100
Received: from rigel.univie.ac.at (dial-143158.HRZ.Uni-Dortmund.DE [129.217.143.158])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id TAA10396;
	Fri, 10 Mar 2000 19:41:36 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id SAA24372;
	Fri, 10 Mar 2000 18:39:01 GMT
To: enf@pobox.com, S.Barany@infosys.tuwien.ac.at,
        Yoshiaki Yanagihara
 <yochi@debian.or.jp>,
        "S. Ciszewski" <grciszew@kinga.cyf-kr.edu.pl>
Cc: groff@ffii.org
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000229224216W.sx0005@sx2.hrz.uni-dortmund.de>
References: <200002291920.NAA66959@216-80-13-65.d.enteract.com>
	<20000229224216W.sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000310183900D.sx0005@sx2.hrz.uni-dortmund.de>
Date: Fri, 10 Mar 2000 18:39:00 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] Unicode, EBCDIC, Latin-2, JIS for groff
Status: O
Content-Length: 1209
Lines: 35

It's amazing to see that people are interested in having Unicode
resp. EBCDIC input within gtroff.

Other people want Latin-2, others again want Japanese...

How to handle this best?

My suggestion is to enlarge gtroff so that it can handle arbitrary
31bit characters (this covers ISO 10646).  Characters with the 32nd
bit set (i.e. negative numbers) can then be used for special gtroff
`characters' like `ESCAPE_c'.

It should use Unicode (resp. ISO 10646) as the internal encoding and
nothing else.

Question: How far is the project of Unicode input?

Additionally, I suggest to use UTF8 exclusively as the external
encoding representation if, say, the command line option `-u' is used.

Groff should then come with a character set conversion tool (as a
preprocessor; maybe with heuristics to recognize the proper encoding?)
to map everything to Unicode in UTF8 representation (e.g. Latin-2, JIS
-- EBCDIC charsets also).

On the output side, I think that no essential changes are necessary
(except better support for very large fonts since gtroff's font handling
mechanism isn't very efficient here).  Of course, grops e.g. should be
extended to support CID-keyed PS fonts.

Comments please.


    Werner


From groff-admin  Fri Mar 10 21:39:29 2000
Received: from 216-80-54-30.d.enteract.com (216-80-54-30.d.enteract.com [216.80.54.30])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA12211
	for <groff@ffii.org>; Fri, 10 Mar 2000 21:39:26 +0100
Received: (from eric@localhost)
	by 216-80-54-30.d.enteract.com (8.9.3/8.9.3) id OAA27942;
	Fri, 10 Mar 2000 14:40:58 -0600 (CST)
	(envelope-from eric)
Date: Fri, 10 Mar 2000 14:40:58 -0600 (CST)
Message-Id: <200003102040.OAA27942@216-80-54-30.d.enteract.com>
From: Eric Fischer <enf@pobox.com>
To: wl@gnu.org
In-Reply-To: <20000310183900D.sx0005@sx2.hrz.uni-dortmund.de>
References: <200002291920.NAA66959@216-80-13-65.d.enteract.com> <20000229224216W.sx0005@sx2.hrz.uni-dortmund.de> <20000310183900D.sx0005@sx2.hrz.uni-dortmund.de>
Cc: S.Barany@infosys.tuwien.ac.at, yochi@debian.or.jp,
        grciszew@kinga.cyf-kr.edu.pl, groff@ffii.org
Subject: [Groff] Re: Unicode, EBCDIC, Latin-2, JIS for groff
Status: O
Content-Length: 1965
Lines: 44

> Question: How far is the project of Unicode input?

Here's what I've done so far:

  *  The file iterator recognizes valid UTF-8 patterns in the input,
     and when they are encountered they get transmuted into \U'number'.
     Latin-1 characters (which is to say, eight-bit characters that are
     not part of a legal UTF-8 sequence) are also temporarily translated
     into \U sequences; ASCII characters are passed through unchanged.

     Accepting Latin-2 or whatever based on a command line option would
     be easy to add; accepting EBCDIC would also be easy if everyone could
     agree on what EBCDIC characters should map to what Unicode characters.

  *  The tokenization routine recognizes \U and converts anything outside
     the range 0x00 to 0xFF into \[char0xNNNN] or \[char0xNNNNNNNN] as
     appropriate.

     This makes non-Latin1 characters second-class citizens (they can't be
     used in the names of macros, etc.), but I was intimidated by the task
     of finding every place in the program that depends on characters being
     at most eight bits wide.

  *  An extension to the ligature mechanism joins Unicode combing accents
     to their base characters as a single character whenever possible.

  *  I've been working on more general support for accents (for the cases
     where there isn't a single Unicode character that represents the
     accented letter or where a character has multiple accents) but this
     doesn't work very well yet.

  *  I haven't done anything with right-to-left or reordered characters.
     As I understand it, Plan 9 troff doesn't support these (or combining
     accents) either.

> Additionally, I suggest to use UTF8 exclusively as the external
> encoding representation if, say, the command line option `-u' is used.

If you want the *output* to be UTF-8 as well as the input, this is also
going to require changes to all the postprocessors.  It is what Plan 9
troff does, though.

eric


From groff-admin  Fri Mar 10 22:26:43 2000
Received: from titans.cisco.com (titans.cisco.com [161.44.216.10])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA12508
	for <groff@ffii.org>; Fri, 10 Mar 2000 22:26:42 +0100
Received: from localhost (srich@localhost)
	by titans.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA07693;
	Fri, 10 Mar 2000 16:26:58 -0500 (EST)
Date: Fri, 10 Mar 2000 16:26:58 -0500 (EST)
From: Steve Rich <srich@cisco.com>
To: Werner LEMBERG <wl@gnu.org>
cc: groff@ffii.org
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
In-Reply-To: <20000309234320I.sx0005@sx2.hrz.uni-dortmund.de>
Message-ID: <Pine.GSO.4.05.10003101623070.5017-100000@titans.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 1330
Lines: 46

vgrind will format C code, sh scripts, etc., into troff output.

There are free versions (I believe with BSD, for example), but I've
always had a bit of trouble finding them. Here's the first part of the
vgrind man page on Solaris:

User Commands                                           vgrind(1)

NAME
     vgrind - grind nice program listings

SYNOPSIS
     vgrind  [ -2fntwWx ]  [ -d defs-file ]   [  -h header  ]   [
     -l language  ]  [ -s n ]  [ -o pagelist ]  [ -P printer ]  [
     -T output-device ] filename ...

DESCRIPTION
     The vgrind  utility formats the program sources named by the
     filename  arguments in a nice style using troff(1). Comments
     are placed in italics, keywords in bold face,  and  as  each
     function  is encountered its name is listed on the page mar-
     gin.

sjr

On Thu, 9 Mar 2000, Werner LEMBERG wrote:

> 
> > This is excerpted from man(1):
> > If the first line is 
> > 	'\" <word>
> > the input is processed by the corresponding preprocessor. 
> > Mind the single Space. <word> contains e for eqn, r for refer
> > t for tbl and v for vgrind.
> 
> I forgot to ask: What is `vgrind'?  Is there a free implementation?
> 
> 
>     Werner
> 
> _______________________________________________
> Groff maillist  -  Groff@ffii.org
> http://ffii.org/mailman/listinfo/groff
> 



From groff-admin  Sat Mar 11 15:04:58 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/GNU) with ESMTP id PAA31495
	for <groff@ffii.org>; Sat, 11 Mar 2000 15:04:58 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 11 Mar 2000 15:06:21 +0100
Received: from rigel.univie.ac.at (dial-143188.HRZ.Uni-Dortmund.DE [129.217.143.188])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id PAA06215;
	Sat, 11 Mar 2000 15:06:09 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id NAA25927;
	Sat, 11 Mar 2000 13:42:07 GMT
To: enf@pobox.com
Cc: S.Barany@infosys.tuwien.ac.at, yochi@debian.or.jp,
        grciszew@kinga.cyf-kr.edu.pl, groff@ffii.org
Subject: Re: [Groff] Re: Unicode, EBCDIC, Latin-2, JIS for groff
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <200003102040.OAA27942@216-80-54-30.d.enteract.com>
References: <20000229224216W.sx0005@sx2.hrz.uni-dortmund.de>
	<20000310183900D.sx0005@sx2.hrz.uni-dortmund.de>
	<200003102040.OAA27942@216-80-54-30.d.enteract.com>
X-Mailer: Mew version 1.94 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
Message-Id: <20000311134207P.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sat, 11 Mar 2000 13:42:07 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 6847
Lines: 133

>   *  The file iterator recognizes valid UTF-8 patterns in the input,
>      and when they are encountered they get transmuted into
>      \U'number'.  Latin-1 characters (which is to say, eight-bit
>      characters that are not part of a legal UTF-8 sequence) are
>      also temporarily translated into \U sequences; ASCII characters
>      are passed through unchanged.

Below you can find Markus Kuhn's UTF8 test file which contains a lot
of small devils...  I strongly suggest that your UTF8-reading routine
handles all this gracefully.

>      Accepting Latin-2 or whatever based on a command line option
>      would be easy to add; accepting EBCDIC would also be easy if
>      everyone could agree on what EBCDIC characters should map to
>      what Unicode characters.

AFAIK, there are 1:1 mapping tables (from ftp.unicode.org?).  Note
that there is not a single EBCDIC; IBM has defined a lot of EBCDIC
code pages.

>   *  The tokenization routine recognizes \U and converts anything
>      outside the range 0x00 to 0xFF into \[char0xNNNN] or
>      \[char0xNNNNNNNN] as appropriate.
> 
>      This makes non-Latin1 characters second-class citizens (they
>      can't be used in the names of macros, etc.), but I was
>      intimidated by the task of finding every place in the program
>      that depends on characters being at most eight bits wide.

Your solution seems to be a first step, but I think we have to convert
groff to 32 bit internally.

>   *  I haven't done anything with right-to-left or reordered
>      characters.  As I understand it, Plan 9 troff doesn't support
>      these (or combining accents) either.

Maybe a preprocessor for that?  Similar to Indic scripts.

> If you want the *output* to be UTF-8 as well as the input, this is
> also going to require changes to all the postprocessors.  It is what
> Plan 9 troff does, though.

I think only the TTY device needs UTF-8, and this has already been
implemented.  Regarding grohtml, I'm not sure...

For typesetting devices, I think we should rather think in glyphs than
in character sets.


    Werner


begin 644 UTF-8-test.txt.gz
M'XL(",#Y[3<"`U541BTX+71E<W0N='AT`-5;^7,C1Q7FY_P5C_DE=B(+6Y*O
M+98B;-:L(4<5NRZ*'UNC'JOCT8PR/6-95*HP))!P)MPW"?=-N`(D)#@)][7A
MOF$WW/>&,X%<O-<]1\](7CQKR_*Z4IOU:O3-ZW=\[W7/-RLGEJ86H,5MO\4#
ML%F7-84KPCXPKP4R#+B4$'(9PHY^KKE@:H<_.\6#/?VYYH++6;`627AFU/;@
MR9TU_-]3F=VI^L'J4V`*9A87%Z>F%Z=J<^.R[T1;Q`X/^48(?(-UA,=E!=I^
M#U;,8$EH8XQ<#NLL$#ZN*>QWN03?R>'9?A!$W9"WP`_`#]L\Z`G)07@AQ]B&
MPEN-426_.N*>S65U7]=[B8T6MLB,T(?EXU?"S/1<8VYJIH(&V:'P/0G/JLZK
M;*Q5ZW8%&*Y_7=@<`FYSL4[?-/'BQ;29Z^I%=@,>XI>L#G,=/^B@(Y*5XN>`
M#@').AQZK(^_L!!$F,-+,22"V&T6,!O_(;X4O1V%4K2XPF$M7SE:1DW)0ZL*
M*I8=SG`-*5XD(S0MOA=]*[,K'P="#WC7939^U,1Z3'[K<"\TXIN:-+%R\=+2
MTJ63%>BUA=T&U_?7R.@FKL@5:VB?ARM>YP'9B/>0Y%V\?;!6,=:+6<)`BHYP
M60"RWVGZ;A660^B(U78(342!5=]O`2Z:4<C61;R@EE#9%`G9QFM2O&V7YP1^
MAUR*^8F!1@#\5TQKO,X3]!?#V68\$L=?%6&)>#Z&=IVAK4TW#:<=(2*ZR/'Q
MCV84&EGO1&1I#L_EJPQ7N(3K;N*%R("2J@T-<SD+\&JTSE_UA%2WT`[!]/(C
MMT7>B"1O54V\9Y!=8M7S`\K,P:235(>1EUF=+E-"3V#2=AB&*L-K\6:TNJJP
M_("CEQU'V)$;JHJP,:1H9HL"@98@?_N>$TF,:W7?^(JH*EW<H5WC[;5]1]K<
M7J.2X)0%&->SU=O$S"15&1(C)A!>@:F&N5TQ\29J^4NP,I&C50+['L_5J%&:
M&'.\C5AGKE&\"D]BKC`7BY;B.5&?5"GL^*[K]RCH5T=^R-)"!>80'!6RJQ(W
M7H.)9RPGJRTL3K2KSUL5$%5>A6[@=Q$(5]'W[';@>^*Y^BXA9I\T\=1R8BIS
M!)4`ZTNP3AP["D>ON-1*BLYEDEC&X\C;/@@'^GX$+=^[D)*#%^JW0I\&V=`1
M,-FF$O$[G+I<DV.`>$)C>%_F(B;5.C(#KXZX'V$)TCJD7EFR:H:UE\1Y?M$L
M6M?W5A-;J>EPC*.!UQ-(*M8UV`V68Z?H4%"?49\QO,$&;TWU1`M_(]*J8.#<
MJ./1C28"Q;LFGP;(!I,)!4ER&.9#Y*E&%;=Z(GEA,[T2F@C0`,/F:G'>8)1N
M4IF'3**F#\Q6>\WM9Y6C0I8;0-!PKR55^//S!N8<>%&GB9?@O0U?H4LYVM97
M=E7'P@?'<.Q!_W9TRZ:E[H:T]MZ^&8#C9%WB1^UQ-0L>"/N>@SF2Y![73GQZ
MP/D:]'",@PO7?-GA%R8>M4[><?]=M]]W[<D[3]YF[:>5-8#+A2<Z44?Q:H=M
MJ+\C_XH6_8G3#Y9:$&=CH1$@1Z]B*>ZC%X>-05GWX`RI)128%!,I)1(;&G@>
MSL)2XC[`I8T;,I4>QC*0R>I8LZ96Q;Q>$@$22]>74JA9*O$W<@0Z`"F+"6_0
M^?ME'UDX@^T\1#:;6)F:CG\F4W:PGF"5`\0DK"E`F0$NF(#W;EJE`.L`]0+@
M0L["T[>41&P`-'*(,X4U/W#39DG(68!9$[)6=.-#-VR6Q<3=^)R!V1@(S2/7
M;98"W?O\P6!?QO8FO4=CW]#\GG<,)S[/*@<X)+_G'1/PU)95"G`POQTG!WAF
MJR1B,;]GG`+B@UME(0OY77>*D`]OE<;,Y_>\,X#YZ%8YT+W.'XS,Y4.VL@=F
M:JI3=J]X?*.+392:)X[1PHOTGD8[=JSV':46'IW%/N-(0?(N-NV08RO7FT.7
M=J(R.U3)G:J8-"-""7[/JQZ(>&0=?W"QTQL+TX?`VBEA:[R$88?B-1W$V[+&
MN=XZT>%@XM$Z=URY)EZ#V'`;O$VK/-XL<>%V>*4LU'AS1(3;XI6Q4./-$PEN
MCU?"0HVW`#!_-KQ-:[SUL8@[/7-&<%V8:V3SPQ`*FZ"ZF:)DGSPT6ONHYVP^
M_P777O?"%UU_PXM?\M*7O?P5-^YVEWS3*U_UZM>\]G6O?\,;W_3FM[SU;3?O
M%N^6M[_CG>]Z]WO>^[[W?^"#'_KP1V[=+=Y'/_;Q3WSRMD]]^C.WW_'9.^_Z
M7,F:'76^$/OYGFH*(0M"\U3E8-A'?$^'9_4:.(KV=<YB9M>F=(=+QP;,8YOR
MN.5,5LYJG]KYZL/0Y"&([#+;.#0_-)[U4GW<#??`O?!Y^`)\$;X$7X:OP%?A
M:_!U^`9\$T["?:7C\2WX-GP'O@O?@^_##^"'\"/X,?P$?@H_@Y_#+^`46&..
M;TW'=V:N&-_ZD/ARBB\_K^-[&NZ'7\*OX-?P&_@M_`Y^#W^`/\*?X,_P%_@K
MG!E[/.HZ'@O%<#2&A,.A<#CSP\-QGL3C`?@;_!W^`?^$?\&_X4$X8/Q,\QK%
MHU&,Q^RP>"Q0/)KG=3P>@O_`?^'A7<1AM/&8U?$8:$=SP^)A4SQ:YW4\'H%'
M]R`6HXI'/9MVI7[PI1X9#N[E.@('X)RH8Q_LHT1)$T3I)&R_TW6YD2?F#CV_
M+2=S79[#&]R?ZP>OZLFG>?+O>VX_@QBB\-!XA6=HE(9H*#U\\>C)T,RT?I)5
MA8DCV95,71S+:*`V.=KXTOQ7F/2,..=".[%RL7%^:]UM#<7#>:-^3GBG-X<#
M8@HVS@GP@<UM$)'R9\\)\:'-[2"1M>;."?*1S6TQYTI$QCS'M4X-QYLO$1GS
M&-<ZLS4<<*%$9,Q37#J^'8ZX6"(RYB&N.KT=#HE%MN/(F&>X^O#6V@>.Q70\
MXGLV"[FG"97.!`>93(ZG!Q#'$F.A'PTQ%&X?JNJ8*S:;)"H%CIPU-#L&7@;2
MY.3UE)4/'8R>IZCM]":2!U6[*L]39[8P8RG%'BUSGK^??1KY9[F3'D*5/CH?
ML7TG<N*HL.?'%MK,4UK`;I>S@+H>*P@H9!@,#A4C\1_U08?#8;`>L_8$#_N@
MXQ#>XWN#5U?VT7].#/S88X^?$_;>^P\9[,IU'I"F:O>/F4:>?YF%)`^C!,R(
MBIFZ9J60XV&H!5$&'GV0Z%UKU6DZV_-:+&A5X1AN,=`3%?IN7^&34Y3RF'N0
MZ#VT3#_#*Z:]%I,$B6*$Q3L7-*D;^*W(5@*>3A4N`4LR3(F\G)#4I^K[5D+'
M`;^*P.E+6H&KA,7#5*ZDKJ'ZS/LOX$SZGCRDE);+(;2YVY5DCI*Y4OVZPF9:
M]BT<\`=S@3R1X=&B0@0-]2RN]3VI/#,&RFG0*M@M;!9)KL5]VH`L'CYNZ!`3
MO8/TUY%:=!MKX7"ZQB%Z2'[BU>LD`A_,%^;B/:D9K_/_9Y82-MO*R^A/89.D
M'_<&36[BD=R8W-7L=YE4TD0UZ>OODM)5;RC(^9<</[*\G!/]D<:Y8)_P*.-H
M=\*2$3'1'RGIH,/Q;Q.7+4U"3UE&_D:+T(%*#=XW'DHJ//4E7(27:N35+U*;
M-;TQS31A5Y0PFR20NLN'I'QN\@'_H6<IT9.=5F93LZ]5CT;6)JI$E]'-8UUJ
M$4]TN=8>+FGY.>Z.HH!>=^GZ`C==&)-UP7N5Q'LX.F&TXC=B\,-B?60YH&7^
MI%2-0UGTO\K<B\@/%YEUF(]O05FL,72+BQ<4,&0!\B2=Z,T[53CA8\AD%,0)
M7<@_20^<R?(A"ZJ09EQ'QAKTH[3T.@KUJ^H_K<O"JR,J\6(I+%%&H.1KE%!$
MA$J5)JLC[1_4?8]N,)IXD[U\:FPA(N/H'\_6BM]!;U?4\[]X3Y]U&(>((UW`
M(-X03B&`XDHE[E':,&$]R9HTCC%T,'DK5[_TGLBV&OF*"G!"&I2A]*Y+*,)(
MJ0T32;/9CX8*XE,QM!8_:O.:'!==B87CBFG:;)V;#(/U-N"X)QZH^;FA=`^T
M,:_19&5/`W-RE^"T=?>M5CG`6@;(IV$ACWF8SCO*(M8S1$<AFJ"'U8%'6<B&
M`;D00Z:HA_6)1UG,60/3SC`U[.'XR.-6:YSA)J%Q+"[V=SNX[KU]3Z.22@N-
MF*$M5MLD[T^&3J6%3M]FTWT8&25R=4%[1*`9WL`2:4@S>Y8J?[K/*A*79[P$
MH'I8_!J),7ZH]]-P0FC1**O>.R""&=*,JNHL7]&AT5)C+DOQ3%(K3*8E7G(<
M:;XHH5JJOB2.F('F`$?<LZ.S`0U82P'GG9@C%IT<)G'$S240ZPDBG6#%'*$0
MFR9'W+A5`K*A(?7)7<P1\S%D,^6(Z[?*8,XJS/CL+N:(>H;9U!QQ[=:.0?<^
MW'5C/YOOU4FKOF+ELAV.)*/>S:KBRK@KKBWU[M59ZLK$*TZ#ZA7RMKEQ2/9J
M"B2;5,@)0^PSYH4#^52KH9]ZZ'-XW>ZQ-Q7;?0E9>D,_]D@!>=+O\NV^)&+=
M0'2,)FJV^Y*0#1-R(=>:LW9?$G/6Q,RW^X7IM-V/4>0?O_.X9WC_`S7IQGM[
#00``
`
end


From groff-admin  Sat Mar 11 18:24:51 2000
Received: from mailgw1.be.to (mailgw1.be.to [210.235.212.5])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA00444
	for <groff@ffii.org>; Sat, 11 Mar 2000 18:24:49 +0100
Received: from mail1.be.to (point1.be.to [210.235.212.29])
	by mailgw1.be.to (8.9.3+3.2W/BETO.2.1-2000030802000035) with ESMTP id CAA05942
	for <groff@ffii.org>; Sun, 12 Mar 2000 02:26:32 +0900
Received: from acidrain (ppp22-Mobara1.mtci.ne.jp [210.172.1.224])
	by mail1.be.to (8.8.8+3.0Wbeta13/BETO.2.0-1999110714000000) with SMTP id CAA02010
	for <groff@ffii.org>; Sun, 12 Mar 2000 02:26:23 +0900
Received: (qmail 19502 invoked from network); 11 Mar 2000 17:25:59 -0000
Received: from localhost (HELO acidrain.localnet) (127.0.0.1)
  by localhost with SMTP; 11 Mar 2000 17:25:59 -0000
Date: Sun, 12 Mar 2000 02:25:58 +0900
Message-ID: <86itytctax.wl@dolphin.be.to>
From: OKAZAKI Tetsurou <okazaki@be.to>
To: groff@ffii.org
User-Agent: Wanderlust/1.1.0 (Overjoyed-pre3) REMI/1.14.1
 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) Chao/1.14.1 (=?ISO-8859-4?Q?Rokujiz?=
 =?ISO-8859-4?Q?=F2?=) APEL/10.2 Emacs/20.6 (i386--freebsd) MULE/4.0
 (HANANOEN)
Organization: Unknown
MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?=
 =?ISO-8859-4?Q?sugi=22?=)
Content-Type: multipart/mixed;
 boundary="Multipart_Sun_Mar_12_02:25:57_2000-1"
Subject: [Groff] [patch] Makefile.comm
Status: O
Content-Length: 1620
Lines: 48

--Multipart_Sun_Mar_12_02:25:57_2000-1
Content-Type: text/plain; charset=US-ASCII

Hi,

Please commit the patch below to the CVS. Without this patch,
building groff on FreeBSD 3.4-STABLE stops at:

<<snip>>
gcc -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 \
-DHAVE_STDLIB_H=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 \
-DSTDIO_H_DECLARES_PCLOSE=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 \
-DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void \
-DHAVE_STRUCT_EXCEPTION=1 -DHAVE_UNISTD_H=1 -DHAVE_GETPAGESIZE=1 \
-DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 \
-DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 \
-DHAVE_STRCASECMP=1 -DHAVE_STRSEP=1 -DSYS_SIGLIST_DECLARED=1 \
-g -O2   -c /opt/cvsroot/GNU/groff/src/libs/libgroff/getopt.c
/opt/cvsroot/GNU/groff/src/libs/libgroff/getopt.c:107: getopt.h: No such file or directory
*** Error code 1

Stop.
*** Error code 1

TIA.

--
Tetsurou


--Multipart_Sun_Mar_12_02:25:57_2000-1
Content-Type: text/plain; charset=US-ASCII

diff -urN groff-cvs/Makefile.comm groff/Makefile.comm
--- groff-cvs/Makefile.comm	Sun Feb  6 18:34:29 2000
+++ groff/Makefile.comm	Sat Mar 11 21:40:09 2000
@@ -24,7 +24,7 @@
   -I$(top_builddir)/src/include -I$(top_srcdir)/src/include
 ALL_CCFLAGS=$(INCLUDES) $(CCDEFINES) $(CCFLAGS) $(CPPFLAGS)
 COMPILE.cc=$(CCC) $(ALL_CCFLAGS) -c
-ALL_CFLAGS=$(CDEFINES) $(CFLAGS) $(CPPFLAGS)
+ALL_CFLAGS=$(INCLUDES) $(CDEFINES) $(CFLAGS) $(CPPFLAGS)
 COMPILE.c=$(CC) $(ALL_CFLAGS)  -c
 LINK.cc=$(CCC) $(CCFLAGS) $(LDFLAGS)
 LINK.c=$(CC) $(CFLAGS) $(LDFLAGS)

--Multipart_Sun_Mar_12_02:25:57_2000-1--


From groff-admin  Sun Mar 12 11:49:21 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/GNU) with ESMTP id LAA04837
	for <groff@ffii.org>; Sun, 12 Mar 2000 11:49:21 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sun, 12 Mar 2000 11:51:03 +0100
Received: from rigel.univie.ac.at (dial-143132.HRZ.Uni-Dortmund.DE [129.217.143.132])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id LAA00907;
	Sun, 12 Mar 2000 11:51:02 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id CAA26705;
	Sun, 12 Mar 2000 02:43:55 GMT
To: okazaki@be.to
Cc: groff@ffii.org
Subject: Re: [Groff] [patch] Makefile.comm
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <86itytctax.wl@dolphin.be.to>
References: <86itytctax.wl@dolphin.be.to>
X-Mailer: Mew version 1.94 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
Message-Id: <20000312024355R.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sun, 12 Mar 2000 02:43:55 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 145
Lines: 8

> Please commit the patch below to the CVS. Without this patch,
> building groff on FreeBSD 3.4-STABLE stops at:

Applied, thanks.


    Werner


From groff-admin  Mon Mar 13 11:54:05 2000
Received: from atlantis.erlm.siemens.de (atlantis.erlm.siemens.de [212.114.202.14])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA26674
	for <groff@ffii.org>; Mon, 13 Mar 2000 11:53:58 +0100
Received: from tcenter.erlm.siemens.de (tcenter.erlm.siemens.de [193.98.99.20])
	by atlantis.erlm.siemens.de (8.9.3/8.9.3) with ESMTP id LAA21703;
	Mon, 13 Mar 2000 11:46:31 +0100 (MET)
Received: from nbgv101a.nbg9.siemens.de (nbgv101a.nbg9.siemens.de [130.170.148.248])
	by tcenter.erlm.siemens.de (8.9.0/8.9.0) with ESMTP id LAA01137;
	Mon, 13 Mar 2000 11:42:41 +0100 (MET)
Received: by NBGV101A with Internet Mail Service (5.5.2650.21)
	id <GG0WDQKA>; Mon, 13 Mar 2000 11:47:54 +0100
Message-ID: <11DD9734B036D311947400805F0DD607036422@NBGV101A>
From: Freudenberger Joerg <Joerg.Freudenberger@nbg9.siemens.de>
To: "'Werner LEMBERG'" <wl@gnu.org>
Cc: groff@ffii.org
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
Date: Mon, 13 Mar 2000 11:47:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id LAA26676
Status: O
Content-Length: 457
Lines: 12

> I forgot to ask: What is `vgrind'?  Is there a free implementation?

vgrind is for typographic preparation of source code examples.
On SunOS 5.4 it is a csh script covered by the BSD License. :-)) 

We might find it on FreeBSD. Two years ago I found a man page which
was equivalent to the Sun man page. But I didn't get enough time
to isolate the code package (there is an additional executable
"/usr/lib/vfontedpr" and a macro package on SunOS).

	Jörg


From groff-admin  Tue Mar 14 18:14:07 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/GNU) with ESMTP id SAA19133
	for <groff@ffii.org>; Tue, 14 Mar 2000 18:14:07 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Mar 2000 18:15:41 +0100
Received: from rigel.univie.ac.at (dial-143157.HRZ.Uni-Dortmund.DE [129.217.143.157])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id SAA20438;
	Tue, 14 Mar 2000 18:15:39 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id RAA10552;
	Tue, 14 Mar 2000 17:09:16 GMT
To: Joerg.Freudenberger@nbg9.siemens.de
Cc: groff@ffii.org
Subject: RE: [Groff] groff_man.man revised -- Fast Reply
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <11DD9734B036D311947400805F0DD607036422@NBGV101A>
References: <11DD9734B036D311947400805F0DD607036422@NBGV101A>
X-Mailer: Mew version 1.94 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
Message-Id: <20000314170916W.sx0005@sx2.hrz.uni-dortmund.de>
Date: Tue, 14 Mar 2000 17:09:16 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 726
Lines: 20

> vgrind is for typographic preparation of source code examples.
> On SunOS 5.4 it is a csh script covered by the BSD License. :-)) 
> 
> We might find it on FreeBSD.

I've found it on www.debian.org (BTW, one of the most excellent sites
I've ever seen in the web -- at least the German site I was pointed to
automatically).

This vgrind version is almost completely unusable.  For example, it is
not possible to embed code samples into, say, a man page since the
tmac.vgrind macro file redefines the layout in a brute manner.
Apparently, tmac.vgrind has been taken from another vgrind
implementation since some macros/variables are defined but not used.

So for the moment, I wont' support vgrind within groff.


    Werner


From groff-admin  Thu Mar 16 00:29:26 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id AAA22992
	for <groff@ffii.org>; Thu, 16 Mar 2000 00:29:25 +0100
Received: (qmail 4066 invoked from network); 15 Mar 2000 23:31:39 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 15 Mar 2000 23:31:39 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id AAA18178
	for groff@ffii.org; Thu, 16 Mar 2000 00:30:20 +0100
Message-ID: <20000316003019.A18176@mayn.de>
Date: Thu, 16 Mar 2000 00:30:19 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] (no subject)
Status: O
Content-Length: 3397
Lines: 119

The following patch implements long options for groff using
getopt_long(3).  I decided to give each existing single character
option a unique long option equivalent.

This approach is minimally invasive because such long options are
internally translated into their equivalent, such that they need not a
be considered in the switch statement.  Moreover, as only short options
are passed on, the existing infrastructure is not affected.

I tried to use the GNU standard option names, but the following names
might be discutable:

define-string (?set-string?)
set-register (?define-register?)
macro-package (?)
number-of-first-page (?)
no-eqn-newlines (?)
append-stdin (?stdin?)
to-stdout (?stdout?)
...(?)

Bernd Warken <bwarken@mayn.de>

#######################################################

--- groff.cc.orig	Thu Mar 16 00:21:32 2000
+++ groff.cc	Thu Mar 16 00:51:50 2000
@@ -25,6 +25,7 @@
 #include <stdlib.h>
 #include <signal.h>
 #include <errno.h>
+#include <getopt.h>
 
 #include "lib.h"
 #include "assert.h"
@@ -109,19 +110,78 @@
   int iflag = 0;
   int Xflag = 0;
   int safer_flag = 1;
-  int opt;
+
+  int opt, longopt_index;
+  static struct option long_options[] = {
+    // Long options with a corresponding short option are internally
+    // replaced by their short equivalent.
+    // Format: {long_option_name, has_arg, 0, short_option_char}
+    // Such long options 
+    {"ascii", 0, 0, 'a'},
+    {"debug", 0, 0, 'b'},
+    {"compat", 0, 0, 'C'},
+    {"define-string", 1, 0, 'd'},
+    {"eqn", 0, 0, 'e'},
+    {"ignore-errors", 0, 0, 'E'},
+    {"font-family", 1, 0, 'f'},
+    {"font-dir", 1, 0, 'F'},
+    {"grn", 0, 0, 'g'},
+    {"help", 0, 0, 'h'},
+    {"append-stdin", 0, 0, 'i'},
+    {"soelim-dir", 1, 0, 'I'},
+    {"print", 0, 0, 'l'},
+    {"print-arg", 1, 0, 'L'},
+    {"macro-package", 1, 0, 'm'},
+    {"macro-dir", 1, 0, 'M'},
+    {"number-of-first-page", 1, 0, 'n'},
+    {"no-eqn-newlines", 0, 0, 'N'},
+    {"output-pages", 1, 0, 'o'},
+    {"pic", 0, 0, 'p'},
+    {"postproc-arg", 1, 0, 'P'},
+    {"set-register", 1, 0, 'r'},
+    {"refer", 0, 0, 'R'},
+    {"soelim", 0, 0, 's'},
+    {"safer", 0, 0, 'S'},
+    {"tbl", 0, 0, 't'},
+    {"device", 1, 0, 'T'},
+    {"unsafe", 0, 0, 'U'},
+    {"version", 0, 0, 'v'},
+    {"to-stdout", 0, 0, 'V'},
+    {"warning", 1, 0, 'w'},
+    {"no-warning", 1, 0, 'W'},
+    {"xditview", 0, 0, 'X'},
+    {"no-output", 0, 0, 'z'},
+    {"no-postproc", 0, 0, 'Z'},
+
+    // Long options without a corresponding short option
+    // Format: {long_option_name, has_arg, 0, 0}
+    //
+    // (none implemented at the moment)
+
+    // last element must be all 0
+    {0, 0, 0, 0}
+  }; 
+
   const char *command_prefix = getenv("GROFF_COMMAND_PREFIX");
   if (!command_prefix)
     command_prefix = PROG_PREFIX;
   commands[TROFF_INDEX].set_name(command_prefix, "troff");
-  while ((opt = getopt(argc, argv,
-		       "abCd:eEf:F:ghiI:lL:m:M:n:No:pP:r:RsStT:UvVw:W:XzZ"))
-	 != EOF) {
+
+  while ((opt = getopt_long(argc, argv,
+			    "abCd:eEf:F:ghiI:lL:m:M:n:No:pP:r:RsStT:UvVw:W:XzZ",
+			    long_options, &longopt_index
+			    )
+	  ) != EOF
+	 )
+  {
     char buf[3];
     buf[0] = '-';
     buf[1] = opt;
     buf[2] = '\0';
     switch (opt) {
+    case 0:
+      // handle long options without a corresponding single-character option
+      break;
     case 'i':
       iflag = 1;
       break;


From groff-admin  Thu Mar 16 20:47:22 2000
Received: from mailserv2.mdsla.com (ip-008.remac.com [207.171.26.8] (may be forged))
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA11356
	for <groff@ffii.org>; Thu, 16 Mar 2000 20:47:21 +0100
Received: from ES1 (207.171.26.123) by mailserv2.mdsla.com (Worldmail 1.3.167) for groff@ffii.org; 16 Mar 2000 11:56:03 -0800
Message-Id: <3.0.6.32.20000316115022.0099dad0>
X-Sender:  (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 16 Mar 2000 11:50:22 -0800
To: groff@ffii.org
From: port22@rnhnet.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Groff] PC / Internet fax solution
Status: O
Content-Length: 493
Lines: 12

I stopped by your web site and thought you may be interested in our
PC/internet based fax service. You can send 1 to 1,000,000 faxes in just
minutes to any destination in the US, Canada, and Europe for as low as 7.4
cents per minute. Our user-friendly submission software lets you queue your
job on our server within minutes. Why not try the system for FREE. We will
be happy to send 100 Faxes on your behalf to your fax list immediately.
Simply go to 

http://www.efaxcast.com/submit.htm

 


From groff-admin  Fri Mar 17 13:33:01 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/GNU) with ESMTP id NAA31381
	for <groff@ffii.org>; Fri, 17 Mar 2000 13:33:01 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 17 Mar 2000 13:35:24 +0100
Received: from rigel.univie.ac.at (dial-143142.HRZ.Uni-Dortmund.DE [129.217.143.142])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id NAA19380;
	Fri, 17 Mar 2000 13:35:21 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id LAA31081;
	Fri, 17 Mar 2000 11:31:02 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] (no subject)
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000316003019.A18176@mayn.de>
References: <20000316003019.A18176@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000317113102P.sx0005@sx2.hrz.uni-dortmund.de>
Date: Fri, 17 Mar 2000 11:31:02 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 2734
Lines: 96

> I tried to use the GNU standard option names, but the following names
> might be discutable:
> [...]

Please look at the following `patch' (it isn't a real patch since I've
simply inserted/removed lines without adjusting the diff headers).

I've changed some option names.  Please comment.


    Werner

--- groff.cc.orig	Thu Mar 16 00:21:32 2000
+++ groff.cc	Thu Mar 16 00:51:50 2000
@@ -25,6 +25,7 @@
 #include <stdlib.h>
 #include <signal.h>
 #include <errno.h>
 
 #include "lib.h"
 #include "assert.h"
@@ -109,19 +110,78 @@
   int iflag = 0;
   int Xflag = 0;
   int safer_flag = 1;
-  int opt;
+
+  int opt, longopt_index;
+  static struct option long_options[] = {
+    /* Long options with a corresponding short option are internally
+       replaced by their short equivalent. */
+    {"ascii", 0, NULL, 'a'},
+    {"debug", 0, NULL, 'b'},
+    {"compat", 0, NULL, 'C'},
+    {"define-string", 1, NULL, 'd'},
+    {"eqn", 0, NULL, 'e'},
+    {"ignore-errors", 0, NULL, 'E'},
+    {"font-family", 1, NULL, 'f'},
+    {"font-dir", 1, NULL, 'F'},
+    {"grn", 0, NULL, 'g'},
+    {"help", 0, NULL, 'h'},
+    {"append-stdin", 0, NULL, 'i'},
+    {"soelim-dir", 1, NULL, 'I'},
+    {"print", 0, NULL, 'l'},
+    {"print-arg", 1, NULL, 'L'},
+    {"macro-package", 1, NULL, 'm'},
+    {"macro-dir", 1, NULL, 'M'},
+    {"first-page-number", 1, NULL, 'n'},
+    {"no-eqn-newlines", 0, NULL, 'N'},
+    {"output-pages", 1, NULL, 'o'},
+    {"pic", 0, NULL, 'p'},
+    {"device-arg", 1, NULL, 'P'},
+    {"set-register", 1, NULL, 'r'},
+    {"refer", 0, NULL, 'R'},
+    {"soelim", 0, NULL, 's'},
+    {"safer", 0, NULL, 'S'},
+    {"tbl", 0, NULL, 't'},
+    {"device", 1, NULL, 'T'},
+    {"unsafe", 0, NULL, 'U'},
+    {"version", 0, NULL, 'v'},
+    {"to-stdout", 0, NULL, 'V'},
+    {"warning", 1, NULL, 'w'},
+    {"no-warning", 1, NULL, 'W'},
+    {"xditview", 0, NULL, 'X'},
+    {"no-output", 0, NULL, 'z'},
+    {"no-device", 0, NULL, 'Z'},
+
+    /* last element must be all 0 */
+    {NULL, 0, NULL, 0}
+  }; 
+
   const char *command_prefix = getenv("GROFF_COMMAND_PREFIX");
   if (!command_prefix)
     command_prefix = PROG_PREFIX;
   commands[TROFF_INDEX].set_name(command_prefix, "troff");
-  while ((opt = getopt(argc, argv,
-		       "abCd:eEf:F:ghiI:lL:m:M:n:No:pP:r:RsStT:UvVw:W:XzZ"))
+
+  while ((opt = getopt_long(argc, argv,
+			     "abCd:eEf:F:ghiI:lL:m:M:n:No:"
+			     "pP:r:RsStT:UvVw:W:XzZ",
+			     long_options, &longopt_index))
	 != EOF) {
     char buf[3];
     buf[0] = '-';
     buf[1] = opt;
     buf[2] = '\0';
     switch (opt) {
+    case 0:
+      /* handle long options without a corresponding
+	  single-character option */
+      break;
     case 'i':
       iflag = 1;
       break;


From groff-admin  Fri Mar 17 13:33:01 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/GNU) with ESMTP id NAA31385
	for <groff@ffii.org>; Fri, 17 Mar 2000 13:33:01 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 17 Mar 2000 13:35:21 +0100
Received: from rigel.univie.ac.at (dial-143142.HRZ.Uni-Dortmund.DE [129.217.143.142])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id NAA19377;
	Fri, 17 Mar 2000 13:35:19 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id LAA31105;
	Fri, 17 Mar 2000 11:47:08 GMT
To: grciszew@cyf-kr.edu.pl
Cc: groff@ffii.org
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000311173341.A209@kinga.cyf-kr.edu.pl>
References: <20000229224216W.sx0005@sx2.hrz.uni-dortmund.de>
	<20000310183900D.sx0005@sx2.hrz.uni-dortmund.de>
	<20000311173341.A209@kinga.cyf-kr.edu.pl>
X-Mailer: Mew version 1.94 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
Message-Id: <20000317114707A.sx0005@sx2.hrz.uni-dortmund.de>
Date: Fri, 17 Mar 2000 11:47:07 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] Re: Unicode, EBCDIC, Latin-2, JIS for groff
Status: O
Content-Length: 1483
Lines: 39

> My suggestion is direct separation of input encoding and output
> language description.

I fully agree.  But I think that this is already done since groff
communicates with the output devices via glyph names only.  The
problem is rather how to make the installation of new fonts easier.

> The "language" consist also of the following elements:
>    * the direction in which fonts are placed. For example in ancient 
>      Latin it was something like this:
>      ----------->---------------->-----------.
>      .----------<----------------<-----------'
>      `---------->---------------->
>      Although, such strange method of writing is probably not used 
>      nowadays, that are languages where the right-to-left or 
>      top-to-button directions are used,

Bustrophedon...  Well, groff won't support this :-)

>    * the hyphenation schema,

This can be done easily, I think.

>    * the local printing customs (i.e. ligatures).

You mean enabling/disabling certain ligatures for a given language?
This is missing yet.  On the other hand, it is highly font-specific.
Currently, the number of ligatures it restricted to the Western ones.
Maybe it should be generalized (e.g. `st' ligature for French etc).

> It will be nice to have tool which allow complex definition of a
> language support as a set of (easy to write) macros.

I'm not an experienced groff macro writer, so please make
suggestions.  A sort of `LaTeX' for groff sounds like a good idea.


    Werner


From groff-admin  Sat Mar 18 13:20:49 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/GNU) with ESMTP id NAA22095
	for <groff@ffii.org>; Sat, 18 Mar 2000 13:20:48 +0100
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id HAA09080
	for <groff@gnu.org>; Sat, 18 Mar 2000 07:23:21 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 18 Mar 2000 13:22:53 +0100
Received: from rigel.univie.ac.at (dial-143177.HRZ.Uni-Dortmund.DE [129.217.143.177])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id NAA03784;
	Sat, 18 Mar 2000 13:22:51 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id HAA32637;
	Sat, 18 Mar 2000 07:19:03 GMT
To: Ted.Harding@nessie.mcc.ac.uk
Cc: groff@gnu.org
Subject: RE: [Groff] funny behaviour of \{
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <20000309150202J.sx0005@sx2.hrz.uni-dortmund.de>
References: <20000308162417Q.sx0005@sx2.hrz.uni-dortmund.de>
	<XFMail.000308230755.Ted.Harding@nessie.mcc.ac.uk>
	<20000309150202J.sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000318071901V.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sat, 18 Mar 2000 07:19:01 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 249
Lines: 10

> > >   .ab\{This causes a funny error message!
> > > 
> > > Is this just pathological behaviour or does it make any sense?

Please, PLEASE, forget everything I've said.  And don't tell anybody
that I've ever written this nonsense :-)


    Werner


From groff-admin  Sat Mar 18 14:48:14 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id OAA22580
	for <groff@ffii.org>; Sat, 18 Mar 2000 14:48:13 +0100
Received: (qmail 20818 invoked from network); 18 Mar 2000 13:50:46 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 18 Mar 2000 13:50:46 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id OAA10614
	for groff@ffii.org; Sat, 18 Mar 2000 14:49:25 +0100
Message-ID: <20000318144924.A10603@mayn.de>
Date: Sat, 18 Mar 2000 14:49:25 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] getopt.h
Status: O
Content-Length: 536
Lines: 14

In src/include there is a file getopt.h which is identical to the
corresponding glibc file installed on my system, well, except from the
copyright.  This local header file is included from lib.h.

Is it possible to get rid of this file and replace the #include "" by
#include <getopt.h>?

Or are there any primitive non-GNU environments that do not provide
longoptions (maybe an autoconf issue)?  In this case, we should include
the latest GNU getopt.h, keep the GNU copyright, and write some comment.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Sat Mar 18 14:49:06 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id OAA22624
	for <groff@ffii.org>; Sat, 18 Mar 2000 14:49:05 +0100
Received: (qmail 20872 invoked from network); 18 Mar 2000 13:51:38 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 18 Mar 2000 13:51:38 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id OAA10654
	for groff@ffii.org; Sat, 18 Mar 2000 14:50:22 +0100
Message-ID: <20000318145022.B10603@mayn.de>
Date: Sat, 18 Mar 2000 14:50:22 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Subject: Re: [Groff] (no subject)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Status: O
Content-Length: 168
Lines: 9

From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>

> I've changed some option names.  Please comment.

Thank you, I'll take them.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Sat Mar 18 14:56:19 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id OAA22695
	for <groff@ffii.org>; Sat, 18 Mar 2000 14:56:17 +0100
Received: (qmail 21002 invoked from network); 18 Mar 2000 13:58:27 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 18 Mar 2000 13:58:27 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id OAA10676
	for groff@ffii.org; Sat, 18 Mar 2000 14:57:10 +0100
Message-ID: <20000318145710.C10603@mayn.de>
Date: Sat, 18 Mar 2000 14:57:10 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Subject: [Groff] Re: Unicode, EBCDIC, Latin-2, JIS for groff
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Status: O
Content-Length: 817
Lines: 19

>>    * the local printing customs (i.e. ligatures).                             
                                                                                
>You mean enabling/disabling certain ligatures for a given language?             
>This is missing yet.  On the other hand, it is highly font-specific.            
>Currently, the number of ligatures it restricted to the Western ones.           
>Maybe it should be generalized (e.g. `st' ligature for French etc).             
                                                                                
I think we should harmonize with the UNICODE standard.   Version 3.0
defines the following latin-like ligatures:

ae U+00E6
oe U+0153
ij U+0133
ff, fi, fl, ffi, ffl, ft, st in U+FB0x
combining half marks U+FE2x

Bernd Warken <bwarken@mayn.de>



From groff-admin  Sat Mar 18 16:22:00 2000
Received: from ns1.greenbush.com (mngovsci@ns1.greenbush.com [209.90.218.2])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA23228
	for <groff@ffii.org>; Sat, 18 Mar 2000 16:21:59 +0100
Received: from localhost (mngovsci@localhost)
	by ns1.greenbush.com (8.9.3/8.8.7) with SMTP id KAA12151;
	Sat, 18 Mar 2000 10:24:26 -0500
Date: Sat, 18 Mar 2000 10:24:26 -0500 (EST)
From: Eddie Maddox <eddie@mngovsci.com>
X-Sender: mngovsci@ns1.greenbush.com
To: Groff Mailing List <groff@ffii.org>
cc: Janet Johnstone <jj@canbible.ca>
Message-ID: <Pine.LNX.3.96.1000318101420.12131A-100000@ns1.greenbush.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] I need help! (fwd)
Status: O
Content-Length: 1319
Lines: 44

Janet sent this to me directly instead of to the Groff mailing list. I
just now checked my mail and saw it. Could someone help her out, please?

Janet: I help maintain the Groff Web sites, but I really know only a
little bit about it since I've used it only a little. From now on just
send your questions to our Groff Mailing List <groff@ffii.org>. There are
several there who have been _very_ helpful to me and others.

Thank you.
------------------
Eddie Maddox
eddie@mngovsci.com


---------- Forwarded message ----------
Date: Fri, 17 Mar 2000 12:31:59 -0500
From: Janet Johnstone <jj@canbible.ca>
To: eddie@mngovsci.com
Subject: I need help!

Hello Eddie


I'm probably not suppose to get in touch with support this way...but I'm
desparately looking for a solution to a problem with groff.     I keep
getting an error message "line too long" when printing to my HPIV laser
printer.    Can you tell me why?

I've searched all places for documentation of groff...and there is lots out
there...but none of it seems to have a section for common error messages.

Anyway I really would appreciate a response.   I am very sorry to bother
you, but I'm running out of time and solutions to this problem.

Janet Johnstone
Computer Systems Administrator
Canadian Bible Society
Toronto, Ontario
M4A 2S4


Thank you so much!



From groff-admin  Sat Mar 18 18:14:37 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/GNU) with ESMTP id SAA23918
	for <groff@ffii.org>; Sat, 18 Mar 2000 18:14:37 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 18 Mar 2000 18:16:57 +0100
Received: from rigel.univie.ac.at (dial-143139.HRZ.Uni-Dortmund.DE [129.217.143.139])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id SAA07544;
	Sat, 18 Mar 2000 18:16:55 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id RAA02362;
	Sat, 18 Mar 2000 17:14:56 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] getopt.h
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000318144924.A10603@mayn.de>
References: <20000318144924.A10603@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000318171456C.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sat, 18 Mar 2000 17:14:56 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 939
Lines: 31

> In src/include there is a file getopt.h which is identical to the
> corresponding glibc file installed on my system, well, except from the
> copyright.  This local header file is included from lib.h.
> 
> Is it possible to get rid of this file and replace the #include "" by
> #include <getopt.h>?

No.  Too many OSes don't have a proper getopt() implementation.

> Or are there any primitive non-GNU environments that do not provide
> longoptions

Correct.  Don't say `primitive' :-)

> (maybe an autoconf issue)?

The logic to recognize GNU getopt is already integrated into
getopt.[ch].  For example, on a GNU box, the contents of those file is
completely skipped.

> In this case, we should include the latest GNU getopt.h, keep the
> GNU copyright, and write some comment.

I took the files from Emacs 20.6 which is just a few weeks old.  Is
there a newer version already?

About the comment: Please submit a patch...


    Werner


From groff-admin  Sat Mar 18 18:14:37 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/GNU) with ESMTP id SAA23921
	for <groff@ffii.org>; Sat, 18 Mar 2000 18:14:37 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 18 Mar 2000 18:17:01 +0100
Received: from rigel.univie.ac.at (dial-143139.HRZ.Uni-Dortmund.DE [129.217.143.139])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id SAA07550;
	Sat, 18 Mar 2000 18:17:00 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id RAA02356;
	Sat, 18 Mar 2000 17:10:46 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] Re: Unicode, EBCDIC, Latin-2, JIS for groff
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000318145710.C10603@mayn.de>
References: <20000318145710.C10603@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000318171046V.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sat, 18 Mar 2000 17:10:46 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 1109
Lines: 33

> >You mean enabling/disabling certain ligatures for a given language?
> >This is missing yet.  On the other hand, it is highly
> >font-specific.  Currently, the number of ligatures it restricted to
> >the Western ones.  Maybe it should be generalized (e.g. `st'
> >ligature for French etc).
>
>
> I think we should harmonize with the UNICODE standard.  Version 3.0
> defines the following latin-like ligatures:
> 
> ae U+00E6
> oe U+0153
> ij U+0133
> ff, fi, fl, ffi, ffl, ft, st in U+FB0x
> combining half marks U+FE2x

This doesn't help at all.  We need an unlimited amount of ligatures
which can be freely defined by the fonts.

As an example, consider Gutenberg's Fraktur-like font which has more
than 30 different ligatures.

Note that Unicode ligatures are only there for compatibility with
other character sets resp. encodings.  Ideally, there should be no
ligatures in Unicode since this is a glyph feature not related to
characters.

BTW, ae, oe, and ij are *not* ligatures but characters, even if they
look like ligatures.  There are some other examples in the Cyrillic
script also.


    Werner


From groff-admin  Sat Mar 18 18:14:37 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/GNU) with ESMTP id SAA23923
	for <groff@ffii.org>; Sat, 18 Mar 2000 18:14:37 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 18 Mar 2000 18:17:04 +0100
Received: from rigel.univie.ac.at (dial-143139.HRZ.Uni-Dortmund.DE [129.217.143.139])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id SAA07554;
	Sat, 18 Mar 2000 18:17:02 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id RAA02351;
	Sat, 18 Mar 2000 17:02:25 GMT
To: eddie@mngovsci.com
Cc: groff@ffii.org, jj@canbible.ca
Subject: Re: [Groff] I need help! (fwd)
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.3.96.1000318101420.12131A-100000@ns1.greenbush.com>
References: <Pine.LNX.3.96.1000318101420.12131A-100000@ns1.greenbush.com>
X-Mailer: Mew version 1.94 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
Message-Id: <20000318170224Q.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sat, 18 Mar 2000 17:02:24 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 1003
Lines: 26

> I'm probably not suppose to get in touch with support this way...but
> I'm desparately looking for a solution to a problem with groff.  I
> keep getting an error message "line too long" when printing to my
> HPIV laser printer.  Can you tell me why?

No.  I've just checked the groff source code, and at no place there is
the phrase `line too long'.  Can you please send more info, e.g. a
sample input file, or an exact error message?

Are you sure that the problem is related to groff at all?

As a quick help, try another output device, say, grops or grodvi (by
using `-Tps' resp. `-Tdvi').  Then use ghostscript (for the PS file)
or dvilj4 for printing to your Laserjet printer.

> I've searched all places for documentation of groff...and there is
> lots out there... but none of it seems to have a section for common
> error messages.

Unfortunately, there is *not* enough documentation about groff.  I'm
working on groff.texinfo which will eventuall document all aspects of
groff.


    Werner


From groff-admin  Sun Mar 19 19:43:04 2000
Received: from ax-nicb.axnet.it (root@[212.141.54.149])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA31282
	for <Groff@ffii.org>; Sun, 19 Mar 2000 19:38:37 +0100
Received: (from nicb@localhost)
	by ax-nicb.axnet.it (8.8.7/8.8.7) id TAA22801;
	Sun, 19 Mar 2000 19:32:28 +0100
Date: Sun, 19 Mar 2000 19:32:28 +0100 (CET)
From: Nicola Bernardini <nicb@axnet.it>
To: Groff@ffii.org
Message-ID: <Pine.LNX.4.10.10003191929230.16439-100000@ax-nicb.axnet.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] soelim outdated
Status: O
Content-Length: 459
Lines: 18

Is someone working on soelim any longer?

at least up to version 1.15, soelim does not understand .mso, \V[$var],
etc. so it is practically unusable on a modern groff setup.
I can work on it and provide a patch if nobody else is working on it.
I can also add other ideas and requests if they're reasonable and I
know how to implement them...

ciao

Nicola

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



From groff-admin  Mon Mar 20 08:19:44 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/GNU) with ESMTP id IAA16255
	for <Groff@ffii.org>; Mon, 20 Mar 2000 08:19:44 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 20 Mar 2000 08:22:27 +0100
Received: from rigel.univie.ac.at (dial-143147.HRZ.Uni-Dortmund.DE [129.217.143.147])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id IAA28307;
	Mon, 20 Mar 2000 08:22:24 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id XAA06066;
	Sun, 19 Mar 2000 23:36:30 GMT
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] soelim outdated
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.4.10.10003191929230.16439-100000@ax-nicb.axnet.it>
References: <Pine.LNX.4.10.10003191929230.16439-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.94 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
Message-Id: <20000319233629L.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sun, 19 Mar 2000 23:36:29 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 1947
Lines: 50

> at least up to version 1.15, soelim does not understand .mso,
> \V[$var], etc. so it is practically unusable on a modern groff
> setup.  I can work on it and provide a patch if nobody else is
> working on it.  I can also add other ideas and requests if they're
> reasonable and I know how to implement them...

Three months ago this has been discussed already:

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

   > >    > > It would be nice to have an "msoelim".  I tried to hack the
   > >    > > present "soelim" but I am no programmer and had no sucess.
   > >    > 
   > >    > But isn't this an abuse of the `mso' request?  Or do you really
   > >    > intend to pipe macro files stored together with other TMAC
   > >    > files through tbl and friends?
   > >    > 
   > >    > Can you give an example how you would use it?
   > > 
   > > I use it just as I use the "so" request, except without the absolute
   > > pathnames in the files.   The example that I had in mind was:  
   > > 
   > > [...]
   > > 
   > > In this way ".mso" acts like the "\input" command in TeX.
   > 
   > I don't believe that you really want an `msoelim' program.  I think
   > you want a GROFF_INPUT_PATH environment variable where .so requests
   > search for files also...
   > 

I thought that was the difference between "so" and "mso"--that "mso"
searched paths in the GROFF_TMAC_PATH while "so" didn't; but I must
have misunderstood the documentation.  Anyway you are right.  I want
an "so" that reads paths from some environment variable.  So "so"
behaves with respect to "GROFF_INPUT_PATH" as "\input" behaves with
respect to "TEXINPUTS".

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

I think this is what you want -- patches are highly welcome :-)

Can you please explain why you think that \V needs to be expanded by
soelim?

And of course we are interested in further suggestions...


    Werner


From groff-admin  Tue Mar 21 06:51:18 2000
Received: from ax-nicb.axnet.it (root@[212.141.54.149])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id GAA05937
	for <Groff@ffii.org>; Tue, 21 Mar 2000 06:51:08 +0100
Received: (from nicb@localhost)
	by ax-nicb.axnet.it (8.8.7/8.8.7) id GAA29922;
	Tue, 21 Mar 2000 06:49:44 +0100
Date: Tue, 21 Mar 2000 06:49:44 +0100 (CET)
From: Nicola Bernardini <nicb@axnet.it>
To: Werner LEMBERG <wl@gnu.org>
cc: Groff@ffii.org
Subject: Re: [Groff] soelim outdated
In-Reply-To: <20000319233629L.sx0005@sx2.hrz.uni-dortmund.de>
Message-ID: <Pine.LNX.4.10.10003210629490.16439-100000@ax-nicb.axnet.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 1659
Lines: 58

Sunday, Werner LEMBERG schrieb:

[snip]
> Three months ago this has been discussed already:

sorry about this repetition, but I think it's necessary to clarify a bit...

[snip]
> I thought that was the difference between "so" and "mso"--that "mso"
> searched paths in the GROFF_TMAC_PATH while "so" didn't; but I must
> have misunderstood the documentation.  Anyway you are right.  I want
> an "so" that reads paths from some environment variable.  So "so"
> behaves with respect to "GROFF_INPUT_PATH" as "\input" behaves with
> respect to "TEXINPUTS".

well, I did a little test:

			.so		.mso

GROFF_INPUT_PATH	no		no
GROFF_TMAC_PATH		no		yes

no means 'does not work with inclusion to some other directory which
is not either the current or the standard tmac dir'

yes means the opposite

> ----------------------------------------------------------------------
> 
> I think this is what you want -- patches are highly welcome :-)

I sometimes need the ability to include extra bits of text (which may
not be macros) which lie on personal directories etc. I generally do
it with the -M option, and with .mso it works quite well (*except* for
soelim).

> Can you please explain why you think that \V needs to be expanded by
> soelim?

here's an example: say that I have a situation like this (in fact I have
*plenty* of situations like this :)

.mso \V[SPECIAL_DIR]/some-file

it'll work for groff, but not for soelim :(

> And of course we are interested in further suggestions...

well I'll try to find the time and propose you some patches...

Nicola

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



From groff-admin  Tue Mar 21 09:20:33 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/GNU) with ESMTP id JAA06794
	for <Groff@ffii.org>; Tue, 21 Mar 2000 09:20:33 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 21 Mar 2000 09:23:08 +0100
Received: from rigel.univie.ac.at (dial-143156.HRZ.Uni-Dortmund.DE [129.217.143.156])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id JAA28005;
	Tue, 21 Mar 2000 09:23:06 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id HAA07863;
	Tue, 21 Mar 2000 07:39:52 GMT
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] soelim outdated
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.4.10.10003210629490.16439-100000@ax-nicb.axnet.it>
References: <20000319233629L.sx0005@sx2.hrz.uni-dortmund.de>
	<Pine.LNX.4.10.10003210629490.16439-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.94 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
Message-Id: <20000321073952X.sx0005@sx2.hrz.uni-dortmund.de>
Date: Tue, 21 Mar 2000 07:39:52 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 887
Lines: 27

> > I thought that was the difference between "so" and "mso"--that
> > "mso" searched paths in the GROFF_TMAC_PATH while "so" didn't; but
> > I must have misunderstood the documentation.  Anyway you are
> > right.  I want an "so" that reads paths from some environment
> > variable.  So "so" behaves with respect to "GROFF_INPUT_PATH" as
> > "\input" behaves with respect to "TEXINPUTS".
> 
> well, I did a little test:
> 
> 			.so		.mso
> 
> GROFF_INPUT_PATH	no		no
> GROFF_TMAC_PATH	no		yes

Of course it doesn't work since it isn't implemented...

> I sometimes need the ability to include extra bits of text (which
> may not be macros) which lie on personal directories etc. I
> generally do it with the -M option, and with .mso it works quite
> well (*except* for soelim).

Again, I think this is an abuse of .mso, and a GROFF_INPUT_PATH
feature should be introduced.


    Werner


From groff-admin  Tue Mar 21 17:00:26 2000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA10608
	for <groff@ffii.org>; Tue, 21 Mar 2000 17:00:26 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e3.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA42484
	for <groff@ffii.org>; Tue, 21 Mar 2000 11:01:51 -0500
Received: from infosys.tuwien.ac.at (ss3.pok.socks.ibm.com [9.14.3.68])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with ESMTP id LAA67048
	for <groff@ffii.org>; Tue, 21 Mar 2000 11:03:02 -0500
Message-ID: <38D79D4D.3B2C2470@infosys.tuwien.ac.at>
Date: Tue, 21 Mar 2000 11:03:25 -0500
From: =?iso-8859-1?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "groff@ffii.org" <groff@ffii.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: [Groff] EBCDIC hyphenation in troff on tty
Status: O
Content-Length: 751
Lines: 18

Lost in source! After converting the font files and making some minor
source changes, troff formats man pages quite right under our EBCDIC
system. The only problem is that the '[' (left bracket, ascii 0132 x5B,
ebcdic 0255 xAD) is used as a hyphenation character at the end of lines,
instead the correct '-' (minus, ascii 0055 x2d, ebcdic 0140 x60).

I could not find out why. Can somebody show me the right piece of code,
please?

Sándor Bárány,
"Using Open Source Software on OS/390 UNIX"
IBM Resident  in Poughkeepsie, NY by 
International Technical Support Organization (ITSO)
(http://www.redbooks.ibm.com/resindex.html)
E-mail:  itsore24@us.ibm.com
IBM Notes:  ITSO Resident 24/Poughkeepsie/IBM@IBMUS
Tel: (1-914) 433-1481 Fax: (1-914) 432-8264


From groff-admin  Wed Mar 22 01:13: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/GNU) with ESMTP id BAA14304
	for <groff@ffii.org>; Wed, 22 Mar 2000 01:13:05 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 22 Mar 2000 01:16:02 +0100
Received: from rigel.univie.ac.at (dial-143178.HRZ.Uni-Dortmund.DE [129.217.143.178])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id BAA12950;
	Wed, 22 Mar 2000 01:15:58 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id AAA08331;
	Wed, 22 Mar 2000 00:09:39 GMT
To: S.Barany@infosys.tuwien.ac.at
Cc: groff@ffii.org
Subject: Re: [Groff] EBCDIC hyphenation in troff on tty
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <38D79D4D.3B2C2470@infosys.tuwien.ac.at>
References: <38D79D4D.3B2C2470@infosys.tuwien.ac.at>
X-Mailer: Mew version 1.94 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
Message-Id: <20000322000939V.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 22 Mar 2000 00:09:39 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 512
Lines: 13

> Lost in source!  After converting the font files and making some
> minor source changes, troff formats man pages quite right under our
> EBCDIC system.  The only problem is that the '[' (left bracket,
> ascii 0132 x5B, ebcdic 0255 xAD) is used as a hyphenation character
> at the end of lines, instead the correct '-' (minus, ascii 0055 x2d,
> ebcdic 0140 x60).

What aboud the shc request to set the soft hyphen character (in
node.cc)?  This defaults to HYPHEN_SYMBOL (which is the glyph `hy').


    Werner


From groff-admin  Wed Mar 22 05:20:39 2000
Received: from ax-nicb.axnet.it (root@[212.141.54.149])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id FAA15896
	for <Groff@ffii.org>; Wed, 22 Mar 2000 05:20:24 +0100
Received: (from nicb@localhost)
	by ax-nicb.axnet.it (8.8.7/8.8.7) id FAA32515;
	Wed, 22 Mar 2000 05:20:03 +0100
Date: Wed, 22 Mar 2000 05:20:03 +0100 (CET)
From: Nicola Bernardini <nicb@axnet.it>
To: Werner LEMBERG <wl@gnu.org>
cc: Groff@ffii.org
Subject: Re: [Groff] soelim outdated
In-Reply-To: <20000321073952X.sx0005@sx2.hrz.uni-dortmund.de>
Message-ID: <Pine.LNX.4.10.10003220515110.16439-100000@ax-nicb.axnet.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 1016
Lines: 31

Yesterday, Werner LEMBERG schrieb:

[snip]
> > I sometimes need the ability to include extra bits of text (which
> > may not be macros) which lie on personal directories etc. I
> > generally do it with the -M option, and with .mso it works quite
> > well (*except* for soelim).
> 
> Again, I think this is an abuse of .mso, and a GROFF_INPUT_PATH
> feature should be introduced.

I'm not sure I understand why it is an abuse (included stuff may well
be macros after all). The .mso line in the groff manpage says:

       .mso file
              The same as the so  request  except  that  file  is
              searched  for  in  the  same  way that tmac.name is
              searched for when the -mname option is specified.

so perhaps soelim should know about it, should'nt it? IMHO dealing
with an environment variable is not the same as dealing with a
command line option (-M vs. GROFF_INPUT_PATH).

Nicola

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



From groff-admin  Wed Mar 22 14:17:54 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/GNU) with ESMTP id OAA00606
	for <Groff@ffii.org>; Wed, 22 Mar 2000 14:17:54 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 22 Mar 2000 14:20:32 +0100
Received: from rigel.univie.ac.at (dial-143146.HRZ.Uni-Dortmund.DE [129.217.143.146])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id OAA04488;
	Wed, 22 Mar 2000 14:20:25 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id HAA08621;
	Wed, 22 Mar 2000 07:33:50 GMT
To: nicb@axnet.it
Cc: Groff@ffii.org
Subject: Re: [Groff] soelim outdated
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.4.10.10003220515110.16439-100000@ax-nicb.axnet.it>
References: <20000321073952X.sx0005@sx2.hrz.uni-dortmund.de>
	<Pine.LNX.4.10.10003220515110.16439-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.94 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
Message-Id: <20000322073350Y.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 22 Mar 2000 07:33:50 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 1478
Lines: 38

> > > I sometimes need the ability to include extra bits of text
> > > (which may not be macros) which lie on personal directories
> > > etc. I generally do it with the -M option, and with .mso it
> > > works quite well (*except* for soelim).
> > 
> > Again, I think this is an abuse of .mso, and a GROFF_INPUT_PATH
> > feature should be introduced.
> 
> I'm not sure I understand why it is an abuse (included stuff may
> well be macros after all).

It is an abuse IMHO to use the groff/tmac directory for storing
private files.

> The .mso line in the groff manpage says:
>        .mso file
>               The same as the so  request  except  that  file  is
>               searched  for  in  the  same  way that tmac.name is
>               searched for when the -mname option is specified.
> 
> so perhaps soelim should know about it, should'nt it?

Hmm.  Maybe you are right that some day people write a standard macro
package <foo> which has to be preprocessed with, say, tbl.
Nevertheless, I think it would be better then to store both a
tmac.<foo>-raw file and a preprocessed tmac.<foo>.  How should a user
know that a given macro package has to always be used with a certain
preprocessor?

> IMHO dealing with an environment variable is not the same as dealing
> with a command line option (-M vs. GROFF_INPUT_PATH).

I agree.  So soelim should be handle to read .so files from
GROFF_INPUT_PATH, .mso files from GROFF_TMAC_PATH, and to expand \V
escapes.


    Werner


From groff-admin  Wed Mar 22 17:31:44 2000
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA02732
	for <groff@ffii.org>; Wed, 22 Mar 2000 17:31:43 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA186916;
	Wed, 22 Mar 2000 11:32:09 -0500
Received: from infosys.tuwien.ac.at (ss3.pok.socks.ibm.com [9.14.3.68])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with ESMTP id LAA135906;
	Wed, 22 Mar 2000 11:33:10 -0500
Message-ID: <38D8F5DD.A7EEE1B0@infosys.tuwien.ac.at>
Date: Wed, 22 Mar 2000 11:33:33 -0500
From: =?iso-8859-1?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Werner LEMBERG <wl@gnu.org>
CC: groff@ffii.org
Subject: Re: [Groff] EBCDIC hyphenation in troff on tty
References: <38D79D4D.3B2C2470@infosys.tuwien.ac.at> <20000322000939V.sx0005@sx2.hrz.uni-dortmund.de>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Status: O
Content-Length: 1433
Lines: 31

> > Lost in source!  After converting the font files and making some
> > minor source changes, troff formats man pages quite right under our
> > EBCDIC system.  The only problem is that the '[' (left bracket,
> > ascii 0132 x5B, ebcdic 0255 xAD) is used as a hyphenation character
> > at the end of lines, instead the correct '-' (minus, ascii 0055 x2d,
> > ebcdic 0140 x60).
> 
> What aboud the shc request to set the soft hyphen character (in
> node.cc)?  This defaults to HYPHEN_SYMBOL (which is the glyph `hy').

My problem is that I get this '[' as the default hyphen char, and I
dislike that. Even after editing troff.man and putting '.shc =' it it I
got the first hyphenated line with '[' at the line end (all others had
'=' there). See:

This manual page describes the GNU version of troff, which
       is  part  of  the groff document formatting system.  It is
       highly compatible with Unix troff.  Usually it  should  be
       invoked  using the groff command, which will also run pre[
       processors and postprocessors in the appropriate order and

It seems to me being an initialisation error somewhere in the code but I
am not able to find that place. 

There is in env.cc:  init_request("hc", hyphen_char);  and in 
input.cc:  init_charset_table(); and   init_hyphen_requests(); - they
should work properly. It is for sure an ascii dependency but I do not
understand the code enough deeply, I think.

Sándor


From groff-admin  Wed Mar 22 20:07:35 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/GNU) with ESMTP id UAA03871
	for <groff@ffii.org>; Wed, 22 Mar 2000 20:07:35 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 22 Mar 2000 20:10:27 +0100
Received: from rigel.univie.ac.at (dial-143182.HRZ.Uni-Dortmund.DE [129.217.143.182])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id UAA23765;
	Wed, 22 Mar 2000 20:10:25 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id TAA09376;
	Wed, 22 Mar 2000 19:05:05 GMT
To: S.Barany@infosys.tuwien.ac.at
Cc: groff@ffii.org
Subject: Re: [Groff] EBCDIC hyphenation in troff on tty
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <38D8F5DD.A7EEE1B0@infosys.tuwien.ac.at>
References: <38D79D4D.3B2C2470@infosys.tuwien.ac.at>
	<20000322000939V.sx0005@sx2.hrz.uni-dortmund.de>
	<38D8F5DD.A7EEE1B0@infosys.tuwien.ac.at>
X-Mailer: Mew version 1.94 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
Message-Id: <20000322190505I.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 22 Mar 2000 19:05:05 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 1751
Lines: 43

> > > Lost in source!  After converting the font files and making some
> > > minor source changes, troff formats man pages quite right under our
> > > EBCDIC system.  The only problem is that the '[' (left bracket,
> > > ascii 0132 x5B, ebcdic 0255 xAD) is used as a hyphenation character
> > > at the end of lines, instead the correct '-' (minus, ascii 0055 x2d,
> > > ebcdic 0140 x60).
> > 
> > What aboud the shc request to set the soft hyphen character (in
> > node.cc)?  This defaults to HYPHEN_SYMBOL (which is the glyph `hy').
> 
> My problem is that I get this '[' as the default hyphen char, and I
> dislike that. Even after editing troff.man and putting '.shc =' it it I
> got the first hyphenated line with '[' at the line end (all others had
> '=' there). See:
> 
> This manual page describes the GNU version of troff, which
>        is  part  of  the groff document formatting system.  It is
>        highly compatible with Unix troff.  Usually it  should  be
>        invoked  using the groff command, which will also run pre[
>        processors and postprocessors in the appropriate order and
> 
> It seems to me being an initialisation error somewhere in the code but I
> am not able to find that place. 

First, modify troffrc to add a proper entry for a tmac.ebcdic.

Then modify tmac.tty to test for the ebcdic device and modify it
accordingly; tmac.tty contains the following line:

  .if c\[char173] .shc \[char173]

char 173 is 0xAD ...

The reference to \[char160] should be modified also since this is
certainly not identical to the EBCDIC value.

Similarly, tmac.tty-char must be modified to load a tmac.ebcdic file
instead of tmac.latin1.

Hope that helps.  I can't find any other reference to character 0xAD.


    Werner


From groff-admin  Wed Mar 22 20:25:24 2000
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA05217
	for <groff@ffii.org>; Wed, 22 Mar 2000 20:25:23 +0100
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id OAA201170
	for <groff@ffii.org>; Wed, 22 Mar 2000 14:26:29 -0500
Received: from infosys.tuwien.ac.at (ss3.pok.socks.ibm.com [9.14.3.68])
	by northrelay02.pok.ibm.com (8.8.8m2/NCO v2.06) with ESMTP id OAA97430
	for <groff@ffii.org>; Wed, 22 Mar 2000 14:27:53 -0500
Message-ID: <38D91ED3.C9E5519B@infosys.tuwien.ac.at>
Date: Wed, 22 Mar 2000 14:28:19 -0500
From: =?iso-8859-1?Q?S=E1ndor=20B=E1r=E1ny?= <S.Barany@infosys.tuwien.ac.at>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: groff@ffii.org
Subject: Re: [Groff] EBCDIC hyphenation in troff on tty
References: <38D79D4D.3B2C2470@infosys.tuwien.ac.at>
		<20000322000939V.sx0005@sx2.hrz.uni-dortmund.de>
		<38D8F5DD.A7EEE1B0@infosys.tuwien.ac.at> <20000322190505I.sx0005@sx2.hrz.uni-dortmund.de>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Status: O
Content-Length: 433
Lines: 17

Werner LEMBERG wrote:

> ... tmac.tty contains the following line:
> 
>   .if c\[char173] .shc \[char173]
> 
> char 173 is 0xAD ...
> 
> The reference to \[char160] should be modified also since this is
> certainly not identical to the EBCDIC value.

Yes, I put '.if c\[char173] .shc -' in tmac.tyy and the hyphenation is -
and not [! Great! Where is this documented? And what should I do with
that char160? What is it for?

Sándor


From groff-admin  Wed Mar 22 21:12:32 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id VAA06270
	for <groff@ffii.org>; Wed, 22 Mar 2000 21:12:32 +0100
Received: (qmail 19318 invoked from network); 22 Mar 2000 20:15:33 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 22 Mar 2000 20:15:33 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13593
	for groff@ffii.org; Wed, 22 Mar 2000 22:08:09 +0100
Message-ID: <20000322220809.A13590@mayn.de>
Date: Wed, 22 Mar 2000 22:08:09 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] man-page macro
Status: O
Content-Length: 624
Lines: 28

I propose to add the following macro .MP to both tmac.an and tmac.mm.
It is a convenient way to display a man page entry in the style required 
by man(7).

.\" format: .MP Entry Section [Punctuation...]
.\" Displays Entry in bold, Section in roman enclosed by () and
.\" optionally appends the rest in the starting font.
.de MP
.ds @tmp@ \\fB\\$1\\fP\\fR(\\$2)\\fP
.shift 2
\\*[@tmp@]\\$*
.rm @tmp@
..

Try the following example sentence:

.MP groff 1
and
.MP grog 1
are the front-end binariess, whereas
.MP groff_man 5 ,
.MP groff_mm 5 , and
.MP groff_ms 5
describe common macro packages.


Bernd Warken <bwarken@mayn.de>


From groff-admin  Wed Mar 22 21:13:00 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id VAA06313
	for <groff@ffii.org>; Wed, 22 Mar 2000 21:12:59 +0100
Received: (qmail 19369 invoked from network); 22 Mar 2000 20:16:01 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 22 Mar 2000 20:16:01 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13604
	for groff@ffii.org; Wed, 22 Mar 2000 22:08:37 +0100
Message-ID: <20000322220836.A13602@mayn.de>
Date: Wed, 22 Mar 2000 22:08:36 +0100
From: Bernd Warken <bwarken@mayn.de>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Subject: [Groff] tmac renaming
Status: O
Content-Length: 1698
Lines: 51

The naming of some macro packages is ridiculous, the ones whose first
letter is (or should be) m.  This includes

tmac.an tmac.andoc tmac.arkup tmac.doc tmac.e tmac.s (... ?)
tmac.m tmac.mse

This curious habit originates from very old UNIX days, where option
arguments were required to immediately follow it soption letter without
an intervening space.  So it was funny to write "troff -man" instead of
"troff -mman".

But after having admired the eye-catching beauty of this monster-hack
for some decades I think it's time to put it to some serious end, before
it will go on blossoming to reach unmatched heights such as the
stupendous "tmac.arkup".  (How about "tmac.ess", "tmac.uck",
"tmac.iaow", or "tmac.om"?)

In order to remain compatible, I propose to
1) rename the above mentioned tmacs by inserting the robbed m
2) create symlinks to the old names

Then it will possible to call the man macro package using "-m man",
"-man", "-m an", or "-mman".

The following script does the trick:


 function fix_tmac {
   mv tmac.$1 tmac.m$1                # insert m into tmac name
   eval /bin/ln -s tmac.$1 tmac.m$1   # supply old handling
 }
 cd $GROFF_SOURE/tmac
 for p in an andoc arkup doc e s
   do fix_tmac $p; done
 cd $GROFF_SOURCE/contrib/mm
 for p in m mse
   do fix_tmac $p; done


Hard links or copies could be better for some primitive OSes.  (Please
note that I didn't say "primitive", I just write it down.  If you don't
like the term, replace it by "POSIX-by-bribing-only" or
"not-to-pay-means-jail" ;).

The final step to adjust the makefiles and the doqs is left as an
exercise ;-)

Bernd Warken <bwarken@mayn.de>

Down with the communist establishment - free markets for all!


From groff-admin  Wed Mar 22 21:17:03 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/GNU) with ESMTP id VAA06386
	for <groff@ffii.org>; Wed, 22 Mar 2000 21:17:03 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 22 Mar 2000 21:20:06 +0100
Received: from rigel.univie.ac.at (dial-143164.HRZ.Uni-Dortmund.DE [129.217.143.164])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id VAA25093;
	Wed, 22 Mar 2000 21:20:04 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id UAA09493;
	Wed, 22 Mar 2000 20:15:00 GMT
To: S.Barany@infosys.tuwien.ac.at
Cc: groff@ffii.org
Subject: Re: [Groff] EBCDIC hyphenation in troff on tty
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <38D91ED3.C9E5519B@infosys.tuwien.ac.at>
References: <38D8F5DD.A7EEE1B0@infosys.tuwien.ac.at>
	<20000322190505I.sx0005@sx2.hrz.uni-dortmund.de>
	<38D91ED3.C9E5519B@infosys.tuwien.ac.at>
X-Mailer: Mew version 1.94 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
Message-Id: <20000322201459H.sx0005@sx2.hrz.uni-dortmund.de>
Date: Wed, 22 Mar 2000 20:14:59 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 776
Lines: 26

> > ... tmac.tty contains the following line:
> > 
> >   .if c\[char173] .shc \[char173]
> > 
> > char 173 is 0xAD ...
> > 
> > The reference to \[char160] should be modified also since this is
> > certainly not identical to the EBCDIC value.
> 
> Yes, I put '.if c\[char173] .shc -' in tmac.tyy and the hyphenation
> is - and not [!  Great!  Where is this documented?

Nowhere.  All tmac.XXX files are badly documented :-( Usually, users
don't have to care at all, only developers who add another
devices/charsets/encodings to groff.

> And what should I do with
> that char160? What is it for?

This maps char160 (a non-breakable space) to the space character --
hmm, I don't know whether that is really the right decision.  I would
rather use `\~' instead...


    Werner


From groff-admin  Thu Mar 23 09:22:18 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/GNU) with ESMTP id JAA23945
	for <groff@ffii.org>; Thu, 23 Mar 2000 09:22:18 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 23 Mar 2000 09:25:21 +0100
Received: from rigel.univie.ac.at (dial-143195.HRZ.Uni-Dortmund.DE [129.217.143.195])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id JAA18031;
	Thu, 23 Mar 2000 09:25:19 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id IAA10507;
	Thu, 23 Mar 2000 08:14:32 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] man-page macro
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000322220809.A13590@mayn.de>
References: <20000322220809.A13590@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000323081432A.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 23 Mar 2000 08:14:32 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 906
Lines: 27

> I propose to add the following macro .MP to both tmac.an and
> tmac.mm.  It is a convenient way to display a man page entry in the
> style required by man(7).

Your macro looks nice!  But I really hesitate to include it into the
`official' tmac.an file.  A lot of people who write programs for Unix
need to create man pages which run on all Unix flavours.  And in such
a situation you can't use `.MP'.

It is the same as with the extensions of gcc.  As usable as they are,
most people don't dare to use it since such source files won't compile
with other compilers.

This means that your macro will be used commonly only for manual pages
specific to GNU systems like Linux or FreeBSD.  But then it is easy to
add, say, a line

  .mso tmac.ext

at the beginning of the man page which loads extensions and useful
additions to various macro packages (not only related to man).

Please comment.


   Werner


From groff-admin  Thu Mar 23 09:22:18 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/GNU) with ESMTP id JAA23943
	for <groff@ffii.org>; Thu, 23 Mar 2000 09:22:17 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 23 Mar 2000 09:25:19 +0100
Received: from rigel.univie.ac.at (dial-143195.HRZ.Uni-Dortmund.DE [129.217.143.195])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id JAA18028;
	Thu, 23 Mar 2000 09:25:17 +0100 (MET)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id IAA10519;
	Thu, 23 Mar 2000 08:19:54 GMT
To: bwarken@mayn.de
Cc: groff@ffii.org
Subject: Re: [Groff] tmac renaming
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000322220836.A13602@mayn.de>
References: <20000322220836.A13602@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000323081954F.sx0005@sx2.hrz.uni-dortmund.de>
Date: Thu, 23 Mar 2000 08:19:54 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 441
Lines: 19

[about tmac.an vs. tmac.man]

> In order to remain compatible, I propose to
> 1) rename the above mentioned tmacs by inserting the robbed m
> 2) create symlinks to the old names
> 
> Then it will possible to call the man macro package using "-m man",
> "-man", "-m an", or "-mman".

I believe a better solution is to simply add a file tmac.man which
contains

  .do mso tmac.an

and similar files for the other macro packages.


    Werner


From groff-admin  Thu Mar 23 10:14:34 2000
Received: from atlantis.erlm.siemens.de (atlantis.erlm.siemens.de [212.114.202.14])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id KAA24409
	for <groff@ffii.org>; Thu, 23 Mar 2000 10:14:33 +0100
Received: from tcenter.erlm.siemens.de (tcenter.erlm.siemens.de [193.98.99.20])
	by atlantis.erlm.siemens.de (8.9.3/8.9.3) with ESMTP id KAA22933;
	Thu, 23 Mar 2000 10:12:58 +0100 (MET)
Received: from nbgv101a.nbg9.siemens.de (nbgv101a.nbg9.siemens.de [130.170.148.248])
	by tcenter.erlm.siemens.de (8.9.0/8.9.0) with ESMTP id KAA08770;
	Thu, 23 Mar 2000 10:06:50 +0100 (MET)
Received: by NBGV101A with Internet Mail Service (5.5.2650.21)
	id <HM603ZCV>; Thu, 23 Mar 2000 10:14:34 +0100
Message-ID: <11DD9734B036D311947400805F0DD60703642C@NBGV101A>
From: Freudenberger Joerg <Joerg.Freudenberger@nbg9.siemens.de>
To: "'Bernd Warken'" <bwarken@mayn.de>, groff@ffii.org
Subject: RE: [Groff] man-page macro
Date: Thu, 23 Mar 2000 10:14:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id KAA24410
Status: O
Content-Length: 574
Lines: 25

As local conception this would be a fine idea.
But the hole set of groff external programs, I know, using 
.BR to generate a logic link.

   Reference to public available
	man-page as hyper-text viewers: tkman, tkman8
	man-page to html converters: man2html, rosetta-man

Your example sentence would fit to :

.BR groff (1)
and
.BR grog (1)
are the front-end binariess, whereas
.BR groff_man (5),
.BR groff_mm (5),
and
.BR groff_ms (5)
describe common macro packages.

I think the .BR Notation derives from the older 4.xBSD world or
from the real original ManPages.

	Jörg 


From groff-admin  Thu Mar 23 11:07:28 2000
Received: from cmailg3.svr.pol.co.uk (cmailg3.svr.pol.co.uk [195.92.195.173])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA24755
	for <groff@ffii.org>; Thu, 23 Mar 2000 11:07:27 +0100
Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk)
	by cmailg3.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 12Y4ZW-0003BP-00
	for groff@ffii.org; Thu, 23 Mar 2000 10:10:34 +0000
Received: from modem-151.green-mandarin.dialup.pol.co.uk ([62.137.23.151] helo=merlin.freeserve.net)
	by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 12Y4ZR-0006tQ-00
	for groff@ffii.org; Thu, 23 Mar 2000 10:10:29 +0000
Received: by merlin.freeserve.net (Linux Smail3.2.0.101 #1)
	id m12Y5dn-000ivaC; Thu, 23 Mar 2000 11:19:03 +0000 (GMT)
Message-Id: <m12Y5dn-000ivaC@merlin.freeserve.net>
Date: Thu, 23 Mar 2000 11:19:03 +0000 (GMT)
From: Gaius Mulley <gaius@glam.ac.uk>
To: bwarken@mayn.de
CC: groff@ffii.org
In-reply-to: <20000322220836.A13602@mayn.de> (message from Bernd Warken on
	Wed, 22 Mar 2000 22:08:36 +0100)
Subject: Re: [Groff] tmac renaming
References:  <20000322220836.A13602@mayn.de>
Status: O
Content-Length: 719
Lines: 23

> But after having admired the eye-catching beauty of this monster-hack
> for some decades I think it's time to put it to some serious end, before
> it will go on blossoming to reach unmatched heights such as the
> stupendous "tmac.arkup".  (How about "tmac.ess", "tmac.uck",
> "tmac.iaow", or "tmac.om"?)

:-) on

how about tmac.other - for the macro of all macros? Which could include
all other non conflicting macros?

and tmac.icrosoft - when -Tms97 device driver has been written.

and tmac.odern - for the -Tpdf related macros.

:-) off

seriously though if tmac.arkup offends, should we rename it
tmac.www perhaps? Since it is alpha I suppose we could rename
it relatively easily? Any other suggestions?

Gaius


From groff-admin  Thu Mar 23 18:57:02 2000
Received: from ns1.greenbush.com (mngovsci@ns1.greenbush.com [209.90.218.2])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA30272
	for <groff@ffii.org>; Thu, 23 Mar 2000 18:57:01 +0100
Received: from localhost (mngovsci@localhost)
	by ns1.greenbush.com (8.9.3/8.8.7) with SMTP id MAA30918;
	Thu, 23 Mar 2000 12:59:54 -0500
Date: Thu, 23 Mar 2000 12:59:54 -0500 (EST)
From: Eddie Maddox <eddie@mngovsci.com>
X-Sender: mngovsci@ns1.greenbush.com
To: Gaius Mulley <gaius@glam.ac.uk>
cc: bwarken@mayn.de, groff@ffii.org
Subject: Re: [Groff] tmac renaming
In-Reply-To: <m12Y5dn-000ivaC@merlin.freeserve.net>
Message-ID: <Pine.LNX.3.96.1000323125049.30863A-100000@ns1.greenbush.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 453
Lines: 16

On Thu, 23 Mar 2000, Gaius Mulley wrote:

> seriously though if tmac.arkup offends, should we rename it
> tmac.www perhaps? Since it is alpha I suppose we could rename
       ^^^

I was using this for a new macro package I was playing with, but, I
decided that package was a dead end and have therefor discontinued work on
it. So, feel free to use the "www" name as I won't be using it after all. 

------------------
Eddie Maddox
eddie@mngovsci.com




From groff-admin  Thu Mar 23 22:17:34 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id WAA31613
	for <Groff@ffii.org>; Thu, 23 Mar 2000 22:17:34 +0100
Received: (qmail 9085 invoked from network); 23 Mar 2000 21:20:41 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 23 Mar 2000 21:20:41 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13884
	for Groff@ffii.org; Thu, 23 Mar 2000 22:20:41 +0100
Message-ID: <20000323222041.A13762@mayn.de>
Date: Thu, 23 Mar 2000 22:20:41 +0100
From: Bernd Warken <bwarken@mayn.de>
To: Groff@ffii.org
Subject: Re: [Groff] tmac renaming
References: <m12Y5dn-000ivaC@merlin.freeserve.net> <Pine.LNX.3.96.1000323125049.30863A-100000@ns1.greenbush.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <Pine.LNX.3.96.1000323125049.30863A-100000@ns1.greenbush.com>; from Eddie Maddox on Thu, Mar 23, 2000 at 12:59:54PM -0500
Status: O
Content-Length: 605
Lines: 17

On Thu, Mar 23, 2000 at 12:59:54PM -0500, Eddie Maddox wrote:
> On Thu, 23 Mar 2000, Gaius Mulley wrote:
> 
> > seriously though if tmac.arkup offends, should we rename it
> > tmac.www perhaps? Since it is alpha I suppose we could rename
>        ^^^
> 
> I was using this for a new macro package I was playing with, but, I
> decided that package was a dead end and have therefor discontinued work on
> it. So, feel free to use the "www" name as I won't be using it after all. 
> 
How about "html"?  I expect many other markups to follow in the future
(DocBook, XML,...)

Bernd Warken <bwarken@mayn.de>



From groff-admin  Thu Mar 23 22:24:02 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/GNU) with ESMTP id WAA31681
	for <groff@ffii.org>; Thu, 23 Mar 2000 22:24:00 +0100
From: dominios@pplmail.com
Received: from tug.org (IDENT:root@tug.org [158.121.106.10])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id QAA10237
	for <groff@gnu.org>; Thu, 23 Mar 2000 16:27:03 -0500
Received: from pinos.com ([200.10.106.2])
	by tug.org (8.9.3/8.9.3) with SMTP id QAA23964
	for <groff@gnu.org>; Thu, 23 Mar 2000 16:26:59 -0500
Date: Thu, 23 Mar 2000 16:26:59 -0500
Message-Id: <200003232126.QAA23964@tug.org>
X-ROUTED: Thu, 23 Mar 2000 18:31:38 -0300
Received: from  [193.153.11.94] by pinos.com with smtp
	id 122a39d8 ; Thu, 23 Mar 2000 18:24:58 -0300
To: groff@gnu.org
Subject: [Groff] PROTEJA SU NOMBRE/PROTECTING YOUR
Status: O
Content-Length: 1580
Lines: 33

Proteja su nombre en Internet. Registre su dominio. Oferta imbatible:
Message-ID: <TCPSMTP_GEN.18169.7869@pinos.com>

                                          50$ dos ańos
                                       .COM.NET.ORG

visite: http://way.to/dominios/

Buena oferta de hospedaje en servidor virtual
                                                -------------------------------------
COLABORE CON NUESTRA POLITICA DE PRIVACIDAD. SI NO QUIERE RECIBIR MAS MENSAJES DESDE ESTA DIRECCION ENVIE UN EMAIL A:
<mailto:registrobaja@eudoramail.com?subject=revomelistadistribucion>
Y SERA DADO DE BAJA INMEDIATAMENTE. COLABORE CON NOSOTROS, NO PRESIONE
A LOS SERVIDORES Y PROVEEDORES, ASI TODO EL MUNDO QUE LO DESEE PODRA 
DARSE DE BAJA DE LA LISTA
---------------------------------------------------------------------------------------------------------------------------------------------
Protecting your name in the Internet. Register your Domain. Great Offer

                                          50 $$ Two years
                                        .COM.NET.ORG

visit: http://go.tagoror.com/domreg

Hosting (4$ moth)
                                                          -------------------------------------
COLLABORATE WITH OUR PRIVACY POLICY. IF it DOES NOT WANT TO RECEIVE BUT MESSAGES SINCE THIS DIRECCION SEND AN EMAIL TO:
<mailto:registrobaja@eudoramail.com?subject=revomelistadistribucion>
And TO BE DROPPED IMMEDIATELY. COLLABORATE WITH US, NOT PRESSING TO THE SERVERS  AND PROVIDERS, IN THIS WAY EVERYONE THAT DESIRE IT TO BE ABLE TO DROP OF THE LIST






From groff-admin  Thu Mar 23 22:24:57 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id WAA31726
	for <Groff@ffii.org>; Thu, 23 Mar 2000 22:24:57 +0100
Received: (qmail 9535 invoked from network); 23 Mar 2000 21:28:06 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 23 Mar 2000 21:28:06 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13918
	for Groff@ffii.org; Thu, 23 Mar 2000 22:28:01 +0100
Message-ID: <20000323222801.B13762@mayn.de>
Date: Thu, 23 Mar 2000 22:28:01 +0100
From: Bernd Warken <bwarken@mayn.de>
To: Groff@ffii.org
Subject: Re: [Groff] man-page macro
References: <20000322220809.A13590@mayn.de> <20000323081432A.sx0005@sx2.hrz.uni-dortmund.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <20000323081432A.sx0005@sx2.hrz.uni-dortmund.de>; from Werner LEMBERG on Thu, Mar 23, 2000 at 08:14:32AM +0000
Status: O
Content-Length: 807
Lines: 24

On Thu, Mar 23, 2000 at 08:14:32AM +0000, Werner LEMBERG wrote:
> 
> > I propose to add the following macro .MP to both tmac.an and
> > tmac.mm.  It is a convenient way to display a man page entry in the
> > style required by man(7).
> 
> This means that your macro will be used commonly only for manual pages
> specific to GNU systems like Linux or FreeBSD.  But then it is easy to
> add, say, a line
> 
>   .mso tmac.ext
> 
> at the beginning of the man page which loads extensions and useful
> additions to various macro packages (not only related to man).
> 
This approach makes sense, tho the name tmac.ext seems too general.
One is limited to troff requests.

One could define an extension file for each macro package, e.g.
tmac.<package>ext.  Or a general tmac.gnu.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Thu Mar 23 22:28:49 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id WAA31795
	for <Groff@ffii.org>; Thu, 23 Mar 2000 22:28:49 +0100
Received: (qmail 9770 invoked from network); 23 Mar 2000 21:31:57 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 23 Mar 2000 21:31:57 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13974
	for Groff@ffii.org; Thu, 23 Mar 2000 22:31:57 +0100
Message-ID: <20000323223157.C13762@mayn.de>
Date: Thu, 23 Mar 2000 22:31:57 +0100
From: Bernd Warken <bwarken@mayn.de>
To: Groff@ffii.org
Subject: Re: [Groff] man-page macro
References: <11DD9734B036D311947400805F0DD60703642C@NBGV101A>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <11DD9734B036D311947400805F0DD60703642C@NBGV101A>; from Freudenberger Joerg on Thu, Mar 23, 2000 at 10:14:32AM +0100
Status: O
Content-Length: 474
Lines: 13

On Thu, Mar 23, 2000 at 10:14:32AM +0100, Freudenberger Joerg wrote:
> As local conception this would be a fine idea.
> But the hole set of groff external programs, I know, using 
> .BR to generate a logic link.
> 
.BR can only handle 2 fonts, but there are situations where 3 are 
required.  Moreover one can easily modify the macro to add additional
information like the @MAN<n>EXT@ element in the groff sources.

Otherwise you are right.

Bernd Warken <bwarken@mayn.de>


From groff-admin  Thu Mar 23 22:32:06 2000
Received: from mayn.de (qmailr@airbus.mayn.de [194.145.150.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id WAA31852
	for <Groff@ffii.org>; Thu, 23 Mar 2000 22:32:06 +0100
Received: (qmail 10072 invoked from network); 23 Mar 2000 21:35:15 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 23 Mar 2000 21:35:15 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id WAA13988
	for Groff@ffii.org; Thu, 23 Mar 2000 22:35:00 +0100
Message-ID: <20000323223459.D13762@mayn.de>
Date: Thu, 23 Mar 2000 22:34:59 +0100
From: Bernd Warken <bwarken@mayn.de>
To: Groff@ffii.org
Subject: Re: [Groff] tmac renaming
References: <20000322220836.A13602@mayn.de> <20000323081954F.sx0005@sx2.hrz.uni-dortmund.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <20000323081954F.sx0005@sx2.hrz.uni-dortmund.de>; from Werner LEMBERG on Thu, Mar 23, 2000 at 08:19:54AM +0000
Status: O
Content-Length: 324
Lines: 15

On Thu, Mar 23, 2000 at 08:19:54AM +0000, Werner LEMBERG wrote:
> 
> [about tmac.an vs. tmac.man]
> 
> I believe a better solution is to simply add a file tmac.man which
> contains
> 
>   .do mso tmac.an
> 
> and similar files for the other macro packages.
> 
Great - that's the roff way :)

Bernd Warken >bwarken@mayn.de>


From groff-admin  Fri Mar 24 08:01:59 2000
Received: from scapa.cs.ualberta.ca (root@scapa.cs.ualberta.ca [129.128.4.44])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id IAA16014
	for <groff@ffii.org>; Fri, 24 Mar 2000 08:01:55 +0100
Received: (from localhost user: 'wgshi' uid#462 fake: stauffer.cs.ualberta.ca)
	by scapa.cs.ualberta.ca id <S435467AbQCXGMi>;
	Thu, 23 Mar 2000 23:12:38 -0700
Date:   Thu, 23 Mar 2000 23:12:38 -0700 (MST)
Sender: Weiguang Shi <wgshi@cs.ualberta.ca>
From: Weiguang Shi <wgshi@cs.ualberta.ca>
To: groff@ffii.org
Message-ID: <Pine.SOL.3.96.1000323230937.6433A-100000@stauffer.cs.ualberta.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] a question on text orientation in groff
Status: O
Content-Length: 497
Lines: 15

Hi, there:
    I am wondering if I can achieve the effect of slides created using MS
PowerPoint. Specifically, I want the lines laid out on an A4 page
vertically. Could you help me please?
    Thanks very much.

Weiguang

Weiguang Shi                              | E-mail: wgshi@cs.ualberta.ca
Department of Computing Science           | http://www.cs.ualberta.ca/~wgshi
University of Alberta                     | Office: CAB 481
Edmonton, AB, Canada, T6G 2H1             | (O) (780)492-3927




From groff-admin  Fri Mar 24 12:55:16 2000
Received: from ns1.greenbush.com (mngovsci@ns1.greenbush.com [209.90.218.2])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id MAA18076
	for <Groff@ffii.org>; Fri, 24 Mar 2000 12:55:15 +0100
Received: from localhost (mngovsci@localhost)
	by ns1.greenbush.com (8.9.3/8.8.7) with SMTP id GAA00732;
	Fri, 24 Mar 2000 06:58:13 -0500
Date: Fri, 24 Mar 2000 06:58:13 -0500 (EST)
From: Eddie Maddox <eddie@mngovsci.com>
X-Sender: mngovsci@ns1.greenbush.com
To: Bernd Warken <bwarken@mayn.de>
cc: Groff@ffii.org
Subject: Re: [Groff] tmac renaming
In-Reply-To: <20000323222041.A13762@mayn.de>
Message-ID: <Pine.LNX.3.96.1000324054849.331B-100000@ns1.greenbush.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 2373
Lines: 58

On Thu, 23 Mar 2000, Bernd Warken wrote:

> On Thu, Mar 23, 2000 at 12:59:54PM -0500, Eddie Maddox wrote:
> > On Thu, 23 Mar 2000, Gaius Mulley wrote:
> > 
> > > seriously though if tmac.arkup offends, should we rename it
> > > tmac.www perhaps? Since it is alpha I suppose we could rename
> >        ^^^
> > 
> > I was using this for a new macro package I was playing with, but, I
> > decided that package was a dead end and have therefor discontinued work on
> > it. So, feel free to use the "www" name as I won't be using it after all. 
> > 
> How about "html"?  I expect many other markups to follow in the future
> (DocBook, XML,...)

Which is _precisely_ why I saw my 'www package as a dead end. Everything
was working fine, as far as I got with it. So, who was going to slave over
the hundreds of elements, values, logic idiosyncrasies for years and years
for a never ending stream of DTDs? Not me.

Good luck. For me, it's Zope and Mozilla. (Netscape 6.0Beta within a
month, they say.) Let them do the work. If their software makes me rich
some day, or at least pays off my house, I'ld be happy to send them a
check or two, too, to say thanks.

Unless I miss something here, I fail to see how Groff makes sense for new
work, given newer tools as well or better suited, and with bodies behind
them.

Never-the-less, if there is deep, lasting value in Groff for the WWW may I
suggest you check out the DTML for Zope.  It appears to do for Zope what
tmac.arkup does for Groff, in a way. Might give you some ideas. 

zope.org 

Note: I am not a real developer, so the above remarks may be biased
against me having to do any real work. And we all know that we don't get
what we don't work, or pay, for... 

I am going to be exploring using Mozilla, Zope, and related things for the
Groff Web pages. This would allow "trusted others" to submit Web content,
links, etc, to our Web pages similar to how CVS works, complete with
"versioning". Having Ted, Werner, etc. posting stuff, and reviewing
submissions by others, stuff like that. Web interfaces.

Imagine all the contributed examples and complete "solutions" our Groff
Web sites could be hosting. Supplementing the materials included in the
Groff releases. Practice and demo areas. Translation stations for
multilanguage support. Tutorial workshops.

Stay tuned.

------------------
Eddie Maddox
eddie@mngovsci.com



From groff-admin  Sun Mar 26 01:05:15 2000
Received: from datenbus.mayn.de (root@datenbus.mayn.de [194.145.150.20])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA22669
	for <Groff@ffii.org>; Sun, 26 Mar 2000 01:05:15 +0100
Received: (from bwarken@localhost)
	by datenbus.mayn.de (8.9.3/8.9.3) id BAA24510
	for Groff@ffii.org; Sun, 26 Mar 2000 01:09:11 +0100
Date: Sun, 26 Mar 2000 01:09:10 +0100
From: Bernd Warken <bwarken@mayn.de>
To: Groff@ffii.org
Message-ID: <20000326010910.A24507@mayn.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Subject: [Groff] split troff(1)
Status: O
Content-Length: 321
Lines: 11

The troff(1) man page contains a mixture of command and language doq.
This should be split into separate man pages.

It's quite easy to, just move all of the USAGE language stuff to a man
page of its own, add a header and some SEE ALSO stuff.

The new man page might be called groff(5).

Bernd Warken <bwarken@mayn.de>



From groff-admin  Sun Mar 26 13:07:43 2000
Received: from unet.univie.ac.at (unet.univie.ac.at [131.130.230.7])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id NAA24563
	for <Groff@ffii.org>; Sun, 26 Mar 2000 13:07:43 +0200
Received: from rigel.univie.ac.at (root@unet3-221.univie.ac.at [131.130.232.221])
	by unet.univie.ac.at (8.9.3/8.9.3) with ESMTP id NAA99824;
	Sun, 26 Mar 2000 13:11:08 +0200
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA00661;
	Sun, 26 Mar 2000 10:23:24 GMT
To: bwarken@mayn.de
Cc: Groff@ffii.org
Subject: Re: [Groff] split troff(1)
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <20000326010910.A24507@mayn.de>
References: <20000326010910.A24507@mayn.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000326102323P.sx0005@sx2.hrz.uni-dortmund.de>
Date: Sun, 26 Mar 2000 10:23:23 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 607
Lines: 18

> The troff(1) man page contains a mixture of command and language doq.
> This should be split into separate man pages.

The troff man page is a mess anyway since it is incomplete.

> It's quite easy to, just move all of the USAGE language stuff to a
> man page of its own, add a header and some SEE ALSO stuff.

I don't think that this helps -- after finishing groff.texinfo, I will
add a sentence to troff(1) like

  Please refer to the authoritative Texinfo documentation of groff for
  a complete survey of groff's capabilitities.

Maybe a volunteer then writes a new troff(1) man page...


    Werner


From groff-admin  Mon Mar 27 11:13:19 2000
Received: from unet.univie.ac.at (unet.univie.ac.at [131.130.230.7])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA15801
	for <groff@ffii.org>; Mon, 27 Mar 2000 11:13:18 +0200
Received: from rigel.univie.ac.at (root@unet3-155.univie.ac.at [131.130.232.155])
	by unet.univie.ac.at (8.9.3/8.9.3) with ESMTP id LAA135150;
	Mon, 27 Mar 2000 11:03:19 +0200
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id IAA02054;
	Mon, 27 Mar 2000 08:56:50 GMT
To: auc-tex@sunsite.auc.dk, Arndt.Prinz@ifs-gmbh.de, Andries.Brouwer@cwi.nl,
        bug-texinfo@gnu.org, bwarken@mayn.de, devel@freetype.org,
        david.turner@freetype.org, eddie@mngovsci.com, ftp-upload@gnu.org,
        faber@lunabase.org, groff@ffii.org, gaius@glam.ac.uk,
        himi@bird.scphys.kyoto-u.ac.jp, handa@etl.go.jp, just@letterror.com,
        mule@m17n.org, opentype@list.sirius.com, robert.wilhelm@freetype.org,
        S.Barany@infosys.tuwien.ac.at, ted.harding@nessie.mcc.ac.uk,
        vvv@vvv.vsu.ru
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
X-Mailer: Mew version 1.94 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
Message-Id: <20000327085650G.sx0005@sx2.hrz.uni-dortmund.de>
Date: Mon, 27 Mar 2000 08:56:50 GMT
X-Dispatcher: imput version 990905(IM130)
Subject: [Groff] mail problems
Status: O
Content-Length: 302
Lines: 14

Dear friends,


due to some braindead actions (by creating an endless loop in
forwarding mail) I've probably lost my mail from the last 48 hours.
In case you've sent something to me, please do it again.

Sorry if you receive this message more than once.

Thank you for your cooperation!


    Werner



From groff-admin  Tue Mar 28 01:02:45 2000
Received: from photon.unm.edu (photon.unm.edu [129.24.163.222])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA21175
	for <groff@ffii.org>; Tue, 28 Mar 2000 01:02:44 +0200
Received: from localhost (jude@localhost)
	by photon.unm.edu (8.9.3/8.9.3) with ESMTP id QAA29417
	for <groff@ffii.org>; Mon, 27 Mar 2000 16:07:51 -0700
Date: Mon, 27 Mar 2000 16:07:51 -0700 (MST)
From: Jude Gabaldon <jude@photon.unm.edu>
To: groff@ffii.org
Message-ID: <Pine.LNX.4.10.10003271544580.29393-100000@photon.unm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] This should be an easy qyestion to answer.
Status: O
Content-Length: 1148
Lines: 48

Hello, I am new to the group so excuse me if this had been covered in
detail.

I can't for the life of me figure out how to get a postscript image into
my ps output from groff.
This is a snip from the file I am using.
snipB
.nr HM 1.0i
.nr FM 0.5i
.nr LL 7.0i
.nr PO 0.5i
.ds CH
.ll 7.5i
.po 0.5i
.pl 11.0i

.fp 4 C
.fp 5 CB
.nr PS 11
.PSPIC logo11.epsi
snip.
If have tried the file as .ps .eps .epsi.  I can view all the extensions
with gs and ghostview, and they showup in the proper place and the proper
size.  But when added to the file they are left out.

I have tried processing the file with.

groff -t -ms
groff -t -ms -Tps
groff -t -p  -pm

I have version 1.14 on solaris.

When I try to process the picture with grops I get.
grops:logo11.epsi:fata error: the first command must be `x T'
I don't know how to interpret this.  Do I have to hand edit the epsi file
to include "x T" in the first line?

Any help will be greatly appreciated.  And links to any web sites that
explain this in detail will also be greatly appreciated.

Jude Gabaldon

P.S. I did search the mail archives and I did not see anything regarding
postscript figures.




From groff-admin  Tue Mar 28 07:15:14 2000
Received: from photon.unm.edu (photon.unm.edu [129.24.163.222])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id HAA03923
	for <groff@ffii.org>; Tue, 28 Mar 2000 07:15:13 +0200
Received: from localhost (jude@localhost)
	by photon.unm.edu (8.9.3/8.9.3) with ESMTP id WAA30059
	for <groff@ffii.org>; Mon, 27 Mar 2000 22:20:20 -0700
Date: Mon, 27 Mar 2000 22:20:20 -0700 (MST)
From: Jude Gabaldon <jude@photon.unm.edu>
To: groff@ffii.org
Message-ID: <Pine.LNX.4.10.10003272219380.30055-100000@photon.unm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] Found the Problem
Status: O
Content-Length: 65
Lines: 6

The groff package we have on the solaris box is broken.

Jude




From groff-admin  Tue Mar 28 11:20:23 2000
Received: from unet.univie.ac.at (unet.univie.ac.at [131.130.230.7])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA05409
	for <groff@ffii.org>; Tue, 28 Mar 2000 11:20:22 +0200
Received: from rigel.univie.ac.at (root@uvo1-89.univie.ac.at [131.130.231.89])
	by unet.univie.ac.at (8.9.3/8.9.3) with ESMTP id LAA139884;
	Tue, 28 Mar 2000 11:24:00 +0200
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id HAA03676;
	Tue, 28 Mar 2000 07:50:38 GMT
To: jude@photon.unm.edu
Cc: groff@ffii.org
Subject: Re: [Groff] This should be an easy qyestion to answer.
From: Werner LEMBERG <sx0005@sx2.hrz.uni-dortmund.de>
In-Reply-To: <Pine.LNX.4.10.10003271544580.29393-100000@photon.unm.edu>
References: <Pine.LNX.4.10.10003271544580.29393-100000@photon.unm.edu>
X-Mailer: Mew version 1.94 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
Message-Id: <20000328075038B.sx0005@sx2.hrz.uni-dortmund.de>
Date: Tue, 28 Mar 2000 07:50:38 GMT
X-Dispatcher: imput version 990905(IM130)
Status: O
Content-Length: 310
Lines: 13

> I have version 1.14 on solaris.

Ask your maintainer to install the latest snapshot from

  ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz

This is a pre-1.16 release basically with no more radical changes in
the code (well, long option names and support for grap will be added
soon).


    Werner


From groff-admin  Thu Mar 30 13:44:48 2000
Received: from sound.scc.net (eddiem@sound.scc.net [199.199.195.35])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id NAA24303
	for <groff@ffii.org>; Thu, 30 Mar 2000 13:44:47 +0200
Received: from localhost (eddiem@localhost)
	by sound.scc.net (8.9.3/8.9.3) with SMTP id FAA12890
	for <groff@ffii.org>; Thu, 30 Mar 2000 05:47:26 -0600
Date: Thu, 30 Mar 2000 05:47:25 -0600 (CST)
From: Eddie Maddox <eddiem@mngovsci.com>
X-Sender: eddiem@sound.scc.net
To: groff@ffii.org
In-Reply-To: <20000328075038B.sx0005@sx2.hrz.uni-dortmund.de>
Message-ID: <Pine.LNX.4.02.10003300520530.12005-100000@sound.scc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] SourceForge.net?
Status: O
Content-Length: 835
Lines: 25

On Tue, 28 Mar 2000, Werner LEMBERG wrote:

> This is a pre-1.16 release basically with no more radical changes in

Any idea when to plan for the next release?

Concerning our Web sites: has anyone here checked out SourceForge.net?
I've registered myself there and things look promising. I need to play
with it more to get the real feel of it, though.

One attractive feature is the ease of having different people working on
different parts of a project's docs and Web site. Project/Team
coordination/collaboration.

Werner/Ted, would you wish to establish a GNU Troff (Groff) project on
SourceForge.net? Primarily for collecting and working on some of the
docs/training materials and building/maintaining our Web sites? Later, if
desired, the CVS can be transfered, too.

Thanks.
------------------
Eddie Maddox
eddie@mngovsci.com



From groff-admin  Thu Mar 30 15:04:54 2000
Received: from unet.univie.ac.at (unet.univie.ac.at [131.130.230.7])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA24862
	for <groff@ffii.org>; Thu, 30 Mar 2000 15:04:54 +0200
Received: from localhost (a7971428@localhost)
	by unet.univie.ac.at (8.9.3/8.9.3) with SMTP id PAA14782
	for <groff@ffii.org>; Thu, 30 Mar 2000 15:08:46 +0200
Date: Thu, 30 Mar 2000 15:08:46 +0200 (MSZ)
From: Werner LEMBERG <a7971428@unet.univie.ac.at>
To: groff@ffii.org
Subject: Re: [Groff] SourceForge.net?
In-Reply-To: <Pine.LNX.4.02.10003300520530.12005-100000@sound.scc.net>
Message-ID: <Pine.A41.3.96.1000330150725.210154D-100000@unet.univie.ac.at>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 415
Lines: 17


> > This is a pre-1.16 release basically with no more radical changes in
> 
> Any idea when to plan for the next release?

In April.

> Werner/Ted, would you wish to establish a GNU Troff (Groff) project on
> SourceForge.net? Primarily for collecting and working on some of the
> docs/training materials and building/maintaining our Web sites?

Sorry, I don't have time for that in the near future.


    Werner



From groff-admin  Thu Mar 30 16:27:17 2000
Received: from sound.scc.net (eddiem@sound.scc.net [199.199.195.35])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA25392
	for <groff@ffii.org>; Thu, 30 Mar 2000 16:27:15 +0200
Received: from localhost (eddiem@localhost)
	by sound.scc.net (8.9.3/8.9.3) with SMTP id IAA21900;
	Thu, 30 Mar 2000 08:29:51 -0600
Date: Thu, 30 Mar 2000 08:29:50 -0600 (CST)
From: Eddie Maddox <eddiem@mngovsci.com>
X-Sender: eddiem@sound.scc.net
To: Werner LEMBERG <a7971428@unet.univie.ac.at>
cc: groff@ffii.org
Subject: Re: [Groff] SourceForge.net?
In-Reply-To: <Pine.A41.3.96.1000330150725.210154D-100000@unet.univie.ac.at>
Message-ID: <Pine.LNX.4.02.10003300817210.12005-100000@sound.scc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 767
Lines: 26

On Thu, 30 Mar 2000, Werner LEMBERG wrote:

> > Werner/Ted, would you wish to establish a GNU Troff (Groff) project on
> > SourceForge.net? Primarily for collecting and working on some of the
> > docs/training materials and building/maintaining our Web sites?
> 
> Sorry, I don't have time for that in the near future.
> 
> 
>     Werner

Ted?

Otherwise, Werner, should I just start it myself and those who wish can
join in? It should at least make things easier for us to pull things
together for a more comprehensive Web site.

Does anyone on this list have experience with SourceForge.net? Can you
share comments and ideas on whether and how it can be helpful for Groff
Web site development and maintainance?

------------------
Eddie Maddox
eddie@mngovsci.com



