From de4e2b578a7b2354135af9049d2ff2aab68fbb02 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 10 Apr 2003 20:03:44 +0000 Subject: Use more stricter syntax and work towards Docbook XML migration (This used to be commit ab8db2ad7d30da4b923bfa11e5c3295446103911) --- docs/docbook/projdoc/CUPS-printing.sgml | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) (limited to 'docs/docbook/projdoc/CUPS-printing.sgml') diff --git a/docs/docbook/projdoc/CUPS-printing.sgml b/docs/docbook/projdoc/CUPS-printing.sgml index fd954cc1c5..ea10ba0e75 100644 --- a/docs/docbook/projdoc/CUPS-printing.sgml +++ b/docs/docbook/projdoc/CUPS-printing.sgml @@ -23,7 +23,7 @@ a very mystical tool. There is a great deal of uncertainty regarding CUPS and ho it works. The result is seen in a large number of posting on the samba mailing lists expressing frustration when MS Windows printers appear not to work with a CUPS backr-end. -/para> + This is a good time to point out how CUPS can be used and what it does. CUPS is more @@ -112,8 +112,8 @@ do any print file format conversion work. The CUPS files that need to be correctly set for RAW mode printers to work are: - /etc/cups/mime.types - /etc/cups/mime.convs + /etc/cups/mime.types + /etc/cups/mime.convs Both contain entries that must be uncommented to allow RAW mode @@ -172,6 +172,7 @@ the process of determining proper treatment while in the print queue system. * application/vnd.cups-postscript + @@ -186,14 +187,14 @@ the filtered file could possibly have an unwanted PJL header. "application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or "<04>%". +have as their first character string one of "%!" or ">04<%". "application/vnd.cups-postscript" will files which contain the string "LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -("<1B>%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS +(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced with a "Generic PostScript driver" will just be tagged "application/postscript". @@ -1072,7 +1073,7 @@ The recommended driver is "ljet4". It has a link to the page for the ljet4 driver too: -http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 +http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 On the driver's page, you'll find important and detailed info about how to use @@ -1173,6 +1174,7 @@ Summary - You need: Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo. Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h") + In the case of the "hpijs" driver, you need a Ghostscript version, which @@ -1227,6 +1229,8 @@ for the whereabouts of your Windows-originating printjobs: are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type? + + -- cgit