From groff-admin  Thu Nov  2 08:51:10 2000
Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA06052
	for <groff@ffii.org>; Thu, 2 Nov 2000 08:51:08 +0100
X-Authentication-Warning: genba.ffii.org: Host mail-a.bezeqint.net [192.115.106.23] claimed to be mail.bezeqint.net
Received: from rakefet (bzq-144-119.bezeqint.net)
 by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
 with ESMTP id <0G3E00C6M0LEF3@mail.bezeqint.net> for groff@ffii.org; Thu,
 2 Nov 2000 09:53:39 +0200 (IST)
Received: from shaul by rakefet with local (Exim 3.16 #1 (Debian))
 id 13rFEL-0001c9-00; Thu, 02 Nov 2000 09:56:13 +0200
Date: Thu, 02 Nov 2000 09:56:13 +0200
From: Shaul Karl <shaulka@bezeqint.net>
To: 75990@bugs.debian.org, debian-i18n@lists.debian.org, groff@ffii.org
Message-id: <E13rFEL-0001c9-00@rakefet>
Subject: [Groff] groff options /tmp/ll does not work any more?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 347
Lines: 10

	Hello,
I do not know if this is only on my unstable Debian machine but
	groff -te -Tlatin1 -mandoc /tmp/ll -
no longer work. I am getting an empty string instead.
Am I missing something? Is there a work around?

[09:55:09 /tmp]$ zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc /tmp/ll -
[09:55:16 /tmp]$ echo $?
0
[09:55:21 /tmp]$ 

From groff-admin  Thu Nov  2 23:40:19 2000
Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA17567
	for <groff@ffii.org>; Thu, 2 Nov 2000 23:40:19 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rT84-00086o-00
	for groff@ffii.org; Thu, 02 Nov 2000 22:46:40 +0000
Received: from modem-92.adunakhor.dialup.pol.co.uk ([62.136.96.220] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rT83-0000Lf-00
	for groff@ffii.org; Thu, 02 Nov 2000 22:46:39 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id WAA32255;
	Thu, 2 Nov 2000 22:46:30 GMT
Message-Id: <200011022246.WAA32255@inputplus.demon.co.uk>
To: groff@ffii.org
Date: Thu, 02 Nov 2000 22:46:29 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Subject: [Groff] Question on Using pic for Entity Relationship Diagrams.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1834
Lines: 83

Hi,

I'm trying to use pic for the first time.  I've got Kernighan's paper
on it and Eric Raymond's later paper on groff's pic.  If the
information I'm missing is in one of these feel free to refer me.

The pic input is below.  I want to position the USERPREFS entity
relative to SECURITY's position.  But it seems that En_security isn't
where I think it should be, hence the XXX and crossed lines in the
middle of nowhere.

What am I missing?

Any other comments on the style of the pic code welcome.  I'd also be
interested in hearing of anyone else using pic for ERDs;  perhaps you
have some handy macros already available?

Many thanks,


Ralph.


.\" groff -mm -p erd.tr >erd.ps
.PS

define entity_box
{
    box wid $1 ht (($2) + 1) * 0.15
}

define crowsfoot
{
    {
        line from $1 - (0.05, 0) to $1 + (0, 0.1)
        line to $1 + (0.05, 0)
        line from $1 + (0, 0.1) to $1
    }
}

down

En_security: [
    entity_box(1, 3)
    "SECURITY" ljust at last box .w + (0.1, 0) \
        "* id" ljust \
        "description" ljust
]

L: line dashed
{ "assigned to" at last line .n - (0.05, 0.1) rjust }
L: line
crowsfoot(L.s)
{ "limited by" at L.s + (0.05, 0.1) ljust }

En_users: [
    entity_box(2, 4)
    "USERS \fIUSER\fP" ljust at last box .w  + (0.1, 0) \
        "* id" ljust \
        "name" ljust \
        "email" ljust
    "" ljust at last box .c  + (0.1, 0) \
        "blurb" ljust \
        "more blurb" ljust \
        "finale" ljust
]

L: line

En_userprefs: [
    line from En_security .w to En_security .e
    line from En_security .n to En_security .s
    move to En_security .e + (1, 0)
    entity_box(1.5, 5)
    "XXX" at En_security .c
    "USERPREFS \fImerge\fP" ljust at last box .w  + (0.1, 0) \
        "* id" ljust \
        "artnum" ljust \
        "sig" ljust \
        "viewmode" ljust
]

.PE

From groff-admin  Fri Nov  3 00:03:48 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA17963
	for <groff@ffii.org>; Fri, 3 Nov 2000 00:03:48 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 3 Nov 2000 00:09:46 +0100
Received: from rigel.univie.ac.at (dial-143136.HRZ.Uni-Dortmund.DE [129.217.143.136])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA2N9g023710;
	Fri, 3 Nov 2000 00:09:42 +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 RAA10896;
	Thu, 2 Nov 2000 17:04:56 +0100
Date: Thu, 02 Nov 2000 17:04:55 +0100 (CET)
Message-Id: <20001102.170455.131912184.wl@gnu.org>
To: shaulka@bezeqint.net
Cc: 75990@bugs.debian.org, debian-i18n@lists.debian.org, groff@ffii.org
Subject: Re: [Groff] groff options /tmp/ll does not work any more?
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <E13rFEL-0001c9-00@rakefet>
References: <E13rFEL-0001c9-00@rakefet>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 577
Lines: 19

> I do not know if this is only on my unstable Debian machine but
> 	groff -te -Tlatin1 -mandoc /tmp/ll -
> no longer work. I am getting an empty string instead.
> Am I missing something? Is there a work around?
> 
> zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc /tmp/ll -

Has this ever worked?  groff tries to open /tmp/ll *and* the standard
input which apparently fails.

What about this:

  zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc > /tmp/ll

(you can omit the `-' for standard input if you don't have another
input file).


    Werner

From groff-admin  Fri Nov  3 09:33:07 2000
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03415
	for <groff@ffii.org>; Fri, 3 Nov 2000 09:33:06 +0100
Received: from tedistan.annex.mcc.ac.uk
	([194.66.22.200] helo=tedistan.annex.umist.ac.uk ident=root)
	by probity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13rcNl-000NWD-00; Fri, 3 Nov 2000 08:39:29 +0000
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id IAA30044;
	Fri, 3 Nov 2000 08:38:30 GMT
Message-ID: <XFMail.001103083830.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: <200011022246.WAA32255@inputplus.demon.co.uk>
Date: Fri, 03 Nov 2000 08:38:30 -0000 (GMT)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Subject: RE: [Groff] Question on Using pic for Entity Relationship Diagra
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2804
Lines: 106

Hi Ralph,

On 02-Nov-00 Ralph Corderoy wrote:
> 
> Hi,
> 
> The pic input is below.  I want to position the USERPREFS entity
> relative to SECURITY's position.  But it seems that En_security isn't
> where I think it should be, hence the XXX and crossed lines in the
> middle of nowhere.
> 
> What am I missing?

I think the immediate answer to your problem is that you are using
a reference to the named block En_security inside another named
block En_userprefs. If you remove the lines

  En_userprefs: [

and

  ]

surrounding that block then it comes out as (I think) you want it.
As to whether this behaviour is in order, I'm not sure. The 'pic'
manual is ambiguous about this (scope of block names) according to
my reading, though my intuitive expectation is that it should work
as you intended. I will have to think a bit about this one.

POssibly also you are being a bit lavish with block labels and,
in particular, you have used the label "L:" several times
for different things; I think only the most recent will apply
(this may be what you want, of course).

Ted. 

> 
> .\" groff -mm -p erd.tr >erd.ps
> .PS
> 
> define entity_box
> {
>     box wid $1 ht (($2) + 1) * 0.15
> }
> 
> define crowsfoot
> {
>     {
>         line from $1 - (0.05, 0) to $1 + (0, 0.1)
>         line to $1 + (0.05, 0)
>         line from $1 + (0, 0.1) to $1
>     }
> }
> 
> down
> 
> En_security: [
>     entity_box(1, 3)
>     "SECURITY" ljust at last box .w + (0.1, 0) \
>         "* id" ljust \
>         "description" ljust
> ]
> 
> L: line dashed
> { "assigned to" at last line .n - (0.05, 0.1) rjust }
> L: line
> crowsfoot(L.s)
> { "limited by" at L.s + (0.05, 0.1) ljust }
> 
> En_users: [
>     entity_box(2, 4)
>     "USERS \fIUSER\fP" ljust at last box .w  + (0.1, 0) \
>         "* id" ljust \
>         "name" ljust \
>         "email" ljust
>     "" ljust at last box .c  + (0.1, 0) \
>         "blurb" ljust \
>         "more blurb" ljust \
>         "finale" ljust
> ]
> 
> L: line
> 
> En_userprefs: [
>     line from En_security .w to En_security .e
>     line from En_security .n to En_security .s
>     move to En_security .e + (1, 0)
>     entity_box(1.5, 5)
>     "XXX" at En_security .c
>     "USERPREFS \fImerge\fP" ljust at last box .w  + (0.1, 0) \
>         "* id" ljust \
>         "artnum" ljust \
>         "sig" ljust \
>         "viewmode" ljust
> ]
> 
> .PE
> _______________________________________________
> Groff maillist  -  Groff@ffii.org
> http://ffii.org/mailman/listinfo/groff

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 03-Nov-00                                       Time: 08:38:30
------------------------------ XFMail ------------------------------

From groff-admin  Fri Nov  3 12:37:36 2000
Received: from mail1.svr.pol.co.uk (mail1.svr.pol.co.uk [195.92.193.18])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA04972
	for <groff@ffii.org>; Fri, 3 Nov 2000 12:37:36 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by mail1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rfGF-0003Jo-00
	for groff@ffii.org; Fri, 03 Nov 2000 11:43:55 +0000
Received: from modem-55.anghabar.dialup.pol.co.uk ([62.136.111.183] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rfGE-00051M-00
	for groff@ffii.org; Fri, 03 Nov 2000 11:43:54 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id LAA07006;
	Fri, 3 Nov 2000 11:43:48 GMT
Message-Id: <200011031143.LAA07006@inputplus.demon.co.uk>
To: Ted.Harding@nessie.mcc.ac.uk
cc: groff@ffii.org
Subject: Re: [Groff] Question on Using pic for Entity Relationship Diagra 
In-Reply-To: Message from (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk> 
   of "Fri, 03 Nov 2000 08:38:30 GMT." <XFMail.001103083830.Ted.Harding@nessie.mcc.ac.uk> 
Date: Fri, 03 Nov 2000 11:43:48 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2064
Lines: 71

Hi Ted,

> > The pic input is below.  I want to position the USERPREFS entity
> > relative to SECURITY's position.  But it seems that En_security isn't
> > where I think it should be, hence the XXX and crossed lines in the
> > middle of nowhere.
> 
> I think the immediate answer to your problem is that you are using
> a reference to the named block En_security inside another named
> block En_userprefs. If you remove the lines
> 
>   En_userprefs: [
> 
> and
> 
>   ]
> 
> surrounding that block then it comes out as (I think) you want it.

Yes, you're right.

> As to whether this behaviour is in order, I'm not sure. The 'pic'
> manual is ambiguous about this (scope of block names) according to my
> reading, though my intuitive expectation is that it should work as
> you intended. I will have to think a bit about this one.

Having re-read Raymond's description I can see why it might not work as
would be intuitive.

If I place a move outside of the block that I want to appear at the
location it works fine.

    En_security: [
        ...
    ]

    En_users: [
        ...
    ]

    move to En_security .ne + (1, 0)
    En_userprefs: [
        ...
    ]

So I guess I'm happy.

> Possibly also you are being a bit lavish with block labels and, in
> particular, you have used the label "L:" several times for different
> things; I think only the most recent will apply (this may be what you
> want, of course).

I want each entity to have a label because it will make relationship
lines easier to draw later.  Raymond says labels aren't constants but
variables, and `L:' can be viewed as an assignment as in `A: A + (1,
0)' so they shouldn't be a problem.  I wanted to refer to a temporarily
important line for a bit and using just `L' instead of a unique name
for each seemed the way to go and avoided the longer `last line' or 2nd
last line, etc.

    L: line dashed
    { "assigned to" at last line .n - (0.05, 0.1) rjust }
    L: line
    crowsfoot(L.s)
    { "limited by" at L.s + (0.05, 0.1) ljust }

Many thanks for your prompt reply.


Ralph.


From groff-admin  Fri Nov  3 18:45:33 2000
Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA09576
	for <groff@ffii.org>; Fri, 3 Nov 2000 18:45:32 +0100
X-Authentication-Warning: genba.ffii.org: Host mail-a.bezeqint.net [192.115.106.23] claimed to be mail.bezeqint.net
Received: from rakefet (bzq-144-158.bezeqint.net)
 by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
 with ESMTP id <0G3G00MO0MSSRO@mail.bezeqint.net> for groff@ffii.org; Fri,
 3 Nov 2000 19:48:29 +0200 (IST)
Received: from localhost ([127.0.0.1] helo=rakefet ident=shaul)
 by rakefet with esmtp (Exim 3.16 #1 (Debian)) id 13rkzY-0000m4-00; Fri,
 03 Nov 2000 19:51:04 +0200
Date: Fri, 03 Nov 2000 19:51:02 +0200
From: Shaul Karl <shaulka@bezeqint.net>
Subject: Re: [Groff] groff options /tmp/ll does not work any more?
In-reply-to: Message from Werner LEMBERG <wl@gnu.org>
 "of Thu, 02 Nov 2000 17:04:55 +0100." <20001102.170455.131912184.wl@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: 75990@bugs.debian.org, debian-i18n@lists.debian.org, groff@ffii.org
Message-id: <E13rkzY-0000m4-00@rakefet>
MIME-version: 1.0
X-Mailer: exmh version 2.2 06/23/2000 (debian 2.2-1) with nmh-1.0.4+dev
Content-type: text/plain; charset=us-ascii
References: <E13rFEL-0001c9-00@rakefet> <20001102.170455.131912184.wl@gnu.org>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1773
Lines: 58

> > I do not know if this is only on my unstable Debian machine but
> > 	groff -te -Tlatin1 -mandoc /tmp/ll -
> > no longer work. I am getting an empty string instead.
> > Am I missing something? Is there a work around?
> > 
> > zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc /tmp/ll -
> 
> Has this ever worked?  groff tries to open /tmp/ll *and* the standard
> input which apparently fails.
> 


Of course it used to work. It is taken from the TkMan (tkman.sourceforge.net) 
Makefile:

[19:38:16 tkman-2.1]$ grep -A6 LONGER Makefile 
# Marco Melgazzi (marco@techie.com) prefers LONGER MAN PAGE LINES 
(recommended).
# The following line adds an entry in Preferences/See to set the length.
# You must use groff and the "/tmp/ll" path for this feature to take effect.
# Lines are cached in .../man/cat<n>@<line-length>; 
#   that is, the line length is appended to the usual cache directory names
#manformat = {groff -te -Tascii -man /tmp/ll -}
#manformat = {groff -te -Tlatin1 -mandoc /tmp/ll -}
[19:38:21 tkman-2.1]$ 

I am not sure what exactly got written to "/tmp/ll" although it is very 
possibly that it was just a copy of stdout.


> What about this:
> 
>   zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc > /tmp/ll
> 
> (you can omit the `-' for standard input if you don't have another
> input file).
> 


I assume this would break the app (TkMan) which expects its input via the pipe 
and probably need to know that its input is available in the file too. I guess 
the app needs the file to be able to seek it.


> 
>     Werner
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-i18n-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

-- 
	
	Shaul Karl <shaulka@bezeqint.net>



From groff-admin  Fri Nov  3 20:26:29 2000
Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA11137
	for <groff@ffii.org>; Fri, 3 Nov 2000 20:26:28 +0100
X-Authentication-Warning: genba.ffii.org: Host mail-a.bezeqint.net [192.115.106.23] claimed to be mail.bezeqint.net
Received: from rakefet (bzq-144-158.bezeqint.net)
 by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
 with ESMTP id <0G3G00JGZR69GO@mail.bezeqint.net> for groff@ffii.org; Fri,
 3 Nov 2000 21:22:58 +0200 (IST)
Received: from localhost ([127.0.0.1] helo=rakefet ident=shaul)
 by rakefet with esmtp (Exim 3.16 #1 (Debian)) id 13rmSz-0000rG-00; Fri,
 03 Nov 2000 21:25:33 +0200
Date: Fri, 03 Nov 2000 21:25:30 +0200
From: Shaul Karl <shaulka@bezeqint.net>
Subject: Re: [Groff] groff options /tmp/ll does not work any more?
In-reply-to: Message from Werner LEMBERG <wl@gnu.org>
 "of Thu, 02 Nov 2000 17:04:55 +0100." <20001102.170455.131912184.wl@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: 75990@bugs.debian.org, debian-i18n@lists.debian.org, groff@ffii.org
Message-id: <E13rmSz-0000rG-00@rakefet>
MIME-version: 1.0
X-Mailer: exmh version 2.2 06/23/2000 (debian 2.2-1) with nmh-1.0.4+dev
Content-type: text/plain; charset=us-ascii
References: <E13rFEL-0001c9-00@rakefet> <20001102.170455.131912184.wl@gnu.org>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 574
Lines: 27

Just observed that the behavior depends on the existence of the /tmp/ll file:

[21:20:29 /tmp]$ rm -v ll
removing `ll'
[21:22:37 /tmp]$ zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc /tmp/ll - | head
/tmp/ll.gz: No such file or directory



LS(1)                          FSF                          LS(1)

[21:22:54 /tmp]$ 


	As opposed to:

[21:24:21 /tmp]$ touch ll
[21:24:30 /tmp]$ zcat /usr/share/man/man1/ls.1.gz | groff -te -Tlatin1 -mandoc /tmp/ll - | head -5
[21:24:36 /tmp]$ echo $?
0
[21:24:44 /tmp]$ 

-- 
	
	Shaul Karl <shaulka@bezeqint.net>



From groff-admin  Fri Nov  3 21:47:13 2000
Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA12524
	for <groff@ffii.org>; Fri, 3 Nov 2000 21:47:13 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rnqG-0004hF-00
	for groff@ffii.org; Fri, 03 Nov 2000 20:53:40 +0000
Received: from modem-47.annuminas.dialup.pol.co.uk ([62.136.116.175] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rnqF-0005BM-00
	for groff@ffii.org; Fri, 03 Nov 2000 20:53:39 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id UAA27568;
	Fri, 3 Nov 2000 20:53:37 GMT
Message-Id: <200011032053.UAA27568@inputplus.demon.co.uk>
To: groff@ffii.org
Date: Fri, 03 Nov 2000 20:53:36 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Subject: [Groff] Dashed Splines in pic.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 261
Lines: 12

Hi,

groff's pic accepts input containing `spline dashed' but the spline
isn't dashed in groff output mode, only in TeX;  the man page documents
this.

Given that PostScript can stroke a spline dashedly is there a big
obstacle to this working in pic?


Ralph.


From groff-admin  Fri Nov  3 22:26:31 2000
Received: from srv1.tsoft.net (news.tsoft.net [198.144.192.3])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA13310
	for <groff@ffii.org>; Fri, 3 Nov 2000 22:26:30 +0100
X-Authentication-Warning: genba.ffii.org: Host news.tsoft.net [198.144.192.3] claimed to be srv1.tsoft.net
Received: from bicho.SynchroDS.COM (daniel.ppp.tsoft.com [198.144.199.225])
	by srv1.tsoft.net (8.8.7/8.8.7) with ESMTP id NAA16565;
	Fri, 3 Nov 2000 13:32:14 -0800 (PST)
Received: (from daniel@localhost)
	by bicho.SynchroDS.COM (8.8.8/8.8.8) id NAA03198;
	Fri, 3 Nov 2000 13:33:36 -0800 (PST)
Date: Fri, 3 Nov 2000 13:33:36 -0800 (PST)
From: Daniel Senderowicz <daniel@bicho.SynchroDS.COM>
Message-Id: <200011032133.NAA03198@bicho.SynchroDS.COM>
To: groff@ffii.org, ralph@inputplus.demon.co.uk
Subject: Re: [Groff] Dashed Splines in pic.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 534
Lines: 14

I don't know about PIC. But when I was working on the grn code, in
order to honor the gremlin line modes, I had to build dashed (and
dotted, dotted-dash) lines by breaking solid lines that is the only
line mode that groff outputs. The original troff had different line
modes.

Dan

>groff's pic accepts input containing `spline dashed' but the spline
>isn't dashed in groff output mode, only in TeX;  the man page documents
>this.
>
>Given that PostScript can stroke a spline dashedly is there a big
>obstacle to this working in pic?

From groff-admin  Fri Nov  3 22:40:35 2000
Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA13539
	for <groff@ffii.org>; Fri, 3 Nov 2000 22:40:35 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13rofu-00068X-00
	for groff@ffii.org; Fri, 03 Nov 2000 21:47:02 +0000
Received: from modem-99.aradan.dialup.pol.co.uk ([62.136.117.227] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13roft-0000Ve-00
	for groff@ffii.org; Fri, 03 Nov 2000 21:47:02 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id VAA30889;
	Fri, 3 Nov 2000 21:46:58 GMT
Message-Id: <200011032146.VAA30889@inputplus.demon.co.uk>
To: Daniel Senderowicz <daniel@bicho.SynchroDS.COM>
cc: groff@ffii.org
Subject: Re: [Groff] Dashed Splines in pic. 
In-Reply-To: Message from Daniel Senderowicz <daniel@bicho.SynchroDS.COM> 
   of "Fri, 03 Nov 2000 13:33:36 PST." <200011032133.NAA03198@bicho.SynchroDS.COM> 
Date: Fri, 03 Nov 2000 21:46:57 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 525
Lines: 17

Hi Dan,

> I don't know about PIC. But when I was working on the grn code, in
> order to honor the gremlin line modes, I had to build dashed (and
> dotted, dotted-dash) lines by breaking solid lines that is the only
> line mode that groff outputs. The original troff had different line
> modes.

Ah, so perhaps pic's ability to output dashed straight lines is also
done by pic breaking the lines itself;  I'd assumed it was getting
troff to do the work.

BTW, have you a link to a grn page?  I'd like to know more.


Ralph.


From groff-admin  Fri Nov  3 22:51:55 2000
Received: from srv1.tsoft.net (news.tsoft.net [198.144.192.3])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA13712
	for <groff@ffii.org>; Fri, 3 Nov 2000 22:51:54 +0100
X-Authentication-Warning: genba.ffii.org: Host news.tsoft.net [198.144.192.3] claimed to be srv1.tsoft.net
Received: from bicho.SynchroDS.COM (daniel.ppp.tsoft.com [198.144.199.225])
	by srv1.tsoft.net (8.8.7/8.8.7) with ESMTP id NAA18845;
	Fri, 3 Nov 2000 13:57:48 -0800 (PST)
Received: (from daniel@localhost)
	by bicho.SynchroDS.COM (8.8.8/8.8.8) id NAA03271;
	Fri, 3 Nov 2000 13:59:03 -0800 (PST)
Date: Fri, 3 Nov 2000 13:59:03 -0800 (PST)
From: Daniel Senderowicz <daniel@bicho.SynchroDS.COM>
Message-Id: <200011032159.NAA03271@bicho.SynchroDS.COM>
To: daniel@bicho.SynchroDS.COM, ralph@inputplus.demon.co.uk
Subject: Re: [Groff] Dashed Splines in pic.
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1022
Lines: 33

Ralph,

I don't know if there is any grn page, but in any case, grn is just
a groff preprocessor (filter), that is well documented in the man
pages. What you probable want to learn about is "gremlin", that is
the X-windows program that generates the files that are further
processed by grn. Once you have gremlin running, it has pretty good
on-line instructions on how to use it. You can fetch it from:

ftp://ftp.ffii.org/pub/groff/xgremlin2-20001003.tar.bz2

Good luck.

Dan

>Hi Dan,
>
>> I don't know about PIC. But when I was working on the grn code, in
>> order to honor the gremlin line modes, I had to build dashed (and
>> dotted, dotted-dash) lines by breaking solid lines that is the only
>> line mode that groff outputs. The original troff had different line
>> modes.
>
>Ah, so perhaps pic's ability to output dashed straight lines is also
>done by pic breaking the lines itself;  I'd assumed it was getting
>troff to do the work.
>
>BTW, have you a link to a grn page?  I'd like to know more.
>
>
>Ralph.
>
>

From groff-admin  Sat Nov  4 01:46:23 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id BAA15838
	for <groff@ffii.org>; Sat, 4 Nov 2000 01:46:23 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 4 Nov 2000 01:52:36 +0100
Received: from rigel.univie.ac.at (dial-143173.HRZ.Uni-Dortmund.DE [129.217.143.173])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA40qQ013658;
	Sat, 4 Nov 2000 01:52:31 +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 BAA15833;
	Sat, 4 Nov 2000 01:49:08 +0100
Date: Sat, 04 Nov 2000 01:49:08 +0100 (CET)
Message-Id: <20001104.014908.71100086.wl@gnu.org>
To: shaulka@bezeqint.net
Cc: 75990@bugs.debian.org, debian-i18n@lists.debian.org, groff@ffii.org
Subject: Re: [Groff] groff options /tmp/ll does not work any more?
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <E13rkzY-0000m4-00@rakefet>
References: <20001102.170455.131912184.wl@gnu.org>
	<wl@gnu.org>
	<E13rkzY-0000m4-00@rakefet>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 732
Lines: 16

> # Marco Melgazzi (marco@techie.com) prefers LONGER MAN PAGE LINES 
> (recommended).
> # The following line adds an entry in Preferences/See to set the length.
> # You must use groff and the "/tmp/ll" path for this feature to take effect.
> # Lines are cached in .../man/cat<n>@<line-length>; 
> #   that is, the line length is appended to the usual cache directory names
> #manformat = {groff -te -Tascii -man /tmp/ll -}
> #manformat = {groff -te -Tlatin1 -mandoc /tmp/ll -}

Aaah, the file /tmp/ll contains one or more groff macros.  It will be
created by TkMan before calling groff.  For some reasons your TkMan
installation doesn't write this file.  Of course, this is just my 2
cents since I've never used TkMan.


    Werner

From groff-admin  Sun Nov  5 18:54:33 2000
Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA06307
	for <groff@ffii.org>; Sun, 5 Nov 2000 18:54:33 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13sU6S-0004Ms-00
	for groff@ffii.org; Sun, 05 Nov 2000 18:01:12 +0000
Received: from modem-89.adunakhor.dialup.pol.co.uk ([62.136.96.217] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13sU6S-0001Ax-00
	for groff@ffii.org; Sun, 05 Nov 2000 18:01:12 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id SAA13819;
	Sun, 5 Nov 2000 18:01:06 GMT
Message-Id: <200011051801.SAA13819@inputplus.demon.co.uk>
To: groff@ffii.org
Date: Sun, 05 Nov 2000 18:01:06 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Subject: [Groff] Switching Page Orientation.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 214
Lines: 12

Hi,

I'd like the page containing a diagram drawn using pic to be A4
landscape format whilst the rest of the document remains A4 portrait.

What's the best way to obtain this.  I'm using tmac.m.

Thanks,


Ralph.


From groff-admin  Mon Nov  6 06:10:05 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id GAA23111
	for <groff@ffii.org>; Mon, 6 Nov 2000 06:10:03 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 1E50F1C11A
	for <groff@ffii.org>; Mon,  6 Nov 2000 14:20:51 +0900 (JST)
Date: Mon, 06 Nov 2000 14:20:46 +0900
Message-ID: <873dh5wua9.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Mail-Reply-To: tkubota@riken.go.jp
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Subject: [Groff] Preprocessor
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 19264
Lines: 559

Hi,

I wrote a preprocessor for the coming Groff.  This converts
standard input or a file from specified encoding to UTF-8.

# This preprocessor is used so that Groff system to be locale-sensible
# and be properly internationalized whereas the only encoding which
# troff can handle is UTF-8.  This topic was discussed last month.
# Please consult http://ffii.org/archive/mails/groff/2000/Oct/0056.html
# and the following discussions for details.

This can be compiled with or without internationalization option.
Non-internationalized version (compiled without internationalization
option) is for OSes which don't have internationalization functions
such as setlocale(), iconv(), and so on.  [Note that these functions
are mandatory for "Unix" brand.  Linux also has.]

Non-internationalized version supports the following encodings as input:
 - latin1 (aka ISO-8859-1)
 - ebcdic
 - utf-8 (i.e. no conversion)
Internationalized version supports not only these encodings but also
encodings which are supported by the OS.

Encoding for input is determined by
 - command line
 - special token in the input
 - default

The 'special token' is emacs-style "-*- coding: foobar; -*-".  This
token must be written in the top comment lines of the roff source.
Emacs-style names for encodings (for example, "euc-japan-dos") are
supported.

The 'default' is 
 - Latin1 for non-internationalized version.
 - For internationalized version:
   - Encoding for the locale when locale is properly configured.
   - Latin1 when locale is not properly configured.

This version lacks the following faculties:
 - Insersion of '.mso tmac.<encoding>' line to specify usable UTF-8
   characters in the encoding.
 - Conversion of encoding names from MIME-style to OS specific.
   (or this version assumes that OS supports MIME-style encoding names.)

The following is the source code.  I developed this code using
Debian GNU/Linux 'woody' (development version).  I also checked
this code with Debian GNU/Linux 2.2 ('potato') (the newest stable
version).  Since this is the first release, I din't care about
efficiency (neither on speed and memory usage).

----------------------------------------------------------------------
#define I18N

#include <stdio.h>
#include <errno.h>
#include <unistd.h>
#include <string.h>

#ifdef I18N
#include <locale.h>
#include <langinfo.h>
#include <iconv.h>
#endif /* I18N */

#define MAX_VAR_LEN 100

char *check_encoding_tag(char *);
char *check_encoding_tag_parse_tag(char *, char **, char **);
char *read_file (FILE *);
char *emacs2mime(char *);
char *mime2locale(char *);
void conversion_latin1 (char *, char *);
void conversion_utf8 (char *, char *);
void conversion_ebcdic (char *, char *);
void conversion_iconv (char *, char *);
void help (char *);

typedef struct {
  char * from;
  char * to;
} encname_t;

encname_t emacs_to_mime[] = {
  {"alternativnyj",                   ""},
  {"big5",                            "Big5"},
  {"chinese-big5",                    "Big5"},
  {"chinese-euc",                     "EUC-CN"},
  {"chinese-hz",                      "HZ-GB-2312"},
  {"chinese-iso-7bit",                ""},
  {"chinese-iso-8bit",                ""},
  {"chinese-iso-8bit-with-esc",       ""},
  {"cn-big5",                         "Big5"},
  {"cn-gb-2312",                      "GB2312"},
  {"compound-text",                   ""},
  {"ctext",                           ""},
  {"cyrillic-alternativnyj",          ""},
  {"cyrillic-iso-8bit",               "ISO-8859-5"},
  {"cyrillic-iso-8bit-with-esc",      ""},
  {"cyrillic-koi8",                   "KOI8-R"},
  {"dos",                             ""},
  {"emacs-mule",                      ""},
  {"euc-china",                       "EUC-CN"},
  {"euc-cn",                          "EUC-CN"},
  {"euc-japan",                       "EUC-JP"},
  {"euc-jisx0213",                    "EUC-JP"},
  {"euc-jisx0213-with-esc",           "EUC-JP"},
  {"euc-jp",                          "EUC-JP"},
  {"euc-korea",                       "EUC-KR"},
  {"euc-kr",                          "EUC-KR"},
  {"gb2312",                          "GB2312"},
  {"greek-iso-8bit",                  "ISO-8859-7"},
  {"greek-iso-8bit-with-esc",         "ISO-8859-7"},
  {"hebrew-iso-8bit",                 "ISO-8859-8"},
  {"hebrew-iso-8bit-with-esc",        "ISO-8859-8"},
  {"hz",                              "HZ-GB-2312"},
  {"hz-gb-2312",                      "HZ-GB-2312"},
  {"in-is13194-devanagari",           ""},
  {"in-is13194-devanagari-with-esc",  ""},
  {"iso-2022-7",                      ""},
  {"iso-2022-7bit",                   ""},
  {"iso-2022-7bit-lock",              ""},
  {"iso-2022-7bit-lock-ss2",          ""},
  {"iso-2022-7bit-ss2",               ""},
  {"iso-2022-8",                      ""},
  {"iso-2022-8bit",                   ""},
  {"iso-2022-8bit-lock"    ,          ""},
  {"iso-2022-8bit-lock-ss2",          ""},
  {"iso-2022-8bit-ss2",               ""},
  {"iso-2022-cjk",                    ""},
  {"iso-2022-cn",                     "ISO-2022-CN"},
  {"iso-2022-cn-ext",                 "ISO-2022-CN-EXT"},
  {"iso-2022-int-1",                  ""},
  {"iso-2022-jp",                     "ISO-2022-JP"},
  {"iso-2022-jp-1978-irv",            "ISO-2022-JP"},
  {"iso-2022-jp-2",                   "ISO-2022-JP-2"},
  {"iso-2022-jp-3",                   ""},
  {"iso-2022-jp-3-compatible",        ""},
  {"iso-2022-jp-3-strict",            ""},
  {"iso-2022-kr",                     "ISO-2022-KR"},
  {"iso-2022-lock",                   ""},
  {"iso-8859-1",                      "ISO-8859-1"},
  {"iso-8859-2",                      "ISO-8859-2"},
  {"iso-8859-3",                      "ISO-8859-3"},
  {"iso-8859-4",                      "ISO-8859-4"},
  {"iso-8859-5",                      "ISO-8859-5"},
  {"iso-8859-6",                      "ISO-8859-6"},
  {"iso-8859-7",                      "ISO-8859-7"},
  {"iso-8859-8",                      "ISO-8859-8"},
  {"iso-8859-9",                      "ISO-8859-9"},
  {"iso-latin-1",                     "ISO-8859-1"},
  {"iso-latin-2",                     "ISO-8859-2"},
  {"iso-latin-3",                     "ISO-8859-3"},
  {"iso-latin-4",                     "ISO-8859-4"},
  {"iso-latin-5",                     "ISO-8859-9"},
  {"iso-safe",                        ""},
  {"japanese-iso-7bit-1978-irv",      "ISO-2022-JP"},
  {"japanese-iso-8bit",               ""},
  {"japanese-iso-8bit-with-esc",      ""},
  {"japanese-euc",                    "EUC-JP"},
  {"japanese-shift-jis",              "Shift_JIS"},
  {"japanese-shift-jisx0213",         ""},
  {"junet",                           "ISO-2022-JP"},
  {"koi8",                            "KOI8-R"},
  {"koi8-r",                          "KOI8-R"},
  {"korean-euc",                      "EUC-KR"},
  {"korean-iso-7bit-lock",            "ISO-2022-KR"},
  {"korean-iso-8bit",                 ""},
  {"korean-iso-8bit-with-esc",        ""},
  {"lao",                             ""},
  {"lao-with-esc",                    ""},
  {"latin-1",                         "ISO-8859-1"},
  {"latin-2",                         "ISO-8859-2"},
  {"latin-3",                         "ISO-8859-3"},
  {"latin-4",                         "ISO-8859-4"},
  {"latin-5",                         "ISO-8859-9"},
  {"mac",                             ""},
  {"old-jis",                         "ISO-2022-JP"},
  {"raw-text",                        ""},
  {"shift_jis",                       "Shift_JIS"},
  {"shift_jisx0213",                  "Shift_JIS"},
  {"sjis",                            "Shift_JIS"},
  {"th-tis620",                       "TIS-620"},
  {"thai-tis620",                     "TIS-620"},
  {"tibetan",                         ""},
  {"tis-620",                         "TIS-620"},
  {"tis620",                          "TIS-620"},
  {"us-ascii",                        "US-ASCII"},
  {"utf-16-be",                       "UTF-16BE"},
  {"utf-16-be-no-signature",          "UTF-16BE"},
  {"utf-16-le",                       "UTF-16LE"},
  {"utf-16-le-no-signature",          "UTF-16LE"},
  {"utf-7",                           "UTF-7"},
  {"utf-7-safe",                      "UTF-7"},
  {"utf-8",                           "UTF-8"},
  {"utf-8-ws",                        "UTF-8"},
  {"vietnamese-viqr",                 "VIQR"},
  {"vietnamese-viscii",               "VISCII"},
  {"vietnamese-vscii",                "VISCII"},
  {"viqr",                            "VIQR"},
  {"viscii",                          "VISCII"},
  {"vscii",                           "VSCII"},
  {"x-ctext",                         ""},
  {NULL,                              NULL}
};

encname_t mime_to_locale[] = {
  {NULL,                              NULL}
};

main(int argc, char **argv)
{
  char *encoding=NULL, *default_encoding, *inbuf, *locale;
  FILE *fp;

  /* determine the default encoding.  This part has to be located
   * before getopt() since the help message shows the default
   * encoding.
   */ 
#ifdef I18N
  setlocale(LC_ALL, "");
  locale = setlocale(LC_CTYPE, NULL);
  if (!locale || !strcmp(locale, "C") || !strcmp(locale, "POSIX")) {
    default_encoding = "latin1";
  } else {
    default_encoding = nl_langinfo(CODESET);
    if (!default_encoding) default_encoding = "latin1";
  }
#else
  default_encoding = "latin1";
#endif

  /* parse the command option */
  while(1){
    int opt;
    opt = getopt(argc, argv, "e:h");
    if (opt == -1) break;
    switch(opt){
    case 'e':
      encoding = (char *)strdup(optarg); break;
    case 'h':
      help(default_encoding); exit(0);
    default:
      exit(1);
    }
  }

  /* read a source */
  if (optind < argc) {
    fp = fopen(argv[optind], "r");
    if (!fp) {
      printf("Cannot open %s\n", argv[optind]);
      exit(1);
    }
    inbuf = read_file(fp);
    fclose(fp);
  } else {
    inbuf = read_file(stdin);
  }

  /* finally determine the encoding */
  if (encoding == NULL) {
    encoding = check_encoding_tag(inbuf);
    if (encoding == NULL) {
      encoding = default_encoding;
    }
  }

  /* translate from MIME & Emacs encoding names to locale encoding names */
  encoding = emacs2mime(encoding);
  encoding = mime2locale(encoding);

  /* call converter (converters write to stdout) */
  if (!strcmp(encoding, "latin1")) {
    conversion_latin1(inbuf, encoding);
  } else if (!strcmp(encoding, "utf8")) {
    conversion_utf8(inbuf, encoding);
  } else if (!strcmp(encoding, "ebcdic")) {
    conversion_ebcdic(inbuf, encoding);
  } else {
#ifdef I18N
    conversion_iconv(inbuf, encoding);
#else
    printf("Conversion from %s to UTF-8 is not supported.\n", encoding);
    exit(1);
#endif
  }
}

/*  ---------------------------------------------------------
 *  print help message
 *  ---------------------------------------------------------
 */
void help(char *default_encoding)
{
  printf(
	 "Preprocessor for Groff system (%s)\n"
	 "Usage: gpreconv [option] [input file]\n"
	 "  -e encoding     specify encoding\n"
	 "  -h              this message\n"
	 "The default encoding is \"%s\".\n",
#ifdef I18N
	 "internationalized version",
#else
	 "non-internationalized version",
#endif
	 default_encoding);
}

/*  ---------------------------------------------------------
 *  read input file
 *  The file has to be inputed as a whole before conversion
 *  since the encoding may be stateful like ISO-2022 series.
 *  ---------------------------------------------------------
 */
char *read_file (FILE *fp)
{
#define READBUF_SIZE 32768
  char *buf = NULL;
  size_t bufsize = 0;
  size_t readsize = 0;
  size_t n;
  while(1) {
    if (readsize == bufsize) {
      bufsize += READBUF_SIZE;
      buf = (char *)realloc(buf, bufsize + 1);
      if (!buf) {
	printf("Unable to allocate memory.\n"); exit(1);
      }
    }
    n = fread (buf+readsize, 1, bufsize-readsize, fp);
    readsize += n;
    if (feof(fp)) break;
    if (ferror(fp)) {
      printf("Read error.\n"); exit(1);
    }
  }
  buf[readsize] = 0;
  return buf;
}

/*  ---------------------------------------------------------
 *  check encoding tag in the read buffer (not implemented yet)
 *  ---------------------------------------------------------
 */
char *check_encoding_tag(char *inbuf)
{
  char *p, *lineend, *d1, *d2, *variable, *value;
  for (p=inbuf ; !strncmp(p, ".\\\"", 3) ; p = lineend + 1) {
    if ((lineend = strchr(p, '\n')) == NULL) break;
    *lineend = 0;
    d1 = strstr(p, "-*-"); if (d1) d2 = strstr(d1+3, "-*-");
    *lineend = '\n';
    if (!d1 || !d2) continue;
    *d2 = 0; d1+=3;
    while(*d1) {
      d1 = check_encoding_tag_parse_tag(d1, &variable, &value);
      if (!strcmp(variable, "coding")) {
	*d2 = '-';
	return value;
      }
    }
    *d2 = '-';
  }
  return NULL;
}

char *check_encoding_tag_parse_tag(char *d1, char **variable, char **value)
{
  static char var[MAX_VAR_LEN], val[MAX_VAR_LEN];
  int l;

  *variable = var; *value = val;

  while (*d1 == ' ' || *d1 == '\t') d1++;
  l = 0;
  while (l<MAX_VAR_LEN-1 && *d1 && !strchr(";: \t", *d1)) {
    var[l++] = *(d1++);
  }
  var[l] = 0;
  while (*d1 && *d1!=':' && *d1!=';') d1++;
  val[0] = 0;
  if (!*d1) return d1;
  if (*d1 == ';') return d1+1;
  d1++;
  while (*d1 == ' ' || *d1 == '\t') d1++;  
  l = 0;
  while (l<MAX_VAR_LEN-1 && *d1 && !strchr("; \t", *d1)) {
    val[l++] = *(d1++);
  }
  val[l] = 0;
  while (*d1 && *d1!=';') d1++;
  if (!*d1) return d1;
  if (*d1 == ';') return d1+1;
}

/*  ---------------------------------------------------------
 *  convert encoding name from emacs to mime
 *  ---------------------------------------------------------
 */
char *emacs2mime(char *emacs_encoding)
{
  static char emacs_enc[MAX_VAR_LEN];
  int emacs_enc_len;
  encname_t *table;

  strncpy(emacs_enc, emacs_encoding, MAX_VAR_LEN-1);
  emacs_enc[MAX_VAR_LEN-1] = 0;
  emacs_enc_len = strlen(emacs_enc);
  if (!strcasecmp(emacs_enc + emacs_enc_len - 4, "-dos"))
    emacs_enc[emacs_enc_len - 4] = 0;
  if (!strcasecmp(emacs_enc + emacs_enc_len - 4, "-mac"))
    emacs_enc[emacs_enc_len - 4] = 0;
  if (!strcasecmp(emacs_enc + emacs_enc_len - 5, "-unix"))
    emacs_enc[emacs_enc_len - 5] = 0;
  for (table = emacs_to_mime; table->from; table++) {
    if (!strcasecmp(emacs_enc, table->from)) return table->to;
  }
  return emacs_enc;
}

/*  ---------------------------------------------------------
 *  convert encoding name from mime to locale
 *  ---------------------------------------------------------
 */
char *mime2locale(char *mime_encoding)
{
  encname_t *table;

  for (table = mime_to_locale; table->from; table++) {
    if (!strcasecmp(mime_encoding, table->from)) return table->to;
  }
  return mime_encoding;
}

/*  ---------------------------------------------------------
 *  conversion functions
 *  ---------------------------------------------------------
 */

/* conversion from ISO-8859-1 (aka Latin-1) to UTF-8 */
void conversion_latin1 (char *inbuf, char *encoding)
{
  unsigned char *p;
  for(p=inbuf; *p; p++) {
    if (*p < 0x80) putchar(*p);
    else {putchar(0xc0 + (*p >> 6)); putchar(0x80 + (*p & 0x3f));}
  }
  return;
}

/* conversion from UTF-8 to UTF-8, i.e., do nothing */
void conversion_utf8 (char *inbuf, char *encoding)
{
  fwrite(inbuf, 1, strlen(inbuf), stdout);
  return;
}

/* conversion from EBCDIC to UTF-8 */
/* the table is made from /font/devutf8/R.proto in groff 1.16 */
void conversion_ebcdic (char *inbuf, char *encoding)
{
  static unsigned char cp1047[] = {
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x00-0x07 */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x08-0x0f */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x10-0x17 */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x18-0x1f */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x20-0x27 */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x28-0x2f */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x30-0x37 */
    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,  /* 0x38-0x3f */
    0x00, 0x00, 0xe2, 0xe4, 0xe0, 0xe1, 0xe3, 0xe5,  /* 0x40-0x47 */
    0xe7, 0xf1, 0xa2, '.' , '<' , '(' , '+' , '|' ,  /* 0x48-0x4f */
    '&' , 0xe8, 0xea, 0xeb, 0xe8, 0xed, 0xee, 0xef,  /* 0x50-0x57 */
    0xec, 0xdf, '!' , '$' , '*' , ')' , ';' , '^' ,  /* 0x58-0x5f */
    '-' , '/' , 0xc2, 0xc4, 0xc0, 0xc1, 0xc3, 0xc5,  /* 0x60-0x67 */
    0xc7, 0xd1, 0xa6, ',' , '%' , '_' , '>' , '?' ,  /* 0x68-0x6f */
    0xf8, 0xc9, 0xca, 0xcb, 0xc8, 0xcd, 0xce, 0xcf,  /* 0x70-0x77 */
    0xcc, '`' , ':' , '#' , '@' , '\'', '=' , '\"',  /* 0x78-0x7f */
    0xd8, 'a' , 'b' , 'c' , 'd' , 'e' , 'f' , 'g' ,  /* 0x80-0x87 */
    'h' , 'i' , 0xab, 0xbb, 0xf0, 0xfd, 0xfe, 0xb1,  /* 0x88-0x8f */
    0xb0, 'j' , 'k' , 'l' , 'm' , 'n' , 'o' , 'p' ,  /* 0x90-0x97 */
    'q' , 'r' , 0xaa, 0xba, 0xe6, 0xb8, 0xc6, 0xa4,  /* 0x98-0x9f */
    0xb5, '~' , 's' , 't' , 'u' , 'v' , 'w' , 'x' ,  /* 0xa0-0xa7 */
    'y' , 'z' , 0xa1, 0xbf, 0xd0, '[' , 0xde, 0xae,  /* 0xa8-0xaf */
    0xac, 0xa3, 0xa5, 0xb7, 0xa9, 0xa7, 0xb6, 0xbc,  /* 0xb0-0xb7 */
    0xbd, 0xbe, 0xdd, 0xa8, 0xaf, ']' , 0xb4, 0xd7,  /* 0xb8-0xbf */
    '{' , 'A' , 'B' , 'C' , 'D' , 'E' , 'F' , 'G' ,  /* 0xc0-0xc7 */
    'H' , 'I' , 0xad, 0xf4, 0xf6, 0xf2, 0xf3, 0xf5,  /* 0xc8-0xcf */
    '}' , 'J' , 'K' , 'L' , 'M' , 'N' , 'O' , 'P' ,  /* 0xd0-0xd7 */
    'Q' , 'R' , 0xb9, 0xfb, 0xfc, 0xf9, 0xfa, 0xff,  /* 0xd8-0xdf */
    '\\', 0xf7, 'S' , 'T' , 'U' , 'V' , 'W' , 'X' ,  /* 0xe0-0xe7 */
    'Y' , 'Z' , 0xb2, 0xd4, 0xd6, 0xd2, 0xd3, 0xd5,  /* 0xe8-0xef */
    '0' , '1' , '2' , '3' , '4' , '5' , '6' , '7' ,  /* 0xf0-0xf7 */
    '8' , '9' , 0xb3, 0xdb, 0xdc, 0xd9, 0xda, 0x00   /* 0xf8-0xff */
  };
  unsigned char *p, c;
  for(p=inbuf; *p; p++) {
    c = cp1047[*p];
    if (c == 0) c = *p; /* fail safe */
    if (c < 0x80) putchar(c);
    else {
      putchar(0xc0 + (c >> 6));
      putchar(0x80 + (c & 0x3f));
    }
  }
  return;
}

/* locale-sensible conversion */
#ifdef I18N
void conversion_iconv (char *inbuf, char *encoding)
{
#define OUTBUF_SIZE 32768
#define OUTBUF_LIMIT 10
  char *outbuf = NULL, *outbuf_top = NULL;
  size_t bufsize = 0;
  size_t inbytesleft, outbytesleft, status;
  iconv_t handle;

  handle = iconv_open("UTF-8", encoding);
  if (handle == (iconv_t)-1) {
    if (errno == EINVAL) {
      printf("Conversion from %s to UTF-8 is not supported.\n", encoding);
      exit(1);
    }
    printf("iconv_open failed!\n"); exit(1);
  }

  inbytesleft = strlen(inbuf) + 1;
  outbytesleft = 0;
  while (inbytesleft > 0) {
    if (outbytesleft < OUTBUF_LIMIT) {
      size_t outsize = outbuf - outbuf_top;
      outbuf_top = (char *)realloc(outbuf_top, bufsize+=OUTBUF_SIZE);
      if (!outbuf_top) {
	printf("Unable to allocate memory.\n"); exit(1);
      }
      outbuf = outbuf_top + outsize;
      outbytesleft += OUTBUF_SIZE;
    }
    status = iconv(handle, &inbuf, &inbytesleft, &outbuf, &outbytesleft);
    if (status == -1) {
      if (errno == EINVAL || errno == EILSEQ) {
	printf("Invalid character.\n"); exit(1);
      }
    }
  }
  fwrite(outbuf_top, 1, strlen(outbuf_top), stdout);
  return;
}
#endif

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

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Mon Nov  6 16:58:47 2000
Received: from tigger.cc.uic.edu ([128.248.155.51])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA27270
	for <groff@ffii.org>; Mon, 6 Nov 2000 16:58:32 +0100
Received: from localhost (rogerd@localhost)
	by tigger.cc.uic.edu (8.9.3/8.9.3) with ESMTP id KAA20928;
	Mon, 6 Nov 2000 10:04:01 -0600
X-Authentication-Warning: tigger.cc.uic.edu: rogerd owned process doing -bs
Date: Mon, 6 Nov 2000 10:04:01 -0600 (CST)
From: Roger Deschner <rogerd@uic.edu>
X-Sender: rogerd@tigger.cc.uic.edu
To: Ralph Corderoy <ralph@inputplus.demon.co.uk>
cc: groff@ffii.org
Subject: Re: [Groff] Switching Page Orientation.
In-Reply-To: <200011051801.SAA13819@inputplus.demon.co.uk>
Message-ID: <Pine.A41.4.10.10011060954010.221574-100000@tigger.cc.uic.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 785
Lines: 29

I'm sure I'll get hate mail for this, but when I had to do that, I ran
the paper through the printer twice. Not recommended on a laser printer,
and tough on a shared printer, but works fine on a personal ink-jet. I
look forward to hearing of a more sophisticated solution, but this was,
umm, just too obvious.
 
Roger Deschner      University of Illinois at Chicago     rogerd@uic.edu


On Sun, 5 Nov 2000, Ralph Corderoy wrote:

>
>Hi,
>
>I'd like the page containing a diagram drawn using pic to be A4
>landscape format whilst the rest of the document remains A4 portrait.
>
>What's the best way to obtain this.  I'm using tmac.m.
>
>Thanks,
>
>
>Ralph.
>
>_______________________________________________
>Groff maillist  -  Groff@ffii.org
>http://ffii.org/mailman/listinfo/groff
>


From groff-admin  Mon Nov  6 17:01:17 2000
Received: from mail1.svr.pol.co.uk (mail1.svr.pol.co.uk [195.92.193.18])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA27401
	for <groff@ffii.org>; Mon, 6 Nov 2000 17:01:16 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by mail1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13sooE-0001xH-00
	for groff@ffii.org; Mon, 06 Nov 2000 16:07:46 +0000
Received: from modem-32.aman.dialup.pol.co.uk ([62.136.103.32] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13sooD-000472-00
	for groff@ffii.org; Mon, 06 Nov 2000 16:07:45 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id QAA16039;
	Mon, 6 Nov 2000 16:07:41 GMT
Message-Id: <200011061607.QAA16039@inputplus.demon.co.uk>
To: Roger Deschner <rogerd@uic.edu>
cc: groff@ffii.org
Subject: Re: [Groff] Switching Page Orientation. 
In-Reply-To: Message from Roger Deschner <rogerd@uic.edu> 
   of "Mon, 06 Nov 2000 10:04:01 CST." <Pine.A41.4.10.10011060954010.221574-100000@tigger.cc.uic.edu> 
Date: Mon, 06 Nov 2000 16:07:41 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 551
Lines: 17

Hi,

> I'm sure I'll get hate mail for this, but when I had to do that, I
> ran the paper through the printer twice. Not recommended on a laser
> printer, and tough on a shared printer, but works fine on a personal
> ink-jet. I look forward to hearing of a more sophisticated solution,
> but this was, umm, just too obvious.
 
Thanks for the suggestion but I want to go from troff to PostScript to
PDF and then distribute the PDF to people on different platforms, etc.
So it won't just be me printing it out.

Any other suggestions, anyone?


Ralph.


From groff-admin  Mon Nov  6 21:06:02 2000
Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA31564
	for <groff@ffii.org>; Mon, 6 Nov 2000 21:06:01 +0100
Received: from beta by smtp.hccnet.nl
	via uds227-120.dial.hccnet.nl [193.173.120.227] with SMTP
	id VAA14865 (8.8.5/1.13); Mon, 6 Nov 2000 21:12:34 +0100 (MET)
Message-ID: <002201c0482d$e6bdcae0$e378adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: <groff@ffii.org>, "Ralph Corderoy" <ralph@inputplus.demon.co.uk>
References: <200011051801.SAA13819@inputplus.demon.co.uk>
Subject: Re: [Groff] Switching Page Orientation.
Date: Mon, 6 Nov 2000 21:12:29 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_001F_01C04836.459991E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3047
Lines: 119

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C04836.459991E0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Enclosed are ms-macros for starting and ending landscape-mode. After a call to LA, all input is
set in landscape until EA is encountered. I have used them successfully to rotate a full page
with wide tables; only the page heading is printed in portrait, as it should be in an otherwise
portrait printed paper. The main problem is not switching to landscape (to do this, simply
insert the string given at the top), but to ensure that the text is printed at the right place.
You should space down to the left-hand upper corner of the block that must be rotated, and
increase the page-length with this amount (since troff knows nothing about the switch to
landscape). The macros use a separate environment to achieve this. It would be more general to
divert the text, and use the width and the height of the diversion to measure the amount of
spacing.
The macros are for ms, but the basics will probably remain the same for mm.

Kees

----- Oorspronkelijk bericht -----
Van: "Ralph Corderoy" <ralph@inputplus.demon.co.uk>
Aan: <groff@ffii.org>
Verzonden: zondag 5 november 2000 19:01
Onderwerp: [Groff] Switching Page Orientation.


>
> Hi,
>
> I'd like the page containing a diagram drawn using pic to be A4
> landscape format whilst the rest of the document remains A4 portrait.
>
> What's the best way to obtain this.  I'm using tmac.m.
>
> Thanks,
>
>
> Ralph.
>
> _______________________________________________
> Groff maillist  -  Groff@ffii.org
> http://ffii.org/mailman/listinfo/groff
>

------=_NextPart_000_001F_01C04836.459991E0
Content-Type: application/octet-stream;
	name="tmac.slandscape"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="tmac.slandscape"

.ds start-landscape \\X'ps: exec gsave currentpoint currentpoint =
translate 90 neg rotate neg exch neg exch translate'
.ds start-rotate \*[start-landscape]
.ds end-rotate \\X'ps: exec currentpoint grestore moveto'
.ds end-landscape \\X'ps: exec gsave currentpoint currentpoint translate =
0 neg rotate neg exch neg exch translate'
.de ROS
\*[start-rotate]
..
.de RON
\*[end-rotate]
..
.de LA		\" set in landscape
.ev LA
.fl
.PV
.nr LA:LA 21c
.\"nr LA:ds-type \n[ds-type]
.\"nr LA:ri \n(ri
.\"nr LA:li \n(li
.nr E1:PL \\n(.pu
.nr LA:PD \\n(PD
.nr LA:PI \\n(PI
.nr LA:PS \\n(PS
.nr LA:VS \\n(VS
.nr LA:LL \\n(LL
.nr LA:LL +\\n(.pu
.nr LA:LL -\\n(PWu
.ll \\n[LA:LL]u
.nr LA:LT \\n[LA:LL]u
.pl +\\n[LA:LA]u
.rs
.sp \\n[LA:LA]u
\*[start-landscape]
..
.de EA		\" end landscape
.br
\*[end-landscape]
.PV
.fl
.ev 0
.br
.ll \\n(LLu
.pl \\n[E1:PL]u
..
.de iniLA
.ev LA
.nr LA:LA 21c
.\"nr LA:ds-type \n[ds-type]
.\"nr LA:ri \n(ri
.\"nr LA:li \n(li
.nr E1:PL \\n(.pu
.nr LA:PD \\n(PD
.nr LA:PI \\n(PI
.nr LA:PS \\n(PS
.nr LA:VS \\n(VS
.nr LA:LL \\n(LL
.nr LA:LL +\\n(.pu
.nr LA:LL -\\n(PWu
.nr LA:LT \\n[LA:LL]u
.ev 0
..
.iniLA

------=_NextPart_000_001F_01C04836.459991E0--


From groff-admin  Mon Nov  6 21:21:00 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA31811
	for <groff@ffii.org>; Mon, 6 Nov 2000 21:21:00 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 6 Nov 2000 21:27:40 +0100
Received: from rigel.univie.ac.at (dial-143193.HRZ.Uni-Dortmund.DE [129.217.143.193])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA6KRW002997
	for <groff@ffii.org>; Mon, 6 Nov 2000 21:27: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 UAA03470
	for <groff@ffii.org>; Mon, 6 Nov 2000 20:40:56 +0100
Date: Mon, 06 Nov 2000 20:40:56 +0100 (CET)
Message-Id: <20001106.204056.18313104.wl@gnu.org>
To: groff@ffii.org
From: Werner LEMBERG <wl@gnu.org>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] groff for old macro packages
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1095
Lines: 27

Dear friends,


groff 1.16.1 checks whether some UNIX troff macro packages are
installed on the system.  If yes, it creates a small wrapper macro
file (containing a `.so' request which calls this particular macro
package), and it adds a prefix (usually `g') to the groff macro file
names.  Note that these wrappers are broken in the current snapshot
since I've partially removed this code erroneously.

As implemented in 1.16.1, wrappers cause some problems with
multiplatform installations: The wrapper files are installed by
default in the same directory as other macro packages, but this is
incorrect because they are platform-dependent.  Assuming that
/usr/local/share/groff/<version>/tmac contains the
architecture-independent data, wrapper files must be installed in
/usr/local/lib/groff/<version>/tmac.

Instead of fixing this I would like to get rid of these wrappers
completely -- is this really used today?  Wouldn't people rather
expect that calling groff causes groff's incarnations of ms, mm, etc.
macros be used by default?  Is there any advantage?

Opinions, please.


    Werner

From groff-admin  Mon Nov  6 21:21:00 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA31809
	for <groff@ffii.org>; Mon, 6 Nov 2000 21:20:59 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 6 Nov 2000 21:27:42 +0100
Received: from rigel.univie.ac.at (dial-143193.HRZ.Uni-Dortmund.DE [129.217.143.193])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA6KRc003005;
	Mon, 6 Nov 2000 21:27:38 +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 QAA03432;
	Mon, 6 Nov 2000 16:30:56 +0100
Date: Mon, 06 Nov 2000 16:30:56 +0100 (CET)
Message-Id: <20001106.163056.74564132.wl@gnu.org>
To: tkubota@riken.go.jp
Cc: groff@ffii.org
Subject: Re: [Groff] Preprocessor
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <873dh5wua9.wl@surfchem0.riken.go.jp>
References: <873dh5wua9.wl@surfchem0.riken.go.jp>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 924
Lines: 29

> I wrote a preprocessor for the coming Groff.  This converts
> standard input or a file from specified encoding to UTF-8.

Very nice!  I'll put it into the CVS (please send me the code
privately again -- I believe that some tabs have been incorrectly
converted to spaces, causing wrong indentation).  Which name of the
preprocessor do you suggest?

> Non-internationalized version supports the following encodings as input:
>  - latin1 (aka ISO-8859-1)
>  - ebcdic
>  - utf-8 (i.e. no conversion)

Please note that there is more than one EBCDIC encoding.  I suggest
that you stay with `cp1047' as the default.

> Encoding for input is determined by
>  - command line
>  - special token in the input
>  - default

Can you add a small man page?

Thanks a lot for your contribution!  Unfortunately, I still don't have
enough time to start with Unicode support in groff -- I first have to
finalize FreeType 2.0...


    Werner

From groff-admin  Mon Nov  6 22:04:18 2000
Received: from sdrc.com (heimdall.sdrc.com [146.122.132.195])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA32653
	for <groff@ffii.org>; Mon, 6 Nov 2000 22:04:14 +0100
X-Authentication-Warning: genba.ffii.org: Host heimdall.sdrc.com [146.122.132.195] claimed to be sdrc.com
Received: from tyr.sdrc.com (mailhub-cvg.sdrc.com [146.122.142.31])
	by sdrc.com (8.9.1/8.9.1) with ESMTP id QAA26856;
	Mon, 6 Nov 2000 16:10:51 -0500 (EST)
Received: from thor.sdrc.com (scjones@thor.sdrc.com [146.122.62.108])
	by tyr.sdrc.com (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id QAA12649;
	Mon, 6 Nov 2000 16:10:50 -0500 (EST)
Received: (from scjones@localhost)
	by thor.sdrc.com (8.9.0/8.9.0) id QAA05008;
	Mon, 6 Nov 2000 16:10:49 -0500 (EST)
Message-Id: <200011062110.QAA05008@thor.sdrc.com>
Subject: Re: [Groff] groff for old macro packages
To: wl@gnu.org (Werner LEMBERG)
Date: Mon, 6 Nov 2000 16:10:49 -0500 (EST)
Cc: groff@ffii.org
In-Reply-To: <20001106.204056.18313104.wl@gnu.org> from "Werner LEMBERG" at Nov 6, 0 08:40:56 pm
From: larry.jones@sdrc.com (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 696
Lines: 17

Werner LEMBERG writes:
> 
> Instead of fixing this I would like to get rid of these wrappers
> completely -- is this really used today?  Wouldn't people rather
> expect that calling groff causes groff's incarnations of ms, mm, etc.
> macros be used by default?  Is there any advantage?

Yes, it's really used today.  Some of the macro package
reimplementations, particularly mm, leave a lot to be desired, so
convenient access to the original macro packages is needed.  (There's
also the case of existing documents that engage in unwaranted chumminess
with the macro package that don't work right with the
reimplementations.)

-Larry Jones

I told her to expect you to deny everything. -- Calvin

From groff-admin  Tue Nov  7 02:25:12 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id CAA04032
	for <groff@ffii.org>; Tue, 7 Nov 2000 02:25:11 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 23D311C11A
	for <groff@ffii.org>; Tue,  7 Nov 2000 10:36:01 +0900 (JST)
Date: Tue, 07 Nov 2000 10:35:49 +0900
Message-ID: <87k8ag1s3u.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Subject: Re: [Groff] Preprocessor
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Mon, 06 Nov 2000 16:30:56 +0100 (CET)"
	<20001106.163056.74564132.wl@gnu.org>
References: <873dh5wua9.wl@surfchem0.riken.go.jp>
	<20001106.163056.74564132.wl@gnu.org>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1846
Lines: 52

Hi,

At Mon, 06 Nov 2000 16:30:56 +0100 (CET),
Werner LEMBERG <wl@gnu.org> wrote:

> Very nice!  I'll put it into the CVS (please send me the code
> privately again -- I believe that some tabs have been incorrectly
> converted to spaces, causing wrong indentation).  Which name of the
> preprocessor do you suggest?

The name space for command names is a limited and precious resource
and we have to be careful to name it.  Though I once suggested
'gpreconv' in the previous discussion, I don't know about traditional
or tacit principles on naming a command, if there are.

I think 'gpreconv' may be too general, though this preprocessor is
used only for Groff system.  However, other executables of Groff
system have long history and general names.

BTW, how will you join my preprocessor to the Groff source tree?
My interest is that 'I18N' directive should be determined by the
'configure' script.  And more, it needs some mechanism to have
a translation table between MIME encoding names and OS-specific
encoding names.  I have no idea how to implement that.  (Thus the
current version have an empty table for this translation.)


> Please note that there is more than one EBCDIC encoding.  I suggest
> that you stay with `cp1047' as the default.

Ok.


> Can you add a small man page?

I see. I will write.


> Thanks a lot for your contribution!  Unfortunately, I still don't have
> enough time to start with Unicode support in groff -- I first have to
> finalize FreeType 2.0...

Oh, you are so busy.
TrueType is also an important topic for Japanese unices users.

Then I will write a postprosessor.  It may share the source code (and
binary) with the preprocessor, i.e., check argv[0] and change the
behavior.  (I found that we have to determine the names:-)

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Tue Nov  7 04:48:11 2000
Received: from tigger.cc.uic.edu (tigger.cc.uic.edu [128.248.155.51])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id EAA05182
	for <groff@ffii.org>; Tue, 7 Nov 2000 04:48:11 +0100
Received: from localhost (rogerd@localhost)
	by tigger.cc.uic.edu (8.9.3/8.9.3) with ESMTP id VAA255358
	for <groff@ffii.org>; Mon, 6 Nov 2000 21:54:55 -0600
X-Authentication-Warning: tigger.cc.uic.edu: rogerd owned process doing -bs
Date: Mon, 6 Nov 2000 21:54:55 -0600 (CST)
From: Roger Deschner <rogerd@uic.edu>
X-Sender: rogerd@tigger.cc.uic.edu
To: GROFF list <groff@ffii.org>
Subject: Re: [Groff] Preprocessor
In-Reply-To: <20001106.163056.74564132.wl@gnu.org>
Message-ID: <Pine.A41.4.10.10011062138350.111922-100000@tigger.cc.uic.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1658
Lines: 49


On Mon, 6 Nov 2000, Werner LEMBERG wrote:

>
>> I wrote a preprocessor for the coming Groff.  This converts
>> standard input or a file from specified encoding to UTF-8.
>
>Very nice!  I'll put it into the CVS (please send me the code
>privately again -- I believe that some tabs have been incorrectly
>converted to spaces, causing wrong indentation).  Which name of the
>preprocessor do you suggest?
>
>> Non-internationalized version supports the following encodings as input:
>>  - latin1 (aka ISO-8859-1)
>>  - ebcdic
>>  - utf-8 (i.e. no conversion)
>
>Please note that there is more than one EBCDIC encoding.  I suggest
>that you stay with `cp1047' as the default.

I just want to second that. There are literally dozens of versions of
EBCDIC. Those of us who deal with EBCDIC computers have embraced cp1047
as the single, new standard. People who run on EBCDIC systems have tools
for converting to or from cp1047, if they need to. Unfortunately, UNIX
tools such as "dd conv=ascii" were written before cp1047, and use EBCDIC
codings that are not standard, so support for cp1047 in your
preprocessor would be a good thing.

Roger Deschner      University of Illinois at Chicago     rogerd@uic.edu

>
>> Encoding for input is determined by
>>  - command line
>>  - special token in the input
>>  - default
>
>Can you add a small man page?
>
>Thanks a lot for your contribution!  Unfortunately, I still don't have
>enough time to start with Unicode support in groff -- I first have to
>finalize FreeType 2.0...
>
>
>    Werner
>_______________________________________________
>Groff maillist  -  Groff@ffii.org
>http://ffii.org/mailman/listinfo/groff
>


From groff-admin  Tue Nov  7 16:27:06 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA26850
	for <groff@ffii.org>; Tue, 7 Nov 2000 16:27:05 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 7 Nov 2000 16:33:42 +0100
Received: from rigel.univie.ac.at (dial-143165.HRZ.Uni-Dortmund.DE [129.217.143.165])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA7FXd027043;
	Tue, 7 Nov 2000 16:33:40 +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 LAA08176;
	Tue, 7 Nov 2000 11:38:23 +0100
Date: Tue, 07 Nov 2000 11:38:22 +0100 (CET)
Message-Id: <20001107.113822.102580710.wl@gnu.org>
To: tkubota@riken.go.jp
Cc: groff@ffii.org
Subject: Re: [Groff] Preprocessor
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <87k8ag1s3u.wl@surfchem0.riken.go.jp>
References: <873dh5wua9.wl@surfchem0.riken.go.jp>
	<20001106.163056.74564132.wl@gnu.org>
	<87k8ag1s3u.wl@surfchem0.riken.go.jp>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1714
Lines: 45

> > Which name of the preprocessor do you suggest?
> 
> The name space for command names is a limited and precious resource
> and we have to be careful to name it.  Though I once suggested
> 'gpreconv' in the previous discussion, I don't know about
> traditional or tacit principles on naming a command, if there are.

AFAIK, there aren't.  See my suggestion below.

> BTW, how will you join my preprocessor to the Groff source tree?

Just literally, without integration, so that other people can look at
it.

BTW, have you signed papers for copyright assignment to the FSF?  If
not, please do so (otherwise I can't use your code); details can be
found at

  http://www.gnu.org/software/gcc/fsf-forms/assignment-instructions.html

> My interest is that 'I18N' directive should be determined by the
> 'configure' script.

Definitely, but it isn't urgent IMHO.  Do you have a test handy to be
included into a4local.m4?  Maybe from another package?

> And more, it needs some mechanism to have a translation table
> between MIME encoding names and OS-specific encoding names.  I have
> no idea how to implement that.  (Thus the current version have an
> empty table for this translation.)

Are there so many OS-specific encodings?  Isn't it possible to have
static tables for that?

> Then I will write a postprosessor.  It may share the source code
> (and binary) with the preprocessor, i.e., check argv[0] and change
> the behavior.  (I found that we have to determine the names:-)

I was told that relying on argv[0] is against the GNU coding
standards, so please use a command line option instead.  If we have
just one program for both in and out conversion, I suggest `groconv'
as the program name.


    Werner

From groff-admin  Wed Nov  8 02:33:00 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id CAA02330
	for <groff@ffii.org>; Wed, 8 Nov 2000 02:32:58 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 815FD1C11A
	for <groff@ffii.org>; Wed,  8 Nov 2000 10:43:50 +0900 (JST)
Date: Wed, 08 Nov 2000 10:43:46 +0900
Message-ID: <87ofzrs0fh.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Subject: Re: [Groff] Preprocessor
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Tue, 07 Nov 2000 11:38:22 +0100 (CET)"
	<20001107.113822.102580710.wl@gnu.org>
References: <873dh5wua9.wl@surfchem0.riken.go.jp>
	<20001106.163056.74564132.wl@gnu.org>
	<87k8ag1s3u.wl@surfchem0.riken.go.jp>
	<20001107.113822.102580710.wl@gnu.org>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1934
Lines: 53

Hi,

At Tue, 07 Nov 2000 11:38:22 +0100 (CET),
Werner LEMBERG <wl@gnu.org> wrote:

> BTW, have you signed papers for copyright assignment to the FSF?  If
> not, please do so (otherwise I can't use your code); details can be
> found at
> 
>   http://www.gnu.org/software/gcc/fsf-forms/assignment-instructions.html

I could not find the page.  Could you tell me which pages should I read?


> > My interest is that 'I18N' directive should be determined by the
> > 'configure' script.
> 
> Definitely, but it isn't urgent IMHO.  Do you have a test handy to be
> included into a4local.m4?  Maybe from another package?

I have to study on autoconf and so on so on...
Ok, it is not urgent problem.  I will study and find how to.


> > And more, it needs some mechanism to have a translation table
> > between MIME encoding names and OS-specific encoding names.  I have
> > no idea how to implement that.  (Thus the current version have an
> > empty table for this translation.)
> 
> Are there so many OS-specific encodings?  Isn't it possible to have
> static tables for that?

I don't know about the real situation.  However, the C standard says
that encoding names are implementation-dependent.  I'd like to supply
a skelton where a user of some OS can add a table for the OS.


> > Then I will write a postprosessor.  It may share the source code
> > (and binary) with the preprocessor, i.e., check argv[0] and change
> > the behavior.  (I found that we have to determine the names:-)
> 
> I was told that relying on argv[0] is against the GNU coding
> standards, so please use a command line option instead.  If we have
> just one program for both in and out conversion, I suggest `groconv'
> as the program name.

I see.  The only term I know on the GNU coding standard is on the
indentation: use two columns.  (I found the standards in the GNU
web page.)

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Wed Nov  8 17:13:30 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA22617
	for <groff@ffii.org>; Wed, 8 Nov 2000 17:13:29 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 8 Nov 2000 17:20:16 +0100
Received: from rigel.univie.ac.at (dial-143148.HRZ.Uni-Dortmund.DE [129.217.143.148])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA8GKE027415;
	Wed, 8 Nov 2000 17:20:14 +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 RAA16272;
	Wed, 8 Nov 2000 17:15:12 +0100
Date: Wed, 08 Nov 2000 17:15:12 +0100 (CET)
Message-Id: <20001108.171512.107948068.wl@gnu.org>
To: larry.jones@sdrc.com
Cc: groff@ffii.org
Subject: Re: [Groff] groff for old macro packages
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <200011062110.QAA05008@thor.sdrc.com>
References: <20001106.204056.18313104.wl@gnu.org>
	<200011062110.QAA05008@thor.sdrc.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 781
Lines: 19

> > Instead of fixing this I would like to get rid of these wrappers
> > completely -- is this really used today?  Wouldn't people rather
> > expect that calling groff causes groff's incarnations of ms, mm,
> > etc.  macros be used by default?  Is there any advantage?
> 
> Yes, it's really used today.  Some of the macro package
> reimplementations, particularly mm, leave a lot to be desired, so
> convenient access to the original macro packages is needed.
> (There's also the case of existing documents that engage in
> unwaranted chumminess with the macro package that don't work right
> with the reimplementations.)

OK, I've reimplemented wrapper support -- those system-specific
wrapper files are now installed in /usr/local/lib/groff/site-tmac.

Please test!


    Werner

From groff-admin  Thu Nov  9 16:25:27 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA13843
	for <groff@ffii.org>; Thu, 9 Nov 2000 16:25:27 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 9 Nov 2000 16:32:23 +0100
Received: from rigel.univie.ac.at (dial-143163.HRZ.Uni-Dortmund.DE [129.217.143.163])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eA9FWB029235;
	Thu, 9 Nov 2000 16:32: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 QAA17440;
	Thu, 9 Nov 2000 16:32:05 +0100
Date: Thu, 09 Nov 2000 16:32:05 +0100 (CET)
Message-Id: <20001109.163205.133160861.wl@gnu.org>
To: tkubota@riken.go.jp
Cc: groff@ffii.org
Subject: Re: [Groff] Preprocessor
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <87ofzrs0fh.wl@surfchem0.riken.go.jp>
References: <87k8ag1s3u.wl@surfchem0.riken.go.jp>
	<20001107.113822.102580710.wl@gnu.org>
	<87ofzrs0fh.wl@surfchem0.riken.go.jp>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1474
Lines: 51

> > BTW, have you signed papers for copyright assignment to the FSF?  If
> > not, please do so (otherwise I can't use your code); details can be
> > found at
> > 
> >   http://www.gnu.org/software/gcc/fsf-forms/assignment-instructions.html
> 
> I could not find the page.  Could you tell me which pages should I read?

Oops, sorry!  It is below -- may I assume that future contributions
from you regarding groff will be assigned to the FSF too?


    Werner

======================================================================


Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full name as the subject line of the message.
----------------------------------------------------------------------
REQUEST:  SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]


[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]

From groff-admin  Fri Nov 10 13:24:36 2000
Received: from smtp.KPNQwest.pt (smtp1.KPNQwest.pt [193.126.4.61])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id NAA08737
	for <groff@ffii.org>; Fri, 10 Nov 2000 13:24:35 +0100
From: shaunjohnson.consultor@edinfor.edp.pt
X-Authentication-Warning: genba.ffii.org: Host smtp1.KPNQwest.pt [193.126.4.61] claimed to be smtp.KPNQwest.pt
Received: from relay1.edp.pt ([193.126.79.70])
	by smtp.KPNQwest.pt (8.11.0/8.11.0) with ESMTP id eAACVZ514511;
	Fri, 10 Nov 2000 12:31:37 GMT
To: groff@ffii.org
Cc: Shaun@slugfest.demon.co.uk
Date: Fri, 10 Nov 2000 12:02:08 +0000
Message-ID: <OF9B39233D.944BD117-ON80256993.004149A1@edp.pt>
X-MIMETrack: Serialize by Router on RELAY1/EDP-INET(Release 5.0.5 |September 22, 2000) at
 11/10/2000 12:31:43 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Groff] PIC misunderstanding?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 598
Lines: 38

Greetings,

I am probably being incredibly stupid but could someone please explain to
me
why the two pictures produced by the following fragment of PIC code are
different?
The second picture is the one I would expect.

Before anyone asks: yes, I have read the manual.

This is with GROFF 1.16.1 on Redhat Linux 6.2 for Intel.

   .PS 5in
   [
      move to (0,0)
      line to (1,1) -> "A"
   ]
   [
      move to (0,0)
      line to (-1, 1) -> "B"
   ]
   .PE

   .PS 5in

      move to (0,0)
      line to (1,1) -> "A"


      move to (0,0)
      line to (-1, 1) -> "B"

   .PE

Thanks,
    S.



From groff-admin  Fri Nov 10 15:15:17 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id PAA09422
	for <groff@ffii.org>; Fri, 10 Nov 2000 15:15:16 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id A8E521C121
	for <groff@ffii.org>; Fri, 10 Nov 2000 23:26:32 +0900 (JST)
Date: Fri, 10 Nov 2000 23:26:25 +0900
Message-ID: <877l6b7vji.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Subject: Re: [Groff] Preprocessor
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Thu, 09 Nov 2000 16:32:05 +0100 (CET)"
	<20001109.163205.133160861.wl@gnu.org>
References: <87k8ag1s3u.wl@surfchem0.riken.go.jp>
	<20001107.113822.102580710.wl@gnu.org>
	<87ofzrs0fh.wl@surfchem0.riken.go.jp>
	<20001109.163205.133160861.wl@gnu.org>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 329
Lines: 13

Hi,

At Thu, 09 Nov 2000 16:32:05 +0100 (CET),
Werner LEMBERG <wl@gnu.org> wrote:

> Oops, sorry!  It is below -- may I assume that future contributions
> from you regarding groff will be assigned to the FSF too?

I just sent to fsf-records@gnu.org.

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Sat Nov 11 17:12:54 2000
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA31915
	for <groff@ffii.org>; Sat, 11 Nov 2000 17:12:54 +0100
Received: from tedistan.annex.mcc.ac.uk
	([194.66.22.200] helo=tedistan.annex.umist.ac.uk ident=root)
	by probity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 13udNt-000Kj9-00; Sat, 11 Nov 2000 16:20:06 +0000
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA16842;
	Sat, 11 Nov 2000 16:09:10 GMT
Message-ID: <XFMail.001111160910.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: <OF9B39233D.944BD117-ON80256993.004149A1@edp.pt>
Date: Sat, 11 Nov 2000 16:09:10 -0000 (GMT)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: shaunjohnson.consultor@edinfor.edp.pt
Subject: RE: [Groff] PIC misunderstanding?
Cc: Shaun@slugfest.demon.co.uk, groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2669
Lines: 81

On 10-Nov-00 shaunjohnson.consultor@edinfor.edp.pt wrote:
> 
> Greetings,
> 
> I am probably being incredibly stupid but could someone please explain
> to me why the two pictures produced by the following fragment of PIC
> code are different?
> The second picture is the one I would expect.

So it would seem, on the surface. I can't be definitive about this,
but I believe it is consistent with intended behaviour, on the
following grounds.

In Kernighan's original PIC manual (section 9, Blocks) it says:

  "Any sequence of pic statements may be enclosed in brackets [ and ]
   to form a block, which can then be treated as a single object, and
   manipulated rather like an ordinary box" ... "By default, blocks
   join with other things as boxes do, at the center of the appropriate
   side."

An interpretation of this which is consistent with the behaviour you
observed is that when you wrote [ ... ] ; [ ... ] the first [] was drawn
from left to right leaving the "current point" at the centre of its
righthand side. Then the second [] was drawn from this point, giving
rise to the result you obtained,

If this is correct, then there is an implicit over-ride of absolute
coordinates given inside the block, by the coordinates of the current
point, in the sense that the contents of the block are drawn
"silently" using the absolute coordinates within, and then the whole
drawn block gets shifted so that its left-hand centre point is at the
current point prior to being physically drawn.

However, my interpretation above is not based on having seen any such
thing documented, merely on trying to see whether your results might
be kosher.

So, either this behaviour is a bug, or it is yet another instance
of the documentation being laconic to the point of being misleading.

One way to see whether groff is being kosher is to check whether
the same happens with a classic UNIX troff. If so, then it's OK!

I hope this helps.
Ted.

> Before anyone asks: yes, I have read the manual.
> 
> This is with GROFF 1.16.1 on Redhat Linux 6.2 for Intel.
> 
>    .PS 5in
>    [
>       move to (0,0)
>       line to (1,1) -> "A"
>    ]
>    [
>       move to (0,0)
>       line to (-1, 1) -> "B"
>    ]
>    .PE
> 
>    .PS 5in
> 
>       move to (0,0)
>       line to (1,1) -> "A"
> 
> 
>       move to (0,0)
>       line to (-1, 1) -> "B"
> 
>    .PE
> 
> Thanks,
>     S.

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

From groff-admin  Sat Nov 11 18:10:41 2000
Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA32218
	for <groff@ffii.org>; Sat, 11 Nov 2000 18:10:41 +0100
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13ueHw-0002eB-00
	for groff@ffii.org; Sat, 11 Nov 2000 17:18:00 +0000
Received: from modem-123.almaren.dialup.pol.co.uk ([62.136.102.123] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 13ueHv-0002K5-00
	for groff@ffii.org; Sat, 11 Nov 2000 17:18:00 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id RAA17438;
	Sat, 11 Nov 2000 17:17:49 GMT
Message-Id: <200011111717.RAA17438@inputplus.demon.co.uk>
To: Ted.Harding@nessie.mcc.ac.uk
cc: shaunjohnson.consultor@edinfor.edp.pt, Shaun@slugfest.demon.co.uk,
        groff@ffii.org
Subject: Re: [Groff] PIC misunderstanding? 
In-Reply-To: Message from (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk> 
   of "Sat, 11 Nov 2000 16:09:10 GMT." <XFMail.001111160910.Ted.Harding@nessie.mcc.ac.uk> 
Date: Sat, 11 Nov 2000 17:17:49 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 545
Lines: 23

Hi Ted,

> So, either this behaviour is a bug, or it is yet another instance of
> the documentation being laconic to the point of being misleading.

I don't think Eric Raymond's guide covers this either.

> One way to see whether groff is being kosher is to check whether the
> same happens with a classic UNIX troff. If so, then it's OK!

I think pic in Plan 9 does as you describe from looking at the code.

http://offworld.fac.cs.cmu.edu/plan9/source/src/cmd/pic/blockgen.c

Use 9fan/glenda to get in.

> I hope this helps.

Ditto.


Ralph.


From groff-admin  Sun Nov 12 23:28:56 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA20625
	for <groff@ffii.org>; Sun, 12 Nov 2000 23:28:56 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sun, 12 Nov 2000 23:36:13 +0100
Received: from rigel.univie.ac.at (dial-143169.HRZ.Uni-Dortmund.DE [129.217.143.169])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eACMaA000706;
	Sun, 12 Nov 2000 23:36:10 +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 UAA32015;
	Sun, 12 Nov 2000 20:45:10 +0100
Date: Sun, 12 Nov 2000 20:45:10 +0100 (CET)
Message-Id: <20001112.204510.108814407.wl@gnu.org>
To: beebe@math.utah.edu
Cc: groff@ffii.org, bwarken@mayn.de
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <CMM.0.92.0.974042694.beebe@suncore.math.utah.edu>
References: <CMM.0.92.0.974042694.beebe@suncore.math.utah.edu>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] Re: Short comment on groff-1.16.1
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 543
Lines: 23

> I notice that the latest groff doesn't support some GNU-standard
> options:
> 
> groff --version
> groff: invalid option -- -

Long options is on the TODO list; a contributor has already started
with implementing it but there was silence the last few months...

> I found that it will produce a version number like this:
> 
> groff -v
> GNU troff version 1.16.1
> 
> However, instead of exiting (the GNU standard), it hangs waiting
> for input.

Hmm, I don't see a problem to implement GNU behaviour.

Any comments from others?


    Werner

From groff-admin  Mon Nov 13 17:45:53 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA20838
	for <groff@ffii.org>; Mon, 13 Nov 2000 17:45:53 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 13 Nov 2000 17:53:08 +0100
Received: from rigel.univie.ac.at (dial-143177.HRZ.Uni-Dortmund.DE [129.217.143.177])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eADGqp803865;
	Mon, 13 Nov 2000 17:52:52 +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 RAA10022;
	Mon, 13 Nov 2000 17:50:19 +0100
Date: Mon, 13 Nov 2000 17:50:19 +0100 (CET)
Message-Id: <20001113.175019.32714776.wl@gnu.org>
To: solar@false.com
Cc: groff@ffii.org
Subject: Re: [Groff] FW: ISS Security Advisory: GNU Groff utilities read
 untrusted com mands from current working directory
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <200010132321.DAA03620@false.com>
References: <20001005.223731.37301821.wl@gnu.org>
	<200010132321.DAA03620@false.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1146
Lines: 25

> > > By default, the "troff" program reads its "troffrc"
> > > initialization file from the current working directory.  From a
> > > security standpoint, it would be desirable to restrict the
> > > searchable path for this file to the invoker's home directory
> > > and/or a trusted system.  Unfortunately, this could present
> > > problems for programs that depend on the current behavior.
> > 
> > My suggestion is to restrict the location of troffrc and
> > troffrc-end to `~' and groff's default tmac directory
> > (e.g. /usr/local/share/groff/tmac) if the -U flag isn't given.

I've now done the following: For searching and scanning troffrc and
troffrc-end, the home directory is used instead of the current
directory for the default path.  Similarly, the current directory in
the font path has been replaced with the home directory.

People can easily add the current directory again (if ever necessary)
either with using -M (resp. -F) or setting GROFF_TMAC_PATH or
GROFF_FONT_PATH.

I've just committed the changes into the CVS.  Please test and report
whether this is solution is sufficient to solve this security problem.


    Werner

From groff-admin  Mon Nov 13 18:38:56 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA21944
	for <groff@ffii.org>; Mon, 13 Nov 2000 18:38:56 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 13 Nov 2000 18:46:05 +0100
Received: from rigel.univie.ac.at (dial-143132.HRZ.Uni-Dortmund.DE [129.217.143.132])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eADHk3806548;
	Mon, 13 Nov 2000 18:46: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 SAA10105;
	Mon, 13 Nov 2000 18:25:13 +0100
Date: Mon, 13 Nov 2000 18:25:13 +0100 (CET)
Message-Id: <20001113.182513.43000841.wl@gnu.org>
To: fpolacco@debian.org
Cc: groff@ffii.org
Subject: Re: [Groff] a cool extension to tmac.an
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20000816102728.C2048@none>
References: <20000813102450.A363@none>
	<20000815.193505.41637897.sx0005@sx2.hrz.uni-dortmund.de>
	<20000816102728.C2048@none>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 306
Lines: 27

Have you received my latest improvement to man.local?


    Werner


======================================================================

.am TH
.if n \{\
.  wh 0
.  wh -1i
.  wh -.5i
.  an-header
.\}
..
.
.de an-end
.  nr % 1
.  pl +3v
.  fl
.  sp 3
.  an-p-footer
.  pl \\n[nl]u
..
.
.if n .em an-end

From groff-admin  Tue Nov 14 00:12:37 2000
Received: from moghedien.mayn.de (moghedien.mayn.de [194.145.150.43])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA27780
	for <groff@ffii.org>; Tue, 14 Nov 2000 00:12:37 +0100
Received: from altair.mayn.de (altair.mayn.de [194.145.150.157])
	by moghedien.mayn.de (8.8.8/8.8.8+NORELAY) with ESMTP id AAA12612
	for <groff@ffii.org>; Tue, 14 Nov 2000 00:17:59 +0100 (CET)
Received: (from mkb@localhost)
	by altair.mayn.de (8.11.0/8.11.0) id eADNIrR05120
	for groff@ffii.org; Tue, 14 Nov 2000 00:18:53 +0100 (CET)
Date: Tue, 14 Nov 2000 00:18:52 +0100
From: Matthias Buelow <mkb@mukappabeta.de>
To: groff list <groff@ffii.org>
Message-ID: <20001114001852.A5070@altair.mayn.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Subject: [Groff] problem with zero top margin with plain groff
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1011
Lines: 25

Hi folks,

  I've got a problem with trying to achieve a zero top and bottom
margin with plain [tg]roff (no macro package).
The problem is, that with postscript output, it'll always display
ca. 1 inch of white top margin, although to my research of various
documents, the first text line should start right at the physical
beginning of the page (troff/groff references say [tg]roff shouldn't
define any top/bottom margins by itself.)
I use A4 sized paper and explicitly give the line and paper length.
The following trivial example demonstrates the problem (I have used
groff 1.10 and 1.15 so far, I don't have 1.16 available right now):

.po 0i
.ll 20.9903c
.pl 29.7039c
foobar baz

which I format with "groff -Tps filename >filename.ps".
The problem is quite annoying, since I cannot write to the first
inch of paper and the text which normally ought to fit on the sheet
is truncated at the end of paper.  It isn't just the printer, the
problem shows up with a previewer (such as ghostview) aswell...

	--mkb

From groff-admin  Tue Nov 14 00:30:42 2000
Received: from inputplus.demon.co.uk (IDENT:root@inputplus.demon.co.uk [194.222.72.27])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA28037
	for <groff@ffii.org>; Tue, 14 Nov 2000 00:30:41 +0100
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id XAA03740;
	Mon, 13 Nov 2000 23:38:04 GMT
Message-Id: <200011132338.XAA03740@inputplus.demon.co.uk>
To: Matthias Buelow <mkb@mukappabeta.de>
cc: groff list <groff@ffii.org>
Subject: Re: [Groff] problem with zero top margin with plain groff 
In-Reply-To: Message from Matthias Buelow <mkb@mukappabeta.de> 
   of "Tue, 14 Nov 2000 00:18:52 +0100." <20001114001852.A5070@altair.mayn.de> 
Date: Mon, 13 Nov 2000 23:38:04 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 214
Lines: 15

Hi Matthias,

I don't have an answer but an observation.

> .po 0i
> .ll 20.9903c
> .pl 29.7039c
> foobar baz

Add `\u\u\u\uxxxxxx yyyyyy' and the new text gets printed in the gap at
the top of the page.


Ralph.


From groff-admin  Tue Nov 14 00:49:53 2000
Received: from moghedien.mayn.de (moghedien.mayn.de [194.145.150.43])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA28399
	for <groff@ffii.org>; Tue, 14 Nov 2000 00:49:52 +0100
Received: from altair.mayn.de (altair.mayn.de [194.145.150.157])
	by moghedien.mayn.de (8.8.8/8.8.8+NORELAY) with ESMTP id AAA12690
	for <groff@ffii.org>; Tue, 14 Nov 2000 00:55:16 +0100 (CET)
Received: (from mkb@localhost)
	by altair.mayn.de (8.11.0/8.11.0) id eADNu9U05235
	for groff@ffii.org; Tue, 14 Nov 2000 00:56:09 +0100 (CET)
Date: Tue, 14 Nov 2000 00:56:09 +0100
From: Matthias Buelow <mkb@mukappabeta.de>
To: groff list <groff@ffii.org>
Subject: Re: [Groff] problem with zero top margin with plain groff
Message-ID: <20001114005609.A5209@altair.mayn.de>
References: <mkb@mukappabeta.de> <200011132338.XAA03740@inputplus.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200011132338.XAA03740@inputplus.demon.co.uk>; from ralph@inputplus.demon.co.uk on Mon, Nov 13, 2000 at 11:38:04PM +0000
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 402
Lines: 17

Ralph Corderoy <ralph@inputplus.demon.co.uk> writes:

>I don't have an answer but an observation.
>
>> .po 0i
>> .ll 20.9903c
>> .pl 29.7039c
>> foobar baz
>
>Add `\u\u\u\uxxxxxx yyyyyy' and the new text gets printed in the gap at
>the top of the page.

Yeah, well but it only affects the current line.
All subsequent lines will be printed at their old position (\u is
local positioning only).

	--mkb

From groff-admin  Tue Nov 14 01: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 8.9.3-21) with ESMTP id BAA28839
	for <groff@ffii.org>; Tue, 14 Nov 2000 01:19:44 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 01:27:02 +0100
Received: from rigel.univie.ac.at (dial-143150.HRZ.Uni-Dortmund.DE [129.217.143.150])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAE0R0814690;
	Tue, 14 Nov 2000 01:27:01 +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 BAA10738;
	Tue, 14 Nov 2000 01:25:23 +0100
Date: Tue, 14 Nov 2000 01:25:22 +0100 (CET)
Message-Id: <20001114.012522.75783617.wl@gnu.org>
To: mkb@mukappabeta.de
Cc: groff@ffii.org
Subject: Re: [Groff] problem with zero top margin with plain groff
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20001114001852.A5070@altair.mayn.de>
References: <20001114001852.A5070@altair.mayn.de>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 418
Lines: 16

> I use A4 sized paper and explicitly give the line and paper length.
> The following trivial example demonstrates the problem (I have used
> groff 1.10 and 1.15 so far, I don't have 1.16 available right now):
> 
> .po 0i
> .ll 20.9903c
> .pl 29.7039c
> foobar baz
> 
> which I format with "groff -Tps filename >filename.ps".

Have you adjusted the paperlength to 841890 (which is A4) in
font/devps/DESC?


    Werner

From groff-admin  Tue Nov 14 01:41:36 2000
Received: from moghedien.mayn.de (moghedien.mayn.de [194.145.150.43])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id BAA29059
	for <groff@ffii.org>; Tue, 14 Nov 2000 01:41:36 +0100
Received: from altair.mayn.de (altair.mayn.de [194.145.150.157])
	by moghedien.mayn.de (8.8.8/8.8.8+NORELAY) with ESMTP id BAA12779
	for <groff@ffii.org>; Tue, 14 Nov 2000 01:47:00 +0100 (CET)
Received: (from mkb@localhost)
	by altair.mayn.de (8.11.0/8.11.0) id eAE0lrL05367
	for groff@ffii.org; Tue, 14 Nov 2000 01:47:53 +0100 (CET)
Date: Tue, 14 Nov 2000 01:47:52 +0100
From: Matthias Buelow <mkb@mukappabeta.de>
To: groff@ffii.org
Subject: Re: [Groff] problem with zero top margin with plain groff
Message-ID: <20001114014752.A5335@altair.mayn.de>
References: <20001114001852.A5070@altair.mayn.de> <20001114.012522.75783617.wl@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001114.012522.75783617.wl@gnu.org>; from wl@gnu.org on Tue, Nov 14, 2000 at 01:25:22AM +0100
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 404
Lines: 12

Werner LEMBERG <wl@gnu.org> writes:

>> I use A4 sized paper and explicitly give the line and paper length.
>Have you adjusted the paperlength to 841890 (which is A4) in
>font/devps/DESC?

Uhm, no.. I did now and it looks a lot better.
Is this the only way possible to achieve this, considering
that one might want to format on systems where one isn't allowed
to change things in /usr/share/...?

	--mkb

From groff-admin  Tue Nov 14 08:21:39 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA13902
	for <groff@ffii.org>; Tue, 14 Nov 2000 08:21:39 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 08:29:13 +0100
Received: from rigel.univie.ac.at (dial-143160.HRZ.Uni-Dortmund.DE [129.217.143.160])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAE7TB819628;
	Tue, 14 Nov 2000 08:29: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 IAA11986;
	Tue, 14 Nov 2000 08:27:49 +0100
Date: Tue, 14 Nov 2000 08:27:48 +0100 (CET)
Message-Id: <20001114.082748.35791549.wl@gnu.org>
To: mkb@mukappabeta.de
Cc: groff@ffii.org
Subject: Re: [Groff] problem with zero top margin with plain groff
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20001114014752.A5335@altair.mayn.de>
References: <20001114001852.A5070@altair.mayn.de>
	<20001114.012522.75783617.wl@gnu.org>
	<20001114014752.A5335@altair.mayn.de>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 646
Lines: 18

> >> I use A4 sized paper and explicitly give the line and paper length.
> >Have you adjusted the paperlength to 841890 (which is A4) in
> >font/devps/DESC?
> 
> Uhm, no.. I did now and it looks a lot better.  Is this the only way
> possible to achieve this, considering that one might want to format
> on systems where one isn't allowed to change things in
> /usr/share/...?

Just copy DESC to the current directory or use the -F switch to add
something to the search path.

Note that with the next groff version, the current directory will no
longer be searched by default for font stuff; instead, the home
directory is used.


    omegalambda

From groff-admin  Tue Nov 14 16:31:05 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA07448
	for <groff@ffii.org>; Tue, 14 Nov 2000 16:31:05 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 16:38:40 +0100
Received: from rigel.univie.ac.at (dial-143170.HRZ.Uni-Dortmund.DE [129.217.143.170])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAEFcb809785;
	Tue, 14 Nov 2000 16:38:38 +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 QAA13574;
	Tue, 14 Nov 2000 16:37:43 +0100
Date: Tue, 14 Nov 2000 16:37:43 +0100 (CET)
Message-Id: <20001114.163743.89124986.wl@gnu.org>
To: eliz@is.elta.co.il
Cc: groff@ffii.org
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <200005302106.AAA05817@alpha.netvision.net.il>
References: <200005281711.UAA15537@alpha.netvision.net.il>
	<20000528.222642.88335812.sx0005@gnu.org>
	<200005302106.AAA05817@alpha.netvision.net.il>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] Re: DJGPP port of Groff
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 306
Lines: 11

A few months ago you've written:

>   - `grog' errs with the file groff_tmac.5: it says Groff should be
>     called with the -me switch, which produces wrong results.  It
>     should say -man, I think.

This has been fixed now.  grog recognizes the -C option to activate
compatibility mode.


    Werner

From groff-admin  Tue Nov 14 16:31:06 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA07450
	for <groff@ffii.org>; Tue, 14 Nov 2000 16:31:06 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 16:38:42 +0100
Received: from rigel.univie.ac.at (dial-143170.HRZ.Uni-Dortmund.DE [129.217.143.170])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAEFce809788
	for <groff@ffii.org>; Tue, 14 Nov 2000 16:38:40 +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 KAA13261
	for <groff@ffii.org>; Tue, 14 Nov 2000 10:09:41 +0100
Date: Tue, 14 Nov 2000 10:09:41 +0100 (CET)
Message-Id: <20001114.100941.00446225.wl@gnu.org>
To: groff@ffii.org
From: Werner LEMBERG <wl@gnu.org>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] grog.pl peculiarities
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 647
Lines: 31

In grog.pl the following code can be found to check whether the pic
preprocessor should be called:

        ...
        elsif (/^\.PS([ 0-9.<].*)?$/) {
            if (/^\.PS\s*<\s*(\S+)/) {
                $pic++;
                $soelim++ if $level;
                &process($1, $level);
            }
            else {
                $_ = <FILE>;
                if (!/^\./ || /^\.ps/) {
                    $pic++;
                    $soelim++ if $level;
                }
            }
        }

This looks very strange.  Can somebody tell me in which macro package

  .PS <foo>

or

  .PS < foo

is used to load a pic file?


    Werner

From groff-admin  Tue Nov 14 16:31:09 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id QAA07473
	for <groff@ffii.org>; Tue, 14 Nov 2000 16:31:09 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 16:38:44 +0100
Received: from rigel.univie.ac.at (dial-143170.HRZ.Uni-Dortmund.DE [129.217.143.170])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAEFch809791;
	Tue, 14 Nov 2000 16:38:43 +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 IAA12050;
	Tue, 14 Nov 2000 08:43:57 +0100
Date: Tue, 14 Nov 2000 08:43:57 +0100 (CET)
Message-Id: <20001114.084357.85390588.wl@gnu.org>
To: mkb@mukappabeta.de
Cc: groff@ffii.org
Subject: Re: [Groff] problem with zero top margin with plain groff
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20001114.082748.35791549.wl@gnu.org>
References: <20001114.012522.75783617.wl@gnu.org>
	<20001114014752.A5335@altair.mayn.de>
	<20001114.082748.35791549.wl@gnu.org>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 388
Lines: 12

> > Uhm, no.. I did now and it looks a lot better.  Is this the only way
> > possible to achieve this, considering that one might want to format
> > on systems where one isn't allowed to change things in
> > /usr/share/...?
> 
> Just copy DESC to the current directory or use the -F switch to add
> something to the search path.

Oops!  I've meant `copy it to ./devps/DESC'.


    Werner

From groff-admin  Tue Nov 14 18:39:22 2000
Received: from mailgw2.netvision.net.il (mailgw2.netvision.net.il [194.90.1.9])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA15453
	for <groff@ffii.org>; Tue, 14 Nov 2000 18:39:19 +0100
Received: from is.elta.co.il (is.elta.co.il [199.203.121.2])
	by mailgw2.netvision.net.il (8.9.3/8.9.3) with ESMTP id TAA27026;
	Tue, 14 Nov 2000 19:47:09 +0200 (IST)
Received: from is (is [199.203.121.2])
	by is.elta.co.il (8.9.3/8.8.8) with SMTP id TAA13875;
	Tue, 14 Nov 2000 19:45:32 +0200 (IST)
Date: Tue, 14 Nov 2000 19:45:32 +0200 (IST)
From: Eli Zaretskii <eliz@is.elta.co.il>
X-Sender: eliz@is
To: Werner LEMBERG <wl@gnu.org>
cc: groff@ffii.org
In-Reply-To: <20001114.163743.89124986.wl@gnu.org>
Message-ID: <Pine.SUN.3.91.1001114194510.13683C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] Re: DJGPP port of Groff
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 324
Lines: 10

On Tue, 14 Nov 2000, Werner LEMBERG wrote:

> >   - `grog' errs with the file groff_tmac.5: it says Groff should be
> >     called with the -me switch, which produces wrong results.  It
> >     should say -man, I think.
> 
> This has been fixed now.  grog recognizes the -C option to activate
> compatibility mode.

Thanks!

From groff-admin  Tue Nov 14 21:37:00 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA23479
	for <groff@ffii.org>; Tue, 14 Nov 2000 21:36:59 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 21:44:24 +0100
Received: from rigel.univie.ac.at (dial-143167.HRZ.Uni-Dortmund.DE [129.217.143.167])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAEKiL817799;
	Tue, 14 Nov 2000 21:44: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 VAA15525;
	Tue, 14 Nov 2000 21:41:26 +0100
Date: Tue, 14 Nov 2000 21:41:26 +0100 (CET)
Message-Id: <20001114.214126.133918232.wl@gnu.org>
To: jsnader@ix.netcom.com
Cc: Ted.Harding@nessie.mcc.ac.uk, ljs@uk2.net, groff@ffii.org
Subject: Re: [Groff] pic solid attribute
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20000731063719.B348@ix.netcom.com>
References: <20000722121511.A1148@TK212017118241.teleweb.at>
	<XFMail.000722132322.Ted.Harding@nessie.mcc.ac.uk>
	<20000731063719.B348@ix.netcom.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 656
Lines: 24

Another old mail...

From: Jon Snader <jsnader@ix.netcom.com>
Subject: Re: [Groff] pic solid attribute
Date: Mon, 31 Jul 2000 06:37:19 -0400

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

I've added it to pic.


    Werner

From groff-admin  Tue Nov 14 21:37:11 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA23497
	for <groff@ffii.org>; Tue, 14 Nov 2000 21:37:11 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 14 Nov 2000 21:44:42 +0100
Received: from rigel.univie.ac.at (dial-143167.HRZ.Uni-Dortmund.DE [129.217.143.167])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAEKiY817805;
	Tue, 14 Nov 2000 21:44: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 SAA13854;
	Tue, 14 Nov 2000 18:09:04 +0100
Date: Tue, 14 Nov 2000 18:09:03 +0100 (CET)
Message-Id: <20001114.180903.66337899.wl@gnu.org>
To: provinsd@enf403-2.ensu.ucalgary.ca
Cc: groff@ffii.org
Subject: Re: [Groff] String editing?
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <m12JIp2-000050C@enf403-2.ensu.ucalgary.ca>
References: <20000211083112X.sx0005@sx2.hrz.uni-dortmund.de>
	<m12JIp2-000050C@enf403-2.ensu.ucalgary.ca>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 495
Lines: 18

Reading again old mails...


From: provinsd@enf403-2.ensu.ucalgary.ca (Dean Allen Provins)
Subject: Re: [Groff] String editing?
Date: Fri, 11 Feb 2000 09:21:32 -0700 (MST)

> Would you also consider adding a macro which returns TRUE or FALSE
> if the string is a numeric (optionally preceded by a plus or minus
> sign) or not?

troff now has the \B'xxx' escape which expands to 1 or 0 according as
xxx is or is not a valid numeric expression.

This should be exactly what you need.


    Werner

From groff-admin  Tue Nov 14 22:20:14 2000
Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA25274
	for <groff@ffii.org>; Tue, 14 Nov 2000 22:20:13 +0100
Received: from beta by smtp.hccnet.nl
	via uds146-120.dial.hccnet.nl [193.173.120.146] with SMTP
	id WAA18243 (8.8.5/1.13); Tue, 14 Nov 2000 22:27:50 +0100 (MET)
Message-ID: <008101c04e81$bd7b5c60$9278adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: "Djgpp Announce" <djgpp-announce@delorie.com>,
        "Groff list" <groff@ffii.org>,
        "Ted Harding" <Ted.Harding@nessie.mcc.ac.uk>
Date: Tue, 14 Nov 2000 22:27:47 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [Groff] grap  for ms-dos and win32
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 346
Lines: 11

Grap version 1.10 compiled with DJGPP is available from
ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2apps/
and its mirrors.
It works on MS-DOS and all Win32-systems (Win95, Win98, WinNT), and can be used as preprocessor
for the DJGPP-version of Groff-1.16, available from
ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/

Kees Zeelenberg




From groff-admin  Wed Nov 15 09:59:43 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA25243
	for <groff@ffii.org>; Wed, 15 Nov 2000 09:59:43 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 15 Nov 2000 10:07:13 +0100
Received: from rigel.univie.ac.at (dial-143131.HRZ.Uni-Dortmund.DE [129.217.143.131])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAF975802276;
	Wed, 15 Nov 2000 10:07: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 KAA17645;
	Wed, 15 Nov 2000 10:06:06 +0100
Date: Wed, 15 Nov 2000 10:06:06 +0100 (CET)
Message-Id: <20001115.100606.73645361.wl@gnu.org>
To: c.zeelenberg@hccnet.nl
Cc: groff@ffii.org
Subject: Re: [Groff] grap for ms-dos and win32
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <008101c04e81$bd7b5c60$9278adc1@beta>
References: <008101c04e81$bd7b5c60$9278adc1@beta>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 98
Lines: 6

> ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2apps/

Added to MORE.STUFF, thanks.


    Werner

From groff-admin  Fri Nov 17 09:00:38 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03070
	for <groff@ffii.org>; Fri, 17 Nov 2000 09:00:37 +0100
Received: from david.siemens.de ([192.35.17.14])
	by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
	id 13wgZU-00033D-00
	for <groff@gnu.org>; Fri, 17 Nov 2000 03:08:33 -0500
X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by david.siemens.de (8.11.0/8.11.0) with ESMTP id eAH88Ru26037
	for <groff@gnu.org>; Fri, 17 Nov 2000 09:08:28 +0100 (MET)
Received: from MOWD019A.mow.siemens.ru ([139.24.18.3])
	by mail3.siemens.de (8.11.1/8.11.1) with ESMTP id eAH88Qk1380487
	for <groff@gnu.org>; Fri, 17 Nov 2000 09:08:27 +0100 (MET)
Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id XBHM2X6B; Fri, 17 Nov 2000 11:15:05 +0300
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <groff@gnu.org>
Date: Fri, 17 Nov 2000 11:08:26 +0300
Message-ID: <000601c0506d$8fd9d910$21c9ca95@mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Subject: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 498
Lines: 14

I'm using Mandrake 7.2 with russian KOI8-R locale set. Somewhat unexpectedly I
discovered, that even in english manual pages there are sometimes characters
from the upper half - obviously, of ISO-8859-1. Example is hyphenation
character at the end of line - that is, sigh, shown as some pseudo-grafik
symbol in my case.

Is there any way to configure groff to _not_ assume that ISO-8859-1 is in use?
Preferably with some parameters - I do not want to recompile it.

-andrej

Have a nice DOS!
B >>


From groff-admin  Fri Nov 17 21:15:07 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA14368
	for <groff@ffii.org>; Fri, 17 Nov 2000 21:15:06 +0100
Received: from nx5.hrz.uni-dortmund.de ([129.217.131.21])
	by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
	id 13ws2D-0000lf-00
	for <groff@gnu.org>; Fri, 17 Nov 2000 15:22:58 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 17 Nov 2000 21:22:26 +0100
Received: from rigel.univie.ac.at (dial-143190.HRZ.Uni-Dortmund.DE [129.217.143.190])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAHKMO827428;
	Fri, 17 Nov 2000 21:22: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 KAA06257;
	Fri, 17 Nov 2000 10:02:36 +0100
Date: Fri, 17 Nov 2000 10:02:36 +0100 (CET)
Message-Id: <20001117.100236.78702681.wl@gnu.org>
To: Andrej.Borsenkow@mow.siemens.ru
Cc: groff@gnu.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <000601c0506d$8fd9d910$21c9ca95@mow.siemens.ru>
References: <000601c0506d$8fd9d910$21c9ca95@mow.siemens.ru>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 545
Lines: 14

> Is there any way to configure groff to _not_ assume that ISO-8859-1
> is in use?  Preferably with some parameters - I do not want to
> recompile it.

Not yet.  It is still hard-coded, unfortunately.  I've got a patch
which adds an `ascii8' device to avoid this dependency, and I will
eventually include that (or probably find a different solution).

For the moment, I suggest to use the .shc request to assign a
different character to the soft hyphen character, in case this is the
only problem you have.  Otherwise, use -Tascii.


    Werner

From groff-admin  Sun Nov 19 06:49:15 2000
Received: from mailgw3.netvision.net.il (mailgw3.netvision.net.il [194.90.1.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id GAA22430
	for <groff@ffii.org>; Sun, 19 Nov 2000 06:49:13 +0100
Received: from is.elta.co.il (is.elta.co.il [199.203.121.2])
	by mailgw3.netvision.net.il (8.9.3/8.9.3) with ESMTP id HAA23214;
	Sun, 19 Nov 2000 07:56:13 +0200 (IST)
Received: from is (is [199.203.121.2])
	by is.elta.co.il (8.9.3/8.8.8) with SMTP id HAA11570;
	Sun, 19 Nov 2000 07:55:48 +0200 (IST)
Date: Sun, 19 Nov 2000 07:55:48 +0200 (IST)
From: Eli Zaretskii <eliz@is.elta.co.il>
X-Sender: eliz@is
To: Kees Zeelenberg <c.zeelenberg@hccnet.nl>
cc: djgpp@delorie.com, Groff list <groff@ffii.org>,
        Ted Harding <Ted.Harding@nessie.mcc.ac.uk>
In-Reply-To: <200011142143.QAA13075@delorie.com>
Message-ID: <Pine.SUN.3.91.1001119074810.11507B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] Re: grap for ms-dos and win32
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 692
Lines: 20

On Tue, 14 Nov 2000, Kees Zeelenberg wrote:

> Grap version 1.10 compiled with DJGPP is available from
> ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2apps/
> and its mirrors.

Thanks!

Allow me a few comments on the packaging.

 - You should not put anything in the top-level directory.  Files like 
   COPYRIGH.gra, README.gra, etc., should unzip into the directory 
   specific for the package, in this case either contrib/grap-1.10 or 
   gnu/grap-1.10.

 - Likewise, you should not put anything under the share/ directory 
   except files required by Grap at run time.  Files like grap.man should 
   go to other places (in this case, man/man1).

Thanks again for working on this port.

From groff-admin  Mon Nov 20 09:15:55 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA00536
	for <groff@ffii.org>; Mon, 20 Nov 2000 09:15:52 +0100
Received: from goliath.siemens.de ([194.138.37.131])
	by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
	id 13xlds-0000Np-00; Mon, 20 Nov 2000 02:45:32 -0500
X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id eAK7jUl29559;
	Mon, 20 Nov 2000 08:45:30 +0100 (MET)
Received: from MOWD019A.mow.siemens.ru ([139.24.18.3])
	by mail3.siemens.de (8.11.1/8.11.1) with ESMTP id eAK7jSj1966426;
	Mon, 20 Nov 2000 08:45:29 +0100 (MET)
Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id XBHM2686; Mon, 20 Nov 2000 10:52:12 +0300
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Werner LEMBERG" <wl@gnu.org>
Cc: <groff@gnu.org>
Subject: RE: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Date: Mon, 20 Nov 2000 10:45:28 +0300
Message-ID: <001701c052c5$d9b72fb0$21c9ca95@mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <20001117.100236.78702681.wl@gnu.org>
Importance: Normal
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1557
Lines: 41

>
>
> > Is there any way to configure groff to _not_ assume that ISO-8859-1
> > is in use?  Preferably with some parameters - I do not want to
> > recompile it.
>
> Not yet.  It is still hard-coded, unfortunately.  I've got a patch
> which adds an `ascii8' device to avoid this dependency, and I will
> eventually include that (or probably find a different solution).
>

Yes, I came to the same idea finally.

> For the moment, I suggest to use the .shc request to assign a
> different character to the soft hyphen character, in case this is the
> only problem you have.  Otherwise, use -Tascii.
>

Unfortunately, -Tascii completely screws up russian man pages :-) So, I assume
I can put up with hyphen problem - it seems like the only one. Ideally, shc
should be set contdionally depending on currentl locale.

But speaking about man pages and i18n - there is more about.

Russian words in average are longer than English (the same applies to German,
BTW :-) and without hyphenation display loks ugly, with several words and
large inter-words gaps. I assume, we could find hypehnation table in TeX, just
as for english - but here are some problems.

Currently, hyphenation table for US is uncondtitionally loaded. Is it possible
to load more than one table, like Russian?

Second, there are three widely used russian charsets and one "standard" one.
Is it possible to access current locale in troffrc? Given possible variety of
locale names, something like locale alias table looks reasonable. I may try to
implement something like this.

cheers

-andrej


From groff-admin  Mon Nov 20 10:58:47 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA01730
	for <groff@ffii.org>; Mon, 20 Nov 2000 10:58:46 +0100
Received: from surfchem0.riken.go.jp ([134.160.25.161])
	by fencepost.gnu.org with smtp (Exim 3.16 #1 (Debian))
	id 13xnoU-0003hO-00
	for <groff@gnu.org>; Mon, 20 Nov 2000 05:04:39 -0500
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 7D30C1C173
	for <groff@gnu.org>; Mon, 20 Nov 2000 19:08:58 +0900 (JST)
Date: Mon, 20 Nov 2000 19:08:54 +0900
Message-ID: <87zoivdkg9.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@gnu.org
Subject: RE: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Mon, 20 Nov 2000 10:45:28 +0300"
	<001701c052c5$d9b72fb0$21c9ca95@mow.siemens.ru>
References: <20001117.100236.78702681.wl@gnu.org>
	<001701c052c5$d9b72fb0$21c9ca95@mow.siemens.ru>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2574
Lines: 66

Hi,

At Mon, 20 Nov 2000 10:45:28 +0300,
Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru> wrote:

> > Not yet.  It is still hard-coded, unfortunately.  I've got a patch
> > which adds an `ascii8' device to avoid this dependency, and I will
> > eventually include that (or probably find a different solution).
> >
> 
> Yes, I came to the same idea finally.

I am glad my patch is so diffusing :-)  (I at first wrote the ascii8
patch for 'groff' package of Debian GNU/Linux distribution).

> But speaking about man pages and i18n - there is more about.

Ok, I am interested in i18n.

(BTW, please read my document on i18n in Debian Documentation Project
http://www.debian.org/doc/manuals/intro-i18n/ which is in great 
rewriting now.)


> Russian words in average are longer than English (the same applies to German,
> BTW :-) and without hyphenation display loks ugly, with several words and
> large inter-words gaps. I assume, we could find hypehnation table in TeX, just
> as for english - but here are some problems.
> 
> Currently, hyphenation table for US is uncondtitionally loaded. Is it possible
> to load more than one table, like Russian?

I can imagine a mechanism, which switches hyphenation rules and other
orthography rules by 'language tag' in the roff source.  (Please note
I am not familiar with the source code of GNU roff!  I am just talking
about a general algorithm.)


> Second, there are three widely used russian charsets and one "standard" one.
> Is it possible to access current locale in troffrc? Given possible variety of
> locale names, something like locale alias table looks reasonable. I may try to
> implement something like this.

I am now working on this problem.  Werner and I discussed on this problem
and concluded:
 - troff, the main typesetting engine, recognizes only UTF-8.
 - preprocessor and postprocessor will be supplied which convert
   encoding between encodings determined by the locale and UTF-8.

The encoding can be written in the roff source or by command line option.

However, I think the idea of 'troffrc' is not nice.  If all softwares
you are using would follow this idea, you will have to edit thousands
of 'rc' files for all softwares.  ISO C determines a nice way: 
LC_ALL, LC_CTYPE, and LANG environmental variables determine the 
encoding.

The discussion is found at:
http://ffii.org/archive/mails/groff/2000/Oct/0056.html

You can find the first version of preprocessor at:
http://ffii.org/archive/mails/groff/2000/Nov/0013.html

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Mon Nov 20 12:23:15 2000
Received: from clyde.ref.collins.co.uk (clyde.ref.collins.co.uk [192.153.153.29])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA02928
	for <groff@ffii.org>; Mon, 20 Nov 2000 12:23:13 +0100
Received: from ref.collins.co.uk (helmsdale [193.119.38.15])
	by clyde.ref.collins.co.uk (8.9.3/8.9.3) with ESMTP id LAA10021
	for <groff@ffii.org>; Mon, 20 Nov 2000 11:29:06 GMT
Received: from ref.collins.co.uk (localhost [127.0.0.1])
	by ref.collins.co.uk (8.9.3+Sun/8.9.1) with ESMTP id LAA02396
	for <groff@ffii.org>; Mon, 20 Nov 2000 11:28:09 GMT
Message-ID: <3A190AC9.DBD6FB3A@ref.collins.co.uk>
Date: Mon, 20 Nov 2000 11:28:09 +0000
From: "Stewart C. Russell" <stewart@ref.collins.co.uk>
Organization: HarperCollins Publishers, Bilingual Division
X-Mailer: Mozilla 4.6 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: groff@ffii.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 166
Lines: 7

Tomohiro KUBOTA wrote:
>
> However, I think the idea of 'troffrc' is not nice.

This is the main problem with lout; it can have user-specified
initialisation.
Bleah!

From groff-admin  Mon Nov 20 14:31:05 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id OAA04503
	for <groff@ffii.org>; Mon, 20 Nov 2000 14:31:05 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 20 Nov 2000 14:36:43 +0100
Received: from rigel.univie.ac.at (dial-143134.HRZ.Uni-Dortmund.DE [129.217.143.134])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAKDaf815729;
	Mon, 20 Nov 2000 14:36: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 JAA10526;
	Mon, 20 Nov 2000 09:34:20 +0100
Date: Mon, 20 Nov 2000 09:34:20 +0100 (CET)
Message-Id: <20001120.093420.125904003.wl@gnu.org>
To: Ted.Harding@nessie.mcc.ac.uk
Cc: groff@ffii.org
Subject: Re: [Groff] .di behaviour
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <XFMail.001020003706.Ted.Harding@nessie.mcc.ac.uk>
References: <20001018.120127.43003101.wl@gnu.org>
	<XFMail.001020003706.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 933
Lines: 47

> The implication is that if you want the entire contents of the
> diversion body to be kept together and output at the point where the
> diversion macro is called, then it is wise to begin the diversion
> with a ".br" and also to end it with a ".br".

I have to correct myself.  The example I gave is wrong.  It is *not*
possible to do

  aaa
  .
  .di xxx
  .br
  ccc
  .br
  .di
  .
  bbb
  \*[xxx]

    => bbb aaa ccc


since the first `.br' has no effect at all (thus the diversion
contains `aaa ccc'.  Consequence: A diversion *always* includes the
last partial line.  I consider this very unfortunate.

My idea is to introduce a new request similar to .di which does not
have this restriction.  I want something similar to a TeX box:

  aaa
  .
  .box xxx
  ccc
  .box
  .
  bbb
  \*[xxx]

    => aaa bbb ccc

It is easy to add -- such code already exists to implement the \w
escape sequence.

What do you think?


    Werner

From groff-admin  Mon Nov 20 15:01:19 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id PAA04974
	for <groff@ffii.org>; Mon, 20 Nov 2000 15:01:18 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 5FC7C1C173
	for <groff@ffii.org>; Mon, 20 Nov 2000 23:11:39 +0900 (JST)
Date: Mon, 20 Nov 2000 23:11:34 +0900
Message-ID: <87wvdyens9.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Mon, 20 Nov 2000 11:28:09 +0000"
	<3A190AC9.DBD6FB3A@ref.collins.co.uk>
References: <3A190AC9.DBD6FB3A@ref.collins.co.uk>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2303
Lines: 64

Hi,

At Mon, 20 Nov 2000 11:28:09 +0000,
Stewart C. Russell <stewart@ref.collins.co.uk> wrote:

> > However, I think the idea of 'troffrc' is not nice.
> 
> This is the main problem with lout; it can have user-specified
> initialisation.
> Bleah!

I cannot understand your point.

The problem is how to determine the encoding of roff source and
tty output.

I thought Andrej proposed to use troffrc.  A user who want to use
KOI8-R encoding can write something in troffrc file.  A user who
want to use EUC-JP encoding can write something in troffrc file.

However, in such a method, a user would have to edit foorc, barrc,
and so on so on besides troffrc, since the user uses softwares of
foo, bar, and so on so on besides troff.  This is troublesome.
Instead, all softwares should work properly with setting LANG
variable.  This is the point I wrote in the last mail.

Thus, I insist _no_ configuration should be needed specially for Groff
to select proper encoding.

Or, do you say you have a good idea to achieve this by writing
something in troffrc file in the Groff distribution archive,
without using C functions such as setlocale() and so on?
I cannot imagine it.


Andrej wrote:
> Is it possible to access current locale in troffrc? Given possible variety of
> locale names, something like locale alias table looks reasonable. I may try to
> implement something like this.

No need for such a table.  Even, no need for accessing the current
locale in troffrc.  The following code will give the encoding.

   setlocale(LC_CTYPE, "");
   char * encoding = nl_langinfo(CODESET);

The value can be used for open_iconv() to convert into UTF-8 in the
preprocessor.

Ok, we have to wait for UTF-8-enabled troff and pre/postprocessor.

Note that Groff is often used to format manpages. Since manpages are
supplied by the vendor, encoding of the manpages is independent on
the current locale.  For example, the following situations are very
likely:
 - read Russian KOI8-R manpages in Russian UTF-8 locale
 - read English ASCII manpages in Russian KOI8-R locale
Thus my preprocessor will have a method that the manpages can have 
information on their own encodings.  This will override the encoding 
decided by current locale.

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Mon Nov 20 18:35:29 2000
Received: from hsh ([211.104.46.232])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id SAA07735
	for <groff@ffii.org>; Mon, 20 Nov 2000 18:35:27 +0100
Message-Id: <200011201735.SAA07735@genba.ffii.org>
X-Authentication-Warning: genba.ffii.org: Host [211.104.46.232] claimed to be hsh
From: "이영섭." <joinda1@hotmail.com>
To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-2022-kr"
Date: Tue, 21 Nov 2000 02:32:52
Subject: [Groff] 안녕하세요 groff@ffii.org님
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 6006
Lines: 85

<html>

<head>
<meta http-equiv="Content-Language" content="ko">
<meta http-equiv="Content-Type" content="text/html; charset=ks_c_5601-1987">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>안녕하세요</title>
</head>

<body>

<p><b><font size="4">제게 메일을 보내실때는 꼭 <A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A>으로    
보내주세요</font></b></p>   
<hr width="70%" align="left" >
   
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px"> 안녕하세요   
groff@ffii.org님...</span></strong></font></p>    
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">우연히 http://www.kr.gnu.org/software에 방문했다가 제      
나름대로 이 정보가 서로에게</span></strong></font></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">도움이 될수있다고      
생각되기에 이렇게 메일을 드려봅니다.</span></strong></font></p>     
<p align="left"><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">기분 상하셨다면      
죄송하구요. 넓은 마음으로 이해 바랍니다.</span></strong></font></p>    
<p align="left"><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">그리고,     
요즘 날씨도 추운데 감기 조심하시구요</span></strong></font></p>    
<p align="left"><span style="LETTER-SPACING: 0px"><strong><font size="4" face="굴림">건강     
하시고 하시는 일 잘 되시길</font></strong> <strong><font size="4" face="굴림">바랍니다.</font></strong></span></p>    
<p align="left"><strong><font size="4" face="굴림"><span style="LETTER-SPACING: 0px">하지만 아래 사항은      
분명한 사실임을 약속드립니다.</span></font></strong></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">기타    
문의사항은 </span></strong></font><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px"><A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A>    
으로 메일을 주시면 언제든</span></strong></font></p>   
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">자세히     
알려드리겠습니다.</span></strong></font></p>    
<hr width="70%" align="left"><b><span style="LETTER-SPACING: 0px"><font face="견고딕" color="#0000ff" size="4">
<P><STRONG><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff face=견고딕 
size=4>*전기요금 인상 걱정 마세요</FONT><FONT color=#ff0000 face=견고딕 size=4>-</FONT><FONT 
color=#ff0000 face=견고딕 size=4>전기를 10~30% 절약할 수 
있습니다.</FONT></SPAN></B></STRONG></P>
<P><STRONG><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff face=견고딕 
size=4>*유해 전자파 걱정하지 마세요</FONT><FONT color=#ff0000 face=견고딕 size=4>-전자파를 차단시킬 수 
있습니다.</FONT></SPAN></B></STRONG></P>
<P>      
 </font></span></b><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff 
face=견고딕 size=4>*저희 제품에 관심이 있으신분은 누구라도 환영합니다 [개인딜러 환영]</FONT></SPAN></B></P>   
<p><font color="#ff0000" size="6" face="견고딕"><b><span style="LETTER-SPACING: 0px">100% 환불 및 교환을      
해 드립니다.</span></b></font></p>    
<p><font face="견고딕" color="#0000ff" size="4"><b><span style="LETTER-SPACING: 0px"><span style="LETTER-SPACING: 0px">전국 어디나 직접      
배달 설치를 해드립니다.(단 지방은 5개이상)</span></span></b></font></p><b><span style="LETTER-SPACING: 0px"><font face="신그래픽" size="5" color="#ff0066">
<P><FONT color=#0000ff size=4>간단히 전기소켓에 꽂아만 주시면 됩니다</FONT></P>     
      </font></span></b>
<P><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#ff0066 face=신그래픽 size=5>*가격 
: 가정용 55000원 , 업소용 : 99000원</FONT><font face="신그래픽" size="4">　</font></SPAN></B></P>    
<p><strong><b><span style="LETTER-SPACING: 0px"><font face="견고딕" size="4" color="#0000ff">      
 </font></span></b></strong>&nbsp;</p>
<P><FONT face=굴림 size=4><STRONG><SPAN style="LETTER-SPACING: 0px">그 외에  
<FONT color=#ff0000>다양한 기능이 </FONT>있지만 이정도만 
하겠습니다.</SPAN></STRONG></FONT></P>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">자세한 사항은&nbsp; 
아래 사이트에서 직접 눈으로 확인해 보세요</span></strong></font></p>     
<p><font size="4" face="굴림"><span style="LETTER-SPACING: 0px"><strong>또한 <font color="#0000ff">검색어</font>를 "<font color="#ff0000"></strong><b>슈퍼에너지</b><strong>"</strong></font><strong>라고      
치시면 많은 정보를 찾으실 수 있으며</strong></SPAN></FONT></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">각종 <font color="#ff0000">일간지      
및 KBS 9시 뉴스</font>에 방영 되었습니다.</span></strong></font></p>     
<p></p>    
<p><a href="http://203.248.251.56/asx.cgi?title=KBS뉴스&amp;url=2000$05$24$230"><span style="LETTER-SPACING: 0px"><b><font size="4">동영상보기</font></b></span></a>     
 <font size="4"><b><span style="LETTER-SPACING: 0px"><font face="견고딕" color="#0000ff">[KBS 9시 뉴스]</font>&nbsp; 관련     
사이트 : <a href="http://www.spenergy.com/">http://www.spenergy.com/</a> 외     
다수</span></b></font></p>    
<p><font face="견고딕" size="3"><strong><span style="LETTER-SPACING: 0px">       
</span></strong></font>&nbsp;</p>    
<p><font face="견고딕" size="3"><strong><span style="LETTER-SPACING: 0px">상담및 
문의처 :&nbsp;슈퍼에너지 인터넷 사업부&nbsp;&nbsp;&nbsp;&nbsp;</p></SPAN></STRONG></FONT>     
<p><strong><font face="굴림"><span style="LETTER-SPACING: 0px">  02-744-0209 <FONT color=#0000ff  
size=4>협력업체 모집중(개인도 가능)</FONT>  </span></font></strong></p>
<P><FONT face=굴림><STRONG>현재 전화량이 많아 통화가 않될때는 음성메세지로 연락처를 
남겨주시거나</STRONG></FONT></P>
<P><FONT face=굴림><STRONG>메일로 연락처를 알려주시면 바로 연락을 드리겠습니다.</STRONG></FONT></P>     
<p><strong><font face="굴림"><span style="LETTER-SPACING: 0px"><FONT color=#0000ff size=4>&nbsp;&nbsp; </FONT> <A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A></span></font></strong></p>     
<p>&nbsp;</p>    
    
</body>    
    
</html>    

From groff-admin  Mon Nov 20 18:36:02 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA07776
	for <groff@ffii.org>; Mon, 20 Nov 2000 18:36:01 +0100
Received: from [211.104.46.232] (helo=hsh)
	by fencepost.gnu.org with smtp (Exim 3.16 #1 (Debian))
	id 13xuwn-0002vM-00
	for <groff@gnu.org>; Mon, 20 Nov 2000 12:41:43 -0500
From: "이영섭." <joinda1@hotmail.com>
To: groff@gnu.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-2022-kr"
Date: Tue, 21 Nov 2000 02:33:07
Message-Id: <E13xuwn-0002vM-00@fencepost.gnu.org>
Subject: [Groff] 안녕하세요 groff@gnu.org님
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 6005
Lines: 85

<html>

<head>
<meta http-equiv="Content-Language" content="ko">
<meta http-equiv="Content-Type" content="text/html; charset=ks_c_5601-1987">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>안녕하세요</title>
</head>

<body>

<p><b><font size="4">제게 메일을 보내실때는 꼭 <A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A>으로    
보내주세요</font></b></p>   
<hr width="70%" align="left" >
   
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px"> 안녕하세요   
groff@gnu.org님...</span></strong></font></p>    
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">우연히 http://www.kr.gnu.org/software에 방문했다가 제      
나름대로 이 정보가 서로에게</span></strong></font></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">도움이 될수있다고      
생각되기에 이렇게 메일을 드려봅니다.</span></strong></font></p>     
<p align="left"><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">기분 상하셨다면      
죄송하구요. 넓은 마음으로 이해 바랍니다.</span></strong></font></p>    
<p align="left"><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">그리고,     
요즘 날씨도 추운데 감기 조심하시구요</span></strong></font></p>    
<p align="left"><span style="LETTER-SPACING: 0px"><strong><font size="4" face="굴림">건강     
하시고 하시는 일 잘 되시길</font></strong> <strong><font size="4" face="굴림">바랍니다.</font></strong></span></p>    
<p align="left"><strong><font size="4" face="굴림"><span style="LETTER-SPACING: 0px">하지만 아래 사항은      
분명한 사실임을 약속드립니다.</span></font></strong></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">기타    
문의사항은 </span></strong></font><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px"><A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A>    
으로 메일을 주시면 언제든</span></strong></font></p>   
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">자세히     
알려드리겠습니다.</span></strong></font></p>    
<hr width="70%" align="left"><b><span style="LETTER-SPACING: 0px"><font face="견고딕" color="#0000ff" size="4">
<P><STRONG><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff face=견고딕 
size=4>*전기요금 인상 걱정 마세요</FONT><FONT color=#ff0000 face=견고딕 size=4>-</FONT><FONT 
color=#ff0000 face=견고딕 size=4>전기를 10~30% 절약할 수 
있습니다.</FONT></SPAN></B></STRONG></P>
<P><STRONG><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff face=견고딕 
size=4>*유해 전자파 걱정하지 마세요</FONT><FONT color=#ff0000 face=견고딕 size=4>-전자파를 차단시킬 수 
있습니다.</FONT></SPAN></B></STRONG></P>
<P>      
 </font></span></b><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#0000ff 
face=견고딕 size=4>*저희 제품에 관심이 있으신분은 누구라도 환영합니다 [개인딜러 환영]</FONT></SPAN></B></P>   
<p><font color="#ff0000" size="6" face="견고딕"><b><span style="LETTER-SPACING: 0px">100% 환불 및 교환을      
해 드립니다.</span></b></font></p>    
<p><font face="견고딕" color="#0000ff" size="4"><b><span style="LETTER-SPACING: 0px"><span style="LETTER-SPACING: 0px">전국 어디나 직접      
배달 설치를 해드립니다.(단 지방은 5개이상)</span></span></b></font></p><b><span style="LETTER-SPACING: 0px"><font face="신그래픽" size="5" color="#ff0066">
<P><FONT color=#0000ff size=4>간단히 전기소켓에 꽂아만 주시면 됩니다</FONT></P>     
      </font></span></b>
<P><B><SPAN style="LETTER-SPACING: 0px"><FONT color=#ff0066 face=신그래픽 size=5>*가격 
: 가정용 55000원 , 업소용 : 99000원</FONT><font face="신그래픽" size="4">　</font></SPAN></B></P>    
<p><strong><b><span style="LETTER-SPACING: 0px"><font face="견고딕" size="4" color="#0000ff">      
 </font></span></b></strong>&nbsp;</p>
<P><FONT face=굴림 size=4><STRONG><SPAN style="LETTER-SPACING: 0px">그 외에  
<FONT color=#ff0000>다양한 기능이 </FONT>있지만 이정도만 
하겠습니다.</SPAN></STRONG></FONT></P>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">자세한 사항은&nbsp; 
아래 사이트에서 직접 눈으로 확인해 보세요</span></strong></font></p>     
<p><font size="4" face="굴림"><span style="LETTER-SPACING: 0px"><strong>또한 <font color="#0000ff">검색어</font>를 "<font color="#ff0000"></strong><b>슈퍼에너지</b><strong>"</strong></font><strong>라고      
치시면 많은 정보를 찾으실 수 있으며</strong></SPAN></FONT></p>     
<p><font size="4" face="굴림"><strong><span style="LETTER-SPACING: 0px">각종 <font color="#ff0000">일간지      
및 KBS 9시 뉴스</font>에 방영 되었습니다.</span></strong></font></p>     
<p></p>    
<p><a href="http://203.248.251.56/asx.cgi?title=KBS뉴스&amp;url=2000$05$24$230"><span style="LETTER-SPACING: 0px"><b><font size="4">동영상보기</font></b></span></a>     
 <font size="4"><b><span style="LETTER-SPACING: 0px"><font face="견고딕" color="#0000ff">[KBS 9시 뉴스]</font>&nbsp; 관련     
사이트 : <a href="http://www.spenergy.com/">http://www.spenergy.com/</a> 외     
다수</span></b></font></p>    
<p><font face="견고딕" size="3"><strong><span style="LETTER-SPACING: 0px">       
</span></strong></font>&nbsp;</p>    
<p><font face="견고딕" size="3"><strong><span style="LETTER-SPACING: 0px">상담및 
문의처 :&nbsp;슈퍼에너지 인터넷 사업부&nbsp;&nbsp;&nbsp;&nbsp;</p></SPAN></STRONG></FONT>     
<p><strong><font face="굴림"><span style="LETTER-SPACING: 0px">  02-744-0209 <FONT color=#0000ff  
size=4>협력업체 모집중(개인도 가능)</FONT>  </span></font></strong></p>
<P><FONT face=굴림><STRONG>현재 전화량이 많아 통화가 않될때는 음성메세지로 연락처를 
남겨주시거나</STRONG></FONT></P>
<P><FONT face=굴림><STRONG>메일로 연락처를 알려주시면 바로 연락을 드리겠습니다.</STRONG></FONT></P>     
<p><strong><font face="굴림"><span style="LETTER-SPACING: 0px"><FONT color=#0000ff size=4>&nbsp;&nbsp; </FONT> <A href="mailto:stopbus@hitel.net">stopbus@hitel.net</A></span></font></strong></p>     
<p>&nbsp;</p>    
    
</body>    
    
</html>    

From groff-admin  Mon Nov 20 21:42:51 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA13169
	for <groff@ffii.org>; Mon, 20 Nov 2000 21:42:50 +0100
Received: from nx5.hrz.uni-dortmund.de ([129.217.131.21])
	by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
	id 13xxrr-0007xv-00
	for <groff@gnu.org>; Mon, 20 Nov 2000 15:48:48 -0500
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 20 Nov 2000 21:48:20 +0100
Received: from rigel.univie.ac.at (dial-143133.HRZ.Uni-Dortmund.DE [129.217.143.133])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAKKmI805161;
	Mon, 20 Nov 2000 21:48:18 +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 VAA10774;
	Mon, 20 Nov 2000 21:46:43 +0100
Date: Mon, 20 Nov 2000 21:46:42 +0100 (CET)
Message-Id: <20001120.214642.23009004.wl@gnu.org>
To: Andrej.Borsenkow@mow.siemens.ru
Cc: groff@gnu.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <001701c052c5$d9b72fb0$21c9ca95@mow.siemens.ru>
References: <20001117.100236.78702681.wl@gnu.org>
	<001701c052c5$d9b72fb0$21c9ca95@mow.siemens.ru>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1748
Lines: 38

> Russian words in average are longer than English (the same applies
> to German, BTW :-) and without hyphenation display loks ugly, with
> several words and large inter-words gaps. I assume, we could find
> hypehnation table in TeX, just as for english - but here are some
> problems.
> 
> Currently, hyphenation table for US is uncondtitionally loaded. Is
> it possible to load more than one table, like Russian?

Yes.  I've just looked into the code, and I believe that it is
possible to use the `.hpf' request more than once.  To get bilingual
hyphenation patterns for both Russian and English (this is what you
want, isn't it?) just load the Russian pattern after (or before) the
English ones *without* using `.hla' to change the hyphenation
language.

Please test!  Of course, the question is which of the 6 (!) Russian
hyphenation patterns available in TeX's ruhyphen package (written by
Vladimir Volovich's and me) you want to use...  Since none of the
packages use macros, it should be possible to directly read the
patterns (after removing the \hyphenation{...} stuff which should be
put into a Russian start-up file using the `.hw' request.

> Second, there are three widely used russian charsets and one
> "standard" one.  Is it possible to access current locale in troffrc?
> Given possible variety of locale names, something like locale alias
> table looks reasonable. I may try to implement something like this.

Yes.  With the \V[...] you can access environment variables.  The
string manipulation functions of groff are very limited, but maybe it
is sufficient.  For the moment, you must convert the patterns into the
target encoding...

The final solution will be that the preprocessor converts everything
to UTF8...


    Werner

From groff-admin  Tue Nov 21 12:26:13 2000
Received: from clyde.ref.collins.co.uk (clyde.ref.collins.co.uk [192.153.153.29])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA09516
	for <groff@ffii.org>; Tue, 21 Nov 2000 12:26:10 +0100
Received: from ref.collins.co.uk (helmsdale [193.119.38.15])
	by clyde.ref.collins.co.uk (8.9.3/8.9.3) with ESMTP id LAA13665
	for <groff@ffii.org>; Tue, 21 Nov 2000 11:32:09 GMT
Received: from ref.collins.co.uk (localhost [127.0.0.1])
	by ref.collins.co.uk (8.9.3+Sun/8.9.1) with ESMTP id LAA11197
	for <groff@ffii.org>; Tue, 21 Nov 2000 11:31:34 GMT
Message-ID: <3A1A5D13.73EB81AD@ref.collins.co.uk>
Date: Tue, 21 Nov 2000 11:31:31 +0000
From: "Stewart C. Russell" <stewart@ref.collins.co.uk>
Organization: HarperCollins Publishers, Bilingual Division
X-Mailer: Mozilla 4.6 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: groff@ffii.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 511
Lines: 16

Tomohiro KUBOTA wrote:
>
> I cannot understand your point.

yes, it was less than eloquent.

One of the most important things about markup formatters is that, given
the same input to the same version of the software, they should (/must?)
generate the same output in all installations, regardless of locale or
operating system. Otherwise, we have to send formatted output rather
than source text.

TeX, for example, has an elaborate test suite, and unless software
passes this, it can't be called TeX.

 Stewart

From groff-admin  Tue Nov 21 13:38:50 2000
Received: from surfchem0.riken.go.jp (surfchem0.riken.go.jp [134.160.25.161])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id NAA11149
	for <groff@ffii.org>; Tue, 21 Nov 2000 13:38:49 +0100
Received: from surfchem0.riken.go.jp (localhost [127.0.0.1])
	by surfchem0.riken.go.jp (Postfix) with ESMTP id 939611C173
	for <groff@ffii.org>; Tue, 21 Nov 2000 21:49:13 +0900 (JST)
Date: Tue, 21 Nov 2000 21:49:08 +0900
Message-ID: <87vgth7anv.wl@surfchem0.riken.go.jp>
From: Tomohiro KUBOTA <tkubota@riken.go.jp>
To: groff@ffii.org
Subject: Re: [Groff] man problem: Latin1 characters in nion-Latin1 locale
Mail-Reply-To: tkubota@riken.go.jp
In-Reply-To: In your message of "Tue, 21 Nov 2000 11:31:31 +0000"
	<3A1A5D13.73EB81AD@ref.collins.co.uk>
References: <3A1A5D13.73EB81AD@ref.collins.co.uk>
User-Agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2520
Lines: 66

Hi,

At Tue, 21 Nov 2000 11:31:31 +0000,
Stewart C. Russell <stewart@ref.collins.co.uk> wrote:

> > I cannot understand your point.
> 
> yes, it was less than eloquent.
> 
> One of the most important things about markup formatters is that, given
> the same input to the same version of the software, they should (/must?)
> generate the same output in all installations, regardless of locale or
> operating system. 

I see.  I think the point is the meaning of the word 'same' in 
the phrases of 'same input' and 'same output'.  IMO, the sameness
should be on _characters_ (for input file and tty output), rather
than on _byte values_.  Since the current locale defines the meaning
(i.e., which character) of the byte values in text files, the same
byte value may mean different character in different locale.  I think
the 'sameness' of  character is important than the sameness of byte
value.

Thus, locale-sensible encoding conversion _changes_ the _byte value_ 
in order to assure the sameness of _character_.

# Please forget about glyph now;  I limit the topic in input source
# and tty output -- they are expressed in _character_ codes, not in
# _glyph_ codes.  Or, in tty output, glyphs have to be expressed in
# character codes.


For non-Latin-1 people, this is rather a living problem for users,
than an discussion on idealism.  Japanese Linux/Unix users have to
buy books on how to display, input, and print Japanese texts without
breaking them.  We have to know which software can use Japanese.
Though we have taken such a situation for granted since Linux is a
difficult system, I want to stop such a crazy situation.


> Otherwise, we have to send formatted output rather
> than source text.

I cannot understand this.


> TeX, for example, has an elaborate test suite, and unless software
> passes this, it can't be called TeX.

I don't know much on TeX.  Anyway, we use Japanese version of TeX.
It change the input encoding (EUC-JP and Shift-JIS, both of them
are popular encodings in Japan) in compile time.  Thus, if we think
about input byte stream and output dvi file, it is obvious that
EUC-JP version and Shift-JIS version give different output from
the same text with same _byte values_.  (Of course these two
versions give the same output from the same texts with same 
_characters_.)

Japanese version of TeX is very popular in Japan.

# Though I know there are projects such as Omega, I don't have time
# to try it.

---
Tomohiro KUBOTA <kubota@debian.org>
http://surfchem0.riken.go.jp/~kubota/

From groff-admin  Tue Nov 21 14:01:11 2000
Received: from president.dataforce.net (president.dataforce.net [195.42.160.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id OAA11633
	for <groff@ffii.org>; Tue, 21 Nov 2000 14:01:10 +0100
Received: (qmail 12495 invoked from network); 21 Nov 2000 13:07:06 -0000
Received: from localhost (HELO openwall.com) (127.0.0.1)
  by localhost with SMTP; 21 Nov 2000 13:07:06 -0000
Received: (from solar@localhost) by openwall.com (8.x.x/8.x.x) id QAA28368; Tue, 21 Nov 2000 16:05:35 +0300
Date: Tue, 21 Nov 2000 16:05:35 +0300
From: Solar Designer <solar@openwall.com>
To: Werner LEMBERG <wl@gnu.org>
Cc: groff@ffii.org
Subject: Re: [Groff] FW: ISS Security Advisory: GNU Groff utilities read untrusted com mands from current working directory
Message-ID: <20001121160535.A28243@openwall.com>
References: <20001005.223731.37301821.wl@gnu.org> <200010132321.DAA03620@false.com> <20001113.175019.32714776.wl@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001113.175019.32714776.wl@gnu.org>; from wl@gnu.org on Mon, Nov 13, 2000 at 05:50:19PM +0100
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3121
Lines: 80

> I've now done the following: For searching and scanning troffrc and
> troffrc-end, the home directory is used instead of the current
> directory for the default path.  Similarly, the current directory in
> the font path has been replaced with the home directory.

What about making this ~/.groff?  Too many files are looked for in
the home directory now, so I'm afraid that it may hit some totally
unrelated file of a matching name.  (This isn't a security issue.)

> People can easily add the current directory again (if ever necessary)
> either with using -M (resp. -F) or setting GROFF_TMAC_PATH or
> GROFF_FONT_PATH.
> 
> I've just committed the changes into the CVS.  Please test and report
> whether this is solution is sufficient to solve this security problem.

Thanks for the opportunity.

This is indeed a lot better, but we aren't there yet:

12395 open("./andoc.tmac", O_RDONLY)    = -1 ENOENT (No such file or directory)
12395 open("./an-old.tmac", O_RDONLY)   = -1 ENOENT (No such file or directory)
12395 open("./man.local", O_RDONLY)     = -1 ENOENT (No such file or directory)

The "./andoc.tmac" is due to "-mandoc" when running from man and
seems to be safe (man does a "cd /usr/man" before this).

3076  open("./eqnrc", O_RDONLY)         = -1 ENOENT (No such file or directory)
3077  open("./andoc.tmac", O_RDONLY)    = -1 ENOENT (No such file or directory)

In this case, "-mandoc" is passed from lesspipe.sh; I've changed my
version to do a "cd /" before running groff, but many distributions
include the dangerous versions.  Maybe we could restrict -m as well?

--- groff-1.16.1/src/preproc/eqn/main.cc.orig	Tue Nov 21 15:46:09 2000
+++ groff-1.16.1/src/preproc/eqn/main.cc	Tue Nov 21 15:46:26 2000
@@ -329,7 +329,7 @@
 	 device, program_name);
   if (load_startup_file) {
     char *path;
-    FILE *fp = macro_path.open_file(STARTUP_FILE, &path);
+    FILE *fp = safer_macro_path.open_file(STARTUP_FILE, &path);
     if (fp) {
       do_file(fp, path);
       fclose(fp);
--- groff-1.16.1/src/roff/troff/input.cc.orig	Tue Nov 21 14:36:25 2000
+++ groff-1.16.1/src/roff/troff/input.cc	Tue Nov 21 14:47:30 2000
@@ -5691,6 +5691,8 @@
     while (!tok.newline() && !tok.eof())
       tok.next();
     char *path;
+    // restrict path for security reasons
+    mac_path = &safer_macro_path;
     FILE *fp = mac_path->open_file(nm.contents(), &path);
     // .mso doesn't (and cannot) go through open_mac_file, so we
     // need to do it here manually: If we have tmac.FOOBAR, try
@@ -5721,6 +5723,7 @@
     }
     else
       error("can't find macro file `%1'", nm.contents());
+    mac_path = &macro_path;
     tok.next();
   }
 }
--- groff-1.16.1/src/roff/troff/env.cc.orig	Tue Nov 21 14:36:25 2000
+++ groff-1.16.1/src/roff/troff/env.cc	Tue Nov 21 14:24:43 2000
@@ -3113,7 +3113,10 @@
   int num[WORD_MAX+1];
   errno = 0;
   char *path = 0;
+  // restrict path for security reasons
+  mac_path = &safer_macro_path;
   FILE *fp = mac_path->open_file(name, &path);
+  mac_path = &macro_path;
   if (fp == 0) {
     error("can't find hyphenation patterns file `%1'", name);
     return;

-- 
/sd

From groff-admin  Wed Nov 22 23:01:55 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA08278
	for <groff@ffii.org>; Wed, 22 Nov 2000 23:01:55 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 22 Nov 2000 23:07:46 +0100
Received: from rigel.univie.ac.at (dial-143137.HRZ.Uni-Dortmund.DE [129.217.143.137])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAMM7h814357;
	Wed, 22 Nov 2000 23:07:44 +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 XAA13068;
	Wed, 22 Nov 2000 23:06:37 +0100
Date: Wed, 22 Nov 2000 23:06:36 +0100 (CET)
Message-Id: <20001122.230636.66181250.wl@gnu.org>
To: solar@openwall.com
Cc: groff@ffii.org
Subject: Re: [Groff] FW: ISS Security Advisory: GNU Groff utilities read
 untrusted commands from current working directory
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20001121160535.A28243@openwall.com>
References: <200010132321.DAA03620@false.com>
	<20001113.175019.32714776.wl@gnu.org>
	<20001121160535.A28243@openwall.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1347
Lines: 43

> In this case, "-mandoc" is passed from lesspipe.sh; I've changed my
> version to do a "cd /" before running groff, but many distributions
> include the dangerous versions.  Maybe we could restrict -m as well?

Yes, see below.

> --- groff-1.16.1/src/preproc/eqn/main.cc.orig	Tue Nov 21 15:46:09 2000
> +++ groff-1.16.1/src/preproc/eqn/main.cc	Tue Nov 21 15:46:26 2000
> @@ -329,7 +329,7 @@
>  	 device, program_name);
>    if (load_startup_file) {
>      char *path;
> -    FILE *fp = macro_path.open_file(STARTUP_FILE, &path);
> +    FILE *fp = safer_macro_path.open_file(STARTUP_FILE, &path);
>      if (fp) {
>        do_file(fp, path);
>        fclose(fp);

This is an error -- I've changed the path for the -M option instead of
this.  Thanks for noticing it.

> [... suggested fixes ...]

Aftersome thinking I've done the following changes which is better
IMHO than my first try:

  In safer mode (the default): macro files are searched in the home
  directory and the default path.

  In unsafe mode, the current directory is scanned additionally.

  troffrc and troffrc-end are neither searched in the current nor in
  the home directory.

  Font files are neither searched in the current nor in the home
  directory but only in the default font path.

There are a lot of possibilities to override that.

Again: Please test.


    Werner

From groff-admin  Thu Nov 23 15:45:09 2000
Received: from president.dataforce.net (president.dataforce.net [195.42.160.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id PAA05659
	for <groff@ffii.org>; Thu, 23 Nov 2000 15:45:08 +0100
Received: (qmail 25184 invoked from network); 23 Nov 2000 14:51:22 -0000
Received: from localhost (HELO openwall.com) (127.0.0.1)
  by localhost with SMTP; 23 Nov 2000 14:51:22 -0000
Received: (from solar@localhost) by openwall.com (8.x.x/8.x.x) id RAA01303; Thu, 23 Nov 2000 17:50:16 +0300
Date: Thu, 23 Nov 2000 17:50:15 +0300
From: Solar Designer <solar@openwall.com>
To: Werner LEMBERG <wl@gnu.org>
Cc: groff@ffii.org
Subject: Re: [Groff] FW: ISS Security Advisory: GNU Groff utilities read untrusted commands from current working directory
Message-ID: <20001123175015.A1294@openwall.com>
References: <200010132321.DAA03620@false.com> <20001113.175019.32714776.wl@gnu.org> <20001121160535.A28243@openwall.com> <20001122.230636.66181250.wl@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001122.230636.66181250.wl@gnu.org>; from wl@gnu.org on Wed, Nov 22, 2000 at 11:06:36PM +0100
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 674
Lines: 25

> Aftersome thinking I've done the following changes which is better
> IMHO than my first try:
> 
>   In safer mode (the default): macro files are searched in the home
>   directory and the default path.
> 
>   In unsafe mode, the current directory is scanned additionally.
> 
>   troffrc and troffrc-end are neither searched in the current nor in
>   the home directory.
> 
>   Font files are neither searched in the current nor in the home
>   directory but only in the default font path.

Sounds reasonable.

> Again: Please test.

It passed my strace tests now.  Thanks!

I think you should announce the next release on Bugtraq, so that
people know to upgrade.

-- 
/sd

From groff-admin  Thu Nov 23 20:24:40 2000
Received: from smtp7.thrunet.com ([211.49.129.168])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA09568
	for <groff@ffii.org>; Thu, 23 Nov 2000 20:24:35 +0100
X-Authentication-Warning: genba.ffii.org: Host [211.49.129.168] claimed to be smtp7.thrunet.com
Received: from thrunet ([210.205.197.216]) by smtp7.thrunet.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 24 Nov 2000 04:06:42 +0900
Date: Fri, 24 Nov 2000 04:08:44 +0900
From: "Online Korea"<olk@olk.co.kr>
To: groff@ffii.org
X-AD2000-Serial: 1033
X-AD2000-Register: "박재현" <olk@olk.co.kr>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: base64
Message-ID: <06ba942061917b0SMTP7@smtp7.thrunet.com>
Subject: [Groff] groff님 안녕하세요?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 6572
Lines: 92

PEhUTUw+DQo8SEVBRD4NCjxNRVRBIE5BTUU9IkdFTkVSQVRPUiIgQ29udGVudD0iTWljcm9z
b2Z0IERIVE1MIEVkaXRpbmcgQ29udHJvbCI+DQo8VElUTEU+PC9USVRMRT4NCjwvSEVBRD4N
CjxCT0RZPg0KPFA+PEZPTlQgZmFjZT2xvLiyw7wgc2l6ZT0yPqaspqymrKaspqymrKaspqym
rKaspqymrKaspqymrKaspqymrKaspqymrKaspqymrKaspqymrKaspqymrKaspqw8QlI+osQg
v8C0w8DHIMCvuNMgx9G4trXwIA0KosU8L0ZPTlQ+PC9QPg0KPFA+PEZPTlQgZmFjZT2xvLiy
w7wgc2l6ZT0yPiZuYnNwOyAiRGFkLCBJIGRvbid0IHdhbnQgdG8gZ28gdG8gc2Nob29sIHRv
ZGF5LiwiIHNhaWQgDQp0aGUgYm95LjxCUj4mbmJzcDsgIldoeSBub3QsIHNvbj8iPEJSPiZu
YnNwOyAiV2VsbCwgb25lIG9mIHRoZSBjaGlja2VucyBvbiB0aGUgDQpzY2hvb2wgZmFybSBk
aWVkIGxhc3Qgd2VlayBhbmQgPEJSPiZuYnNwOyZuYnNwOyB3ZSBoYWQgY2hpY2tlbiBzb3Vw
IGZvciBsdW5jaCANCnRoZSBuZXh0IGRheS4gQW5kIHRocmVlIGRheXMgYWdvIDxCUj4mbmJz
cDsmbmJzcDsgb25lIG9mIHRoZSBwaWdzIGRpZWQgYW5kIHdlIA0KaGFkIHJvYXN0IHBvcmsg
dGhlIG5leHQgZGF5LCwsLiI8QlI+Jm5ic3A7ICJCdXQgd2h5IGRvbid0IHlvdSB3YW50IHRv
IGdvIA0KdG9kYXk/IjxCUj4mbmJzcDsgIkJlY2F1c2UgdGhlIEVuZ2xpc2ggdGVhY2hlciBk
aWVkIHllc3RlcmRheSEiPEJSPiZuYnNwOyANCiIuLi4uLiI8L0ZPTlQ+PC9QPg0KPFA+PEZP
TlQgZmFjZT2xvLiyw7wgc2l6ZT0yPiZuYnNwOyAivsa6/Cwgs6ogv8C0wyDH0LGzILChseIg
vci+7i4iIMfPsO0gvNKz4sDMILi7x9+02S48QlI+Jm5ic3A7ICK/1iCwobHiIA0Kvci+7j8i
PEJSPiZuYnNwOyAiwfazrSDB1r+hIMfQsbMgs/PA5b+hvK0gtN8gx9EguLa4rrChIMHXvvq0
wrWlILTZwL2zryDBob3JwLi3ziA8QlI+Jm5ic3A7Jm5ic3A7ILTfIL26x8G4piC41L76vu4u
IA0Ksde4rrDtIDPAzyDA/L+htMIgtcXB9iDH0SC4triusKEgwde++rTCtaUgPEJSPiZuYnNw
OyZuYnNwOyCx1yC02cC9ILOvv6G0wiC1xcH2ILrSsO2x4rimILjUvvqw7S4uLi4iPEJSPiZu
YnNwOyANCiKx17extaUgv8C0w8C6IL/WIMfQsbO/oSCwobHiIL3Ivu4/IjxCUj4mbmJzcDsg
Ir7uwaYgv7W+7iC8sbv9tNTAzCC1ub7GsKG8zLTcILi7vt8hIjxCUj4mbmJzcDsgDQoiLi4u
Li4iPC9GT05UPjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj6ixCC/wLTDwMcg
v7W+7iDH0bi2tfAgosUmbmJzcDsmbmJzcDsmbmJzcDsgPC9GT05UPjwvUD4NCjxQPjxGT05U
IGZhY2U9sby4ssO8IHNpemU9Mj6iwiBJIGZlbHQgb24gdG9wIG9mIHRoZSANCndvcmxkJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KPC9GT05UPjwvUD4N
CjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj6757b3wLogtKmxuLOqILy6sPjHz7jpILHi
utDAzCDBwcC6ILDNwLogtOe/rMfPwfa/5C4gPEJSPrmwt9AsIL7utrIgu+e297XpwLogvLqw
+MffwLsgtqe/oSC09SANCrDivNXH2MH2wfa4uCC067rOutDAxyC757b3tenAuiA8QlI+W7Oq
uKYgusEhILO7sKEgw9aw7b7fXbbzsO0gu/2wosfVtM+02S4gPEJSPsDMv80gsLDAuiCx4rrQ
wLsgs6rFuLO7tMIgx6XH9sDMICdvbiB0b3Agb2YgDQp0aGUgd29ybGQntvi0z7TZLjwvRk9O
VD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+QTogSSBoZWFyZCB5b3Ugd2Vy
ZSBlbmdhZ2VkIHRvIE1hcmlhbi48L0ZPTlQ+PC9QPg0KPFA+PEZPTlQgZmFjZT2xvLiyw7wg
c2l6ZT0yPkI6IEFjdHVhbGx5LCBJIHdhcy48L0ZPTlQ+PC9QPg0KPFA+PEZPTlQgZmFjZT2x
vLiyw7wgc2l6ZT0yPkE6IE9oLCByZWFsbHk/IFNvLCBob3cgZGlkIHlvdSBmZWVsIG9uIHRo
ZSBuaWdodCBvZiANCnlvdXIgZW5nYWdlbWVudD88L0ZPTlQ+PC9QPg0KPFA+PEZPTlQgZmFj
ZT2xvLiyw7wgc2l6ZT0yPkI6IEkgZmVsdCBsaWtlIEkgd2FzIG9uIHRvcCBvZiB0aGUgd29y
bGQuPC9GT05UPjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj6h4SdvbiB0b3Ag
b2YgdGhlIHdvcmxkJ7imIMH3v6rHz7jpIFu8vLvzILLAtOux4r+hXbbztMIgwMe5zMDMuOcg
DQo8QlI+Jm5ic3A7ICdJIGZlbHQgb24gdG9wIG9mIHRoZSB3b3JsZC4ntMIgIry8u/MgssC0
67Hiv6EgwNa0wiC0wLOmwMy++rTZLiI8QlI+Jm5ic3A7IMHvLCAosbLA5cj3IA0KseK60MDM
IMHBvtK02Sm4piC25sfVtM+02S48QlI+Jm5ic3A7IMjnyPcgW7HiutDAzCDBwb7Svu5dtvO0
wiDAx7nMt84gJ0kgZmVsdCBnb29kLie4uMC7ILv9sKLHz7HiIL2sv+yzqiANCjxCUj4mbmJz
cDsgwMwgx6XH9rW1IL7LsO0gwNbAuLjpILCowaTAxyDHpcf2wLsgtPUgwN8gx9IgvPYgwNbA
uyCwxb+hv+QuPC9GT05UPjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj6iwSAn
b24gdG9wIG9mIHRoZSB3b3JsZCe0wiC8vLvzILLAtOux4r+hIMDWtMIgtMCzpiEuILHXt7i0
2bjpIA0KPEJSPiZuYnNwOyZuYnNwOyAnb3V0IG9mIHRoaXMgd29ybGQntMI/IMDMILy8u/PA
xyDAzyCwsMH2IL7KsNQgsdm758fRW3dvbmRlcmZ1bF0sIA0KPEJSPiZuYnNwOyZuYnNwOyDI
pMC6IMivu/PA+8DOW2ZhbnRhc3RpY13AzLb1ILbmwMy/ob/kLjwvRk9OVD48L1A+DQo8UD48
Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+QToguN64rr7IsPogvuDIpcfRtNmw7SC16b76tMK1
pS48QlI+Qjogu+e9xyDAzLnMIMffvu4uPEJSPkE6IL7uLCANCsGkuLvAzL7fPyZuYnNwOyCx
17ehLL7gyKW9xMfRILHXs68gueO/oSCx4rrQwMwgvu62rr7uPzxCUj5COiC8vLvzwLsgvvLA
uiCx4rrQwMy++sH2LjwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+
osQgv8C0w8DHIMDPvu4mbmJzcDsgx9G4trXwIKLFPC9GT05UPjwvUD4NCjxQPjxGT05UIGZh
Y2U9sby4ssO8IHNpemU9Mj4mbmJzcDsmbmJzcDsgodjAz77utbUgv7W+7r/NILCwwLogx/zF
wrfOILG4vLogtce+7iANCsDWvcC0z7TZLjxCUj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08QlI+Z3JvZma01CANCr7Is+fH
z7y8v+Q/IDwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+wPrI8bTC
IMD8yK24piDAzL/rx9i8rSCwrbvnv80gMToxt84gv9yxub7uIMfQvcDAuyDH0iC89iDA1rTC
IDxCUj6ixCBPbmxpbmUgS29yZWEgDQpbJm5ic3A7IDxBIGhyZWY9Imh0dHA6Ly93d3cub2xr
LmNvLmtyIj5odHRwOi8vd3d3Lm9say5jby5rcjwvQT4mbmJzcDsgXSCixSC287DtIA0Kx9W0
z7TZLjwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+uNXA+iwgx+O2
9L74wMwgxu3B9iC15bfBIMHLvNvH1bTPtNkuILrOtfAgs8qx17evv+4gv+u8rbimLi4uLi4u
PC9GT05UPjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj7A+sjxIMi4u+e/obyt
tMIgv7W+7iDAr7jTv80gu/3IsCDIuMitv6EgsPy9ySDA1rTCILrQtemysiC4xcDPKL/5LbHd
KSwgPEJSPr+1vu4gwK+407/NIL3HIA0Ku/3IsL+hIMfKv+TH0SC7/ciwyLjIrSDH0SC5rsDl
vr/AuyC5q7fht84gurizuyC15biusO0gwNa+7r/kLjwvRk9OVD48L1A+DQo8UD48Rk9OVCBm
YWNlPbG8uLLDvCBzaXplPTI+wKe/zbCwwLogs7u/68DHILytuvG9urimILnevsa6uLHiIL/4
x8+9w7jpIKHsIDxBIA0KaHJlZj0ibWFpbHRvOm9sa0BvbGsuY28ua3IiPm9sa0BvbGsuY28u
a3I8L0E+IKHtt84gPEJSPiJ5ZXMitvO0wiCzu7/rwMcgtOTA5cC7IMHWvcOx4iANCrnZtvi0
z7TZLjwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+sde4rrDtLCDA
+sjxIMD8yK0gv9yxub7uILCtwMewoSCxw7Hdx8+9xSC60LXpwLsgwKfH2CZuYnNwOyA8QSAN
CmhyZWY9Imh0dHA6Ly93d3cub2xrLmNvLmtyL2xlY3R1cmVfZnJhbWUuaHRtIj6iwiC9w7n8
sK3AxyCiwiA8L0E+tbUgPEJSPjHIuL+hIMfRx9i8rSC5q7fht84gDQq9x73Dx8+w7SDA1sC4
tM8gx9G5+CC16b7uuriw7SC9zcC4vcO46SDB9rHdIL3Fw7vH2CDB1ry8v+QuPC9GT05UPjwv
UD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj65q7fhIL3DufywrcDHIL3Fw7sguea5
/cC6IDxBIA0KaHJlZj0iaHR0cDovL3d3dy5vbGsuY28ua3IvbGVjdHVyZV9mcmFtZS5odG0i
PqK6IL+pseIgorggPC9BPrimIMWsuK/Hz73FIMjEILCtwMcgvcXDu7b1v6EgDQrA1rTCPEJS
Pr3DufywrcDHuKYgvcXDu8fPvcO46SDA+sjxsKEgwPzIrbimILXlt8EgvcO5/LCtwMe4piDH
2CC15biwtOS0z7TZLjwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+
ubC30CwgwPzIrSAwMi01ODgtMDUxMCDAuLfOtbUgvcXDu8fPvccgvPYgwNaxuL/kLjwvRk9O
VD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+vsa5q8LJt88gwMwgx9C9wLn9
wMwgZ3JvZma01MDHIMi4yK0gvce3wiDH4rvzv6EgwNvAuiC6uMXGwMwgDQq1x776wLi46TxC
Uj7H1bTPtNkuPC9GT05UPjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj6wqLvn
x9W0z7TZLjwvRk9OVD48L1A+DQo8UD48Rk9OVCBmYWNlPbG8uLLDvCBzaXplPTI+Z3JvZma0
1LKytMIgaHR0cDovL2ZyZWVkb20uc2FyYW5nLm5ldC9zb2Z0d2FyZS9ncm9mZi9ncm9mZi5o
dG1sv6EgwNa0wiDB1rzSuKYguriw7SC43sDPILXluK6w1CANCrXHvvq9wLTPtNkuPC9GT05U
PjwvUD4NCjxQPjxGT05UIGZhY2U9sby4ssO8IHNpemU9Mj660sfKv+TH0SDBpLq4v7S02bjp
IMGkuLsgwcu828fVtM+02S48QlI+PC9GT05UPjwvUD4NCjwvQk9EWT4NCjwvSFRNTD4NCg==



From groff-admin  Thu Nov 23 20:53:11 2000
Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA09909
	for <groff@ffii.org>; Thu, 23 Nov 2000 20:53:11 +0100
Received: from beta by smtp.hccnet.nl
	via uds239-120.dial.hccnet.nl [193.173.120.239] with SMTP
	id UAA09715 (8.8.5/1.13); Thu, 23 Nov 2000 20:54:38 +0100 (MET)
Message-ID: <007901c05587$366c7f80$ef78adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: "Djgpp Announce" <djgpp-announce@delorie.com>,
        "Haardt, Michael" <michael@moria.de>, "Groff list" <groff@ffii.org>
Date: Thu, 23 Nov 2000 20:54:33 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [Groff] Deroff for DJGPP
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 276
Lines: 10

Deroff version 1.6 compiled with DJGPP is available from
ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2apps/
and its mirrors.
Deroff removes troff, tbl, eqn and pic constructs from documents. It works on MS-DOS and all
Win32-systems (Win95, Win98, WinNT)

Kees Zeelenberg




From groff-admin  Thu Nov 23 23:13:36 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA11243
	for <groff@ffii.org>; Thu, 23 Nov 2000 23:13:35 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Thu, 23 Nov 2000 23:19:35 +0100
Received: from rigel.univie.ac.at (dial-143153.HRZ.Uni-Dortmund.DE [129.217.143.153])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eANMJW807140;
	Thu, 23 Nov 2000 23:19:32 +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 WAA02798;
	Thu, 23 Nov 2000 22:55:19 +0100
Date: Thu, 23 Nov 2000 22:55:19 +0100 (CET)
Message-Id: <20001123.225519.88699917.wl@gnu.org>
To: solar@openwall.com
Cc: groff@ffii.org
Subject: Re: [Groff] FW: ISS Security Advisory: GNU Groff utilities read
 untrusted commands from current working directory
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <20001123175015.A1294@openwall.com>
References: <20001121160535.A28243@openwall.com>
	<20001122.230636.66181250.wl@gnu.org>
	<20001123175015.A1294@openwall.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 200
Lines: 11

> It passed my strace tests now.  Thanks!

Excellent!

> I think you should announce the next release on Bugtraq, so that
> people know to upgrade.

Please give the proper email address.


    Werner

From groff-admin  Sat Nov 25 23:12: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 8.9.3-21) with ESMTP id XAA03207
	for <groff@ffii.org>; Sat, 25 Nov 2000 23:12:20 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 25 Nov 2000 23:18:51 +0100
Received: from rigel.univie.ac.at (dial-143169.HRZ.Uni-Dortmund.DE [129.217.143.169])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAPMIn902426
	for <groff@ffii.org>; Sat, 25 Nov 2000 23:18:49 +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 UAA00614
	for <groff@ffii.org>; Sat, 25 Nov 2000 20:46:55 +0100
Date: Sat, 25 Nov 2000 20:46:54 +0100 (CET)
Message-Id: <20001125.204654.74751433.wl@gnu.org>
To: groff@ffii.org
From: Werner LEMBERG <wl@gnu.org>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] space and \~ in .tr request
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1441
Lines: 41

My current work on groff is to allow `\~' in the `.tr' request (only
as a character to be mapped to):

  .tr \[char160]\~

This is needed e.g. to implement full latin-1 input encoding support
which has a non-breakable space.

The similar request, as you all know,

  .tr \[xxx]

maps the character `xxx' onto the space character, or rather, it maps
onto `\ ', i.e., an unpaddable, unbreakable space character. (Can
someone please check this with AT&T troff?)  BTW, a real bug is that
hyphenation (both implicit and explicit) doesn't work before the
mapped space.  The original troff documentation says (in section
10.5):

  All text processing takes place with the input character which
  appears to have the width of the final character.

But is this the ideal solution for a space character?

I would like to change groff's `.tr' implementation so that mapping a
character onto a space is either a) or b):

  a) an unpaddable, breakable space character
  b) a paddable, breakable space character

My favor is b).  Please tell me whether you have ever used mapping
onto a space and which solution you prefer.  groff will of course
emulate the original troff behaviour (whatever it is) while in
compatibility mode.  I would also add `\ ' to the .tr request in case
b) appears to be the right choice.

Regardless which solution will be implemented for the space character,
`\~' in `.tr' will yield a paddable, unbreakable space.


    Werner

From groff-admin  Sat Nov 25 23:12: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 8.9.3-21) with ESMTP id XAA03232
	for <groff@ffii.org>; Sat, 25 Nov 2000 23:12:37 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 25 Nov 2000 23:18:55 +0100
Received: from rigel.univie.ac.at (dial-143169.HRZ.Uni-Dortmund.DE [129.217.143.169])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAPMIr902432
	for <groff@ffii.org>; Sat, 25 Nov 2000 23:18:53 +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 UAA00619
	for <groff@ffii.org>; Sat, 25 Nov 2000 20:50:21 +0100
Date: Sat, 25 Nov 2000 20:50:20 +0100 (CET)
Message-Id: <20001125.205020.41625912.wl@gnu.org>
To: groff@ffii.org
In-Reply-To: <XFMail.991129155354.Ted.Harding@nessie.mcc.ac.uk>
References: <XFMail.991129155354.Ted.Harding@nessie.mcc.ac.uk>
From: Werner LEMBERG <wl@gnu.org>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] Re: Groff hyphenation problem
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1458
Lines: 49

This problem was the very reason to start maintaining groff together
with Ted:

> Why does groff suppress hyphenation break at "-" in the context of
> words with escapes like "\ " in them?

The problem is even more serious: Any word which is not finished by
either a space or a newline character won't be hyphenated.  Most
escape sequences fall into this category; most notably `\ ' and `\~'.
Below are two tiny patches which solve this problem, I believe.
Before committing it I ask you all for testing.


    Werner


======================================================================

--- env.h.old	Sun Nov 12 16:19:15 2000
+++ env.h	Thu Nov 23 22:22:22 2000
@@ -189,7 +189,6 @@
 #ifdef WIDOW_CONTROL
   void mark_last_line();
 #endif /* WIDOW_CONTROL */
-  void possibly_break_line(int forced = 0);
   breakpoint *choose_breakpoint();
   void hyphenate_line();
   void start_field();
@@ -268,6 +267,7 @@
   void set_input_line_position(hunits);	// used by \n(hp
   void interrupt();
   void spread() { spread_flag = 1; }
+  void possibly_break_line(int forced = 0);
   void do_break();			// .br
   void final_break();
   void add_html_tag (const char *name);

======================================================================

--- input.cc.old	Thu Nov 23 08:27:19 2000
+++ input.cc	Thu Nov 23 22:38:09 2000
@@ -2292,6 +2292,7 @@
 	  curenv->add_node(tok.nd);
 	  tok.nd = 0;
 	  bol = 0;
+	  curenv->possibly_break_line();
 	}
 	break;
       }

From groff-admin  Mon Nov 27 17:05:12 2000
Received: from burns.conectiva (brutus.conectiva.com.br [200.250.58.146])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id RAA04417
	for <groff@ffii.org>; Mon, 27 Nov 2000 17:05:09 +0100
X-Authentication-Warning: genba.ffii.org: Host brutus.conectiva.com.br [200.250.58.146] claimed to be burns.conectiva
Received: (qmail 12400 invoked by uid 0); 27 Nov 2000 16:11:40 -0000
Received: from soneca.conectiva (HELO conectiva.com.br) (root@10.0.2.41)
  by burns.conectiva with SMTP; 27 Nov 2000 16:11:40 -0000
Message-ID: <3A22874A.808E88E9@conectiva.com.br>
Date: Mon, 27 Nov 2000 14:09:46 -0200
From: Ricardo <ricardo@conectiva.com.br>
Reply-To: ricardo@conectiva.com.br
Organization: Conectiva SA
X-Mailer: Mozilla 4.76 [pt_BR] (X11; U; Linux 2.2.16-13cl i586)
X-Accept-Language: pt-BR
MIME-Version: 1.0
To: groff@ffii.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: [Groff] Groff version
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 264
Lines: 11

Actualy, how is the groff version? 1.16.2?

hugs
-- 
Ricardo Soares Guimar�es (GNOME - Brazil / KDE Brazil)
LDP-BR - LIE-BR
ricardo@conectiva.com.br +55 041-360-2682 uin: 39252777

	A alma tem ilusoes, como o passaro, asas; isso e que a 
	sustem.
		-- Victor Hugo

From groff-admin  Mon Nov 27 21:34:45 2000
Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA06866
	for <groff@ffii.org>; Mon, 27 Nov 2000 21:34:43 +0100
Received: from postoffice2.mail.cornell.edu ([132.236.56.10])
	by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
	id 140V5Z-0007jH-00
	for <groff@gnu.org>; Mon, 27 Nov 2000 15:41:25 -0500
Received: from cornell.edu (d5052.dialup.cornell.edu [132.236.102.52])
	by postoffice2.mail.cornell.edu (8.9.3/8.9.3) with ESMTP id PAA04955;
	Mon, 27 Nov 2000 15:41:19 -0500 (EST)
Message-ID: <3A22C6F7.E09C0291@cornell.edu>
Date: Mon, 27 Nov 2000 15:41:27 -0500
From: Richard Liu <rcl3@cornell.edu>
X-Mailer: Mozilla 4.73 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: groff@gnu.org, rcl3@cornell.edu
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Subject: [Groff] question on "groff"
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 417
Lines: 16

Dear Sir/Madam:

       I was a frequent user of "Troff" with the "ms"-macros on the
Sun-workstation
for a long period of time, and I like it a lot.       I wonder whether
the "groff" installed
on "Linux" works the same as the "Troff" on "Unix"?       Moreover, is
there a similar
"ms"-macros attached in the "groff" application to make the writing
easier?

      Thanks a lot for all your kind responses.


Richard


From groff-admin  Mon Nov 27 22:15:29 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id WAA07235
	for <groff@ffii.org>; Mon, 27 Nov 2000 22:15:29 +0100
Received: from cmailg1.svr.pol.co.uk ([195.92.195.171])
	by fencepost.gnu.org with smtp (Exim 3.16 #1 (Debian))
	id 140Vj2-0000Nc-00
	for <groff@gnu.org>; Mon, 27 Nov 2000 16:22:12 -0500
Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 140Viz-00050Q-00
	for groff@gnu.org; Mon, 27 Nov 2000 21:22:09 +0000
Received: from modem-6.aman.dialup.pol.co.uk ([62.136.103.6] helo=inputplus.demon.co.uk)
	by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 140Viy-0003JS-00
	for groff@gnu.org; Mon, 27 Nov 2000 21:22:08 +0000
Received: from inputplus (ralph@localhost [127.0.0.1])
	by inputplus.demon.co.uk (8.8.7/8.8.7) with ESMTP id VAA29492;
	Mon, 27 Nov 2000 21:22:00 GMT
Message-Id: <200011272122.VAA29492@inputplus.demon.co.uk>
To: Richard Liu <rcl3@cornell.edu>
cc: groff@gnu.org
Subject: Re: [Groff] question on "groff" 
In-Reply-To: Message from Richard Liu <rcl3@cornell.edu> 
   of "Mon, 27 Nov 2000 15:41:27 EST." <3A22C6F7.E09C0291@cornell.edu> 
Date: Mon, 27 Nov 2000 21:21:59 +0000
From: Ralph Corderoy <ralph@inputplus.demon.co.uk>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 659
Lines: 18

Hi Richard,

> I was a frequent user of "Troff" with the "ms"-macros on the
> Sun-workstation for a long period of time, and I like it a lot.
> I wonder whether the "groff" installed on "Linux" works the same as
> the "Troff" on "Unix"?       Moreover, is there a similar "ms"-macros
> attached in the "groff" application to make the writing easier?

groff is intended to be a replacement for troff and it does come with a
set of ms macros although since I personally use mm I can't vouch for
how compatible they are.  Looking at the groff_ms man page they claim
to be very compatible.

I'd highly recommend obtaining groff and seeing for yourself.


Ralph.


From groff-admin  Mon Nov 27 23:07:54 2000
Received: from fencepost.gnu.org (we-refuse-to-spy-on-our-users@fencepost.gnu.org [199.232.76.164])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA07885
	for <groff@ffii.org>; Mon, 27 Nov 2000 23:07:54 +0100
Received: from smtp.hccnet.nl ([193.172.127.93])
	by fencepost.gnu.org with smtp (Exim 3.16 #1 (Debian))
	id 140WXl-0001m2-00
	for <groff@gnu.org>; Mon, 27 Nov 2000 17:14:37 -0500
Received: from beta by smtp.hccnet.nl
	via uds196-120.dial.hccnet.nl [193.173.120.196] with SMTP
	id XAA22734 (8.8.5/1.13); Mon, 27 Nov 2000 23:14:26 +0100 (MET)
Message-ID: <003101c058bf$67a77740$c478adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: "Richard Liu" <rcl3@cornell.edu>,
        "Ralph Corderoy" <ralph@inputplus.demon.co.uk>
Cc: <groff@gnu.org>
References: <200011272122.VAA29492@inputplus.demon.co.uk>
Subject: Re: [Groff] question on "groff" 
Date: Mon, 27 Nov 2000 23:14:15 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1510
Lines: 40

The ms-macros from groff are indeed compatible with those from troff. As long as your own
macros don't rely on some internal mechanism or variables of the ms-macros, it should be
possible to compile all your old troff-papers with groff. In fact the original troff ms-macros
are still available from http://plan9.bell-labs.com/7thEdMan/, and can be used when groff is
called with compatibility mode on (-C); it usually gives quite acceptable results.

Kees

----- Oorspronkelijk bericht -----
Van: "Ralph Corderoy" <ralph@inputplus.demon.co.uk>
Aan: "Richard Liu" <rcl3@cornell.edu>
CC: <groff@gnu.org>
Verzonden: maandag 27 november 2000 22:21
Onderwerp: Re: [Groff] question on "groff"


>
> Hi Richard,
>
> > I was a frequent user of "Troff" with the "ms"-macros on the
> > Sun-workstation for a long period of time, and I like it a lot.
> > I wonder whether the "groff" installed on "Linux" works the same as
> > the "Troff" on "Unix"?       Moreover, is there a similar "ms"-macros
> > attached in the "groff" application to make the writing easier?
>
> groff is intended to be a replacement for troff and it does come with a
> set of ms macros although since I personally use mm I can't vouch for
> how compatible they are.  Looking at the groff_ms man page they claim
> to be very compatible.
>
> I'd highly recommend obtaining groff and seeing for yourself.
>
>
> Ralph.
>
> _______________________________________________
> Groff maillist  -  Groff@ffii.org
> http://ffii.org/mailman/listinfo/groff
>


From groff-admin  Tue Nov 28 08:01:14 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA26328
	for <groff@ffii.org>; Tue, 28 Nov 2000 08:01:13 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 28 Nov 2000 08:07:42 +0100
Received: from rigel.univie.ac.at (dial-143133.HRZ.Uni-Dortmund.DE [129.217.143.133])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAS77d923391;
	Tue, 28 Nov 2000 08:07: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 HAA04127;
	Tue, 28 Nov 2000 07:49:21 +0100
Date: Tue, 28 Nov 2000 07:49:21 +0100 (CET)
Message-Id: <20001128.074921.68037281.wl@gnu.org>
To: ricardo@conectiva.com.br
Cc: groff@ffii.org
Subject: Re: [Groff] Groff version
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <3A22874A.808E88E9@conectiva.com.br>
References: <3A22874A.808E88E9@conectiva.com.br>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 147
Lines: 7

> Actualy, how is the groff version? 1.16.2?

Rather 1.17 since I'm introducing some new (small) features.  Expect
it in a few weeks.


    Werner

From groff-admin  Tue Nov 28 12:04:18 2000
Received: from mail-r1.comhill.com (w211.z06400044.nyc-ny.dsl.cnc.net [64.0.44.211])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA28837
	for <groff@ffii.org>; Tue, 28 Nov 2000 12:04:17 +0100
X-Authentication-Warning: genba.ffii.org: Host w211.z06400044.nyc-ny.dsl.cnc.net [64.0.44.211] claimed to be mail-r1.comhill.com
Received: from mail-r1.comhill.com ([64.0.44.211]) by
          mail-r1.comhill.com (Netscape Messaging Server 4.15) with SMTP
          id G4QF7200.C4J for <groff@ffii.org>; Tue, 28 Nov 2000 06:13:50 -0500 
Received: from 212.179.8.212 by mail-r1.comhill.com (InterScan E-Mail VirusWall NT); Tue, 28 Nov 2000 06:13:48 -0500 (Eastern Standard Time)
From: "Ephraim Yawitz" <ephraim@comhill.com>
To: <groff@ffii.org>
Date: Tue, 28 Nov 2000 13:11:28 +0200
Message-ID: <003701c0592b$f4a05d30$7b01050a@yawitz.alerts.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Importance: Normal
Subject: [Groff] Hebrew for groff?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 390
Lines: 11

I hope it's OK for me to just send an e-mail to the list like this; that's
the impression I got from the webpage describing the list.
What would have to be done in order to make groff produce right-to-left
output for Hebrew, etc?  I might be able to work on it if I knew at least
where in the code to start hacking.  Is this something reasonable, or
outlandish?

Thank you,

Efraim Yawitz


From groff-admin  Tue Nov 28 17:33:21 2000
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA32136
	for <groff@ffii.org>; Tue, 28 Nov 2000 17:33:21 +0100
Received: from tedistan.annex.mcc.ac.uk
	([194.66.22.200] helo=tedistan.annex.umist.ac.uk ident=root)
	by probity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 140nna-000LIy-00; Tue, 28 Nov 2000 16:40:06 +0000
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA26014;
	Tue, 28 Nov 2000 16:35:58 GMT
Message-ID: <XFMail.001128163558.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: <003701c0592b$f4a05d30$7b01050a@yawitz.alerts.co.il>
Date: Tue, 28 Nov 2000 16:35:58 -0000 (GMT)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Ephraim Yawitz <ephraim@comhill.com>
Subject: RE: [Groff] Hebrew for groff?
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2448
Lines: 53

Hi,

On 28-Nov-00 Ephraim Yawitz wrote:
> I hope it's OK for me to just send an e-mail to the list like this;
> that's the impression I got from the webpage describing the list.
> What would have to be done in order to make groff produce right-to-left
> output for Hebrew, etc?  I might be able to work on it if I knew at
> least where in the code to start hacking.  Is this something
> reasonable, or outlandish?
> 
> Thank you,
> 
> Efraim Yawitz

This was achieved for UNIX device-independent troff ("ditroff") a good
while ago by Dan Berry, who created the "ffortid" postprocessor to handle
right-to-left languages.

Done in the first place for Hebrew, this was later extended to cope
with Arabic including the "calligraphic" lateral extensions and
overlaps required for classy printing.

I really must try to put together either a collection of Dan's source
code and sample outputs for people to consult, or try myself to get it
to work for groff (which it does not straightforwardly do, since Dan's
code depends rather intimately on the format of ditroff font descriptions
which differ from groff's).

However, the basic trick for Hebrew is simple. When right-to-left text
is encountered, a special code is passed through to the post-processor
(using \X'ps: ... ') announcing the fact. The troff formatting, however,
is still done left-to-right so as to get the line-filling and spacings
correct. Each line therefore comes out of troff as Hebrew left-to-right
(possibly with some non-Hebrew left-to-right). The post-processor then
picks up the sequence of characters that should be right-to-left in each
line, and reverses their order. Some tweaking using the font metrics may
then be required. Similarly, when text reverts to left-to-right, a
corresponding code is passed through to the post-processor and all
subsequent text simply goes straight through unchanged.

Dan Berry also implemented a "triroff" which includes capability to
print up-and-down languages like Chinese and Japanese. This essentially
treats each character as a cell in a table, but saves the user having
to construct the table with his bare hands.

I hope this helps.
Ted.

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

From groff-admin  Wed Nov 29 16:31:43 2000
Received: from abgate.alfredberg.se (ns.alfredberg.se [130.244.126.137])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id QAA25085
	for <groff@ffii.org>; Wed, 29 Nov 2000 16:31:42 +0100
X-Authentication-Warning: genba.ffii.org: Host ns.alfredberg.se [130.244.126.137] claimed to be abgate.alfredberg.se
Received: by abgate.alfredberg.se; (5.65v4.0/1.3/10May95) id AA02266; Wed, 29 Nov 2000 16:38:38 +0100
Received: from mail.sto.alfredberg.se (unverified) by abslns7220.sto.alfredberg.se
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc26789dc502db05e89@abslns7220.sto.alfredberg.se> for <groff@ffii.org>;
 Wed, 29 Nov 2000 16:38:36 +0100
Received: from ab-konsult.com ([194.103.139.194]) by mail.sto.alfredberg.se
          (Netscape Messaging Server 3.6)  with ESMTP id AAAE1D
          for <groff@ffii.org>; Wed, 29 Nov 2000 16:38:36 +0100
Message-Id: <3A2522FC.B3C08607@ab-konsult.com>
Date: Wed, 29 Nov 2000 16:38:36 +0100
From: "Stefan Westerberg" <stefan.westerberg@ab-konsult.com>
Reply-To: stefan.westerberg@ab-konsult.com
Organization: stefan.westerberg@hps.se http://hps.se
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
Mime-Version: 1.0
To: groff@ffii.org
Content-Type: multipart/mixed ; boundary="------------9DCAF088FEB4953BDB585A0A"
Subject: [Groff] Build groff 1.16.1 on Compaq TruUnix 4.0F fails.
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 3061
Lines: 72

This is a multi-part message in MIME format.
--------------9DCAF088FEB4953BDB585A0A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

When I try to build groff 1.16.1 on Compaq TruUnix 4.0F I get the following error:

make[1]: Entering directory `/usr/users/stefanw/kit/groff-1.16.1'
make[2]: Entering directory `/usr/users/stefanw/kit/groff-1.16.1/src/include'
make[2]: Leaving directory `/usr/users/stefanw/kit/groff-1.16.1/src/include'
make[2]: Entering directory `/usr/users/stefanw/kit/groff-1.16.1/src/libs/libgroff'
c++ -I. -I/usr/users/stefanw/kit/groff-1.16.1/src/libs/libgroff -I/usr/users/stefanw/kit/groff-1.16.
1/src/include -I/usr/users/stefanw/kit/groff-1.16.1/src/include -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1
-DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STRING_H=1
-DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1
-DHAVE_SYS_ERRLIST=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_STRNCASECMP=1 -DHAVE_STRDUP=1  -g -O2  -c font.cc
In file included from /usr/users/stefanw/kit/groff-1.16.1/src/include/lib.h:29,
                 from font.cc:31:
/usr/users/stefanw/kit/groff-1.16.1/src/include/groff-getopt.h:39: redefinition of `struct option'
/usr/users/stefanw/kit/groff-1.16.1/src/include/getopt.h:95: previous definition here
make[2]: *** [font.o] Error 1
make[2]: Leaving directory `/usr/users/stefanw/kit/groff-1.16.1/src/libs/libgroff'
make[1]: *** [src/libs/libgroff] Error 2
make[1]: Leaving directory `/usr/users/stefanw/kit/groff-1.16.1'
make: *** [all] Error 2

Has anybody seen this before and is there a simple fix to get groff to the correct header files ?

I am using gcc 2.95 and make 3.79.1

Regards
Stefan W



*******DISCLAIMER*******
This message and any attachment are confidential and may be privileged
or otherwise protected from disclosure and solely for the use of the
person(s) or entity to whom it is intended.  Please note that this
message contains an e-mail confidentiality note and disclaimer. To read 
the full e-mail disclaimer please point your Web browser to: http://www.alfredberg.se/disclaimer/external.htm
*******DISCLAIMER*******

--------------9DCAF088FEB4953BDB585A0A
Content-Type: text/x-vcard; charset=us-ascii;
 name="stefan.westerberg.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Stefan Westerberg
Content-Disposition: attachment;
 filename="stefan.westerberg.vcf"

begin:vcard 
n:Westerberg;Stefan
tel;cell:+46-706-288559
tel;fax:+46-8-6242730
tel;work:+46-8-6249962
x-mozilla-html:TRUE
url:http://hps.se
org:High Performance Systems AB;Alfred Berg Data
version:2.1
email;internet:stefan.westerberg@hps.se
title:Konsult 
adr;quoted-printable:;;Box 600=0D=0ABrov=E4gen 1;182 16  Danderyd;;;Sweden
x-mozilla-cpt:;-1520
fn:Stefan Westerberg
end:vcard

--------------9DCAF088FEB4953BDB585A0A--


From groff-admin  Wed Nov 29 22:59: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 8.9.3-21) with ESMTP id WAA29330
	for <groff@ffii.org>; Wed, 29 Nov 2000 22:59:02 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 29 Nov 2000 23:05:48 +0100
Received: from rigel.univie.ac.at (dial-143179.HRZ.Uni-Dortmund.DE [129.217.143.179])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eATM5k906589;
	Wed, 29 Nov 2000 23:05:46 +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 WAA02530;
	Wed, 29 Nov 2000 22:36:26 +0100
Date: Wed, 29 Nov 2000 22:36:25 +0100 (CET)
Message-Id: <20001129.223625.48536414.wl@gnu.org>
To: stefan.westerberg@ab-konsult.com
Cc: groff@ffii.org
Subject: Re: [Groff] Build groff 1.16.1 on Compaq TruUnix 4.0F fails.
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <3A2522FC.B3C08607@ab-konsult.com>
References: <3A2522FC.B3C08607@ab-konsult.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 481
Lines: 13

> /usr/users/stefanw/kit/groff-1.16.1/src/include/groff-getopt.h:39:
> redefinition of `struct option'
> /usr/users/stefanw/kit/groff-1.16.1/src/include/getopt.h:95:
> previous definition here

Please send me the platform identifier macro (something like __osf__),
and I will add it to line 31 in lib.h (as in the current snapshot).

Note that special cases for __sgi and __osf__ have already been added;
if I find some time I'll replace it with an autoconf solution.


    Werner

From groff-admin  Thu Nov 30 12:10:25 2000
Received: from abgate.alfredberg.se (ns.alfredberg.se [130.244.126.137])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id MAA19959
	for <groff@ffii.org>; Thu, 30 Nov 2000 12:10:25 +0100
X-Authentication-Warning: genba.ffii.org: Host ns.alfredberg.se [130.244.126.137] claimed to be abgate.alfredberg.se
Received: by abgate.alfredberg.se; (5.65v4.0/1.3/10May95) id AA16953; Thu, 30 Nov 2000 12:17:25 +0100
Received: from mail.sto.alfredberg.se (unverified) by abslns7220.sto.alfredberg.se
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc26789dc5031e73d07@abslns7220.sto.alfredberg.se> for <groff@ffii.org>;
 Thu, 30 Nov 2000 12:17:01 +0100
Received: from ab-konsult.com ([194.103.139.194]) by mail.sto.alfredberg.se
          (Netscape Messaging Server 3.6)  with ESMTP id AAAF2;
          Thu, 30 Nov 2000 12:17:00 +0100
Message-Id: <3A26372E.45948153@ab-konsult.com>
Date: Thu, 30 Nov 2000 12:17:02 +0100
From: "Stefan Westerberg" <stefan.westerberg@ab-konsult.com>
Reply-To: stefan.westerberg@ab-konsult.com
Organization: stefan.westerberg@hps.se http://hps.se
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
Mime-Version: 1.0
To: Werner LEMBERG <wl@gnu.org>
Cc: groff@ffii.org
Subject: Re: [Groff] Build groff 1.16.1 on Compaq TruUnix 4.0F fails.
References: <3A2522FC.B3C08607@ab-konsult.com> <20001129.223625.48536414.wl@gnu.org>
Content-Type: multipart/mixed ; boundary="------------32B58B9F47222718B3E5B4FB"
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 2156
Lines: 64

This is a multi-part message in MIME format.
--------------32B58B9F47222718B3E5B4FB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I fund no reference in the source for any thing like __osf__. Do you know where I could
find what the platform identifier is ?

I also fund a workaround and compiled it successfully. My work around was to rename
groff-1.16.1/src/include/getopt.h when I got the error. I then to renamed it back to successfully
compile getopt.c.

/Stefan W

Werner LEMBERG wrote:

> > /usr/users/stefanw/kit/groff-1.16.1/src/include/groff-getopt.h:39:
> > redefinition of `struct option'
> > /usr/users/stefanw/kit/groff-1.16.1/src/include/getopt.h:95:
> > previous definition here
>
> Please send me the platform identifier macro (something like __osf__),
> and I will add it to line 31 in lib.h (as in the current snapshot).
>
> Note that special cases for __sgi and __osf__ have already been added;
> if I find some time I'll replace it with an autoconf solution.
>
>     Werner


*******DISCLAIMER*******
This message and any attachment are confidential and may be privileged
or otherwise protected from disclosure and solely for the use of the
person(s) or entity to whom it is intended.  Please note that this
message contains an e-mail confidentiality note and disclaimer. To read 
the full e-mail disclaimer please point your Web browser to: http://www.alfredberg.se/disclaimer/external.htm
*******DISCLAIMER*******

--------------32B58B9F47222718B3E5B4FB
Content-Type: text/x-vcard; charset=us-ascii;
 name="stefan.westerberg.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Stefan Westerberg
Content-Disposition: attachment;
 filename="stefan.westerberg.vcf"

begin:vcard 
n:Westerberg;Stefan
tel;cell:+46-706-288559
tel;fax:+46-8-6242730
tel;work:+46-8-6249962
x-mozilla-html:TRUE
url:http://hps.se
org:High Performance Systems AB;Alfred Berg Data
version:2.1
email;internet:stefan.westerberg@hps.se
title:Konsult 
adr;quoted-printable:;;Box 600=0D=0ABrov=E4gen 1;182 16  Danderyd;;;Sweden
x-mozilla-cpt:;-1520
fn:Stefan Westerberg
end:vcard

--------------32B58B9F47222718B3E5B4FB--


From groff-admin  Fri Dec  1 00:29:38 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA28245
	for <groff@ffii.org>; Fri, 1 Dec 2000 00:29:38 +0100
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Fri, 1 Dec 2000 00:36:25 +0100
Received: from rigel.univie.ac.at (dial-143141.HRZ.Uni-Dortmund.DE [129.217.143.141])
	by sx2.hrz.uni-dortmund.de (8.10.2+Sun/8.9.3) with ESMTP id eAUNaL407597;
	Fri, 1 Dec 2000 00:36: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 AAA04548;
	Fri, 1 Dec 2000 00:16:04 +0100
Date: Fri, 01 Dec 2000 00:16:03 +0100 (CET)
Message-Id: <20001201.001603.116351345.wl@gnu.org>
To: stefan.westerberg@ab-konsult.com
Cc: groff@ffii.org
Subject: Re: [Groff] Build groff 1.16.1 on Compaq TruUnix 4.0F fails.
From: Werner LEMBERG <wl@gnu.org>
In-Reply-To: <3A26372E.45948153@ab-konsult.com>
References: <3A2522FC.B3C08607@ab-konsult.com>
	<20001129.223625.48536414.wl@gnu.org>
	<3A26372E.45948153@ab-konsult.com>
X-Mailer: Mew version 1.95b54 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 323
Lines: 9

> I fund no reference in the source for any thing like __osf__. Do you
> know where I could find what the platform identifier is ?

Say `g++ -E -dM foo.cc' and check the list for platform specific
symbols similar to `__linux__' (I prefer symbols which start and stop
with two underscoresto be ANSI-compliant).


    Werner

From groff-admin  Fri Dec  1 01: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 8.9.3-21) with ESMTP id BAA28512
	for <groff@ffii.org>; Fri, 1 Dec 2000 01:24:49 +0100
Received: from mail1.be.to (mail1.be.to [210.235.212.2])
	by mailgw1.be.to (8.11.0+3.3W/8.11.0/BETO3.11-20000907025324) with ESMTP id eB10Vqo13282
	for <groff@ffii.org>; Fri, 1 Dec 2000 09:31:52 +0900
	(envelope-from okazaki@be.to)
Received: from REISHI (hawaii.isola.co.jp [211.0.101.206])
	by mail1.be.to (8.9.3+3.2W/BETO.2.0-2000090621000000) with SMTP id JAA11374
	for <groff@ffii.org>; Fri, 1 Dec 2000 09:31:51 +0900
Received: (qmail 13669 invoked from network); 1 Dec 2000 00:30:48 -0000
Received: from localhost (HELO acidrain.localnet) (127.0.0.1)
  by localhost with SMTP; 1 Dec 2000 00:30:48 -0000
Date: Fri, 01 Dec 2000 09:30:46 +0900
Message-ID: <86wvdlnft5.wl@dolphin.be.to>
From: OKAZAKI Tetsurou <okazaki@be.to>
To: Werner LEMBERG <wl@gnu.org>
Cc: stefan.westerberg@ab-konsult.com, groff@ffii.org
Subject: Re: [Groff] Build groff 1.16.1 on Compaq TruUnix 4.0F fails.
In-Reply-To: <20001201.001603.116351345.wl@gnu.org>
References: <3A2522FC.B3C08607@ab-konsult.com>
	<20001129.223625.48536414.wl@gnu.org>
	<3A26372E.45948153@ab-konsult.com>
	<20001201.001603.116351345.wl@gnu.org>
User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.14.0 (Iburihashi) FLIM/1.14.0 (Ninokuchi) APEL/10.2 Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.0 - "Iburihashi")
Content-Type: text/plain; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 535
Lines: 17

Hi, Werner,

In the message <20001201.001603.116351345.wl@gnu.org> 
Werner LEMBERG <wl@gnu.org> wrote:

> > I fund no reference in the source for any thing like __osf__. Do you
> > know where I could find what the platform identifier is ?

> Say `g++ -E -dM foo.cc' and check the list for platform specific
> symbols similar to `__linux__' (I prefer symbols which start and stop
> with two underscoresto be ANSI-compliant).

Type `g++ -E -dM -' and push ^D (ctrl-d) have same effect,
and no need to touch dummy file :-).

-- 
Tetsurou

