[Printing-architecture] Questions about Ghostscript and IJS and OpenPrinting Vector

Fujinaka, Todd todd.fujinaka at intel.com
Fri Jul 28 15:16:45 PDT 2006


Please forgive the simplicity of these questions, but since I'm going to
have to evaluate IJS and OpenPrinting vector and then add them to the
LSB standard, I have a few questions. I'm sure I'll have to dive into
the code, but I thought some pointers would help me so I don't get lost.

First, does the open IJS standard map to the HP standard? The IJS page
on LinuxPrinting.org appears to be just a skeleton
www.linuxprinting.org/ijs.

It looks like both IJS and OpenPrinting vector use ghostscript to
convert Postscript or PDF to API calls, and then a plugin with the API
definition talks to the output device. The APIs are defined but I'm not
quite sure what happens on both sides of that API, so that's just a
guess. It also looks like there's glue code linked into ghostscript that
creates the API calls as well as drivers that consume the calls and then
talk to the output device. Please correct me if I'm wrong.

If that's the case, does the driver have any access back into
ghostscript? If not, can a plugin be provided as a binary with no
source? (This is with the assumption that we're using the GPL version of
ghostscript.)

Thanks for any help.
Todd




More information about the Printing-architecture mailing list