9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] HP: Printing with the Illiterate
Date: Fri, 14 Aug 2009 21:48:18 -0400	[thread overview]
Message-ID: <3aaafc130908141848n7a24547as64078c05e71c779@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0908141806g493b00e6w31ee3ff0a5641820@mail.gmail.com>

On Fri, Aug 14, 2009 at 9:06 PM, Russ Cox<rsc@swtch.com> wrote:
> On Fri, Aug 14, 2009 at 5:37 PM, J.R. Mauro<jrm8005@gmail.com> wrote:
>> IJS is probably it; that's the PCL driver for the home-office class printers.
>
> IJS is not PCL.
>
> IJS is a custom protocol that is spoken between a bitmap-producing
> program like Ghostscript and a bitmap-printing program like /usr/bin/hpijs
> http://svn.ghostscript.com/ghostscript/branches/mtrender/ijs/ijs_spec.pdf
>
> /usr/bin/hpijs speaks IJS to Ghostscript (or whatever is on standard
> input/output) and speaks a new HP protocol called LIDIL to the printer
> on the other end.  Rather than commit to a full specification of LIDIL
> and have to worry about backwards compatibility in the future,
> HP chose to use IJS as a shim protocol and distribute a binary
> that talks to the printer (source is available but it's still a binary).
>
> PCL is not in the picture.  Getting PCL out of the picture is exactly
> the reason that IJS and LIDIL were introduced, because LIDIL is
> basically "here is a bitmap" whereas PCL is a real language that
> requires actual memory and computing power inside the printer.
> LIDIL moves the memory and computing requirements out of
> the printer into the computer proper.
>
> Russ
>
>

I thought IJS was also used to turn a raster into PCL, since IIRC some
non-business-class HP printers come with a stripped-down PCL 5e or
some such.

I'm probably wrong again, though. I try to not think about the HP PDLs
too much. Probably it's not IJS I'm thinking of and some other cruft
from HP -- it's been a long time.



  reply	other threads:[~2009-08-15  1:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 10:04 Akshat Kumar
2009-08-14 11:29 ` Akshat Kumar
2009-08-14 17:15   ` Russ Cox
2009-08-15  0:37     ` J.R. Mauro
2009-08-15  1:06       ` Russ Cox
2009-08-15  1:48         ` J.R. Mauro [this message]
2009-08-15  1:56           ` erik quanstrom
2009-08-15  2:12             ` Akshat Kumar
2009-08-15  2:28               ` erik quanstrom
2009-08-15 15:12               ` J.R. Mauro
2009-08-17  7:50               ` Daniel Lyons
2009-08-17  8:09                 ` matt
2009-08-17  9:32                 ` Mechiel Lukkien
2009-08-15 10:58     ` Akshat Kumar
2009-08-15 17:50       ` Akshat Kumar
2009-08-17  2:55         ` Akshat Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3aaafc130908141848n7a24547as64078c05e71c779@mail.gmail.com \
    --to=jrm8005@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).