summaryrefslogtreecommitdiffstats
path: root/doc/kdeprint/highlights.docbook
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-06 02:28:57 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-06 02:28:57 -0600
commit7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04 (patch)
treeb7c6396f4f7fe78dcd49424bff707e977541de18 /doc/kdeprint/highlights.docbook
parent66c0fa70796c1989a9f3adb0c5c0ad799ade48ca (diff)
downloadtdebase-7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04.tar.gz
tdebase-7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04.zip
Additional kde to tde renaming
Diffstat (limited to 'doc/kdeprint/highlights.docbook')
-rw-r--r--doc/kdeprint/highlights.docbook76
1 files changed, 38 insertions, 38 deletions
diff --git a/doc/kdeprint/highlights.docbook b/doc/kdeprint/highlights.docbook
index 85e0e348f..72982c10c 100644
--- a/doc/kdeprint/highlights.docbook
+++ b/doc/kdeprint/highlights.docbook
@@ -1,19 +1,19 @@
-<chapter id="kdeprint-highlights">
-<title>&kdeprint;'s Highlights</title>
+<chapter id="tdeprint-highlights">
+<title>&tdeprint;'s Highlights</title>
-<para>The new &kdeprint; system includes more than one highlight.
+<para>The new &tdeprint; system includes more than one highlight.
Having worked in an environment in the past that is not exactly
sophisticated, as far as printing is concerned, take a look at some of
-the benefits that come with &kdeprint;</para>
+the benefits that come with &tdeprint;</para>
<sect1 id="add-printer-wizard">
<title>The <quote>Add Printer</quote> Wizard</title>
-<para>&kdeprint; has an <quote>Add Printer Wizard</quote>. The Add
+<para>&tdeprint; has an <quote>Add Printer Wizard</quote>. The Add
Printer Wizard helps you with adding and configuring a new printer. Of
course, you may do this manually as well.</para>
-<para>&kdeprint; helps you <quote>discover</quote> printers. It is able
+<para>&tdeprint; helps you <quote>discover</quote> printers. It is able
to scan the environment for available devices and queues. This works for
network connections using <acronym>TCP</acronym> (AppSocket,
<acronym>aka</acronym> &HP; <trademark
@@ -67,22 +67,22 @@ subsystem.</para>
</listitem>
</itemizedlist>
-<para>A screenshot of the &kdeprint; PrintJob Viewer shows the information
+<para>A screenshot of the &tdeprint; PrintJob Viewer shows the information
you get: Job-ID, target printer, job name, job owner, job status and job
-size. In the next &kdeprint; release you will also see information about the
+size. In the next &tdeprint; release you will also see information about the
number of pages (as &CUPS; calculates it; see chapter on page accounting
for more information about its merits and limitations).</para>
<screenshot>
-<screeninfo>A screenshot of the &kdeprint; PrintJob Viewer</screeninfo>
+<screeninfo>A screenshot of the &tdeprint; PrintJob Viewer</screeninfo>
<mediaobject>
<imageobject>
-<imagedata fileref="kdeprint-jobviewer.png" format="PNG"/>
+<imagedata fileref="tdeprint-jobviewer.png" format="PNG"/>
</imageobject>
<textobject>
-<phrase>Here's a screenshot of the &kdeprint; PrintJob Viewer.</phrase>
+<phrase>Here's a screenshot of the &tdeprint; PrintJob Viewer.</phrase>
</textobject>
-<caption><para>A screenshot of the &kdeprint; PrintJob
+<caption><para>A screenshot of the &tdeprint; PrintJob
Viewer.</para></caption>
</mediaobject>
</screenshot>
@@ -106,7 +106,7 @@ to see this:</para>
<imagedata fileref="kcontrolcenter-printmanager-jobcontrol-2.png" format="PNG"/>
</imageobject>
<textobject>
-<phrase>Here's a screenshot of the &kdeprint; PrintJob Viewer.</phrase>
+<phrase>Here's a screenshot of the &tdeprint; PrintJob Viewer.</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -116,7 +116,7 @@ to see this:</para>
<sect1 id="modules-for-different-subsystems">
<title>Modules for different print subsystems</title>
-<para>&kdeprint; uses different modules to realize the interface to the
+<para>&tdeprint; uses different modules to realize the interface to the
possible print subsystems. Not all the modules are yet developed fully,
but you will have basic printing functionality with:</para>
@@ -142,7 +142,7 @@ Modules for other print subsystems, such as <acronym>PLP</acronym>,
<acronym>PPR</acronym> and <acronym>PDQ</acronym> may be available
later.</para>
-<para>&kdeprint; makes &kde; much more flexible. It gives freedom of
+<para>&tdeprint; makes &kde; much more flexible. It gives freedom of
choice to &kde; 2.2 users. To use different available print subsystems,
these must, of course, be installed independently from &kde;. In
former versions, users were stuck with the old <acronym>LPD</acronym>
@@ -152,19 +152,19 @@ appear on the scene.</para>
</sect1>
-<sect1 id="kdeprint-goodies">
-<title>More &kdeprint; <quote>Goodies</quote></title>
+<sect1 id="tdeprint-goodies">
+<title>More &tdeprint; <quote>Goodies</quote></title>
<subtitle>Benefitting all Print SubSystems.</subtitle>
-<para>Some specific features of &kdeprint; depend on the chosen print
+<para>Some specific features of &tdeprint; depend on the chosen print
subsystem. This dependency might exist because those features are only
-implemented there; remember, &kdeprint; is an intermediate layer between
+implemented there; remember, &tdeprint; is an intermediate layer between
&kde; applications, and the print subsystem, but it's no replacement for
any print subsystem by itself. Such dependency may exist for another
-reason: that &kdeprint; has not yet implemented an interface to all the
+reason: that &tdeprint; has not yet implemented an interface to all the
features of all the subsystems.</para>
-<para>Other features include benefits from &kdeprint; that are
+<para>Other features include benefits from &tdeprint; that are
independent of the chosen print subsystem, and are available with all of
them. At present there are <quote>special</quote> or
<quote>virtual</quote> printers, and some generic
@@ -183,7 +183,7 @@ displaying on screen using &kghostview;.</para>
<varlistentry>
<term><guilabel>Special Printers</guilabel></term>
<listitem>
-<para>Amongst these additional &kdeprint; features are a few
+<para>Amongst these additional &tdeprint; features are a few
<quote>special</quote> or <quote>virtual</quote> printers:</para>
<para>These special printers may:</para>
@@ -232,7 +232,7 @@ configurable on a per-user basis.</para>
<varlistentry>
<term><guilabel>Generic Pre-Filtering</guilabel></term>
<listitem>
-<para>&kdeprint; provides you with a framework to define and configure
+<para>&tdeprint; provides you with a framework to define and configure
your own <quote>pre-filters</quote>. These pre-filters may take effect
<emphasis>before</emphasis> they are passed to your print subsystem for
further processing, but <emphasis>after</emphasis> the (&PostScript;,
@@ -264,13 +264,13 @@ any one of those formats.</para>
This makes an extension of the concept very easy for experienced developers,
but end-user configuration is also done through an intuitive graphical
user interface. So, fear not, you don't need to learn
-<acronym>XML</acronym> because of &kdeprint;!</para>
+<acronym>XML</acronym> because of &tdeprint;!</para>
<variablelist>
<varlistentry>
<term><guilabel>Multiple Pages Per Sheet Filter</guilabel></term>
<listitem>
-<para>This is a predefined filter that installs with &kdeprint;. It
+<para>This is a predefined filter that installs with &tdeprint;. It
allows you to create a modified &PostScript; output, from &PostScript;
input, that prints 1, 2, or 4 logical pages on a single sheet of
paper.</para>
@@ -280,7 +280,7 @@ paper.</para>
<varlistentry>
<term><guilabel>Enscript Text Filter</guilabel></term>
<listitem>
-<para>This is a predefined filter that installs with &kdeprint;. It
+<para>This is a predefined filter that installs with &tdeprint;. It
allows you to create &PostScript; output from any text file input, that
includes syntax highlighting for program listings, pretty-printing, and
nice configurable page frames and headers.</para>
@@ -315,9 +315,9 @@ side. These can then be folded to make a pamphlet.</para>
</variablelist>
</sect1>
<sect1 id="cups-plugin">
-<title>&CUPS; Support: the Most Important Module in &kdeprint;</title>
+<title>&CUPS; Support: the Most Important Module in &tdeprint;</title>
-<para>&kdeprint; contains a module for &CUPS;. &CUPS;, the
+<para>&tdeprint; contains a module for &CUPS;. &CUPS;, the
<quote>Common &UNIX; Printing System</quote> (<ulink
url="http://www.cups.org">http://www.cups.org/</ulink>), is the most
advanced, powerful and flexible of all print subsystems on &UNIX; and
@@ -325,7 +325,7 @@ other &UNIX;-like operating systems. It is still quite new on the
horizon, but is based on <acronym>IPP</acronym>, the Internet Printing
Protocol, the newly emerging standard for the future of network
printing. &CUPS; is clearly the print system of choice for Michael
-Goffioul, the principal &kdeprint; developer.</para>
+Goffioul, the principal &tdeprint; developer.</para>
<para>Experienced &kde; users may already be familiar with Michael's
utilities <application>qtcups</application> and
@@ -360,9 +360,9 @@ restart it.</para>
</sect2>
<sect2>
-<title>&kdeprint; &mdash; The Heir</title>
+<title>&tdeprint; &mdash; The Heir</title>
-<para>The &CUPS; Module in &kdeprint; now contains all (and more)
+<para>The &CUPS; Module in &tdeprint; now contains all (and more)
functions that were provided by <application>qtcups</application> and
<application>kups</application> in former &kde; versions.</para>
@@ -372,7 +372,7 @@ functions that were provided by <application>qtcups</application> and
<command>kcmshell printers</command> from now on.
</para>
-<para>The &kdeprint; module for &CUPS; also lets you fully administer
+<para>The &tdeprint; module for &CUPS; also lets you fully administer
the print subsystem, just like <application>kups</application> did
before. It can start, stop and configure your &CUPS; daemon. It can also
start, stop, add and delete <quote>printers</quote> (&ie; printer
@@ -385,7 +385,7 @@ different default setting of print options.</para>
<sect2>
<title>&kprinter; &mdash; Graphical Print Command</title>
-<para>&kdeprint;'s &CUPS; module gives you access to a <quote>graphical
+<para>&tdeprint;'s &CUPS; module gives you access to a <quote>graphical
print command</quote>, like <application>qtcups</application> did
before.</para>
@@ -469,16 +469,16 @@ for you. Read more about this in <xref linkend="ppd-files"/>.</para>
<title>Plans for Future Development</title>
<para>What you have now is the first, already very feature-rich
-version of &kdeprint;. This version is, of course, fully usable for
+version of &tdeprint;. This version is, of course, fully usable for
printing. You might even think that <quote>it was never so
easy</quote> (not even back in the days when you had to use
&Microsoft; &Windows;).</para>
-<para> In the future, &kdeprint; will become even better. It will do a
+<para> In the future, &tdeprint; will become even better. It will do a
better job of <quote>detecting</quote> your installed print subsystem
-itself. Already &kdeprint; is doing quite well in automatically
+itself. Already &tdeprint; is doing quite well in automatically
sensing if you have &CUPS; on your system. But in many cases you will
-have to tell &kdeprint; what you are using, if you want to keep a
+have to tell &tdeprint; what you are using, if you want to keep a
legacy print system.</para>
<para>The most important improvement in the near future will be a
@@ -511,7 +511,7 @@ a virtual folder to the services section of the &konqueror; navigation
panel, giving a nice integrated way to browse and manage your print
system via the &URL; <userinput>print:/manager</userinput>.</para>
-<para>Please contact Michael Goffioul at <email>kdeprint@swing.be</email>
+<para>Please contact Michael Goffioul at <email>tdeprint@swing.be</email>
with any further user or developer suggestions.</para>
</sect1>