[gs-devel] xefitra internalise ijs?
lazer1 at blueyonder.co.uk
Mon Nov 19 13:10:04 PST 2007
On 19-Nov-07, Till Kamppeter wrote:
>IJS is intended as a plug-in interface. It depends on external driver
>binaries which are specific to the printer. This allows to create a
>driver and to add it to a system without needing to compile Ghostscript.
>This way printer manufacturers could make printer drivers which users
>can easily install without knowledge of compiling programs. This is a
>very important step to make printing user-friendly.
>In addition, this allows the driver and Ghostscript having different
>licenses. So manufacturers can easily publish a closed-source driver,
>without steps like buying a commercial license for Ghostscript or any
>other program (and then even replacing system components by their own
>Also a driver in a separate plug-in can be easily used with another
>renderer than Ghostscript, for example Poppler, a PDF renderer (Note
>that PostScript will soon be replaced by PDF as standard print job format).
>Drivers which are built into Ghostscript are deprecated due to all the
>advantages of plug-ins which I have mentioned above. Other plug-in
>interfaces are CUPS Raster and OpenPrinting Vector.
the disadvantage is that it prevents all printers being usable from all
you have to be on a platform that the manufacturer decides to support
and that will usually be Windows.
I dont understand why printers will use closed source drivers as all the
is in the printer itself not the driver, eg all monitors use VGA.
what they should do is standardise a bitmap protocol to the printer and
move the driver to the printer itself, that way all printers by all
would be supported on all platforms.
eg standardise an opensource line compression algorithm as that is the main
The standardisation concept has been used for ATA, SCSI, VGA, mice, keyboards,
I dont see why it cannot be used for printers. eg there are 100s of different
hard drives manufactured and you can essentially use all of them on all
>> On 19-Nov-07, Ralph Giles wrote:
>>> On Mon, Nov 19, 2007 at 08:03:57PM +0100, lazer1 wrote:
>>>> I was wondering if it is possible for Ghostscript to
>>>> internalise ijs?
>>> Can you be more clear about this? Ghostscript already includes an IJS
>>> client internally. There are other tools, such as cups and foomatic
>>> which can look up how to invoke gs to print to a specific printer for
>> but does the gs ijs client depend on an external ijs server binary in order
>> print things?
>> if it does, my question is whether the external binary can be incorporated
>> into gs?
>> ie so that you could print things entirely via gs and no other binaries
>> the way traditional gs printer drivers function.
>> if gs can do that anyway can you give an example command line for an
>> example printer of how you would convert say annots.pdf to
>> a printer binary file for that printer.
>> for instance for say epson you can create a binary thus:
>> gs -sDEVICE=epson -dBATCH -dNOPAUSE -sOutputFile=somefile%d annots.pdf
>> and then in an OS dependent way the binary files just need to be
>> sent down a parallel port to the printer.
>> can this be done via gs ijs using some platform-independent driver file
>> for supported printers?
>> because I got the impression that I needed to port another program an ijs
>> in order to utilise the gs ijs driver.
>> gs-devel mailing list
>> gs-devel at ghostscript.com
More information about the gs-devel