> is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. </para>
> is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. </para>
<glossseealso otherterm="gloss-tdeprinthandbook"
<glossseealso otherterm="gloss-tdeprinthandbook"
>KDEPrint Handbook</glossseealso>
>TDEPrint Handbook</glossseealso>
</glossdef>
</glossdef>
</glossentry>
</glossentry>
@ -442,7 +442,7 @@
><para
><para
>Foomatic started out as the wrapper name for a set of different tools available from <ulink url="http://www.linuxprinting.org/"
>Foomatic started out as the wrapper name for a set of different tools available from <ulink url="http://www.linuxprinting.org/"
>Linuxprinting.org</ulink
>Linuxprinting.org</ulink
> These tools aimed to make the usage of traditional Ghostscript and other print filters easier for users and extend the filters' capabilities by adding more command line switches or explain the driver's execution data. Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and Direct-O-Matic. All of these allow the generation of appropriate printer configuration files online, by simply selection the suitable model and suggested (or alternate) driver for that machine. More recently, Foomatic gravitated towards becoming a "meta-spooling" system, that allows configuration of the underlying print subsystem through a unified set of commands (however, this is much more complicated than KDEPrint's &GUI; interface, which performs a similar task with regards to different print subsystems). </para>
> These tools aimed to make the usage of traditional Ghostscript and other print filters easier for users and extend the filters' capabilities by adding more command line switches or explain the driver's execution data. Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and Direct-O-Matic. All of these allow the generation of appropriate printer configuration files online, by simply selection the suitable model and suggested (or alternate) driver for that machine. More recently, Foomatic gravitated towards becoming a "meta-spooling" system, that allows configuration of the underlying print subsystem through a unified set of commands (however, this is much more complicated than TDEPrint's &GUI; interface, which performs a similar task with regards to different print subsystems). </para>
<glossseealso otherterm="gloss-cups-o-matic"
<glossseealso otherterm="gloss-cups-o-matic"
>&CUPS;-O-Matic</glossseealso
>&CUPS;-O-Matic</glossseealso
> <glossseealso otherterm="gloss-PPD-O-Matic"
> <glossseealso otherterm="gloss-PPD-O-Matic"
@ -589,11 +589,11 @@
<glossentry id="gloss-tdeprint">
<glossentry id="gloss-tdeprint">
<glossterm
<glossterm
><acronym
><acronym
>KDEPrint</acronym
>TDEPrint</acronym
></glossterm>
></glossterm>
<glossdef
<glossdef
><para
><para
>The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...) into nice &kde; desktop &GUI; windows and dialogues to ease their usage. Most important for day-to-day usage is "kprinter", the new &GUI; print command. -- Note: KDEPrint does <emphasis
>The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...) into nice &kde; desktop &GUI; windows and dialogues to ease their usage. Most important for day-to-day usage is "kprinter", the new &GUI; print command. -- Note: TDEPrint does <emphasis
>not</emphasis
>not</emphasis
> implement its own spooling mechanism or its own &PostScript; processing; for this it relies on the selected <emphasis
> implement its own spooling mechanism or its own &PostScript; processing; for this it relies on the selected <emphasis
>...is the name of the reference document that describes KDEPrint functions to users and administrators. You can load it into Konqueror by typing "help:/tdeprint" into the address field. The <ulink url="http://printing.kde.org/"
>...is the name of the reference document that describes TDEPrint functions to users and administrators. You can load it into Konqueror by typing "help:/tdeprint" into the address field. The <ulink url="http://printing.kde.org/"
>KDEPrint website</ulink
>TDEPrint website</ulink
> is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt Pfeifle. </para>
> is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt Pfeifle. </para>
<glossseealso otherterm="gloss-cupsfaq"
<glossseealso otherterm="gloss-cupsfaq"
>&CUPS;-FAQ</glossseealso>
>&CUPS;-FAQ</glossseealso>
@ -873,7 +873,7 @@
>P</emphasis
>P</emphasis
>rinter <emphasis
>rinter <emphasis
>D</emphasis
>D</emphasis
>escription; PPDs are ASCII files storing all information about the special capabilities of a printer, plus definitions of the (PostScript- or PJL-) commands to call on a certain capability (like print duplexing). As the explanation of the acronym reveals, PPDs were originally only used for &PostScript; printers. &CUPS; has extended the PPD concept to all types of printers. PPDs for &PostScript; printers are provided by the printer vendors. They can be used with &CUPS; and KDEPrint to have access to the full features of any &PostScript; printer. The KDEPrint Team recommends using a PPD originally intended for use with &Microsoft; Windows NT. PPDs for non-PostScript printers <emphasis
>escription; PPDs are ASCII files storing all information about the special capabilities of a printer, plus definitions of the (PostScript- or PJL-) commands to call on a certain capability (like print duplexing). As the explanation of the acronym reveals, PPDs were originally only used for &PostScript; printers. &CUPS; has extended the PPD concept to all types of printers. PPDs for &PostScript; printers are provided by the printer vendors. They can be used with &CUPS; and TDEPrint to have access to the full features of any &PostScript; printer. The TDEPrint Team recommends using a PPD originally intended for use with &Microsoft; Windows NT. PPDs for non-PostScript printers <emphasis
>need</emphasis
>need</emphasis
> a companion "filter" to process the &PostScript; print files into a format digestible for the non-PostScript target device. Those PPD/filter combos are not (yet) available from the vendors. After the initiative by the &CUPS; developers to utilise PPDs, the Free Software community was creative enough to quickly come up with support for most of the currently used printer models, through PPDs and classical Ghostscript filters. But note: the printout quality varies from "hi-quality photographic output" (using Gimp-Print with most Epson inkjets) to "hardly readable" (using Foomatic-enabled Ghostscript filters for models rated as "paperweight" in the Linuxprinting.org database). </para>
> a companion "filter" to process the &PostScript; print files into a format digestible for the non-PostScript target device. Those PPD/filter combos are not (yet) available from the vendors. After the initiative by the &CUPS; developers to utilise PPDs, the Free Software community was creative enough to quickly come up with support for most of the currently used printer models, through PPDs and classical Ghostscript filters. But note: the printout quality varies from "hi-quality photographic output" (using Gimp-Print with most Epson inkjets) to "hardly readable" (using Foomatic-enabled Ghostscript filters for models rated as "paperweight" in the Linuxprinting.org database). </para>
<glossseealso otherterm="gloss-cups"
<glossseealso otherterm="gloss-cups"
@ -890,7 +890,7 @@
>PPD-O-Matic</glossterm>
>PPD-O-Matic</glossterm>
<glossdef
<glossdef
><para
><para
>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org web server and can be used online to generate PPDs for any printer that is known to print with Ghostscript. These PPDs can be hooked up to &CUPS;/KDEPrint, as well as used inside PPD-aware applications like StarOffice to determine all different parameters of your printjobs. It is now recommended, in most cases, to use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. To generate a PPD, go to the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org web server and can be used online to generate PPDs for any printer that is known to print with Ghostscript. These PPDs can be hooked up to &CUPS;/TDEPrint, as well as used inside PPD-aware applications like StarOffice to determine all different parameters of your printjobs. It is now recommended, in most cases, to use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. To generate a PPD, go to the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
>printer database</ulink
>printer database</ulink
>, select your printer model, follow the link to show the available Ghostscript filters for that printer, select one, click "generate" and finally save the file to your local system. Be sure to read the instructions. Make sure that your local system does indeed have Ghostscript and the filter, which you chose before generating the PPD, installed. </para>
>, select your printer model, follow the link to show the available Ghostscript filters for that printer, select one, click "generate" and finally save the file to your local system. Be sure to read the instructions. Make sure that your local system does indeed have Ghostscript and the filter, which you chose before generating the PPD, installed. </para>
<glossseealso otherterm="gloss-postscript"
<glossseealso otherterm="gloss-postscript"
@ -969,7 +969,7 @@
>print:/ KIO Slave</glossterm>
>print:/ KIO Slave</glossterm>
<glossdef
<glossdef
><para
><para
>You can use a syntax of "print:/..." to get quick access to KDEPrint resources. Typing "print:/manager" as a Konqueror URL address gives administrative access to KDEPrint. Konqueror uses &kde;'s famous "KParts" technology to achieve that. </para>
>You can use a syntax of "print:/..." to get quick access to TDEPrint resources. Typing "print:/manager" as a Konqueror URL address gives administrative access to TDEPrint. Konqueror uses &kde;'s famous "KParts" technology to achieve that. </para>
<glossseealso otherterm="gloss-ioslave"
<glossseealso otherterm="gloss-ioslave"
>IO Slave</glossseealso
>IO Slave</glossseealso
> <glossseealso otherterm="gloss-kparts"
> <glossseealso otherterm="gloss-kparts"
@ -996,7 +996,7 @@
></glossterm>
></glossterm>
<glossdef
<glossdef
><para
><para
>Qt&CUPS; and KUPS were the predecessors of KDEPrint; they are now deprecated and no longer maintained. What was good in qtcups is all inherited by "kprinter", the new KDE print dialogue (which is much improved over qtcups); what you liked about kups is now all in the KDEPrint Manager (accessible via the KDE Control Centre or via the URL "print:/manager" from Konqueror) -- with more functionality and less bugs... Its former developer, Michael Goffioul, is now the developer of KDEPrint -- a very nice and productive guy and quick bug fixer... </para>
>Qt&CUPS; and KUPS were the predecessors of TDEPrint; they are now deprecated and no longer maintained. What was good in qtcups is all inherited by "kprinter", the new TDE print dialogue (which is much improved over qtcups); what you liked about kups is now all in the TDEPrint Manager (accessible via the KDE Control Centre or via the URL "print:/manager" from Konqueror) -- with more functionality and less bugs... Its former developer, Michael Goffioul, is now the developer of TDEPrint -- a very nice and productive guy and quick bug fixer... </para>
<glossseealso otherterm="gloss-kprinter"
<glossseealso otherterm="gloss-kprinter"
>kprinter</glossseealso>
>kprinter</glossseealso>
</glossdef>
</glossdef>
@ -1064,9 +1064,9 @@
>P</emphasis
>P</emphasis
>rinting <emphasis
>rinting <emphasis
>R</emphasis
>R</emphasis
>equest; this is a BSD-style printing system, that needs no root privileges to be installed, and no "printcap" to work: all parameters may be specified on the command line. RLPR comes in handy for many laptop users who are working in frequently changing environments. This is because it may be installed concurrently with every other printing sub system, and allows a very flexible and quick way to install a printer for direct access via LPR/LPD. KDEPrint has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time.</para>
>equest; this is a BSD-style printing system, that needs no root privileges to be installed, and no "printcap" to work: all parameters may be specified on the command line. RLPR comes in handy for many laptop users who are working in frequently changing environments. This is because it may be installed concurrently with every other printing sub system, and allows a very flexible and quick way to install a printer for direct access via LPR/LPD. TDEPrint has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time.</para>
> is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. </para>
> is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. </para>
<glossseealso otherterm="gloss-tdeprinthandbook"
<glossseealso otherterm="gloss-tdeprinthandbook"
>KDEPrint Handbook</glossseealso>
>TDEPrint Handbook</glossseealso>
</glossdef>
</glossdef>
</glossentry>
</glossentry>
@ -442,7 +442,7 @@
><para
><para
>Foomatic started out as the wrapper name for a set of different tools available from <ulink url="http://www.linuxprinting.org/"
>Foomatic started out as the wrapper name for a set of different tools available from <ulink url="http://www.linuxprinting.org/"
>Linuxprinting.org</ulink
>Linuxprinting.org</ulink
> These tools aimed to make the usage of traditional Ghostscript and other print filters easier for users and extend the filters' capabilities by adding more command line switches or explain the driver's execution data. Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and Direct-O-Matic. All of these allow the generation of appropriate printer configuration files online, by simply selection the suitable model and suggested (or alternate) driver for that machine. More recently, Foomatic gravitated towards becoming a "meta-spooling" system, that allows configuration of the underlying print subsystem through a unified set of commands (however, this is much more complicated than KDEPrint's &GUI; interface, which performs a similar task with regards to different print subsystems). </para>
> These tools aimed to make the usage of traditional Ghostscript and other print filters easier for users and extend the filters' capabilities by adding more command line switches or explain the driver's execution data. Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and Direct-O-Matic. All of these allow the generation of appropriate printer configuration files online, by simply selection the suitable model and suggested (or alternate) driver for that machine. More recently, Foomatic gravitated towards becoming a "meta-spooling" system, that allows configuration of the underlying print subsystem through a unified set of commands (however, this is much more complicated than TDEPrint's &GUI; interface, which performs a similar task with regards to different print subsystems). </para>
<glossseealso otherterm="gloss-cups-o-matic"
<glossseealso otherterm="gloss-cups-o-matic"
>&CUPS;-O-Matic</glossseealso
>&CUPS;-O-Matic</glossseealso
> <glossseealso otherterm="gloss-PPD-O-Matic"
> <glossseealso otherterm="gloss-PPD-O-Matic"
@ -589,11 +589,11 @@
<glossentry id="gloss-tdeprint">
<glossentry id="gloss-tdeprint">
<glossterm
<glossterm
><acronym
><acronym
>KDEPrint</acronym
>TDEPrint</acronym
></glossterm>
></glossterm>
<glossdef
<glossdef
><para
><para
>The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...) into nice &kde; desktop &GUI; windows and dialogues to ease their usage. Most important for day-to-day usage is "kprinter", the new &GUI; print command. -- Note: KDEPrint does <emphasis
>The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...) into nice &kde; desktop &GUI; windows and dialogues to ease their usage. Most important for day-to-day usage is "kprinter", the new &GUI; print command. -- Note: TDEPrint does <emphasis
>not</emphasis
>not</emphasis
> implement its own spooling mechanism or its own &PostScript; processing; for this it relies on the selected <emphasis
> implement its own spooling mechanism or its own &PostScript; processing; for this it relies on the selected <emphasis
>...is the name of the reference document that describes KDEPrint functions to users and administrators. You can load it into Konqueror by typing "help:/tdeprint" into the address field. The <ulink url="http://printing.kde.org/"
>...is the name of the reference document that describes TDEPrint functions to users and administrators. You can load it into Konqueror by typing "help:/tdeprint" into the address field. The <ulink url="http://printing.kde.org/"
>KDEPrint website</ulink
>TDEPrint website</ulink
> is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt Pfeifle. </para>
> is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt Pfeifle. </para>
<glossseealso otherterm="gloss-cupsfaq"
<glossseealso otherterm="gloss-cupsfaq"
>&CUPS;-FAQ</glossseealso>
>&CUPS;-FAQ</glossseealso>
@ -873,7 +873,7 @@
>P</emphasis
>P</emphasis
>rinter <emphasis
>rinter <emphasis
>D</emphasis
>D</emphasis
>escription; PPDs are ASCII files storing all information about the special capabilities of a printer, plus definitions of the (PostScript- or PJL-) commands to call on a certain capability (like print duplexing). As the explanation of the acronym reveals, PPDs were originally only used for &PostScript; printers. &CUPS; has extended the PPD concept to all types of printers. PPDs for &PostScript; printers are provided by the printer vendors. They can be used with &CUPS; and KDEPrint to have access to the full features of any &PostScript; printer. The KDEPrint Team recommends using a PPD originally intended for use with &Microsoft; Windows NT. PPDs for non-PostScript printers <emphasis
>escription; PPDs are ASCII files storing all information about the special capabilities of a printer, plus definitions of the (PostScript- or PJL-) commands to call on a certain capability (like print duplexing). As the explanation of the acronym reveals, PPDs were originally only used for &PostScript; printers. &CUPS; has extended the PPD concept to all types of printers. PPDs for &PostScript; printers are provided by the printer vendors. They can be used with &CUPS; and TDEPrint to have access to the full features of any &PostScript; printer. The TDEPrint Team recommends using a PPD originally intended for use with &Microsoft; Windows NT. PPDs for non-PostScript printers <emphasis
>need</emphasis
>need</emphasis
> a companion "filter" to process the &PostScript; print files into a format digestible for the non-PostScript target device. Those PPD/filter combos are not (yet) available from the vendors. After the initiative by the &CUPS; developers to utilise PPDs, the Free Software community was creative enough to quickly come up with support for most of the currently used printer models, through PPDs and classical Ghostscript filters. But note: the printout quality varies from "hi-quality photographic output" (using Gimp-Print with most Epson inkjets) to "hardly readable" (using Foomatic-enabled Ghostscript filters for models rated as "paperweight" in the Linuxprinting.org database). </para>
> a companion "filter" to process the &PostScript; print files into a format digestible for the non-PostScript target device. Those PPD/filter combos are not (yet) available from the vendors. After the initiative by the &CUPS; developers to utilise PPDs, the Free Software community was creative enough to quickly come up with support for most of the currently used printer models, through PPDs and classical Ghostscript filters. But note: the printout quality varies from "hi-quality photographic output" (using Gimp-Print with most Epson inkjets) to "hardly readable" (using Foomatic-enabled Ghostscript filters for models rated as "paperweight" in the Linuxprinting.org database). </para>
<glossseealso otherterm="gloss-cups"
<glossseealso otherterm="gloss-cups"
@ -890,7 +890,7 @@
>PPD-O-Matic</glossterm>
>PPD-O-Matic</glossterm>
<glossdef
<glossdef
><para
><para
>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org web server and can be used online to generate PPDs for any printer that is known to print with Ghostscript. These PPDs can be hooked up to &CUPS;/KDEPrint, as well as used inside PPD-aware applications like StarOffice to determine all different parameters of your printjobs. It is now recommended, in most cases, to use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. To generate a PPD, go to the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org web server and can be used online to generate PPDs for any printer that is known to print with Ghostscript. These PPDs can be hooked up to &CUPS;/TDEPrint, as well as used inside PPD-aware applications like StarOffice to determine all different parameters of your printjobs. It is now recommended, in most cases, to use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. To generate a PPD, go to the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
>printer database</ulink
>printer database</ulink
>, select your printer model, follow the link to show the available Ghostscript filters for that printer, select one, click "generate" and finally save the file to your local system. Be sure to read the instructions. Make sure that your local system does indeed have Ghostscript and the filter, which you chose before generating the PPD, installed. </para>
>, select your printer model, follow the link to show the available Ghostscript filters for that printer, select one, click "generate" and finally save the file to your local system. Be sure to read the instructions. Make sure that your local system does indeed have Ghostscript and the filter, which you chose before generating the PPD, installed. </para>
<glossseealso otherterm="gloss-postscript"
<glossseealso otherterm="gloss-postscript"
@ -969,7 +969,7 @@
>print:/ KIO Slave</glossterm>
>print:/ KIO Slave</glossterm>
<glossdef
<glossdef
><para
><para
>You can use a syntax of "print:/..." to get quick access to KDEPrint resources. Typing "print:/manager" as a Konqueror URL address gives administrative access to KDEPrint. Konqueror uses &kde;'s famous "KParts" technology to achieve that. </para>
>You can use a syntax of "print:/..." to get quick access to TDEPrint resources. Typing "print:/manager" as a Konqueror URL address gives administrative access to TDEPrint. Konqueror uses &kde;'s famous "KParts" technology to achieve that. </para>
<glossseealso otherterm="gloss-ioslave"
<glossseealso otherterm="gloss-ioslave"
>IO Slave</glossseealso
>IO Slave</glossseealso
> <glossseealso otherterm="gloss-kparts"
> <glossseealso otherterm="gloss-kparts"
@ -996,7 +996,7 @@
></glossterm>
></glossterm>
<glossdef
<glossdef
><para
><para
>Qt&CUPS; and KUPS were the predecessors of KDEPrint; they are now deprecated and no longer maintained. What was good in qtcups is all inherited by "kprinter", the new KDE print dialogue (which is much improved over qtcups); what you liked about kups is now all in the KDEPrint Manager (accessible via the KDE Control Centre or via the URL "print:/manager" from Konqueror) -- with more functionality and less bugs... Its former developer, Michael Goffioul, is now the developer of KDEPrint -- a very nice and productive guy and quick bug fixer... </para>
>Qt&CUPS; and KUPS were the predecessors of TDEPrint; they are now deprecated and no longer maintained. What was good in qtcups is all inherited by "kprinter", the new TDE print dialogue (which is much improved over qtcups); what you liked about kups is now all in the TDEPrint Manager (accessible via the KDE Control Centre or via the URL "print:/manager" from Konqueror) -- with more functionality and less bugs... Its former developer, Michael Goffioul, is now the developer of TDEPrint -- a very nice and productive guy and quick bug fixer... </para>
<glossseealso otherterm="gloss-kprinter"
<glossseealso otherterm="gloss-kprinter"
>kprinter</glossseealso>
>kprinter</glossseealso>
</glossdef>
</glossdef>
@ -1064,9 +1064,9 @@
>P</emphasis
>P</emphasis
>rinting <emphasis
>rinting <emphasis
>R</emphasis
>R</emphasis
>equest; this is a BSD-style printing system, that needs no root privileges to be installed, and no "printcap" to work: all parameters may be specified on the command line. RLPR comes in handy for many laptop users who are working in frequently changing environments. This is because it may be installed concurrently with every other printing sub system, and allows a very flexible and quick way to install a printer for direct access via LPR/LPD. KDEPrint has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time.</para>
>equest; this is a BSD-style printing system, that needs no root privileges to be installed, and no "printcap" to work: all parameters may be specified on the command line. RLPR comes in handy for many laptop users who are working in frequently changing environments. This is because it may be installed concurrently with every other printing sub system, and allows a very flexible and quick way to install a printer for direct access via LPR/LPD. TDEPrint has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time.</para>
Darrell Anderson
13 years ago