<?xml version="1.0" ?>
<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
"dtd/kdex.dtd" [
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % English "INCLUDE" > <!-- change language only here -->
]>

<glossary id="mainglossary">
<title>A big glossary conglomerate</title>


<glossentry id="gloss-ioslave">
<glossterm><acronym>IO</acronym> Slave</glossterm>
<glossdef><para><acronym>IO</acronym> Slaves enable &kde; applications to
access remote resources as easily as local resources (making them
<quote>network transparent</quote>). Remote resources (&eg; files) might
be stored on <acronym>SMB</acronym> shares or similar.</para>
<glossseealso otherterm="gloss-smb"><acronym>SMB</acronym></glossseealso>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kio">
<glossterm><acronym>KIO</acronym></glossterm>
<glossdef><para>The &kde; Input/Output system which makes use of so-called
<quote><acronym>IO</acronym> Slaves</quote>.</para>
<glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym> 
Slave</glossseealso>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kparts">
<glossterm>KParts</glossterm>
<glossdef><para>KParts is an embedding technology which allows &kde;
applications to embed other &kde; applications. For example, the text
view used by &konqueror; is a KPart.</para>
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-ksycoca">
<glossterm><acronym>KSycoca</acronym></glossterm>
<glossdef><para><acronym>KSycoca</acronym> (&kde; <emphasis>Sy</emphasis>stem
<emphasis>Co</emphasis>nfiguration <emphasis>Ca</emphasis>che) is a
configuration cache which, for example, guarantees fast access to the menu
entries.</para>
<glossseealso 
otherterm="gloss-kbuildsycoca"><application>KBuildSycoca</application></glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-antialiasing">
<glossterm>Antialiasing</glossterm>
<glossdef><para>If mentioned in context with &kde;, antialiasing often means
the smoothing of the fonts visible on the screen. &Qt; version 2.3.0
or higher used together with XFree86 4.x makes this possible under &kde;
as well.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-qt">&Qt;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-xserver">
<glossterm>&X-Server;</glossterm>
<glossdef><para>The &X-Server; represents a basic layer upon which the
various &GUI;s like &kde; are built. It manages the
basic mouse and keyboard input (from the local host as well as from
remote hosts) and provides elementary graphic routines to draw
rectangles and other primitives.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kbuildsycoca">
<glossterm><application>KBuildSycoca</application></glossterm>
<glossdef><para><application>KBuildSycoca</application> is a command line 
program and regenerates the
so-called <acronym>KSycoca</acronym>. This is useful, for example, if some 
or all modules in
&kcontrol; are missing.</para>
<glossseealso 
otherterm="gloss-ksycoca"><acronym>KSycoca</acronym></glossseealso>
<glossseealso otherterm="gloss-kcontrol">&kcontrol;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kcontrol">
<glossterm>&kcontrol;</glossterm>
<glossdef><para>This is the project and filename of the &kde; control
center. &kcontrol; allows you to customize virtually
every configuration option of &kde;.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kicker">
<glossterm>&kicker;</glossterm>
<glossdef><para>&kicker; is the nickname as well as project name of the
&kde; panel.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-panel">Panel</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-konqueror">
<glossterm>&konqueror;</glossterm>
<glossdef><para>&konqueror; is a filemanager, web browser, picture viewer
and more, and a core part of the &kde; project. You can
find more information about &konqueror; at <ulink
url="http://www.konqueror.org">www.konqueror.org</ulink>.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-ksirc">
<glossterm>&ksirc;</glossterm>
<glossdef><para>&ksirc; is the default <acronym>IRC</acronym> client,
which is shipped with &kde;. You can use &ksirc; to chat with anyone on
an <acronym>IRC</acronym> network.</para>
<glossseealso otherterm="gloss-irc"><acronym>IRC</acronym></glossseealso>
</glossdef>
</glossentry>			 	

<glossentry id="gloss-draganddrop">
<glossterm>Drag and Drop</glossterm>
<glossdef><para>This concept tries to replace many actions like copying
files from one place to another by a certain mouse movement, &eg;
clicking on an icon in a &konqueror; window, moving the mouse to another
window while keeping the mouse button pressed, and releasing the mouse
button (<quote>dropping</quote> the object) copies files.</para>
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-gui">
<glossterm>&GUI;</glossterm>
<glossdef><para>Abbreviation for <emphasis>G</emphasis>raphical
<emphasis>U</emphasis>ser <emphasis>I</emphasis>nterface. Every desktop
environment (like &kde;) is a &GUI;. Most
&GUI;s feature mouse support and/or windows to manage
the programs.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kde">
<glossterm>&kde;</glossterm>
<glossdef><para>Abbreviation for <quote>K Desktop Environment</quote>, a
leading &GUI; for &UNIX;-based systems. You can find more
detailled information at <ulink
url="http://www.kde.org">www.kde.org</ulink>.</para>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-gnome">
<glossterm><acronym>GNOME</acronym></glossterm>
<glossdef>
<para><emphasis>G</emphasis>NU <emphasis>N</emphasis>etwork <emphasis>O</emphasis>bject
<emphasis>M</emphasis>odel <emphasis>E</emphasis>nvironment, one of the
leading &UNIX; &GUI;s.</para>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-panel">
<glossterm>Panel</glossterm>
<glossdef><para>Refers to the panel (also known as
<quote>&kicker;</quote>) which often resides at the bottom of the
screen.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-kicker">&kicker;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-ripping">
<glossterm>ripping</glossterm>
<glossdef><para>The process of reading audio data from a &cdrom; and
storing it on the hard disk.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-qt">
<glossterm>&Qt;</glossterm>
<glossdef><para>The &GUI; of &kde; is built on top of
the &Qt; toolkit, which provides many graphical elements (so-called
<quote>Widgets</quote>) which are used to construct the desktop. You
can find more information about &Qt; at <ulink
url="http://www.trolltech.com">www.trolltech.com</ulink>.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
<glossseealso otherterm="gloss-widget">Widget</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-i18n">
<glossterm>i18n</glossterm>
<glossdef><para>Abbreviation for <quote>internationalization</quote>. &kde;
supports many different languages, and several i18n techniques make it
easy to translate the &GUI; as well as the accompanying
documents of &kde; into all these languages. More information about the
i18n process is available at <ulink
url="http://i18n.kde.org">i18n.kde.org</ulink>.</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-l10n">
<glossterm>l10n</glossterm>
<glossdef><para>Abbreviation for <quote>localization</quote>, the process
of adapting a program to the local environment. This includes &eg; the
currency used for monetary values or the time format.</para>
<glossseealso otherterm="gloss-i18n">i18n</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-widget">
<glossterm>Widget</glossterm>
<glossdef><para>Graphical elements like scrollbars, buttons or input
fields which are used by &kde; to construct the &GUI;.
</para>
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-cvs-1">
<glossterm><acronym>CVS</acronym></glossterm>
<glossdef>
<para><emphasis>C</emphasis>oncurrent <emphasis>V</emphasis>ersion 
<emphasis>S</emphasis>ystem.
The <acronym>CVS</acronym> is a very elegant way of managing file 
versions that allow more than one developer
to easily work on the same project. You can find a description of how to 
get the latest (developer) version of the
&kde; sources via anonymous <acronym>CVS</acronym> on
<ulink 
url="http://www.kde.org/anoncvs.html">http://www.kde.org/anoncvs.html</ulink>.
More about <acronym>CVS</acronym> is available at <ulink 
url="http://www.cvshome.org">www.cvshome.org</ulink>.

</para>
</glossdef>
</glossentry>




<glossentry id="gloss-rfc">
<glossterm><acronym>RFC</acronym></glossterm>
<glossdef><para><emphasis>R</emphasis>equest <emphasis>F</emphasis>or
<emphasis>C</emphasis>omment. A common way to publish new protocol
ideas or procedures for evaluation of the Internet community. Though
<acronym>RFC</acronym>s are not mandatory, many applications try to
adhere to them, once they have been approved by the community. More
information about <acronym>RFC</acronym>s can be found at the
<ulink url="http://www.rfc-editor.org">RFC Homepage</ulink>.</para>
</glossdef>
</glossentry>	




<glossentry id="gloss-smb">
<glossterm><acronym>SMB</acronym></glossterm>
<glossdef><para><emphasis>S</emphasis>erver <emphasis>M</emphasis>essage
<emphasis>B</emphasis>lock. A network protocol used in &Microsoft; &Windows;
networks to access the filesystems of other computers.</para>
<glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym> 
Slave</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-irc">
<glossterm><acronym>IRC</acronym></glossterm>
<glossdef><para><emphasis>I</emphasis>nternet <emphasis>R</emphasis>elay
<emphasis>C</emphasis>hat. A protocol defined in <acronym>RFC</acronym>
1459, which handles the specification to enable real time text chat.</para>
<glossseealso otherterm="gloss-rfc"><acronym>RFC</acronym></glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-host">
<glossterm>host</glossterm>
<glossdef><para>This can either be a name from your 
<filename>/etc/hosts</filename> file
(<systemitem class="systemname">mycomputer</systemitem>), 
an Internet name (<systemitem 
class="systemname">www.kde.org</systemitem>) or an IP-Address 
(<systemitem>192.168.0.10</systemitem>).
</para>
</glossdef>
</glossentry>

-->




<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 taken AppSocket, added a few minor
extensions around it and been very successful in renaming
and marketing 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,
disguised 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.

It is
similar to Magicfilter and mostly uses Ghostscript for file conversions. 
Some Linux Distributions (like &SuSE;) use APSfilter, others
Magicfilter (like &RedHat;), some have both for preference selection
(like *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>Proving 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
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 hole-punched, continuous paper, fed through by a tractor
mechanism, with simple rows of ASCII text mechanically hammered on to
the medium, drawn from a cardboard box beneath the table. It came out
like a zig-zag folded paper "snake". Remote printing consisted of a
neighboring host in the next room sending a file
asking for printout.
<!--
</para>
<para>
-->
How technology has changed! Printers generally 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 powerful page description
languages (PDL). Many are network nodes in their own right,
with CPU, RAM, a hard disk and their own Operation System, and
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.

It is strong proof of the flexibility of &UNIX;; that "Line Printing" works
reliably, 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 the most modern &UNIX; and Linux
printing system, also providing cross-platform print services
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), targeted 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-kdeprint">KDEPrint</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>Currently 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 resource to answer many questions that anyone new to 
&CUPS; printing might have at first.
</para>
<glossseealso otherterm="gloss-kdeprinthandbook">KDEPrint 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 redirects output from the native <application>pstops</application> filter into
a chain of suitable Ghostscript filters. Upon completion, it
passes the resulting data back to a &CUPS; "backend" for sending
to the printer.
<!--
</para>
<para>
-->
In this way, &CUPS;-O-Matic enables support for any printer 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 Perl script <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 command line 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 of the available
information 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 (with content that could be described along the lines
"Which device prints with which Ghostscript or other
filter?", "How well?", and "What command line 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 now developed into a broader
concept, known as "Foomatic". Foomatic extends the capabilities
of spoolers other than &CUPS; (LPR/LPD, LPRng, PDQ, PPR) to a certain
degree ("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 also find valuable information
and software there.
</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
to a Linux or &UNIX; platform. A "driver" functionality
is supplied on &UNIX; by different modular components working
together. At the core of the printer drivers are "filters". Filters convert
print files from a given input format to another format that is acceptable
to the target printer. In many cases filters may be connected to a whole
filter "chain", where only the result of the last conversion is sent to the
printer. The actual transfer of the print data to the device is performed 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 within intranets.
<!--
</para>
<para>
-->
Printing
via traditional protocols is not encrypted at all -- it is very easy
to tap and eavesdrop &eg; into &PostScript; or PCL data transfered
over the wire.
<!--
</para>
<para>
-->
Therefore, in the design of IPP, provision was made for the 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 are among 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 Stylus
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, having now developed a full-blown
Page Description Language (PDL) from these 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. Besides &PostScript; and PCL, Epson's ESC/P
printer language is one of the best known.</para>
<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
will produce photographic quality prints in many cases, especially
with the Epson Stylus model series. ESP Ghostscript is GPL-software.
</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 also sell 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 is presently) into a printable format. Sometimes
whole "filter chains" have to be constructed to achieve the
goal, piping the output of one filter as the 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 easier for users and
extend the filters' capabilities by adding more command line
switches or explain the driver's execution data.
<!--
</para>
<para>
-->
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.
<!--
</para>
<para>
-->
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>
<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>Ghostscript is a &PostScript; Raster Image Processor (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 to 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 no 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
photographic output quality in many cases;
<!--
</para>
<para>
-->

*...a Ghostscript 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 Ghostscript 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>;
one of the first companies to distribute their own Linux printer
drivers. -- More recently, the Company has released their
"HPIJS" package of drivers, including source code and a Free license. 
This is the first printer manufacturer to do so. HPIJS supports most
current models of HP Ink- and DeskJets.
</para>
</glossdef>
</glossentry>


<glossentry id="gloss-hpgl">
<glossterm><acronym>&HP;/GL</acronym></glossterm>
<glossdef><para>Abbreviation for <emphasis>&HP;</emphasis>
<emphasis>G</emphasis>raphical <emphasis>L</emphasis>anguage;
a &HP; printer language mainly used for plotters; many CAD
(Computer Aided Design) 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 Printing" 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 example.
<!--
</para>
<para>
-->

IETF standards, as well as
drafts, discussions, ideas and useful tutorials, are
put in writing in the famous series of "RFCs", which
are available to the public and included in most Linux and
BSD distributions.</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 utilizes 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 relatively easily 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
also to the network; or to check for passwords while
performing 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-kdeprint">
<glossterm><acronym>KDEPrint</acronym></glossterm>
<glossdef><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 dialogs to ease their
usage.
<!--
</para>
<para>
-->
Most important for day-to-day usage is "kprinter", the new
&GUI; print command. -- Note: KDEPrint 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-kdeprinthandbook">KDEPrint Handbook</glossseealso>
</glossdef>
</glossentry>


<glossentry id="gloss-kdeprinthandbook">
<glossterm><acronym>KDEPrint Handbook...</acronym></glossterm>
<glossdef><para>...is the name of the reference document that describes KDEPrint
functions to users and administrators. You can load it into Konqueror by
typing "help:/kdeprint" into the address field. The <ulink
url="http://printing.kde.org/">KDEPrint 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>
<glossseealso otherterm="gloss-cupsfaq">&CUPS;-FAQ</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-kprinter">
<glossterm>kprinter</glossterm>
<glossdef><para><emphasis>kprinter</emphasis> is the new powerful
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 print subsystem "on the fly", in between two jobs,
without re-configuration. Of course, due to the powerful
features of &CUPS;, <emphasis>kprinter</emphasis> is
best suited for use with a &CUPS; frontend.
<!--
</para>
<para>
-->
<emphasis>kprinter</emphasis> is the successor
to "qtcups", which is no longer being actively maintained. It has
inherited all the best features of qtcups and added several new ones.
<!--
</para>
<para>
-->

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, Acrobat Reader, 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 folders, with different 
formats, in one job and simultaneously, without the need to first open the
files in the applications! (File formats supported this way are &PostScript;,
PDF, International and ASCII Text, as well as many different popular graphic
formats, such as PNG, TIFF, JPEG, PNM, Sun RASTER, &etc;)
</para>
<glossseealso otherterm="gloss-qtcups">QtCUPS</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-lexmark">
<glossterm><acronym>Lexmark</acronym></glossterm>
<glossdef><para>was one of the first companies to distribute their own Linux printer
drivers for some of their models. However, those drivers are binary only
(no source code available), and therefore cannot be used to integrate into
other Free printing software projects.  
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-linuxprintingorg">
<glossterm>Linuxprinting.org</glossterm>
<glossdef><para>Linuxprinting.org = not just for Linux; all &UNIX;-like OS-es,
like *BSD and commercial Unices may find useful printing
information on this site. This web site is the home for the interesting 
Foomatic project, that strives to develop the "Meta Print Spool and Driver
Configuration Toolset" (being able to configure, through one common
interface, different print subsystems and their required drivers) with the
ability to transfer all queues, printers and configuration files seamlessly
to another spooler without new configuration effort. -- Also, they maintain
the Printing Database; a collection of driver and device information that
enables everybody to find the most current information about printer models,
and also generate online the configuration files for any
spooler/driver/device combo known to work with one of the common Linux or
&UNIX; print subsystems.	
</para>
<glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting database</glossseealso>
</glossdef>
</glossentry>


<glossentry id="gloss-linuxprintingdatabase">
<glossterm><acronym>Linuxprinting.org Database</acronym></glossterm>
<glossdef><para>....Database containing printers and drivers that are 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 database 
for most of the commonly used print subsystems, for generating "on the fly" 
working configurations for your printer model.
</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
graphics) 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 non-ambiguous, way.
From &Windows; everybody knows the .doc extensions for &Microsoft; Word files.
This is handled ambiguously 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 renamed with a different extension, it can no longer be
opened by the program.
<!--
</para>
<para>
-->
&MIME; typed files carry a recognition string with them, describing
their file format based on <emphasis>main_category/sub_category</emphasis>.
Inside IPP, print files are also described using the &MIME; type scheme.
&MIME; types are registered with the IANA (Internet Assigning Numbers
<emphasis>Association</emphasis>) to keep them unambiguous.
<!--
</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 graphics
and 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 graphical representation
of a page. - Before it is actually transferred into
toner or ink laid down on to 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 displayed on a monitor by cathode rays or LCD elements). As
any graphical or image representation on those types 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. It 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 print job, 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 to "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 powerful 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 print
duplexing).
<!--
</para>
<para>
-->

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.
<!--
</para>
<para>
-->

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.
<!--
</para>
<para>
-->

PPDs for non-PostScript printers <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 utilize 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">&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
web server and can be used online to generate PPDs for any printer that is known
to print with Ghostscript.
<!--
</para>
<para>
-->

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.
<!--
</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 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">&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>In BSD-style print systems, the "printcap" file holds
the configuration information; the printing daemon reads this file
to determine which printers are available, what filters are to be
user for each, where the spooling folder is located,
if there are banner pages to be used, and so on...
Some applications also depend on read access to the printcap 
file, to obtain the names of available printers. </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) 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 network printing. These 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-ipp">IPP</glossseealso>
<glossseealso otherterm="gloss-printermib">Printer-MIB</glossseealso>
<glossseealso otherterm="gloss-snmp">SNMP</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-printkioslave">
<glossterm>print:/ KIO Slave</glossterm>
<glossdef><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>
<glossseealso otherterm="gloss-ioslave">IO Slave</glossseealso>
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
</glossdef>
</glossentry>


<glossentry id="gloss-printerdatabase">
<glossterm>Printer Database</glossterm>
<glossdef><para>.</para>
<glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting Database</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-qtcups">
<glossterm><acronym>Qt&CUPS;</acronym></glossterm>
<glossdef><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 dialog (which is much improved over qtcups);
what you liked about kups is now all in the KDEPrint Manager (accessible 
via the KDE Control Center 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>
<glossseealso otherterm="gloss-kprinter">kprinter</glossseealso>
</glossdef>
</glossentry>

<glossentry id="gloss-raster">
<glossterm>Raster Image</glossterm>
<glossdef><para>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 as opposed to a "vector image"
where the graphic is described in terms of continuous curves, shades,
forms and filled areas, represented by mathematical formula. Vector images
normally have a smaller file size and may be scaled in size 
without any loss of information and quality --- but they cannot be
output directly, but always have to be "rendered" or "rasterized"
first to the given resolution that 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 formats
that are 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 perceive a "grain of truth" in the
slogan "Ghostscript turns your printer into a &PostScript;
machine", which of course is not correct in the true sense of the
meaning).</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 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.
<!--
</para>
<para>
-->

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.
<!--
</para>
<para>
-->

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>
<glossseealso otherterm="gloss-kdeprint">KDEPrint</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 types of network node (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. It is now being 
replaced by an IETF standard named TLS.
</para>
<glossseealso otherterm="gloss-tls"><acronym>TLS</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>eripheral <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>,
which 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>TLS</acronym> is an encryption standard for
data transfered over HTTP 1.1; it is defined in RFC 2246;
although based on the former SSL development
(from Netscape) it is not fully compatible with it.
</para>
<glossseealso otherterm="gloss-ssl"><acronym>SSL(3)</acronym></glossseealso>
</glossdef>
</glossentry>


<glossentry id="gloss-systemVstyleprinting">
<glossterm>System V-style printing</glossterm>
<glossdef><para>This is the second flavor of traditional &UNIX;
printing (as opposed to BSD-style printing). It uses
a different command set (lp, lpadmin,...) to 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 cannot 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>Shareware software providing photo quality printing for many
inkjet printers. It is useful if you are unable to find a driver for your
printer and may be hooked into either a traditional Ghostscript system
or 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-greeter">
<glossterm>greeter</glossterm>
<glossdef><para>The greeter is the login dialog, &ie; the part of &kdm;
which the user sees.</para>
</glossdef>
</glossentry>

<glossentry>
<glossterm id="gloss-entropy">entropy</glossterm>
<glossdef><para>...</para></glossdef>
</glossentry>

 

<glossentry id="gloss-terminal-emulator">
<glossterm>Terminal emulator</glossterm>
<glossdef>
<para>Terminal emulator is simply a windowed shell; this is known as
<quote>command line window</quote> in some other environments. If you
want to use the shell, you should know at least a few of the
system-level commands for your operating system.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-applet">
<glossterm>Applet</glossterm>
<glossdef><para>A small application that occupies very little memory
and screen space, and at the same time gives you some useful
information or provides a control shortcut. For instance the
<application>Clock</application> applet shows current time and date
(and even a month diary if you click it), and <application>System
Monitor</application> applet shows how busy your machine currently is
in real-time.</para> </glossdef> 
</glossentry>

<glossentry id="gloss-legacy-application">
<glossterm>Legacy Application</glossterm>
<glossdef>

<para>An X-window application which was not written with &kde; in
mind. Such applications run fine in &kde;. However, they are not
warned automatically when you shut down your &kde; session. You
therefore must not forget to save documents open in these applications
before you log out from &kde;. </para> <para>Additionally, many of
these applications do not support copying and pasting from
&kde; compliant applications. &Netscape; 4.x browser is a prominent
example of such application <footnote><para>Some <ulink
url="http://www.gnome.org">GNOME</ulink> applications may provide
limited interoperability with the &kde;.</para></footnote>.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-console-application">
<glossterm>Console Application</glossterm>
<glossdef>

<para>Application originally written for non-graphic, text oriented
environment. Such applications run fine in &kde;. They must run within
console emulator, like &konsole;. They are not warned automatically
when you shut down your &kde; session. You therefore must not forget
to save documents open in these applications before you log out from
the &kde;.</para>

<para>Console applications support copying and pasting from
KDE-compliant applications.Simply mark the text in the console
application with your mouse, switch to the KDE-compliant application
and press <keycombo action="simul">&Ctrl;
<keycap>V</keycap></keycombo> to paste the text. If you want to copy
from &kde; application to a console application, first mark the text
with your mouse, press <keycombo action="simul">&Ctrl;
<keycap>C</keycap></keycombo>, switch to the console application and
press the middle button on your mouse<footnote><para>If your mouse
does not have a middle button, you must press
<mousebutton>left</mousebutton> and <mousebutton>right</mousebutton>
button at the same time. This is called <quote>middle button
emulation</quote> and it must be supported by your operating system to
work.</para></footnote>.</para>

</glossdef>
</glossentry>

<glossentry id="gloss-active-task">
<glossterm>active task</glossterm>
<glossdef><para>A task which has a timer running.</para></glossdef>
</glossentry>

<glossentry id="gloss-desktop">
<glossterm>desktop</glossterm>
<glossdef><para>GNU/Linux, FreeBSD and other systems that run X-Windows have
multiple desktops.  You typically have four different desktops installed by
default.  Each desktop can display it's own set of programs and files.  When
KDE first starts up, the desktop you see is Desktop 1.  If you press
<keycombo action="simul">&Alt;<keycap>F2</keycap></keycombo>, you will see
Desktop 2.  Pressing <keycombo
action="simul">&Alt;<keycap>F1</keycap></keycombo> will bring back Desktop
1.  </para></glossdef> </glossentry>

<glossentry id="gloss-history">
<glossterm>history</glossterm>
<glossdef><para>If &karm; is configured to log history, it will record ever
start/stop timer event. This history is never cleared when times are reset
cleared and remains on file until the task is deleted.</para></glossdef>
</glossentry>

<glossentry id="gloss-session"> <glossterm>session</glossterm>
<glossdef><para>A user-defined starting point for the session timers.  A new
session begins when you select <menuchoice> <guimenu>File</guimenu>
<guimenuitem>Start New Session</guimenuitem> </menuchoice>.
Session data is not saved when you create a new session.
</para></glossdef> </glossentry>

<glossentry id="gloss-system-time"> <glossterm><guilabel>Session
Time</guilabel></glossterm> <glossdef><para>The time spent on the task
since the session began.</para></glossdef> </glossentry> 

<glossentry id="gloss-system-tray"> <glossterm>system tray</glossterm>
<glossdef><para>The system tray is in the bar that (by default) appears at
the bottom of the screen.  In this system tray <inlinemediaobject>
<imageobject> <imagedata fileref="systray.png"
format="PNG"/></imageobject> </inlinemediaobject> the &karm; icon is on the far
right.</para></glossdef>
</glossentry>

<glossentry id="gloss-top-level-task">
<glossterm>top level task</glossterm>
<glossdef><para>A task with no parent tasks.</para></glossdef>
</glossentry>

<glossentry id="gloss-total-session-time"> <glossterm><guilabel>Total Session
Time</guilabel></glossterm> <glossdef><para>The time spent on the task and
all it's subtasks since the session began.</para></glossdef> </glossentry>
<glossentry> <glossterm><guilabel>Time</guilabel></glossterm>
<glossdef><para>The time spent on the task since all times were
reset.</para></glossdef> </glossentry> 

<glossentry id="gloss-total-time"> <glossterm><guilabel>Total Time</guilabel></glossterm>
<glossdef><para>The time spent on the task and all it's subtasks since all
times were reset.</para></glossdef> </glossentry> 




 
<glossentry id="gloss-article"> 
<glossterm>Article</glossterm> 
<glossdef> 
<para>An <glossterm>article</glossterm> in the sense of
newspapers: special <glossterm>articles</glossterm> are, for example,
followups; replies are not <glossterm>articles</glossterm> but
Email.</para>
</glossdef> 
</glossentry> 


 
 

<glossentry id="gloss-cancel">
<glossterm>Canceling</glossterm>
<glossdef>
<para>To delete one of your articles from the newsserver: the newsreader
generates a special control message to tell the server to delete this
article.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-crossposting">
<glossterm>Crossposting</glossterm> 
<glossdef>
<para>The posting of an article in several newsgroups; this is very
often disliked, because it disturbs the topic-oriented association of
the newsgroups.</para>
</glossdef> 
</glossentry> 
 

 


<glossentry id="gloss-expire">
<glossterm>Expire</glossterm> 
<glossdef> 
<para><glossterm>Articles</glossterm> can not be held for eternity
because of harddisk limits. Because of this there is usually a program
called <application>expire</application> on most computer
systems; this program deletes all articles which are older than a
configured number of days. &knode; includes this functionality on its
own.</para>
</glossdef> 
</glossentry> 
 

 
 
<glossentry id="gloss-faq">
<glossterm><acronym>FAQ</acronym></glossterm> 
<glossdef>
<para><acronym>FAQ</acronym> is the acronym for <quote>Frequently
Asked Questions</quote>.</para>
</glossdef> 
</glossentry> 

<glossentry id="gloss-follow-up">
<glossterm>Followup</glossterm>
<glossdef> 
<para>An <glossterm>article</glossterm> which is written as an answer
to another <glossterm>article</glossterm>.</para>
</glossdef> 
</glossentry> 
 

 
 
<glossentry id="gloss-gknsa">
<glossterm><acronym>GNKSA</acronym></glossterm>
<glossdef>
<para><acronym>GNKSA</acronym> is a kind of seal-of-approval for
newsreaders; you can get more information at <ulink
url="http://www.gnksa.org">http://www.gnksa.org</ulink>.</para>
</glossdef> 
</glossentry> 


 
 
<glossentry id="gloss-header">
<glossterm>Header</glossterm>
<glossdef>
<para>The Header of an <glossterm>article</glossterm> contains
information about the sender, the subject, and the newsgroup of the
article.</para>
</glossdef> 
</glossentry> 
 

 
<title> 
K</title> 
<glossentry id="gloss-killfile">
<glossterm>Killfile</glossterm> 
<glossdef> 
<para>This is a functionality of a newsreader to hide
<glossterm>articles</glossterm> of a determined sender or
with certain contents.</para>
</glossdef> 
</glossentry> 
 

 
 
<glossentry id="gloss-message-id">
<glossterm>Message-ID</glossterm> 
<glossdef> 

<para>The <glossterm>Message-ID</glossterm> of an article is a clear
mark for the newsserver to identify the article. A
<glossterm>Message-ID</glossterm> should not be used twice in the
whole usenet for about 2 years; wrong or double
<glossterm>Message-IDs</glossterm> could cause problems when
forwarding them and could overwrite other articles.</para>
</glossdef> 
</glossentry>
 

 
 
<glossentry id="gloss-newbie">
<glossterm>Newbie</glossterm> 
<glossdef> 
<para>Somebody who is new somewhere, in relationship to usenet:
somebody who is new to the newsgroup, or new to usenet in
general.</para>
</glossdef> 
</glossentry> 

<glossentry id="gloss-newsgroup">
<glossterm>Newsgroup</glossterm> 
<glossdef> 
<para>A kind-of bulletin board in the usenet about a special topic or
a group of topics. This is where you post your
<glossterm>articles</glossterm>.</para>
</glossdef> 
</glossentry> 

<glossentry id="gloss-newsreader"> 
<glossterm>Newsreader</glossterm> 
<glossdef> 
<para>A program for reading and writing <glossterm>news</glossterm>.</para> 
</glossdef> 
</glossentry> 

<glossentry id="gloss-nntp"> <glossterm>
<acronym><acronym>NNTP</acronym></acronym> 
</glossterm> 
<glossdef>
<para>Network News Transport Protocol; this is the protocol which
defines how the articles in the usenet are spread.</para>
</glossdef> 
</glossentry> 
 

 
 

<glossentry id="gloss-port">
<glossterm>Port</glossterm>
<glossdef> 
<para>A kind-of address for the application to listen for data on and
for connecting to another computer; the standard-port for the
connection between the newsreader and the newsserver is 119.</para>
</glossdef> 
</glossentry> 

<glossentry id="gloss-pgp-signature">
<glossterm>PGP-Signature</glossterm> 
<glossdef>
<para>A digital signature; you can use it to determine whether the document
has been changed since it was signed or if it is the original text from
the author.</para>
</glossdef> 
</glossentry> 

<glossentry id="gloss-posting">
<glossterm>Posting</glossterm> 
<glossdef> 
<para>Either an <glossterm>article</glossterm> which is sent to usenet or the
act of sending itself; you are <quote>posting</quote> an
<glossterm>article</glossterm> into a newsgroup.</para>
</glossdef> 
</glossentry> 
 

 
 

<glossentry id="gloss-quoting">
<glossterm>Quoting</glossterm> 
<glossdef> 
<para>This is the act of citing of an article to which you are answering:
you quote the original <glossterm>article</glossterm> to make clear
which passages of text your answer refers to.</para>
</glossdef> 
</glossentry> 
 

 
 
<glossentry id="gloss-reply">

<glossterm>Reply</glossterm> 
<glossdef> 
<para>A <glossterm>reply</glossterm> is an answer to the author of an
article by e-mail.</para>
</glossdef> 
</glossentry> 
 

 
 

<glossentry id="gloss-scoring">
<glossterm>Scoring</glossterm>
<glossdef>

<para>This is the valuation of an article or a thread.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-signature">
<glossterm>Signature</glossterm>
<glossdef>
<para>A <glossterm>signature</glossterm> is a personal sign of the
author which is attached at the end of the normal contents of the article;
it is like a visiting card &mdash; very often there are e-mail addresses, a
homepage <acronym>URL</acronym> or other personal data. The
<glossterm>signature</glossterm> should not be longer than 4 lines. Note that
the <glossterm>signature</glossterm> should not be mixed up with the
<glossterm>PGP-signature</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-supersede">
<glossterm>Supersede</glossterm>
<glossdef>

<para>This is the overwriting of an existing article: the newsreader
generates a special article with a control message in the header which
tells the newsserver to overwrite the existing article with this
one.</para>

</glossdef>
</glossentry>




<glossentry id="gloss-calendar-widget">
<glossterm>Calendar Widget</glossterm>
<glossdef>

<para>A tool for choosing the date inside certain entry windows, like event
editing window. It is displayed as a small button to the right of the date
field. When you click the button, you will see a month calendar. Use the arrows
to go to a desired date, or click on the month name or year number to go
directly to the desired month or year.</para>

</glossdef>
</glossentry>

<glossentry id="gloss-date-navigator">
<glossterm>Date Navigator</glossterm>
<glossdef>

<para>The calendar that is in the upper-left corner of the &korganizer; window.
It is the
main way provided to navigate among dates, and to select from them. The
single-arrow icons move forwards and backwards in time by increments of a month,
while the double-arrows allow moving by years at a time. Today's date will be
outlined with a small box. Dates which have events scheduled on them will be
bold. If you want to select a date, simply click on it. Hold down the Control
key and click the dates if you wish to select multiple neighbor dates at
once. The dates will be displayed in the main panel.</para>

<para>Recurring events are not always displayed. You can forbid the display of
recurring appointments in the Date Navigator.</para>

</glossdef>
</glossentry>

<glossentry id="gloss-due-date">
<glossterm>Due Date</glossterm>
<glossdef>

<para>A due date is simply the date when your task must be finished. For
instance, if your To-Do task is that you must return your books to the library
by 16th November, that date is called <quote>the To-Do task due
date</quote></para>

</glossdef>
</glossentry>


<glossentry id="gloss-main-panel">
<glossterm>Main panel</glossterm>
<glossdef>
<para>Normally the largest part of the screen, to the right of the Date
Navigator. It displays the View of the day, workdays, week or month, the List
View or the To-Do View.</para>
<para>The right mouse button can be used in the List view and To-Do view
only. It displays a local menu. The left mouse button can be used in any
view.</para>
</glossdef>
</glossentry>





<glossentry id="gloss-rdf">
<glossterm>RDF</glossterm>
<glossdef>
<para>Resource Description Framework. A language derived from
<acronym>XML</acronym> which describes metadata. Commonly used as a
backend format for articles and other publications. For more detailed
information on <acronym>RDF</acronym> files, you might want to go
directly to the <ulink url="http://www.w3.org/RDF/">official page on
<acronym>RDF</acronym> files</ulink> at the
<ulink url="http://www.w3.org">World Wide Web
Consortium</ulink>.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-rss">
<glossterm>RSS</glossterm>
<glossdef>
<para>The <acronym>RDF</acronym> Site Summary is actually an
extension to the <acronym>RDF</acronym> language. Quoting the official
<ulink url="http://www.purl.org/rss/1.0/">RSS v1.0
specification</ulink>:</para>
<para><quote><acronym>RDF</acronym> Site Summary
(RSS) is a lightweight multipurpose extensible
metadata description and syndication format. RSS is
an <acronym>XML</acronym> application, conforms to the
<acronym>W3C</acronym>'s <acronym>RDF</acronym> specification and is
extensible via <acronym>XML</acronym>-namespace and/or
<acronym>RDF</acronym> based modularization.</quote></para>
</glossdef>
</glossentry>

<glossentry id="gloss-xml">
<glossterm>XML</glossterm>
<glossdef>
<para>The Extensible Markup Language is the <quote>universal format
for structured documents and data on the Web</quote>. It's a derivate of
<acronym>SGML</acronym> which fits the need of the world wide web. You
might want to check the the
<ulink url="http://www.w3.org/XML/">Extensible Markup Language</ulink>
page at the <ulink url="http://www.w3.org">World Wide Web
Consortium</ulink> for further information.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-w3c">
<glossterm>W3C</glossterm>
<glossdef>
<para>An abbreviation for <quote>World Wide Web Consortium</quote>.
Quoting the <ulink url="http://www.w3.org">official homepage</ulink> of
the <acronym>W3C</acronym>, <quote>the World Wide Web Consortium
(<acronym>W3C</acronym>) develops interoperable technologies
(specifications, guidelines, software, and tools) to lead the Web to
its full potential as a forum for information, commerce, communication,
and collective understanding</quote></para>
</glossdef>
</glossentry>

<glossentry id="gloss-url">
<glossterm>&URL;</glossterm>
<glossdef>
<para>&URL; stands for <quote>Uniform Resource Locator</quote>,
a specially formatted string which can reference resources like images,
documents and other things on the Internet. Please refer to the
corresponding <ulink url="http://www.w3.org/Addressing/">webpage</ulink>
for more detailed information on this topic.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-dcop">
<glossterm>DCOP</glossterm>
<glossdef>
<para>The Desktop COmmunication Protocol is a way for applications
to communicate to each other. For instance, &knewsticker;'s
configuration dialog uses
<acronym>DCOP</acronym> to tell the applet itself about the current
configuration.</para>
<para>&knewsticker; provides an extensive
<acronym>DCOP</acronym> interface
which makes it possible to control many of &knewsticker;'s functions
from the commandline.</para>
<para>For more detailled information on <acronym>DCOP</acronym>
you might want to visit
<ulink url="http://developer.kde.org/documentation/library/2.0-api/dcop/HOWTO.html">http://developer.kde.org/documentation/library/2.0-api/dcop/HOWTO.html</ulink>
for a complete explanation.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-alsa">
<glossterm><acronym>ALSA</acronym></glossterm>
<glossdef>
<para>
Advanced &Linux; Sound Architecture; a &Linux; sound card driver; not
currently included with the standard kernel source code.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-arts">
<glossterm>&arts;</glossterm>
<glossdef>
<para>
Analog Real-Time Synthesizer; the name of the multimedia
architecture/library/toolkit used by the &kde; project (note
capitalization)
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-bsd">
<glossterm><acronym>BSD</acronym></glossterm>
<glossdef>
<para>
Berkeley Software Distribution; here refers to any of several free
&UNIX;-compatible operating systems derived from <acronym>BSD</acronym>
&UNIX;.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-corba">
<glossterm><acronym>CORBA</acronym></glossterm>
<glossdef>
<para>
Common Object Request Broker Architecture; a standard for implementing
object-oriented remote execution.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-cvs">
<glossterm><acronym>CVS</acronym></glossterm>
<glossdef>
<para>
Concurrent Versions System; a software configuration management system
used by many software projects including &kde; and &arts;.
</para>
</glossdef>
</glossentry>

<glossentry id="glos-fft">
<glossterm><acronym>FFT</acronym></glossterm>
<glossdef>
<para>
Fast Fourier Transform; an algorithm for converting data from the time
to frequency domain; often used in signal processing.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-full-duplex">
<glossterm>Full Duplex</glossterm>
<glossdef>
<para>
The ability of a sound card to simultaneously record and play audio.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-gpl">
<glossterm><acronym>GPL</acronym></glossterm>
<glossdef>
<para>
<acronym>GNU</acronym> General Public License; a software license
created by the Free Software Foundation defining the terms for releasing
free software.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-gui-1">
<glossterm>&GUI;</glossterm>
<glossdef>
<para>
Graphical User Interface
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-idl">
<glossterm><acronym>IDL</acronym></glossterm>
<glossdef>
<para>
Interface Definition Language; a programming language independent format
for specifying interfaces (methods and data).
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-kde-1">
<glossterm>&kde;</glossterm>
<glossdef>
<para>
K Desktop Environment; a project to develop a free graphical desktop
environment for &UNIX; compatible systems.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-lgpl">
<glossterm><acronym>LGPL</acronym></glossterm>
<glossdef>
<para>
<acronym>GNU</acronym> Lesser General Public License; a software license
created by the Free Software Foundation defining the terms for releasing
free software; less restrictive than the <acronym>GPL</acronym> and
often used for software libraries.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-mcop">
<glossterm>MCOP</glossterm>
<glossdef>
<para>
Multimedia COmmunication Protocol; the protocol used for communication
between &arts; software modules; similar to <acronym>CORBA</acronym> but
simpler and optimized for multimedia.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-midi">
<glossterm>&MIDI;</glossterm>
<glossdef>
<para>
Musical Instrument Digital Interface; a standard protocol for
communication between electronic musical instruments; often also used to
refer to a file format for storing &MIDI; commands.
</para>
</glossdef>
</glossentry>

<glossentry id="gloss-oss">
<glossterm><acronym>OSS</acronym></glossterm>
<glossdef>
<para>
Open Sound System; the sound drivers included with the &Linux; kernel
(sometimes called <acronym>OSS</acronym>/Free) or a commercial version
sold by 4Front Technologies.
</para>
</glossdef>
</glossentry>



<glossentry id="gloss-mc">
<glossterm>Milk Chocolate</glossterm><glossdef>
<para>
Milk Chocolate is a simple, minimalist user interface plugin
</para></glossdef></glossentry>

<glossentry id="gloss-arts-1">
<glossterm>&arts;</glossterm><glossdef>
<para>
&arts; is the Analog Real-time Synthesizer.  A powerful
media framework used by &noatun;
</para></glossdef></glossentry>
<glossentry id="gloss-kj">
<glossterm>K-J&ouml;fol</glossterm><glossdef>
<para>
This plugin loads skins originally used under a &Windows;
media player under the same name.
</para></glossdef></glossentry>

<glossentry id="gloss-keyz">
<glossterm>Keyz</glossterm><glossdef>
<para>
Keyz allows you to assign keystrokes to actions in &noatun;
</para></glossdef></glossentry>
<glossentry id="gloss-young-hickory">
<glossterm>Young Hickory</glossterm><glossdef>
<para>
Young Hickory is a system tray plugin.
</para></glossdef></glossentry>
<glossentry id="gloss-kaiman">
<glossterm>Noatun</glossterm><glossdef>
<para>
Kaiman is a plugin that loads skins from the media player
GQMPEG.  Kaiman is also &noatun;'s predecessor, and was
distributed with &kde; for &kde; 2.0. When
&noatun; was introduced in &kde; 2.1, Kaiman's skin loader
became a &noatun; plugin.
</para></glossdef></glossentry>



<glossentry id="defascii">
<glossterm><acronym>ASCII</acronym></glossterm>
<glossdef>
<para>Stands for <emphasis>American standard code for information
interchange</emphasis>. This is what many people mean when they say
<emphasis>plain text</emphasis>. &kword; can read and write documents in
<acronym>ASCII</acronym> format.</para>
</glossdef>
</glossentry>

<glossentry id="defaspectratio">
<glossterm>Aspect Ratio</glossterm>
<glossdef>
<para>This is the ratio of the measurement of a screen, picture or document
horizontally compared to the vertical measurement.  All standard
computer monitors have the same aspect ratio, regardless of their
resolution. Any &kword; document that conforms to the standard
screen will look good on any monitor.</para>
<para>For many images, it is important to maintain the aspect ratio.  This prevents
distortion to the picture.</para>
</glossdef>
</glossentry>

<glossentry id="defbinarycode">
<glossterm>Binary code</glossterm>
<glossdef>
<para>Binary code is the actual instructions for the computer. So if we
refer to <emphasis>binaries</emphasis> we mean the executable &kword;
program.  While computers have no difficulties reading binary files,
they are not easily understood by people.  Compare to <glossterm
linkend="defsourcecode">Source Code</glossterm>.</para>
</glossdef> 
</glossentry>

<glossentry id="defbitmap">
<glossterm>Bitmap Image</glossterm>
<glossdef>
<para>Bit mapped images are composed of individual dots.  This type of
file is very good for photographs and complex drawings. The downside of
using bitmap images, is that when you change the size of the image on
the page, there is a loss of detail. The file names of such pictures
often end in <emphasis>jpeg</emphasis>, <emphasis>png</emphasis> or 
<emphasis>gif</emphasis>. Compare to <glossterm
linkend="defclipart">Clipart</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defcell">
<glossterm>Cells</glossterm>
<glossdef>
<para>Tables are made up of rows and columns of cells.  Each cell is
defined by a combination of the row and column of a heading.</para>
</glossdef>
</glossentry>

<glossentry id="defclipart">
<glossterm>Clipart</glossterm>
<glossdef>
<para>Clip art refers to vector based graphics. These graphic files
describe the picture as a collection of lines, curves and dots.  These
file formats are preferable to bit-mapped images, because their size can
be made larger or smaller, without any loss in quality. The downside of
vector formats, is that it can be quite difficult to describe certain
types of photographs using only lines and curves.  These images result in
difficult, complicated files and most of the benefits of vector formats
are lost.  Compare to <glossterm linkend="defbitmap">Bitmap
images</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defclipboard">
<glossterm>Clipboard</glossterm>
<glossdef>
<para>The clipboard is a temporary storage area in memory.  Whenever you
use the <guimenuitem>Cut</guimenuitem> or
<guimenuitem>Copy</guimenuitem> command, you are placing the object that
was selected into this memory location.  Then when you use the
<guimenuitem>Paste</guimenuitem> command, you insert the information
from the clipboard into the document.  For more information see the
section on Cut/Copy/Paste.</para>
</glossdef>
</glossentry>

<glossentry id="defcompiling">
<glossterm>Compiling</glossterm>
<glossdef>
<para>When you compile a program, you are converting it from
a source file (which is easily edited by a programmer) into a binary
file (which the computer uses). If you are planning on compiling &kword;,
please try to find a binary version of &koffice; first. Compiling programs
is not for the beginner. For more information on compiling &kword;, see
the section entitled Installation</para></glossdef>
</glossentry>

<glossentry id="defcustomvariables">
<glossterm>Custom Variables</glossterm>
<glossdef>
<para>Using custom variables you can store certain values (&eg; numbers
or text) for later use in your document or in a script.</para>
</glossdef>
</glossentry>

<glossentry id="defdeb">
<glossterm>DEB</glossterm>
<glossdef>
<para>This is a binary file format that is used by Debian and Debian
based distributions.  This will be the suffix of a file specifically for
these distributions.  An example would be
<filename>koffice-1.2.deb</filename>. For more information on installing
these files, refer to the <ulink url="http://www.debian.org">Debian Web
Site</ulink>.</para>
</glossdef>
</glossentry>

<glossentry id="defdialogbox">
<glossterm>Dialog Box</glossterm>
<glossdef>
<para>A dialog box is a small window that appears on top of your working
document.  This window usually has questions, information or
configuration options related to the task you are performing.  When you
are finished with the dialog box, it will disappear and return you to
your document (possibly after making some changes to the
document).</para>
</glossdef>
</glossentry>

<glossentry id="defdtp">
<glossterm><acronym>DTP</acronym></glossterm>
<glossdef>
<para>Stands for <emphasis>DeskTop Publishing</emphasis>.</para>
</glossdef>
</glossentry>

<glossentry id="deffaq">
<glossterm><acronym>FAQ</acronym></glossterm>
<glossdef>
<para>Stands for <emphasis>Frequently Asked Questions</emphasis> and
normally means a document, where questions that arise many times are answered. If you
have a question to the developers of &koffice;, you should always have a
look at the <acronym>FAQ</acronym> first. You'll find the latest version
<ulink
url="http://koffice.kde.org/faq">here</ulink>.</para>
</glossdef>
</glossentry>

<glossentry id="deffilemask">
<glossterm>File Mask</glossterm>
<glossdef>
<para>A file mask can be thought of as a strainer for you.  On the
average computer, there are several thousand files. These files are
sorted into sub-directories, but it is not uncommon for many users to
have 100's of data files in a single sub-directory.</para>
<para>Fortunately for us, most applications use a suffix to their
filenames.  By applying a file mask, &kword; will only show you the
files which are not filtered out by the mask. (That is to say &kword;
only shows the files that fit through the strainer).  This can be
helpful if you have many files from many different applications. The
file mask is incorporated in the <guilabel>File Type</guilabel> line of
the save and load dialog boxes.</para>
<para>As an example. If you use a file mask for &kword; files, the file
mask will try to filter out all files that are not for
&kword;.</para></glossdef>
</glossentry>

<glossentry id="deffilter">
<glossterm>Filter</glossterm>
<glossdef>
<para>A filter takes a document file from one program (&eg; &Microsoft;
<application>Word</application>), and <emphasis>filters</emphasis> out
the text and formatting information and converts that information into a
&kword; document.  Filters are used to read and write files for other
programs.</para>
</glossdef>
</glossentry>

<glossentry id="deffooter">
<glossterm>Footer</glossterm>
<glossdef>
<para>The footer of a page is an area below the normal text area. Often
it contains the page numbering and maybe some additional
information. The contents of the footer are normally the same for most
pages, and changing the footer on one page will change all other pages
as well. See <glossterm linkend="defheader">Header</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defframe">
<glossterm>Frame</glossterm>
<glossdef>
<para>Nearly everything in &kword; is in a frame. Text is always in
a text frame. Pictures are in picture frames. Parts are in part
frames. A frame is basically just a rectangle that can contain some part
of your document. Frames can be moved, resized, deleted etc.</para>
</glossdef>
</glossentry>

<glossentry id="defframeset">
<glossterm>Frameset</glossterm>
<glossdef>
<para>A frame-set is a group of frames which are connected together. If
you're writing text that doesn't fit into the first frame of a frame-set,
it will continue in the next frame belonging to that frame-set.</para>
</glossdef>
</glossentry>

<glossentry id="defftp">
<glossterm>&FTP;</glossterm>
<glossdef>
<para>&FTP; is the <emphasis>File Transfer Protocol</emphasis>. It's an
Internet protocol that allows you to retrieve files from so-called &FTP;
servers. If you want to download &koffice; from the Internet, you'll
probably use &FTP;.</para>
</glossdef>
</glossentry>

<glossentry id="defhardramebreak">
<glossterm>Hard Frame Break</glossterm>
<glossdef>
<para>Normally, &kword; automatically adjusts text so it fits into a
text frame. By inserting a hard frame break you can force &kword; to
always start the next frame in the frameset with the text that follows
the break.</para>
</glossdef>
</glossentry>

<glossentry id="defheader">
<glossterm>Header</glossterm>
<glossdef>
<para>The header of a page is an area above the normal text area. Often
it contains the page numbering and maybe some additional
information. The contents of the header normally are the same for most
pages, and changing the header on one page will change all other pages
as well. See <glossterm linkend="deffooter">Footer</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defhtml">
<glossterm><acronym>HTML</acronym></glossterm>
<glossdef>
<para>Stands for <emphasis>HyperText Markup Language</emphasis>. Most
web pages on the Internet are written in
<acronym>HTML</acronym>. &kword; can read and write
<acronym>HTML</acronym> documents for publishing on the World Wide
Web.</para>
</glossdef>
</glossentry>

<glossentry id="defhue">
<glossterm><acronym>Hue</acronym></glossterm>
<glossdef>
<para>Hue is a more technically correct term for what we generally refer to as <emphasis>color</emphasis>.</para>
<para>Examples of hues include red, green, blue and purple.</para>
</glossdef>
</glossentry>

<glossentry id="definlineframe">
<glossterm>Inline frame</glossterm>
<glossdef>
<para>An inline frame is a special frame type in &kword;.  Inline frames are associated with a position in a text frame.  
&kword; will keep the inline frame near the specified text.  You will not be able to determine where exactly on a page the 
frame will appear, but it will be located close to the specified text.</para>
<para>If you insert or delete text in front of the specified text, the inline image will move up or down the page to follow the 
specified text</para>
<para><tip><para>Inline frames are very useful when they contain a picture, graph or figure.  Simply place the inline frame within the 
text which describes the object, and &kword; will make sure both the text and the inline frame are always near each other.</para></tip></para>
</glossdef>
</glossentry>

<glossentry id="defkde2">
<glossterm>&kde;</glossterm>
<glossdef>
<para>Stands for the <emphasis>K Desktop Environment</emphasis>.  Part of &kde; is
required for &kword; to operate.  The K Desktop Environment is a user
interface which allows users to manipulate files and operate programs
graphically.  For more information, please visit <ulink
url="http://www.kde.org">www.kde.org</ulink>.</para>
</glossdef> 
</glossentry>

<glossentry id="defkeybinding">
<glossterm>Key Binding</glossterm>
<glossdef>
<para>Foo</para>
</glossdef>
</glossentry>

<glossentry id="deflandscape">
<glossterm>Landscape</glossterm>
<glossdef>
<para>When you have a standard sheet of paper, you can either orient
your document with the long side vertically or horizontally.  When the
horizontal dimension is greater than the vertical, this is termed
Landscape.</para>
<para> Compare
with <glossterm linkend="defportrait">Portrait</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defmenubar">
<glossterm>Menubar</glossterm>
<glossdef>
<para>The menubar is located at the top of the &kword; screen.  You can
use it to access all features of &kword;.</para> 
<para>Menubar: <inlinemediaobject><imageobject> <imagedata
fileref="basic.png" format="PNG"
align="center"/></imageobject></inlinemediaobject></para>
</glossdef>
</glossentry>

<glossentry id="defportrait">
<glossterm>Portrait</glossterm>
<glossdef>
<para>When you have a standard sheet of paper, you can either orient
your document with the long side vertically or horizontally.  When the
vertical dimension is greater than the horizontal, this is termed
Portrait.</para>
<para>Example: <inlinemediaobject><imageobject><imagedata
fileref="portrait.png" format="PNG"
align="center"/></imageobject></inlinemediaobject></para>
<para>Compare with <glossterm
linkend="deflandscape">Landscape</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="defrpm">
<glossterm><acronym>RPM</acronym></glossterm>
<glossdef>
<para>This is the binary file format for distributions based on the
&RedHat; package manager, a widely used packaging tool for the &Linux;
operating system.  If you still have to get &koffice; and your system
supports <acronym>RPM</acronym> packages, you should get &koffice;
packages ending in <literal role="extension">.rpm</literal>. They are
very easy to use.</para>
</glossdef>
</glossentry>

<glossentry id="defsaturation">
<glossterm><acronym>Saturation</acronym></glossterm>
<glossdef>
<para>Saturation refers to the subjective quantity of a specific hue in a color.  Colors with a low saturation appear more white.
Colors with high saturation appear more richly colored.</para>
<para>This is a set of four red dots which increase in saturation from left to right.
<inlinemediaobject><imageobject><imagedata
fileref="saturation.png" format="PNG"/></imageobject></inlinemediaobject></para>
</glossdef>
</glossentry>

<glossentry id="defscalingpicture">
<glossterm>Scaling Pictures</glossterm>
<glossdef>
<para>Whenever you change the size of a graphics image, you are scaling
that image.  In &kword; you scale the pictures by changing the shape of
the frame which surrounds the graphic.</para>
</glossdef>
</glossentry>

<glossentry id="defsourcecode">
<glossterm>Source Code</glossterm>
<glossdef>
<para>Source code is the human readable version of an application (such
as &kword;).  Computers cannot use source code directly.  Instead,
source code must be <glossterm linkend="defcompiling">compiled</glossterm> into
binary code, before use.</para>
</glossdef>
</glossentry>

<glossentry id="deftar">
<glossterm>TAR</glossterm>
<glossdef>
<para>Tar is a tool used for the archiving of files in so-called
<emphasis>tar-files</emphasis> which you recognize by their suffix
<literal role="extension">.tar</literal>.  You'll find &koffice; source
and binary distributions as <glossterm linkend="deftgz">gzipped
tar-files</glossterm>. However, you shouldn't use them if there are special
packages for your system and package manager. See <glossterm
linkend="defrpm">RPM</glossterm>, <glossterm linkend="defdeb">DEB</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="deftargz">
<glossterm><literal role="extension">tar.gz</literal></glossterm>
<glossdef>
<para>See <glossterm linkend="deftgz"><acronym>TGZ</acronym></glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="deftgz">
<glossterm><acronym>TGZ</acronym></glossterm>
<glossdef>
<para>Files ending in <literal role="extension">.tar.gz</literal> or
<literal role="extension">.tgz</literal> are <glossterm
linkend="deftar">tar-files</glossterm> compressed with the
<command>gzip</command> program.  This makes the tar files smaller and
quicker to download.  You'll find &koffice; source and binary
distributions in this format. However, you shouldn't use them if there
are special packages for your system and package manager. See <glossterm
linkend="defrpm">RPM</glossterm>, <glossterm linkend="defdeb">DEB</glossterm>.</para>
</glossdef>
</glossentry>

<glossentry id="deftoolbar">
<glossterm>Toolbar</glossterm>
<glossdef>
<para>A toolbar is a line of buttons which are shortcuts to more of the
commonly used features of &kword;.</para>
</glossdef>
</glossentry>

<glossentry id="defurl">
<glossterm>&URL;</glossterm>
<glossdef>
<para>&URL; is an abbreviation for Universal Resource Locater.  A universal resource locater is 
the technical term for what is commonly referred to as a websites address.</para>
<para>Examples of &URL;s include <ulink url="http://www.koffice.org">http://www.koffice.org</ulink> and
<ulink url="http://www.kde.org">http://www.kde.org</ulink></para>
</glossdef>
</glossentry>

<glossentry id="defvalue">
<glossterm><acronym>Value (color)</acronym></glossterm>
<glossdef>
<para>Color value refers to how bright or dark a color is.  Colors with low value are more black in appearance.  Colors with high 
value are more richly colored.</para>
<para>This is a set of four red dots which increase in value from left to right.
<inlinemediaobject><imageobject><imagedata
fileref="value.png" format="PNG"/></imageobject></inlinemediaobject></para>
</glossdef>
</glossentry>


<glossentry id="defvectorimage">
<glossterm>Vector Image</glossterm>
<glossdef>
<para>A vector based graphic is described in terms of lines and shapes,
not in terms of dots.  These files are often referred to as <glossterm
linkend="defclipart">clip-art</glossterm>. Because of this, clipart usually
scales better than bit-mapped images. </para>
</glossdef>
</glossentry>

<glossentry id="defwysiwyg">
<glossterm><acronym>WYSIWYG</acronym></glossterm>
<glossdef>
<para>Stands for <emphasis>What You See Is What You Get</emphasis>.
&kword; is a <acronym>WYSIWYG</acronym> word processor, which means that
the document will appear the same on the screen while you are editing
it, as it will on the printed page.</para>
</glossdef>
</glossentry>

<glossentry id="defx">
<glossterm>&X-Window; system</glossterm>
<glossdef>
<para>The &X-Window; System (also known simply as <quote>X</quote>) is
required for &koffice; to operate.  More information on &X-Window; for
&Linux; can be found at <ulink
url="http://www.xfree86.org">http://www.xfree86.org</ulink></para>
</glossdef>
</glossentry>

<glossentry id="gloss-bump-map">
<glossterm>Bump Map</glossterm>
<glossdef>
<para>A bump map is a way to simulate a rough surface, without having
to model every single <quote>bump</quote> on the surface, and without
changing the underlying geometric shape of the object itself.</para>
<para>It is common to use the same file as both a bump map and a <link
linkend="gloss-texture-map">texture map</link>.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-primitives">
<glossterm>Primitives</glossterm>
<glossdef>
<para>Primitives are the basic geometric shapes that you can use as
<quote>building blocks</quote>.  Most complex 3d models are created
from many dozens, or even hundreds, of these primitives, which are
then edited and manipulated to give a more realistic
appearance.</para>
</glossdef>
</glossentry>

<glossentry id="gloss-rendering">
<glossterm>Rendering</glossterm>
<glossdef>
<para>Not yet written</para>
</glossdef>
</glossentry>

<glossentry id="gloss-texture-map">
<glossterm>Texture Map</glossterm>
<glossdef>
<para>A texture map is a way of applying color to the surface of an
object on a pixel by pixel basis, by applying an image file as a color
map.</para>
<para>It is common to use the same image file as a <link
linkend="gloss-bump-map">bump map</link>.</para>
</glossdef>
</glossentry>



</glossary>