Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

troff blues

0 views
Skip to first unread message

Joe Campbell

unread,
Feb 21, 1992, 2:24:37 AM2/21/92
to
It appears that a number of Khoros users are having the same problems
that we have trying to print the manuals. The problem appears to be
a limitation in troff (on our Suns) and your long path names. Here's
an excerpt from an unanswered posting on the Khoros news group that
addresses our problem:

...troff only allow a maximum path length of 62 characters after a .so command.
Thus, when the text formatter attempts to execute a source file with a path
length longer than this, it cuts off the last characters of the path and
complains that it cannot find the file (because there is no full file name
after it has been trimmed). This happens when we have paths like
/usr/from/khoros/doc/xprism/xprism2/plot/input_function/manual/Overview.

Do you have any suggestions?
Joe

George Lindholm

unread,
Feb 21, 1992, 7:14:01 PM2/21/92
to
In article <36...@pprg.eece.unm.edu.pprg.unm.edu>, jpc...@afterlife.ncsc.mil (Joe Campbell) writes:
> It appears that a number of Khoros users are having the same problems
> that we have trying to print the manuals. The problem appears to be
> a limitation in troff (on our Suns) and your long path names. Here's
> an excerpt from an unanswered posting on the Khoros news group that
> addresses our problem:
>
> ...troff only allow a maximum path length of 62 characters after a .so command.
> Do you have any suggestions?

Try groff. I had no problem with the 1.0(?) khoros release (except a large
number of warning message due to improper command use).

George
--
George Lindholm phone: (604) 822-4375
University Computing Services, UBC fax: (604) 822-5116
6356 Agricultural Road, Vancouver, B.C., Canada internet: lind...@ucs.ubc.ca
V6T 1Z2 bitnet: USERGNL@UBCMTSG

Joe Campbell

unread,
Feb 22, 1992, 12:58:04 AM2/22/92
to
In article <1992Feb22.0...@unixg.ubc.ca> lind...@ucs.ubc.ca (George Lindholm) writes:
>In article <36...@pprg.eece.unm.edu.pprg.unm.edu>, jpc...@afterlife.ncsc.mil (Joe Campbell) writes:
>> It appears that a number of Khoros users are having the same problems
>> that we have trying to print the manuals. The problem appears to be
>> a limitation in troff (on our Suns) and your long path names. Here's
>> an excerpt from an unanswered posting on the Khoros news group that
>> addresses our problem:
>>
>> ...troff only allow a maximum path length of 62 characters after a .so command.
>> Do you have any suggestions?
>
>Try groff. I had no problem with the 1.0(?) khoros release (except a large
>number of warning message due to improper command use).
>
> [.sig removed]

George:
I wish groff was an option, but my facility can't use PD stuff. Do you
know of any way to make stock Sun software do the trick?
Joe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Joe Campbell | Happiness = Reality - Expectations | My opinions |
| N3JBC | - Click & Clack Brothers | are mine! |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fritz Zaucker

unread,
Feb 24, 1992, 8:59:34 AM2/24/92
to
>>
>> ...troff only allow a maximum path length of 62 characters after a .so command.
>> Do you have any suggestions?
>
>Try groff. I had no problem with the 1.0(?) khoros release (except a large
>number of warning message due to improper command use).
>
> [.sig removed]

George:
I wish groff was an option, but my facility can't use PD stuff. Do you
know of any way to make stock Sun software do the trick?
Joe


Hmmm, I know Khoros has a Copyright notice in it. Does this make it
"usable" for you? And groff (which I guess is from the FSF) having a
Copyleft notice not???

Fritz

Len Makin, Supercomputing Support Group, CSIRO DIT Melbourne.

unread,
Feb 24, 1992, 7:10:36 PM2/24/92
to

>Try groff. I had no problem with the 1.0(?) khoros release (except a large
>number of warning message due to improper command use).

I also used groff, but had to use -C option, and still got incredibly tiny
font point size ( ~3 pt??) on the Tables of Contents for Volume III Ch 1,2.
Yes, I got heaps of warning messages too, but the text seems to be OK
apart from the TOC.

| Len Makin, CSIRO, Division of Information Technology (Melbourne) |
| Supercomputing Support Group |
|723 Swanston St, Carlton| (TEL) +61 3 282 2622 (FAX) +61 3 282 2600 |
|VIC 3053, Australia | Internet:l...@mel.dit.csiro.au |

Joe Campbell

unread,
Feb 24, 1992, 9:32:58 PM2/24/92
to

Fritz:
Interesting, isn't it. Because Khoros can be purchased ($250), it's
possible to use it. I don't make the rules. Can groff be purchased?
Joe
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|Joe Campbell jpc...@afterlife.ncsc.mil 7404...@compuserve.com N3JBC|
|My opinions are mine! Happiness = Reality-Expectations, Click & Clack|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

George Lindholm

unread,
Feb 25, 1992, 1:45:52 PM2/25/92
to
In article <1992Feb25.0...@afterlife.ncsc.mil>, jpc...@afterlife.ncsc.mil (Joe Campbell) writes:
> In article <FRITZZ.92F...@oracles.ldgo.columbia.edu> fri...@lamont.ldgo.columbia.edu (Fritz Zaucker) writes:
> >Hmmm, I know Khoros has a Copyright notice in it. Does this make it
> >"usable" for you? And groff (which I guess is from the FSF) having a
> >Copyleft notice not???
> >
> >Fritz
>
> Fritz:
> Interesting, isn't it. Because Khoros can be purchased ($250), it's
> possible to use it. I don't make the rules. Can groff be purchased?
> Joe
You can buy a set of 3 distribution tapes from GNU that has all the gnu
source on them (including groff) for about $600 US. This is a similar
arrangement to what khoros offers.
You can get more information from:

Free Software Foundation
675 Massachusetts Avenue
Cambridge, MA 02139, USA
617-876-3296

Hope this helps.

0 new messages