omniprint-user — User discussion of the Omni driver

[Omniprint-user] New LaserJet command.

[Mark H. <ha...@us...>]

Hey Guys,

It looks like the command <esc> & l # U where # is in decipoints (1/720")
can move the logical page left
if it is negative.  It seems that there is 25/300" space between the
unprintable area for Letter and 21/300"
for A4.

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

[Omniprint-user] Re: [printing-driver] proposal of what features the communication to a printer driver should support

[Mark H. <ha...@us...>]

Hi Robert,

I still think that defining a programmatic way to query the language
level is feasible.  The driver developers could come up with a
structure that describes how the language is formatted.  But you
are right in that it would be difficult and perhaps error prone.

> How do we handle printers that happily handle arbitrary paper sizes?
> Epson inkjet printers (I keep coming back to them because I understand
> them best) don't particularly care what the size of the paper is, as
> long as it's within bounds (about 8.7x1200 inches for the 870, for
> example).  And there are a number of printers that support roll feed
> paper, where this is actually of quite significant use.

How do you handle them to begin with?  One method is to define a
presentation space that is based on the size of the page.  For that,
the size needs to be known in advance and cannot be arbitrary.
User defined forms can be created for any size paper that you want
to print on.

Another way would be to receive chunks of the page with no real way
to know when it will stop and hope that the printer can handle it.
Programs that print banners would probably be coded this way.

> I think we also need to handle constraints in a more general fashion.
> Some printers may have different margins depending upon the resolution
> (or resolution plus other quality information) selected, for example.
> Most Epson printers can print closer to the top and bottom edges of
> the paper if a soft weave mode is chosen than if firmware microweave
> is.

I was thinking that the form name would have an informational part to
it that would not affect the selection if the margins change.  For
example,

   na_letter_8.5x11x0.01x0.01x0.01x0.01in   at   300 dpi
   na_letter_8.5x11x0.02x0.02x0.02x0.02in   at   600 dpi

would only need to be passed form=na_letter to be selected correctly.
Although it could accept the more ugly full name.

> It seems like a weird concept to me.  With on-the-fly output
> generation, this can be done with most inkjets, but it still feels
> very strange to me.  With laser printers, this doesn't make a whole lot
> of sense at all, and even I have difficulty envisioning a situation
> where this would be useful.  In any event, aborting a page is
> something I think we should defer.

Yes.  I agree.  It was a weird concept for me as well.  Which is why
I chose to go with the abort job path.

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

[Omniprint-user] proposal of what features the communication to a printer driver should support

[Mark H. <ha...@us...>]

Here is a proposal of what features the communication to a printer
driver should support.

Rather than giving a list of low-level omni commands, I have provided
a high level overview.

Session management
------------------

 - The first command should be a handshaking of the versions.
 - Close the session.

Device management
-----------------

 - Enumerate all supported devices that a printer driver supports.
   NOTE:  This can either the entire list or what subset is installed.
 - Query a device's programmatic language description. (PCL, ESC/P2, PS,
HG/GL)
   NOTE:  This can allow spoolers to move jobs between similar print
queues.
 - Enumerate all devices for a language.
 - Start a print job for a device.
   NOTE: This should be a required command and should invalidate the
         session if a non-supported device should be selected.

Job Properties
--------------

Drivers should support a set of core properties.  For example, at a
minimum,
a driver should support (note: this is only a sample):
   form
   media
   tray
   resolution
   orientation
   color/monochrome

For the core properties, a driver should support a set of standardized
selections.  This will help in moving jobs between different printer
drivers that support a printer.  For example:
   form
      Here is a sample proposal from IPP/UPDF/UPnP.
        na_letter_8.5x11in
        na_legal_8.5x14in
        iso_a3_297x420mm
        jis_b4_257x364mm
        jpn_hagaki_100x148mm
      It has some good points to it:
        All forms have a name to it.  If, in the future, a new form is
          created, then a program would not know how to call a form
          that was selected with only its size (6.12x7.59 is called what?).
        More information is returned.  The size of the form is returned
          with the name.
      Some bad points are:
        Hard copy clipping information should also be returned.
   media
     Here is a sample proposal from UPDF
       stationery
       stationery-coated
       stationery-inkjet
       stationery-preprinted

The driver should also have a set of driver specific properties.

 - Set the job properties for a session.
   NOTE: I think that all the properties should be set in one command.  I
         can envision scenarios where individual sets could paint the
         driver into a corner.
         There should be default job properties if some or none of the
         job properties are set.
 - Query the current job properties.
   NOTE: This can happen both before and after the job properties are set.
 - Enumerating the job properties.
 - Enumerating the options for a job property.
 - Enumerating the type of a job property.

Printer Properties
------------------

Drivers need to know about what optional features are installed for
a printer.

Perhaps there can be a core set of printer properties.  For example,
   a duplexer is installed
   extra memory is installed
   an extra tray is installed or is configured to hold certain paper

 - Set the printer properties.
 - Query the printer properties.
 - Enumerate the printer properties.
 - Enumerate the options for a printer property.
 - Enumerate the type of a printer property.

Job Control
-----------

 - Start a job.
 - Start a page.
 - End a page.
 - Optionally change the properties for the next page.
 - End a job.
 - Abort a job.
   NOTE: I think that it is easier to abort a print job rather than
         aborting a print page.  How do you recover and still keep
         printing new pages?

Job Data
--------

Here is where you have to ask yourself:  Are you a graphics engine
that is talking to a printer driver or are you an application that
is talking to a printer driver.

If you are a graphics engine, then you will want to allow the
device to accelerate high level commands (Ex: drawing a box with rounded
corners).  Every command that is not supported at a high level will be
rasterized into a series of banded bitmaps and then sent down to the
device.  It should be drawn into the bitmap format that the device
wants  (Ex: RGB, CMYK, CcMmYK; 1, 8, 24 bits per pel; 8 or 32 bit scan
line aligned; top or bottom orientation; etc).

If you are an application, you want to print simply.  Some examples are:
   a series (1 or more) of bitmaps of any color depth
   postscript commands
   printer specific data
   plain text

Job Information
---------------

 - Query printable area.
 - Font metric information.
 - Resolution of the page.


Bidirectional information
-------------------------

 - Error reporting.  (Printer offline, busy, out of ink)
 - Device reporting.  (Printer name)

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

Hi Mark,

Thanks for the info, changing the hardcoded value worked when it was
positive
but not when negative (we needed to shift the page to the left). However,
we
can live with the shift (amout 5mm).

Thanks for the help.

By the way, we are developers of X-Windows accessability software for
visually impaired people (screen magnification and screen reading with
speach and braille support). We are looking to port this software to Linux.

I know IBM is getting involved in Linux, is there anyone at IBM
who may be interested in this, perhaps with funding ?

Some info is on http://www.beam.ltd.uk/xvil


Terry

Mark Hamzy wrote:

> Hey Terry,
>
> Sorry about the delay for Thanksgiving.
>
> If you take a look at "HP LaserJet PCL Instance.cpp", at line 179, it
> calculates the vertical offset.  It uses
> it at line 375.  The second parameter is the x offset in the units of
> measurement (UOM) which is hardcoded
> to 0.  Try changing that value.
>
> Some reasons to have spaces in the filenames are that it is more natural
> (that is a one to one mapping of
> the device name to the file name) and to tell the difference between an
> actual file (that has spaces) and
> a build-generated file (that has underscores).
>
> Mark
>
> Take a look at the Linux Omni printer driver at
> http://www.ibm.com/linux/ltc/projects/omni/
>
> _______________________________________________
> Omniprint-user mailing list
> Omn...@li...
> https://lists.sourceforge.net/lists/listinfo/omniprint-user

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hey Terry,

Sorry about the delay for Thanksgiving.

If you take a look at "HP LaserJet PCL Instance.cpp", at line 179, it
calculates the vertical offset.  It uses
it at line 375.  The second parameter is the x offset in the units of
measurement (UOM) which is hardcoded
to 0.  Try changing that value.

Some reasons to have spaces in the filenames are that it is more natural
(that is a one to one mapping of
the device name to the file name) and to tell the difference between an
actual file (that has spaces) and
a build-generated file (that has underscores).

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

Hi Mark,

I've tried changing hardCopyCapLeft but this only seems
to alter the clipping of the page on the right. No shift of the page is
performed.
The hardCopyCapBottom parameter does move the print up from the bottom
of the page. On our printer a shift to the left of about 6mm is required.
Does this need to be done within Ghostscript ?
Any Ideas ?

I would call the command line use of spaces as separators a feature and the
allowing of space in file names a bug :)
It is not only the shell but most unix tools such as make, sed, awk, grep etc
that
use the space character as a separator allowing a single string to contain a
list
of elements.
As a matter of interest what are the advantages of using spaces in file names
?

Cheers


Terry

Mark Hamzy wrote:

> Hey Terry,
>
> The values in the hard copy caps used to be in hundredths of a millimeter
> but were later expanded to be in
> thousandths of a millimeter to avoid conversion losses between inches and
> millimeters in form sizes.
> I have just updated docs/HowToCreateADevice.  Hopefully, that was the last
> place which referenced the old
> unit size.
>
> You are on the right track.  Please be aware of the DeviceTester program.
> If you call it as follows:
>      DeviceTester drawbox driver libHP_LaserJet_III.so cout output1.prn
> cerr output1.err && cp output1.prn /dev/lp0
>
> It will draw a box around the printable area of the page.  The right and
> bottom sides will have incremental lines
> to help determine how many pels are missing from the sides.
>
> Yeah, I know the spaces in file names causes problems, but I think that the
> advantages outweigh the disadvantages.
> I wish they would fix the bugs in the command line programs because space
> is a valid filename character.
>
> Mark
>
> Take a look at the Linux Omni printer driver at
> http://www.ibm.com/linux/ltc/projects/omni/
>
> _______________________________________________
> Omniprint-user mailing list
> Omn...@li...
> https://lists.sourceforge.net/lists/listinfo/omniprint-user

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hey Terry,

The values in the hard copy caps used to be in hundredths of a millimeter
but were later expanded to be in
thousandths of a millimeter to avoid conversion losses between inches and
millimeters in form sizes.
I have just updated docs/HowToCreateADevice.  Hopefully, that was the last
place which referenced the old
unit size.

You are on the right track.  Please be aware of the DeviceTester program.
If you call it as follows:
     DeviceTester drawbox driver libHP_LaserJet_III.so cout output1.prn
cerr output1.err && cp output1.prn /dev/lp0

It will draw a box around the printable area of the page.  The right and
bottom sides will have incremental lines
to help determine how many pels are missing from the sides.

Yeah, I know the spaces in file names causes problems, but I think that the
advantages outweigh the disadvantages.
I wish they would fix the bugs in the command line programs because space
is a valid filename character.

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

Hi Mark,

Success !
The current CVS tree builds, installs and the printer prints !
Thanks for the help.
One little thing remains: The printed page is not aligned correctly.
I am using the command:  gs -sDEVICE=omni -sDeviceName="HP_LaserJet_III"
-sproperties="form=FORM_A4" -r300x300 -sOutputFile=out.lj -sPAPERSIZE=a4
-q -

I have tried to change the hardCopyCap values in "HP LaserJet III
Forms.xml". These don't
seem to have any effect. (Also what units are these in, the documentation
says hundreths of mm
but the values in the file are in the order 4000-9000 which does not seem
to make much sense.)
Any pointers ?

Cheers

Terry

PS: The use of spaces in file names is awkward for us old time command
line users ! and also
casues problems when writing automated scripts :(.

Terry

Mark Hamzy wrote:

> Hey Terry,
>
> Thanks for the patience.  It appears that Red Hat patches Omni to load
> devices in /usr/lib/Omni and that patch is
> not in cvs.  I have now updated cvs to include that patch.  After you
> compile make sure that you copy libomni.so
> over to /usr/lib/Omni as well.
>
> Mark
>
> Take a look at the Linux Omni printer driver at
> http://www.ibm.com/linux/ltc/projects/omni/
>
> _______________________________________________
> Omniprint-user mailing list
> Omn...@li...
> https://lists.sourceforge.net/lists/listinfo/omniprint-user

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hey Terry,

Thanks for the patience.  It appears that Red Hat patches Omni to load
devices in /usr/lib/Omni and that patch is
not in cvs.  I have now updated cvs to include that patch.  After you
compile make sure that you copy libomni.so
over to /usr/lib/Omni as well.

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

Thanks for the CVS update,

It compiles now bu when I try to run Ghostscipt I get the error:

-----------------
<<<<<<<<<<<<<<<<<<<<<< ERROR >>>>>>>>>>>>>>>>>>>>>>>


GhostscriptInterface::createDevice: g_module_error returns
libHP_LaserJet_III.so: cannot open shared object file: No such file or
directory
GhostscriptInterface::createDevice: cDeviceName = libHP_LaserJet_III.so
GhostscriptInterface::createDevice: pszDeviceName = HP_LaserJet_III


Unrecoverable error: rangecheck in .putdeviceprops
-----------------

To test I simply recompiled Omni and coppied all of the .so's to the
directory /usr/lib/Omni where they are normally in the RedHat system.

Any ideas ?

Terry

Mark Hamzy wrote:

> Hey Terry,
>
> Sigh.  I forgot to update clone LaserJet devices and it looks like there
> was a hole in the dependancy generation.
>
> I have updated CVS again.
>
> Mark
>
> Take a look at the Linux Omni printer driver at
> http://www.ibm.com/linux/ltc/projects/omni/

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"

[Omniprint-user] UPDF proposal for form names

[Mark H. <ha...@us...>]

na_index-3x5_3x5in
na_personal_3.625x6.5in
na_monarch_3.875x7.5in
na_number-9_3.875x8.875in
na_index-4x6_4x6in
na_number-10_4.125x9.5in
na_a2_4.375x5.75in
na_number-11_4.5x10.375in
na_number-12_4.75x11in
na_5x7_5x7in
na_index-5x8_5x8in
na_number-14_5x11.5in
na_invoice_5.5x8.5in
na_index-4x6-ext_6x8in
na_6x9_6x9in
na_c5_6.5x9.5in
na_7x9_7x9in
na_executive_7.25x10.5in
na_govt-letter_8x10in
na_govt-legal_8x13in
na_quarto_8.5x10.83in
na_letter_8.5x11in
na_fanfold-eur_8.5x12in
na_letter-plus_8.5x12.69in
na_foolscap_8.5x13in
na_legal_8.5x14in
na_super-a_8.94x14in
na_9x11_9x11in
na_arch-a_9x12in
na_letter-extra_9.5x12in
na_legal-extra_9.5x15in
na_10x11_10x11in
na_10x13_10x13in
na_10x14_10x14in
na_10x15_10x15in
na_11x12_11x12in
na_edp_11x14in
na_fanfold-us_11x14.875in
na_11x15_11x15in
na_ledger_11x17in
na_eur-edp_12x14in
na_arch-b_12x18in
na_12x19_12x19in
na_b-plus_12x19.17in
na_super-b_13x19in
na_c_17x22in
na_arch-c_18x24in
na_d_22x34in
na_arch-d_24x36in
asme_f_28x40in
na_wide-format_30x42in
na_e_34x44in
na_arch-e_36x48in
na_f_44x68in
iso_a10_26x37mm
iso_a9_37x52mm
iso_a8_52x74mm
iso_a7_74x105mm
iso_a6_105x148mm
iso_a5_148x210mm
iso_a5-extra_174x235mm
iso_a4_210x297mm
iso_a4-tab_225x297mm
iso_a4-extra_235.5x322.3mm
iso_a3_297x420mm
iso_a4x3_297x630mm
iso_a4x4_297x841mm
iso_a4x5_297x1051mm
iso_a4x6_297x1261mm
iso_a4x7_297x1471mm
iso_a4x8_297x1682mm
iso_a4x9_297x1892mm
iso_a3-extra_322x445mm
iso_a2_420x594mm
iso_a3x3_420x891mm
iso_a3x4_420x1189mm
iso_a3x5_420x1486mm
iso_a3x6_420x1783mm
iso_a3x7_420x2080mm
iso_a1_594x841mm
iso_a2x3_594x1261mm
iso_a2x4_594x1682mm
iso_a2x5_594x2102mm
iso_a0_841x1189mm
iso_a1x3_841x1783mm
iso_a1x4_841x2378mm
iso_2a0_1189x1682mm
iso_a0x3_1189x2523mm
iso_4a0_1682x2378mm
iso_b10_31x44mm
iso_b9_44x62mm
iso_b8_62x88mm
iso_b7_88x125mm
iso_b6_125x176mm
iso_b6c4_125x324mm
iso_b5_176x250mm
iso_b5-extra_201x276mm
iso_b4_250x353mm
iso_b3_353x500mm
iso_b2_500x707mm
iso_b1_707x1000mm
iso_b0_1000x1414mm
iso_c10_28x40mm
iso_c9_40x57mm
iso_c8_57x81mm
iso_c7_81x114mm
iso_c7c6_81x162mm
iso_c6_114x162mm
iso_c6c5_114x229mm
iso_c5_162x229mm
iso_c4_229x324mm
iso_c3_324x458mm
iso_c2_458x648mm
iso_c1_648x917mm
iso_c0_917x1297mm
iso_dl_110x220mm
iso_ra2_430x610mm
iso_sra2_450x640mm
iso_ra1_610x860mm
iso_sra1_640x900mm
iso_ra0_860x1220mm
iso_sra0_900x1280mm
jis_b10_32x45mm
jis_b9_45x64mm
jis_b8_64x91mm
jis_b7_91x128mm
jis_b6_128x182mm
jis_b5_182x257mm
jis_b4_257x364mm
jis_b3_364x515mm
jis_b2_515x728mm
jis_b1_728x1030mm
jis_b0_1030x1456mm
jis_exec_216x330mm
jpn_chou4_90x205mm
jpn_hagaki_100x148mm
jpn_you4_105x235mm
jpn_chou2_111.1x146mm
jpn_chou3_120x235mm
jpn_oufuku_148x200mm
jpn_kahu_240x322.1mm
jpn_kaku2_240x332mm
prc_32k_97x151mm
prc_1_102x165mm
prc_2_102x176mm
prc_4_110x208mm
prc_5_110x220mm
prc_8_120x309mm
prc_6_120x320mm
prc_3_125x176mm
prc_16k_146x215mm
prc_7_160x230mm
roc_16k_7.75x10.25in
om_juuro-ku-kai_198x275mm
om_pa-kai_267x389mm
roc_8k_10.75x15.5in
om_dai-pa-kai_275x395mm
prc_10_324x458mm
om_small-photo_100x150mm
om_italian_100x230mm
om_postfix_114x229mm
om_large-photo_200x300
om_folio_210x330mm
om_folio-sp_215x315mm
om_invite_220x220mm

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hey Terry,

Sigh.  I forgot to update clone LaserJet devices and it looks like there
was a hole in the dependancy generation.

I have updated CVS again.

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

Hi Mark,

I've retreived the CVS tree but I susspect it is not quite up to date.
I get lots of compilation errors such as:

Brother_MFC_P2000.cpp: In method `void Brother_MFC_P2000::commonInit()':
Brother_MFC_P2000.cpp:64: `PT_AUTO_ROTATE' is not a member of type
`Brother_PCL_Instance'

Terry

Mark Hamzy wrote:

> Hey Terry,
>
> Thanks for catching that.  I have made a lot of changes and put them in
> CVS.  Can you extract them and try it?
>
> Mark
>
> Take a look at the Linux Omni printer driver at
> http://www.ibm.com/linux/ltc/projects/omni/
>
> _______________________________________________
> Omniprint-user mailing list
> Omn...@li...
> https://lists.sourceforge.net/lists/listinfo/omniprint-user

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hey Terry,

Thanks for catching that.  I have made a lot of changes and put them in
CVS.  Can you extract them and try it?

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

Re: [Omniprint-user] Problem with HP-LaserJet_III

[Mark H. <ha...@us...>]

Hi Terry,

Thanks for reporting the error.

> I am using RedHat 7.2 with latest updates (12/11/01) using Omni 0.5.0
> and am having
> printing problems. As the printer configuration system has got so messy
> in RedHat 7.2
> I have simplified the problem to running ghostscript manually with the
> following command:
>
> gs -sDEVICE=omni -sDeviceName="HP_LaserJet_III" -r300x300
> -sOutputFile=out.lj -sPAPERSIZE=a4
>
> Using this command gives two errors:
>
> 1. A page is first emitted with a single line "@PJL ENTER LANGUAGE=PCL"
> at the top.

I dug up a LaserJet III to test with and it is broken.  So, can you try
the following:
   edit HP LaserJet/HP LaserJet III.xml
   remove line 32 that should say "<DeviceOptions type="PT_SUPPORT_PJL"/>"

This should remove that from the printout.

> 2. At the second page the printer stops with the message "Load Letter"
> and will complete the
> print if the "continue" button on the printer is pressed. The page
> printed is offset off the top of the paper.

Ghostscript is an application that needs to be told the papersize.  Also,
we need to be told the papersize.  Right now, we both have different
command line parameters for that.

Can you add '-sproperties="form=FORM_A4"' to the command line?

Hopefully, that should fix both errors.

Thanks,

Mark

Take a look at the Linux Omni printer driver at
http://www.ibm.com/linux/ltc/projects/omni/

[Omniprint-user] Problem with HP-LaserJet_III

[Terry B. <te...@be...>]

I am using RedHat 7.2 with latest updates (12/11/01) using Omni 0.5.0
and am having
printing problems. As the printer configuration system has got so messy
in RedHat 7.2
I have simplified the problem to running ghostscript manually with the
following command:

gs -sDEVICE=omni -sDeviceName="HP_LaserJet_III" -r300x300
-sOutputFile=out.lj -sPAPERSIZE=a4

Using this command gives two errors:

1. A page is first emitted with a single line "@PJL ENTER LANGUAGE=PCL"
at the top.
2. At the second page the printer stops with the message "Load Letter"
and will complete the
print if the "continue" button on the printer is pressed. The page
printed is offset off the top of the paper.

I pursume these are bugs with the driver .....

Terry

--
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: te...@be...        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"