HP3000-L Archives

February 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Byler <[log in to unmask]>
Reply To:
Larry Byler <[log in to unmask]>
Date:
Tue, 4 Feb 1997 21:08:48 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
[log in to unmask] wrote:

[...]

: That's why I was wondering how hard it would be to build
: an environment file by hand

It can be trivially easy or impossibly difficult, depending on the
complexity of your environment file.  For example, we generated the five
(network printing) PCL environment files we shipped with Release 5.5 by
hand.  Take a look at PCLELITE.HPENV.SYS for an example.  This file
specifies orientation (portrait), single-sided operation, paper size,
etc.  But if you need to include fonts and forms in your environment,
the ENV file explodes in both size and complexity, and should not be
attempted by hand.

: or write a program to take PCL text and wrap
: an environment file around it.

Such a program is called Word for Windows :-) (or one of the other equally
fine word processors), with output directed to an HP LaserJet printer.
If you want an example of a complex ENV, print a WforW document to a
file using the LaserJet print environment.  Then look at that file.  If
you're lucky, the text of the document starts about 3/4 of the way into
the file -- everything before that is environment information.  Fonts,
and so on.

The good new is that you're on Release 5.5.  This means the OS supports
straight PCL environment files.

Sorry I don't have more information on tools to build complex ENV files.
Maybe one of our other correspondents has a hot tip.

-Larry "MPE/iX Spoolers 'R' Us" Byler-

ATOM RSS1 RSS2