diff options
author | Slávek Banko <slavek.banko@axis.cz> | 2020-11-17 23:50:55 +0100 |
---|---|---|
committer | Slávek Banko <slavek.banko@axis.cz> | 2020-11-17 23:50:55 +0100 |
commit | dc7d2fcb9b6d044fd9bc1bdc5d077ed11c0686b1 (patch) | |
tree | eb6b216344555e136ff38747f5f3462377c2eacf /tde-i18n-sl/docs/tdebase/khelpcenter/glossary | |
parent | fff371d8d9ed1ea3b1c771fbc07f95a12658e723 (diff) | |
download | tde-i18n-dc7d2fcb9b6d044fd9bc1bdc5d077ed11c0686b1.tar.gz tde-i18n-dc7d2fcb9b6d044fd9bc1bdc5d077ed11c0686b1.zip |
Move the khelpcenter guides to the directory level in which they are installed.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
Diffstat (limited to 'tde-i18n-sl/docs/tdebase/khelpcenter/glossary')
3 files changed, 1369 insertions, 0 deletions
diff --git a/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/CMakeLists.txt b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/CMakeLists.txt new file mode 100644 index 00000000000..db7ae551cf5 --- /dev/null +++ b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/CMakeLists.txt @@ -0,0 +1,7 @@ +# This file is genereted by trinity-automake-cmake-convert script by Fat-Zer + +tde_create_handbook( + DESTINATION khelpcenter/glossary + NOINDEX + LANG sl +) diff --git a/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/Makefile.am b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/Makefile.am new file mode 100644 index 00000000000..0149bf1975a --- /dev/null +++ b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = sl +SUBDIRS = $(AUTODIRS) +KDE_DOCS = khelpcenter/glossary +KDE_MANS = AUTO diff --git a/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook new file mode 100644 index 00000000000..cf4063a5839 --- /dev/null +++ b/tde-i18n-sl/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook @@ -0,0 +1,1358 @@ + +<!-- +<?xml version="1.0" ?> +<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" +"customization/dtd/kdex.dtd" [ +<!ENTITY % addindex "IGNORE"> +<!ENTITY % Slovenian "INCLUDE"> +<!ENTITY glossary-tdeprinting SYSTEM "tdeprintingglossary.docbook"> + +]> +<glossary id="glossary"> +--> + <glossdiv id="glossdiv-printing"> + <title>Tiskanje</title> + + + <glossentry id="gloss-acl"> + <glossterm><acronym>ACLs</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>A</emphasis>ccess + <emphasis>C</emphasis>ontrol <emphasis>L</emphasis>ists; + ACLs are used to check for the access by a given + (authenticated) user. A first rough support for ACLs + for printing is available from &CUPS;; this will be refined + in future versions. </para> + <glossseealso otherterm="gloss-authentication"/>Authentication</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-appsocketprotocol"> + <glossterm>AppSocket Protocol</glossterm> + <glossdef><para>AppSocket is a protocol for the transfer of + print data, also frequently called "Direct TCP/IP Printing". + &Hewlett-Packard; have used AppSocket to add a few minor + extensions around it and were very successfull to re-name + and market it under the brand "&HP; JetDirect"...</para> + <glossseealso otherterm="gloss-hpjetdirectprotocol"/>&HP; JetDirect Protocol</glossseealso> + <glossseealso otherterm="gloss-directtcpipprinting"/>Direct TCP/IP Printing</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-apsfilter"> + <glossterm>APSfilter</glossterm> + <glossdef><para>APSfilter is used mainly in the context of "classical" + &UNIX; printing (BSD-style LPD). It is a sophisticated shell script, + disguising as an "all-in-one" filtering program. In reality, + APSfilter calls "real filters" to do the jobs needed. It sends + printjobs automatically through these other filters, based on an + initial file-type analysis of the printfile. + It is written and maintained by Andreas Klemm. +<!-- + </para> + <para> +--> + It is + similar to Magicfilter and uses mostly Ghostscript for file conversions. + Some Linux-Distributions (like SuSE) use APSfilter, others + Magicfilter (⪚ &RedHat;), some have both for preference selection + (like has *BSD). +<!-- + </para> + <para> +--> + &CUPS; has <emphasis>no</emphasis> need for APSfilter, + as it runs its own file type recognition (based on &MIME; types) + and applies its own filtering logic.</para> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + <glossseealso otherterm="gloss-magicfilter"/>Magicfilter</glossseealso> + <glossseealso otherterm="gloss-mimetypes"/>&MIME;-Types</glossseealso> + <glossseealso otherterm="gloss-printcap"/>printcap</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-authentication"> + <glossterm>Authentication</glossterm> + <glossdef><para>Proofing the identity of a certain person (maybe via username/password + or by means of a certificate) is often called authentication. Once you are + authenticated, you may or may not get access to a requested ressource, + possibly based on ACLs.</para> + <glossseealso otherterm="gloss-acl"/>ACLs</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-bidirectionalcommunication"> + <glossterm>Bi-directional communication</glossterm> + <glossdef><para>In the context of printing, a server or a host may receive additional + information sent back from the printer (status messages &etc;), either + upon a query or unrequested. AppSocket ( = &HP; JetDirect), &CUPS; and IPP do + support bi-directional communication, LPR/LPD and BSD-style printing + do not...</para> + <glossseealso otherterm="gloss-appsocketprotocol"/>AppSocket Protocol</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-directtcpipprinting"/>Direct TCP/IP Printing</glossseealso> + <glossseealso otherterm="gloss-hpjetdirectprotocol"/>&HP; JetDirect</glossseealso> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-lprlpd"/>LPR/LPD</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-bsdstyleprinting"> + <glossterm>BSD-style Printing</glossterm> + <glossdef><para>Generic term for different variants of the traditional &UNIX; + printing method. Its first version appeared in the early 70s on + BSD &UNIX; and was formally described in <ulink url="http://www.rfc.net/rfc1179.html">RFC 1179</ulink> only as late + as 1990. +<!-- + </para> + <para> +--> + At the time when BSD "remote" printing was first designed, printers + were serially or otherwise directly connected devices to a host + (with the internet hardly consisting of more than 100 nodes!); printers + used pre-punched, endless paperbands, fed through by a tractor + mechanism, with simple rows of ASCII text mechanically hammered onto + the medium, drawn from a cardboard beneath the table, giving it back + as a zig-zag folded paper"snake". Remote printing consisted in + neighouring host from the next room sending a file + asking for printout. +<!-- + </para> + <para> +--> + How technology has changed! Printers use cut-sheet media, they have + built-in intelligence to compute the raster images of pages after pages + that are sent to them using one of the powerfull page description + languages (PDL), many are network nodes in their own right, + with CPU, RAM, HardDisk and an own Operation System and + they are hooked to a net with potentially millions of users... +<!-- + </para> + <para> +--> + It is a vast proof of the flexible &UNIX; concept for doing things, + that it made "Line Printing" reliably work even under these modern + conditions. But time has finally come now to go for something new + -- the IPP. + </para> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-lprlpd"/>LPR/LPD printing</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-cups"> + <glossterm>&CUPS;</glossterm> + <glossdef><para>Abbreviation for <emphasis>C</emphasis>ommon + <emphasis>U</emphasis>NIX <emphasis>P</emphasis>rinting + <emphasis>S</emphasis>ystem; &CUPS; is most modern &UNIX; and Linux + printing system, providing also cross-platform printservices + to &Microsoft; &Windows; and Apple MacOS clients. Based on IPP, it does + away with all the pitfalls of old-style BSD printing, + providing authentication, encryption and ACLs, plus many more + features. At the same time it is backward-compatible enough + to serve all legacy clients that are not yet up to IPP via + LPR/LPD (BSD-style). +<!-- + </para> + <para> +--> + &CUPS; is able to control any &PostScript; printer by + utilizing the vendor-supplied PPD (PostScript Printer + Description file), targetted originally for &Microsoft; Windows NT + printing only. &kde; Printing is most powerful if based on + &CUPS;.</para> + <glossseealso otherterm="gloss-acl"/>ACLs</glossseealso> + <glossseealso otherterm="gloss-authentication"/>Authentication</glossseealso> + <glossseealso otherterm="gloss-bsdstyleprinting"/>BSD-style printing</glossseealso> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-tdeprint"/>TDEPrint</glossseealso> + <glossseealso otherterm="gloss-lprlpd"/>LPR/LPD</glossseealso> + <glossseealso otherterm="gloss-ppd"/>PPD</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-cupsfaq"> + <glossterm><acronym>&CUPS;-FAQ</acronym></glossterm> + <glossdef><para>Presently only available in German (translation is on the way), + the <ulink url="http://www.danka.de/printpro/faq.html">&CUPS;-FAQ</ulink> + is a valuable ressource to answer many question anyone new to + &CUPS; printing might have at first. + </para> + <glossseealso otherterm="gloss-tdeprinthandbook"/>TDEPrint Handbook</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-cups-o-matic"> + <glossterm>&CUPS;-O-Matic</glossterm> + <glossdef><para>&CUPS;-O-Matic was the first "Third Party" plugin for + the &CUPS; printing software. It is available on the <ulink + url="http://www.linuxprinting.org/cups-doc.html">Linuxprinting.org + website</ulink> to provide an online PPD-generating service. +<!-- + </para> + <para> +--> + + Together with the companion <application>cupsomatic</application> Perl-Script, + that needs to be installed as an additional &CUPS; backend, + it re-directs output from the native <application>pstops</application> filter into + a chain of suitable Ghostscript filters. Upon finishing, it + gives the resulting data back to a &CUPS; "backend" for sending + them onward to the printer. +<!-- + </para> + <para> +--> + Thusly, &CUPS;-O-Matic enables support for any printers known to + have worked previously in a "classical" ghostscript environment, + if no native &CUPS; support for that printer is in sight... &CUPS;-O-Matic + is now replaced by the more capable PPD-O-Matic.</para> + <glossseealso otherterm="gloss-cupsomatic"/>cupsomatic</glossseealso> + <glossseealso otherterm="gloss-PPD-O-Matic"/>PPD-O-Matic</glossseealso> + <glossseealso otherterm="gloss-foomatic"/>Foomatic</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-cupsomatic"> + <glossterm>cupsomatic</glossterm> + <glossdef><para>The Perlscript <application>cupsomatic</application> (plus a working Perl installation + on your system) is needed to make any &CUPS;-O-Matic (or PPD-O-Matic) + generated PPD work with &CUPS;. It was written by Grant Taylor, Author of + the Linux Printing HOWTO and Maintainer of the <ulink + url="http://www.linuxprinting.org/printer_list.cgi">printer + database</ulink> at the Linuxprinting.org website.</para> + <glossseealso otherterm="gloss-cups-o-matic"/>&CUPS;-O-Matic</glossseealso> + <glossseealso otherterm="gloss-foomatic"/>Foomatic</glossseealso> + <glossseealso otherterm="gloss-cupsomatic"/>cupsomatic</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-daemon"> + <glossterm><acronym>Daemon</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>D</emphasis>isk + <emphasis>a</emphasis>nd <emphasis>e</emphasis>xecution + <emphasis>mon</emphasis>itor; <acronym>Daemons</acronym> are present + on all &UNIX; systems to perform tasks independent of user + intervention. Readers more familiar with &Microsoft; &Windows; might + want to compare daemons and the tasks they are responsible + with "services". +<!-- + </para> + <para> +--> + One example of a daemon present on most + legacy &UNIX; systems is the LPD (Line Printer Daemon); &CUPS; is + widely seen as the successor to LPD in the &UNIX; world and + it also operates through a daemon. </para> + <glossseealso otherterm="gloss-spooling"/>SPOOLing</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-databaselinuxprinting"> + <glossterm>Database, Linuxprinting.org</glossterm> + <glossdef><para>Already years ago, when Linux printing was still really difficult + (only commandline printing was known to most Linux users, no device + specific print options were available for doing the jobs), Grant Taylor, + Author of the "Linux Printing HOWTO", collected most or the available + infos about printers, drivers and filters in his database. +<!-- + </para> + <para> +--> + With the emerging + &CUPS; concept, extending the use of PPDs even to non-PostScript printers, + he realized the potential of this database: if one puts the different + datablobs (whith content that could be described along the lines + "Which device prints with which ghostscript or other + filter how well and what commandline switches are available?") into + PPD-compatible files, he could have all the power of &CUPS; on top of + the traditional printer "drivers". +<!-- + </para> + <para> +--> + This has developed now into a broader + concept, known as "Foomatic". Foomatic extends the capabilities + of other spoolers than &CUPS; (LPR/LPD, LPRng, PDQ, PPR) to a certain + extend ("stealing" some concepts from &CUPS;). The Linuxprinting + Database is not a Linux-only stop -- people running other &UNIX; + based OSes (like *BSD or MacOS X) will find valuable infos and + software there too. + </para> + <glossseealso otherterm="gloss-foomatic"/>Foomatic</glossseealso> + <glossseealso otherterm="gloss-linuxprintingdatabase"/>Linuxprinting database</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-directtcpipprinting"> + <glossterm>Direct TCP/IP Printing</glossterm> + <glossdef><para>This is a method that often uses TCP/IP port 9100 to connect + to the printer. It works with many modern network printers and has + a few advantages over LPR/LPD, as it is faster and provides some + "backchannel feedback data" from the printer to the host sending + the job.</para> + <glossseealso otherterm="gloss-appsocketprotocol"/>AppSocket Protocol</glossseealso> + <glossseealso otherterm="gloss-hpjetdirectprotocol"/>&HP; JetDirect Protocol</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-drivers"> + <glossterm>Drivers, Printer Drivers</glossterm> + <glossdef><para>The term "printer drivers", used in the same sense + as on the &Microsoft; &Windows; platform, is not entirely applicable + for a Linux or &UNIX; platform. A "driver" functionality + is supplied on &UNIX; by different modular components working + together. At the core are the "filters" converting a given format + waeiting for their printing, to another format that is acceptable + to the target printer. The filter output is sent to the + printer by a "backend". + </para> + <glossseealso otherterm="gloss-filter"/>Filter</glossseealso> + <glossseealso otherterm="gloss-ppd"/>PPDs</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-easysoftwareproducts"> + <glossterm>Easy Software Products</glossterm> + <glossdef><para>Mike Sweet's company, which has contributed a few substantial + software products towards the Free Software community; amongst + them the initial version of <ulink + url="http://gimp-print.sf.net/">Gimp-Print,</ulink>, the <ulink + url="http://www.easysw.com/epm/">EPM software packaging</ulink> tool + and <ulink url="http://www.easysw.com/htmldoc/">HTMLDOC</ulink> + (used by the "Linux Documentation Project" to build the PDF versions + of the HOWTOs) -- but most importantly: <ulink + url="http://www.cups.org/">&CUPS;</ulink> (the 'Common &UNIX; Printing + System'). +<!-- + </para> + <para> +--> + ESP finance themselves by selling a commercial version + of &CUPS;, called <ulink url="http://www.easysw.com/">ESP PrintPro</ulink>, + that includes some professional enhancements. + </para> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-espprintpro"/>ESP PrintPro</glossseealso> + <glossseealso otherterm="gloss-esp"/>ESP</glossseealso> + <glossseealso otherterm="gloss-gimpprint"/>Gimp-Print</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-encryption"> + <glossterm>Encryption</glossterm> + <glossdef><para>Encryption of confidential data is an all-important issue if + you transfer it over the internet or even inside intra-nets. +<!-- + </para> + <para> +--> + Printing + via traditional protocols is not encrypted at all -- it is very easy + to tap and eavesdrop ⪚ into &PostScript; or PCL data transfered + over the wire. +<!-- + </para> + <para> +--> + Thus in the design of IPP the provision was made for an easy + plugin of encryption mechanisms (which can be provided by the same + means as the encryption standards for HTTP traffic: SSL and TLS.</para> + <glossseealso otherterm="gloss-authentication"/>Authentication</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-ssl"/>SSL</glossseealso> + <glossseealso otherterm="gloss-tls"/>TLS</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-epson"> + <glossterm><acronym>Epson</acronym></glossterm> + <glossdef><para>Epson inkjets belong to the best supported models by Free software + drivers as the company was not necessarily as secretive about their + devices and handed technical specification documents to developers. + The excellent print quality achieved by Gimp-Print on the Styli + series of printers can be attributed to this openness. +<!-- + </para> + <para> +--> + They have also + contracted Easy Software Products to maintain an enhanced version + of Ghostscript ("ESP GhostScript") for improved support of their + printer portfolio. + </para> + <glossseealso otherterm="gloss-ghostscript"/>ESP Ghostscript</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-escapesequence"> + <glossterm>Escape Sequences</glossterm> + <glossdef><para>The first ever printers printed ASCII data only. To + initiate a new line, or eject a page, they included special + command sequences, often carrying a leading [ESC]-character. + &HP; evolved this concept through its series of PCL language + editions until today, when they have developed a fullblown + Page Description Language (PDL) from this humble beginnings. + </para> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + <glossseealso otherterm="gloss-pdl"/>PDL</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-escp"> + <glossterm><acronym>ESC/P</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>E</emphasis>pson + <emphasis>S</emphasis>tandard <emphasis>C</emphasis>odes for + <emphasis>P</emphasis>rinters. Epsons ESC/P printer language is besides + &PostScript; and PCL one of the best known.</para> + <glossseealso otherterm="gloss-escp"/>ESC/P</glossseealso> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-hpgl"/>hpgl</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-esp"> + <glossterm><acronym>ESP</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>E</emphasis>asy + <emphasis>S</emphasis>oftware <emphasis>P</emphasis>roducts; + the company that developed &CUPS; (the "Common &UNIX; Printing System"). + </para> + <glossseealso otherterm="gloss-easysoftwareproducts"/>Easy Software Products</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-espprintpro"/>ESP PrintPro</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-espghostscript"> + <glossterm><acronym>ESP</acronym> Ghostscript</glossterm> + <glossdef><para>A Ghostscript version that is maintained by Easy Software + Products. It includes pre-compiled Gimp-Print drivers for + many inkjets ()plus some other goodies). ESP Ghostscript + drives especially the Epson Stylus model series to photographic + quality in many cases. + </para> + <glossseealso otherterm="gloss-easysoftwareproducts"/>Easy Software Products</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-espprintpro"/>ESP PrintPro</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-espprintpro"> + <glossterm><acronym>ESP</acronym> PrintPro</glossterm> + <glossdef><para> This professional enhancement to &CUPS; (the "Common &UNIX; + Printing System") is sold by the developers + of &CUPS; complete with more than 2.300 printer drivers for several commercial + &UNIX; platforms. <ulink url="http://www.easysw.com/printpro/">ESP PrintPro</ulink> + is supposed to work "out of the box" with little or no configuration + for users or admins. ESP sell also support contracts for + &CUPS; and PrintPro. These sales help to feed the programmers who + develop the Free version of &CUPS;. + </para> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-filter"> + <glossterm>Filter</glossterm> + <glossdef><para>Filters, in general, are programs that take some input + data, work on it and pass it on as their output data. Filters + may or may not change the data. +<!-- + </para> + <para> +--> + Filters in the context of printing, are programs that convert + a given file (destined for printing, but not suitable in the + format it has presently) into a printable format. Sometimes + whole "filter chains" have to be constructed to achieve the + goal, piping the output of one filter as input to the next. + </para> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + <glossseealso otherterm="gloss-rip"/>RIP</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-foomatic"> + <glossterm>Foomatic</glossterm> + <glossdef><para>Foomatic started out as the wrapper name for a set of + different tools available from <ulink + url="http://www.linuxprinting.org/">Linuxprinting.org</ulink> + These tools aimed to make the usage of traditional + ghostscript and other print filters more easy for users and + extend the filters capabilities by adding more commandline + switches or explain the drivers execution data. +<!-- + </para> + <para> +--> + Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, + PDQ-O-Matic, LPD-O-Matic and xyz. 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. +<!-- + </para> + <para> +--> + More recently, Foomatic gravitated towards becoming a "meta-spooling" + system, that allows to configure the underlying print subsystem + through a unified set of commands. (However this is much more + complicated than TDEPrints &GUI; interface, which does a similar + thing regarding different print subsystems.) </para> + <glossseealso otherterm="gloss-cups-o-matic"/>&CUPS;-O-Matic</glossseealso> + <glossseealso otherterm="gloss-PPD-O-Matic"/>PPD-O-Matic</glossseealso> + <glossseealso otherterm="gloss-cupsomatic"/>cupsomatic</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-ghostscript"> + <glossterm>Ghostscript</glossterm> + <glossdef><para>Ghostscipt is a &PostScript; RIP in software, originally + developed by L. Peter Deutsch. There is always a <acronym>GPL</acronym> version + of ghostscript available for free usage and distribution + (mostly 1 year old) while + the current version is commercially sold under another license. +<!-- + </para> + <para> +--> + Ghostscript is widely used inside the Linux and &UNIX; world + for transforming &PostScript; into raster data suitable + for sending towards non-&PostScript; devices.</para> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-rip"/>RIP</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-gimpprint"> + <glossterm>Gimp-Print</glossterm> + <glossdef><para>Contrary to its name, Gimp-Print is not any longer + just the plugin to be used for printing from the popular + Gimp program -- its codebase can also serve to be compiled + into... + <!-- + </para> + <para> +--> + *...a set of PPDs and associated filters that integrate seamlessly + into &CUPS;, supporting around 130 different printer models, providing + photografic output quality in many cases; +<!-- + </para> + <para> +--> + + *...a Gostscript filter that can be used with any other + program that needs a software-RIP; +<!-- + </para> + <para> +--> + + *...a library that can be used by other software applications + in need of rasterization functions. + + +<!-- +after 4 hours fiddling, I +could not get those s!@*#? +<itemizedlist> to pass +through the meinproc checks. +For the time being I gave up +on it and handle it differently +now. + <itemizedlist> + <listitem>...a set of PPDs and associated filters that integrate seamlessly + into &CUPS;, supporting around 130 different printer models, providing + photografic output quality in many cases;</listitem> + <listitem>...a Gostscript filter that can be used with any other + program that needs a software-RIP;</listitem> + <listitem>...a library that can be used by other software applications + in need of rasterization functions.</listitem> + </itemizedlist> +--> + </para> + <glossseealso otherterm="gloss-lexmark"/>Lexmark Drivers</glossseealso> + <glossseealso otherterm="gloss-rip"/>RIP</glossseealso> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-hp"> + <glossterm><acronym>&HP;</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>H</emphasis>ewlett-<emphasis>Packard</emphasis>; + none of the first companys to distribute their own Linux printer + drivers [...to be completed...] + </para> + </glossdef> + </glossentry> + + + <glossentry id="gloss-hpgl"> + <glossterm><acronym>&HP;/GL</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>&HP;</emphasis> + <emphasis>G</emphasis>rafical <emphasis>L</emphasis>anguage; + a &HP; printer language mainly used for plotters; many CAD + (Computer Aided software programs output &HP;/GL files for + printing.</para> + <glossseealso otherterm="gloss-escp"/>ESC/P</glossseealso> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-hpjetdirectprotocol"> + <glossterm>&HP; JetDirect Protocol</glossterm> + <glossdef><para>A term branded by &HP; to describe their implementation + of print data transfer to the printer via an otherwise "AppSocket" or + "Direct TCP/IP Prining" named protocol.</para> + <glossseealso otherterm="gloss-appsocketprotocol"/>AppSocket Protocol</glossseealso> + <glossseealso otherterm="gloss-directtcpipprinting"/>Direct TCP/IP Printing</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-ietf"> + <glossterm><acronym>IETF</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>I</emphasis>nternet + <emphasis>E</emphasis>ngineering <emphasis>T</emphasis>ask + <emphasis>F</emphasis>orce; an assembly of internet, software + and hardware experts that discuss + new networking technologies and very often arrive at + conclusions that are regarded by many as standards. "TCP/IP" + is the most famous of examples. +<!-- + </para> + <para> +--> + + IETF standards, but also + drafts, discussions, ideas or useful tutorials are + put in writing in the famous series of "RFCs" which + are available to the public and on burnt onto most Linux or + BSD-CDs.</para> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-pwg"/>PWG</glossseealso> + <glossseealso otherterm="gloss-rfc"/>RFC</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-ipp"> + <glossterm><acronym>IPP</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>I</emphasis>nternet + <emphasis>P</emphasis>rinting <emphasis>P</emphasis>rotocol; + defined in a series of RFCs accepted by the IETF with + status "proposed standard"; was designed + by the PWG. -- IPP is a completely new design for network printing, + but it is utilizing a very well-known and proven method for the + actual data transfer: HTTP 1.1! By not "re-inventing the wheel", + and basing itself on an existing and robust internet standard, + IPP is able to relativly easy bolt other HTTP-compatible standard + mechanisms into its framework: +<!-- + </para> + <para> +--> + * Basic, Digest or Certificate authentication + mechanisms; +<!-- + </para> + <para> +--> + * SSL or TLS for encryption of transferred + data; +<!-- + </para> + <para> +--> + * LDAP for directory services (to publish + data on printers, device-options, drivers, costs or + elso to the network; or to check for passwords while + conducting authentication). +<!-- + </para> + <para> +--> + +<!-- + </para> + <itemizedlist> + <listitem>Basic, Digest or Certificate authentication + mechanisms</listitem> + <listitem>SSL or TLS for encryption of transferred + data</listitem> + <listitem>LDAP for directory services (to publish + data on printers, device-options, drivers, costs or + elso to the network; or to check for passwords while + conducting authentication)</listitem> + </itemizedlist> +--> + </para> + + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-pwg"/>PWG</glossseealso> + <glossseealso otherterm="gloss-ietf"/>IETF</glossseealso> + <glossseealso otherterm="gloss-rfc"/>RFC</glossseealso> + <glossseealso otherterm="gloss-tls"/>TLS</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-tdeprint"> + <glossterm><acronym>TDEPrint</acronym></glossterm> + <glossdef><para>The new printing functionality of &kde; since its 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; representation and dialogs to ease their + usage. +<!-- + </para> + <para> +--> + Most important for day-to-day usage is "kprinter", the new + &GUI; print command. -- Note: TDEPrint does <emphasis>not</emphasis> implement its own + spooling mechanism or its own &PostScript; processing; for this it + relies on the selected <emphasis>print subsystem</emphasis> + -- however it does add some functionality of its own on top of this + foundation... + </para> + <glossseealso otherterm="gloss-bsdstyleprinting"/>BSD-style printing</glossseealso> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-kprinter"/>kprinter</glossseealso> + <glossseealso otherterm="gloss-tdeprinthandbook"/>TDEPrint Handbook</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-tdeprinthandbook"> + <glossterm><acronym>TDEPrint Handbook...</acronym></glossterm> + <glossdef><para>...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. It is authored and maintained by Kurt + Pfeifle. + </para> + <glossseealso otherterm="gloss-cupsfaq"/>&CUPS;-FAQ</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-kprinter"> + <glossterm>kprinter</glossterm> + <glossdef><para><emphasis>kprinter</emphasis> is the new powerfull + print utility that is natively used by all &kde; applications. +<!-- + </para> + <para> +--> + Contrary to some common misconceptions, + <emphasis>kprinter</emphasis> is <emphasis>not</emphasis> a &CUPS;-only tool, + but supports different print subsystems. You can even switch + to a different printsubsystem "on the fly", in between two jobs, + without re-configuration. Of course, due to the powerful + features of &CUPS;, <emphasis>kprinter</emphasis> is in + best shape when used as a &CUPS; frontend. +<!-- + </para> + <para> +--> + <emphasis>kprinter</emphasis> is the successor + to "qtcups", which is no longer being actively maintained. kprinter has + inherited all the best features of qtcups and added several new ones. +<!-- + </para> + <para> +--> + + AND MOST IMPORTANT: you can use <emphasis>kprinter</emphasis> + with all its features in all non-&kde; applications that allow + a customized print command, like gv, AcrobatReader, Netscape, + Mozilla, Galeon, StarOffice, OpenOffice and all GNOME programs. +<!-- + </para> + <para> +--> + <emphasis>kprinter</emphasis> can act as a "standalone" + utility, started from an X-Terminal or a "Mini-CLI" to + print many different files, from different directories, with different + formats, in one job and at once, without the need to first open the + files in the applications! (File formats supported this way are &PostScript;, + PDF, International and ASCII Text and many different popular Grafic + formats, such as PNG, TIFF, JPEG, PNM, Sun RASTER &etc;) + </para> + <glossseealso otherterm="gloss-kprinter"/>kprinter</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-lexmark"> + <glossterm><acronym>Lexmark</acronym></glossterm> + <glossdef><para>was one of the first companys to distribute their own Linux printer + drivers for some of their models. [...to be completed...] + </para> + </glossdef> + </glossentry> + + <glossentry id="gloss-linuxprintingorg"> + <glossterm>Linuxprinting.org</glossterm> + <glossdef><para>Linuxprinting.org = not only for Linux; all &UNIX;-like OS-es + like *BSD and also commercial Unices may find useful printing + information on that site; Foomatic -- Printer Data Base -- Driver Data + Base....</para> + <glossseealso otherterm="gloss-linuxprintingdatabase"/>Linuxprinting database</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-linuxprintingdatabase"> + <glossterm><acronym>Linuxprinting.org Database</acronym></glossterm> + <glossdef><para>....Data Base containing printers and drivers suitable + for them... ...a lot of information and documentation to be found... ...it + is now also providing some tools and utilities for easing the integration + of those drivers into a given system... ...the "Foomatic" family + of utilities being the toolset to make use of the data base + [.............TO BE COMPLETED........] + </para> + <glossseealso otherterm="gloss-foomatic"/>Foomatic</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-lprlpd"> + <glossterm><acronym>LPR/LPD</acronym> printing</glossterm> + <glossdef><para>LPR == some people translate <emphasis>L</emphasis>ine + <emphasis>P</emphasis>rinting <emphasis>R</emphasis>equest, others: + <emphasis>L</emphasis>ine <emphasis>P</emphasis>rinter + <emphasis>R</emphasis>emote.</para> + <glossseealso otherterm="gloss-bsdstyleprinting"/>BSD-style printing</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-magicfilter"> + <glossterm>Magicfilter</glossterm> + <glossdef><para>Similarly to the APSfilter program, Magicfilter + provides automatic file type recognition functions, and base + on that, automatic file conversion to a printable format, + depending on the target printer.</para> + <glossseealso otherterm="gloss-apsfilter"/>APSfilter</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-mimetypes"> + <glossterm>&MIME;-Types</glossterm> + <glossdef><para>Abbreviation for <emphasis>M</emphasis>ultipurpose (or + Multimedia) <emphasis>I</emphasis>nternet <emphasis>M</emphasis>ail + <emphasis>E</emphasis>xtensions; &MIME;-Types were first used to allow + the transport of binary data (like mail attachments containing + grafics) over mail connections that were normally only transmitting + ASCII characters: the data had to be encoded into an ASCII representation. +<!-- + </para> + <para> +--> + Later this concept was extended to describe a data format in + a platform independent, but at the same time in a non-ambigious way. + From &Windows; everybody knows the *.doc extensions for &Microsoft; Word files. + This is handled ambigiously on the &Windows; platform: *.doc extensions are also + used for simple text files or for Adobe Framemaker files. And if a real + Word file is re-named to get a different extension, it can't be + opened any longer by the program +<!-- + </para> + <para> +--> + &MIME; typed filed carry a recognition string with them, describing + their file format base on <emphasis>main_category/sub_category</emphasis>. + Inside IPP, printfiled are also described using the &MIME; type scheme. + &MIME; types are registered with the IANA (Internet Assigning Numbers + <emphasis>Association</emphasis>) to keep them unambigious. +<!-- + </para> + <para> +--> + &CUPS; has some &MIME; types of its own registered, like + <emphasis>application/vnd.cups-raster</emphasis> (for the &CUPS;-internal + raster image format). + + </para> + <glossseealso otherterm="gloss-cups"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-easysoftwareproducts"/>Easy Software Products</glossseealso> + <glossseealso otherterm="gloss-espprintpro"/>ESP PrintPro</glossseealso> + <glossseealso otherterm="gloss-gimpprint"/>Gimp-Print</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-pcl"> + <glossterm><acronym>PCL</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>P</emphasis>rinter + <emphasis>C</emphasis>ontrol <emphasis>L</emphasis>anguage; + developed by &HP;. PCL started off in version 1 as a simple + command set for ASCII printing; now, + in its versions PCL6 and PCL-X it is capable of printing grafics + and printing color -- but outside the &Microsoft; &Windows; realm and &HP-UX; + (&HP;'s own brand of &UNIX;) it is not commonly used...</para> + <glossseealso otherterm="gloss-escp"/>ESC/P</glossseealso> + <glossseealso otherterm="gloss-hpgl"/>&HP;/GL</glossseealso> + <glossseealso otherterm="gloss-pdl"/>PDL</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-pdl"> + <glossterm><acronym>PDL</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>P</emphasis>age + <emphasis>D</emphasis>escription <emphasis>L</emphasis>anguage; + PDLs describe in an abstract way the grafical representation + of a page. - Before it is actually transferred into + toner or ink layed down onto paper, a PDL needs to be + "interpreted" first. In &UNIX;, the most important PDL + is PostScript. + </para> + <glossseealso otherterm="gloss-escp"/>ESC/P</glossseealso> + <glossseealso otherterm="gloss-hpgl"/>&HP;/GL</glossseealso> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-pixel"> + <glossterm>Pixel</glossterm> + <glossdef><para>Abbreviation for <emphasis>Pic</emphasis>ture + <emphasis>El</emphasis>ement; this term describes the smallest + part of a raster picture (either as printed on paper + or as put on a monitor by cathode rays or LCD elements). As + any grafical or image representation on those kind of output + devices is composed of pixels, the values of "ppi" (pixel per inch) + and &dpi; (dots per inch) are one important parameter for the + overall quality and resolution of an image.</para> + <glossseealso otherterm="gloss-filter"/>Filter</glossseealso> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-raster"/>Raster</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-pjl"> + <glossterm><acronym>PJL</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>P</emphasis>rint + <emphasis>J</emphasis>ob <emphasis>L</emphasis>anguage; + developed by &HP; to control and influence default and per-job + settings of a printer. May not only be used + for &HP;'s own (PCL-)printers; also many &PostScript; + and other printers understand PJL commands sent to them + inside a printjob or in a separate signal.</para> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-postscript"> + <glossterm>&PostScript;</glossterm> + <glossdef><para>&PostScript; (often shortened "PS") is the de-facto + standard in the &UNIX; world for printing files. It was + developed by Adobe and licensed to printer manufacturers + and software companies. +<!-- + </para> + <para> +--> + As the &PostScript; specifications were + published by Adobe, there are also "Third Party" implementations + of &PostScript; generating and &PostScript; interpreting software + available (one of the best-known in the Free software world + being Ghostscript, a powerfull PS-interpreter) + .</para> + <glossseealso otherterm="gloss-escp"/>ESC/P</glossseealso> + <glossseealso otherterm="gloss-hpgl"/>&HP;/GL</glossseealso> + <glossseealso otherterm="gloss-pcl"/>PCL</glossseealso> + <glossseealso otherterm="gloss-ppd"/>PPD</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-ppd"> + <glossterm><acronym>PPD</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>P</emphasis>ostScript + <emphasis>P</emphasis>rinter <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 printing + duplex). +<!-- + </para> + <para> +--> + + As the explanation of the acronym reveals, PPDs were originally + only used for &PostScript; printers. &CUPS; has extended the + PPD-concept towards all types of printers. +<!-- + </para> + <para> +--> + + 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 to use a PPD originally intended for use with + &Microsoft; Windows NT. +<!-- + </para> + <para> +--> + + PPDs for non-PostScript printers <emphasis>need</emphasis> a + companion "filter" to process the &PostScript; print files towards + a format digestable 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 utilize PPDs, the Free + Software community was creative enough to quickly come up with + a support for most of the currently used printer models through + PPDs and classical Ghostscript filters. But note: the printout + quality differs from "hi-quality photografic 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"/>&CUPS;</glossseealso> + <glossseealso otherterm="gloss-linuxprintingorg"/>Linuxprinting.org</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-PPD-O-Matic"> + <glossterm>PPD-O-Matic</glossterm> + <glossdef><para>PPD-O-Matic is a set of Perl-Scripts that run on the Linuxprinting.org + webserver and can be used online to generate PPDs for any printer that is known + to print with ghostscript. +<!-- + </para> + <para> +--> + + These PPDs can be hook 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 for most cases to + use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. +<!-- + </para> + <para> +--> + + To generate a PPD, go to the <ulink + url="http://www.linuxprinting.org/printer_list.cgi">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 safe the file to your local system. + Make sure to read the instructions. Make sure your local system + does indeed have ghostscript and the filter installed, which you chose + before generating the PPD. + </para> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-cups-o-matic"/>&CUPS;-O-Matic</glossseealso> + <glossseealso otherterm="gloss-linuxprintingorg"/>Linuxprinting.org</glossseealso> + <glossseealso otherterm="gloss-foomatic"/>Foomatic</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-printcap"> + <glossterm>printcap</glossterm> + <glossdef><para>The "printcap" file holds in BSD-style print systems + the configuration information; the printing daemon reads this file + to know which printers are available, what filters are to + user for each, where the spooling directory is located, + if there are banner pages to be used, and so on... + Some applications also depend on reading access to the printcap + file to grap the names of available printer. </para> + <glossseealso otherterm="gloss-bsdstyleprinting"/>BSD-style printing</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-printermib"> + <glossterm>Printer-<acronym>MIB</acronym></glossterm> + <glossdef><para>Abbreviation for + <emphasis>Printer</emphasis>-<emphasis>M</emphasis>anagement + <emphasis>I</emphasis>nformation <emphasis>B</emphasis>ase; the + Printer-MIB defines a set of parameters that are to be + stored inside the printer for access + through the network. This is useful if many (in some cases, literally + thousands of) network printers are managed centrally + with the help of SNMP (Simple Network Management Protocol).</para> + <glossseealso otherterm="gloss-pwg"/>PWG</glossseealso> + <glossseealso otherterm="gloss-snmp"/>SNMP</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-pwg"> + <glossterm><acronym>PWG</acronym></glossterm> + <glossdef><para>Abbreviation for + <emphasis>P</emphasis>rinter <emphasis>W</emphasis>orking + <emphasis>G</emphasis>roup; the PWG is a loose grouping of + representatives of the printer industry that has in the past + years developed different standards + in relation to nework printing, which were later accepted by the + IETF as RFC standards, like the "Printer-MIB" and the IPP.</para> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-ipp"/>IPP</glossseealso> + <glossseealso otherterm="gloss-printermib"/>Printer-MIB</glossseealso> + <glossseealso otherterm="gloss-snmp"/>SNMP</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-printtdeioslave"> + <glossterm>print:/ TDEIO Slave</glossterm> + <glossdef><para>You can use a syntax of "print:/..." to get quick access + to TDEPrint ressources. 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"/>IO Slave</glossseealso> + <glossseealso otherterm="gloss-tdeparts"/>KParts</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-printerdatabase"> + <glossterm>Printer Data Base</glossterm> + <glossdef><para>.</para> + <glossseealso otherterm="gloss-linuxprintingdatabase"/>Linuxprinting Data Base</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-qtcups"> + <glossterm><acronym>Qt&CUPS;</acronym></glossterm> + <glossdef><para>co-developer of Qt&CUPS; and KUPS, the predecessors of TDEPrint, + sole developer of TDEPrint -- a very nice and productive guy and quick bug fixer... ;-) + </para> + <glossseealso otherterm="gloss-kprinter"/>kprinter</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-raster"> + <glossterm>Raster Image</glossterm> + <glossdef><para>In the last resort, every picture on a physical medium + is composed of a pattern of discrete dots in different colors and (maybe) + sizes. This is called a "raster image". +<!-- + </para> + <para> +--> + + This is opposed to a "vector image" + where the grafic is described in terms of continuous curves, shades, + forms and fills, represented by mathematical formula. Vector images + normally are of a smaller file size and may be scaled in size + without any loss of information and quality --- but they can't be + output directly, they always need to be "rendered" or "rasterized" + first to the given resolution, the output device is capable of... +<!-- + </para> + <para> +--> + + + The rasterization is done by a Raster Image Processor (RIP, + often the Ghostscript software) or some other filtering + instance.</para> + <glossseealso otherterm="gloss-pixel"/>Pixel</glossseealso> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-filter"/>Filter</glossseealso> + <glossseealso otherterm="gloss-rip"/>RIP</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-rip"> + <glossterm><acronym>RIP</acronym></glossterm> + <glossdef><para>Abbreviation for + <emphasis>R</emphasis>aster <emphasis>I</emphasis>mage + <emphasis>P</emphasis>rocess(or); if used in the context of + printing, "RIP" means a hardware or software + instance that converts &PostScript; (or other print files + that represented in one of the non-Raster PDLs) into a + raster image format in such a way that it is acceptable + for the "marking engine" of the printer. +<!-- + </para> + <para> +--> + + &PostScript; printers + contain their own PostScript-RIPs. A RIP may or may not be located + inside a printer. +<!-- + </para> + <para> +--> + + For many &UNIX; systems, Ghostscript is the package that provides + a "RIP in software", running on the host computer, and pre-digesting + the &PostScript; or other data to become ready to be sent to the + printing device (hence you may sense a "grain of truth" in the + slogan "Ghostscript turns your printer into a &PostScript; + machine", which of course is not correct in the sense of the + letter.)</para> + <glossseealso otherterm="gloss-filter"/>Filter</glossseealso> + <glossseealso otherterm="gloss-ghostscript"/>Ghostscript</glossseealso> + <glossseealso otherterm="gloss-postscript"/>&PostScript;</glossseealso> + <glossseealso otherterm="gloss-pdl"/>PDL</glossseealso> + <glossseealso otherterm="gloss-raster"/>Raster</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-rlpr"> + <glossterm><acronym>RLPR</acronym> (Remote LPR)</glossterm> + <glossdef><para>Abbreviation for <emphasis>R</emphasis>emote + <emphasis>L</emphasis>ine <emphasis>P</emphasis>rinting + <emphasis>R</emphasis>equest; this is a a BSD-style printing system, + that needs no root priviledges to be installed and no "printcap" to + work: all parameters may be specified on the command + line. +<!-- + </para> + <para> +--> + + RLPR comes in handy for many laptop users who are + working in frequently changing environments, because it + may be installed concurrently with every other printing + sub system and allows a very flexible and wuick + way to install a printer for direct access via LPR/LPD. +<!-- + </para> + <para> +--> + + TDEPrint + has an "Add Printer Wizard" to make RLPR usage even more + easy. The kprinter command allows to switch to RLPR "on + the fly" at any time.</para> + <glossseealso otherterm="gloss-tdeprint"/>TDEPrint</glossseealso> + <glossseealso otherterm="gloss-kprinter"/>kprinter</glossseealso> + <glossseealso otherterm="gloss-printcap"/>printcap</glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-snmp"> + <glossterm><acronym>SNMP</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>S</emphasis>imple + <emphasis>N</emphasis>etwork <emphasis>M</emphasis>anagement + <emphasis>P</emphasis>rotocol; SNMP is widely used to control + all sorts network nodes (Hosts, Routers, Switches, Gateways, + Printers...) remotely.</para> + <glossseealso otherterm="gloss-pwg"/>PWG</glossseealso> + <glossseealso otherterm="gloss-printermib"/>Printer-MIB</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-ssl"> + <glossterm><acronym>SSL(3)</acronym> encryption</glossterm> + <glossdef><para>Abbreviation for <emphasis>S</emphasis>ecure + <emphasis>S</emphasis>ocket <emphasis>L</emphasis>ayer; + <acronym>SSL</acronym> is a proprietary encryption method for data + transfer over HTTP that was developed by Netscape and is now being + re-placed by an IETF standard named TLS. + </para> + <glossseealso otherterm="gloss-daemon"/><acronym>Daemon</acronym></glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-spooling"> + <glossterm><acronym>SPOOL</acronym>ing</glossterm> + <glossdef><para>Abbreviation for <emphasis>S</emphasis>ynchronous + <emphasis>P</emphasis>eripherals <emphasis>O</emphasis>perations + <emphasis>O</emphasis>n<emphasis>L</emphasis>ine; + <acronym>SPOOL</acronym>ing enables printing applications + (and users) to continue their work + as the job is being taken care of by a system <acronym>daemon</acronym> + who stores the file at a temporary location until the printer is ready + to print. </para> + <glossseealso otherterm="gloss-daemon"/><acronym>Daemon</acronym></glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-tls"> + <glossterm><acronym>TLS</acronym> encryption</glossterm> + <glossdef><para>Abbreviation for <emphasis>T</emphasis>ransport + <emphasis>L</emphasis>ayer <emphasis>S</emphasis>ecurity; + <acronym>SSL</acronym> is an encryption standard for + data transfered over HTTP 1.1; it is defined in RFC ???? [#look up + number --TO BE DONE--] ; although based on the former SSL development + (from Netscape) it is not fully compatible to it. + </para> + <glossseealso otherterm="gloss-daemon"/><acronym>Daemon</acronym></glossseealso> + </glossdef> + </glossentry> + + + <glossentry id="gloss-systemVstyleprinting"> + <glossterm>System V-style printing</glossterm> + <glossdef><para>This is the second flavour of traditional &UNIX; + printing (as opposed to BSD-style printing). It uses + a different command set (lp, lpadmin,...) from BSD, + but is not fundamentally different from it. However, the + gap between the two is big enough to make the two + incompatible so that a BSD-client can't simply print + to a System V style print server without additional + tweaking... IPP is supposed to resolve this weakness + and more. + </para> + <glossseealso otherterm="gloss-bsdstyleprinting"/><acronym>BSD-style printing</acronym></glossseealso> + <glossseealso otherterm="gloss-ipp"/><acronym>IPP</acronym></glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-turboprint"> + <glossterm>TurboPrint</glossterm> + <glossdef><para>A Shareware providing photo quality printing for many + inkjet printers; it is useful if you don't find a driver for your + printer otherwise; it may be hooked into a traditional Ghostscript + or into a modern &CUPS; system.</para> + <glossseealso otherterm="gloss-gimpprint"/>Gimp-Print</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-xpp"> + <glossterm><acronym>XPP</acronym></glossterm> + <glossdef><para>Abbreviation for <emphasis>X</emphasis> + <emphasis>P</emphasis>rinting <emphasis>P</emphasis>anel; + <acronym>XPP</acronym> was the first Free + graphical print command for &CUPS;, written by Till Kamppeter, + and in some ways a model for the "kprinter" utility in &kde;.</para> + </glossdef> + </glossentry> +<!-- + <glossentry id="gloss-1"> + <glossterm>xxxx</glossterm> + <glossdef><para>.</para> + <glossseealso otherterm="gloss-1"/>xyz</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-3"> + <glossterm>xxxx</glossterm> + <glossdef><para>.</para> + <glossseealso otherterm="gloss-1"/>xyz</glossseealso> + </glossdef> + </glossentry> + + <glossentry id="gloss-4"> + <glossterm>xxxx</glossterm> + <glossdef><para>.</para> + <glossseealso otherterm="gloss-1"/>xyz</glossseealso> + </glossdef> + </glossentry> +--> + </glossdiv> + + +<!-- +</glossary> +--> + |