> In other words, it's trying to use the compiled mode, not the XML
> mode. What am I doing wrong?
Yes. The -sDeviceName=XXX is the parameter to say which device library to
use. The
compiled devices are still valid but are not compiled by default. Instead
the is only
one device library (libXMLOmniDevice.so) now. This device library can
emulate any omni
device with a required job property XMLMasterFile=XXX.
So, the correct gs options are:
gs -q -dPARANOIDSAFER -dBATCH -dNOPAUSE -sOutputFile=- -sDEVICE=omni
-sDeviceName=libXMLOmniDevice.so
-sproperties='XMLMasterFile="/opt/Omni/share/IBM Infoprint 70.xml"
form=iso_a4_2100.00x2970.00mm tray=TRAY_AUTO media=MEDIA_PLAIN
resolution=600x600 printmode=PRINT_MODE_1_ANY
dither=DITHER_STUCKI_DIFFUSION orientation=portrait HardwareScaling=0' -
I have put a new docs/Usage and OmniDeviceOptions.cpp in CVS to make it
easier for users.
Mark
Take a look at the Linux Omni Printer Driver Framework at
http://www.ibm.com/linux/ltc/projects/omni/
> But it suggests that the foomatic data that Omni generates is
> incorrect, doesn't it?
I left it in as a visible reminder/warning/todo. I don't know if it is a
problem or not,
it just looks like a potential problem to me. Hopefully, the authority,
Till, could make
a ruling. :)
Mark
Take a look at the Linux Omni Printer Driver Framework at
http://www.ibm.com/linux/ltc/projects/omni/
On Fri, Apr 04, 2003 at 11:07:32AM -0600, Mark Hamzy wrote:
> I have put a new docs/Usage and OmniDeviceOptions.cpp in CVS to make it
> easier for users.
But it suggests that the foomatic data that Omni generates is
incorrect, doesn't it?
Tim.
*/
