summaryrefslogtreecommitdiffstats
path: root/tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-02 22:36:59 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-02 22:36:59 -0600
commit85ca18776aa487b06b9d5ab7459b8f837ba637f3 (patch)
tree7bbd04c5b00831b04c53c371f5b7a5c32154fb1c /tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook
parent9b58d35185905f8334142bf4988cb784e993aea7 (diff)
downloadtde-i18n-85ca18776aa487b06b9d5ab7459b8f837ba637f3.tar.gz
tde-i18n-85ca18776aa487b06b9d5ab7459b8f837ba637f3.zip
Initial kde-tde rename
Diffstat (limited to 'tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook')
-rw-r--r--tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook66
1 files changed, 33 insertions, 33 deletions
diff --git a/tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook b/tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook
index 26466730066..38e6cc497e8 100644
--- a/tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook
+++ b/tde-i18n-en_GB/docs/kdebase/kdeprint/highlights.docbook
@@ -1,9 +1,9 @@
-<chapter id="kdeprint-highlights">
+<chapter id="tdeprint-highlights">
<title
->&kdeprint;'s Highlights</title>
+>&tdeprint;'s Highlights</title>
<para
->The new &kdeprint; 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 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 &tdeprint;</para>
<sect1 id="add-printer-wizard">
<title
@@ -12,12 +12,12 @@
> Wizard</title>
<para
->&kdeprint; has an <quote
+>&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
+>&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
@@ -89,22 +89,22 @@
</itemizedlist>
<para
->A screenshot of the &kdeprint; 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 number of pages (as &CUPS; calculates it; see chapter on page accounting for more information about its merits and limitations).</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 &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>
+>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>
+>Here's a screenshot of the &tdeprint; PrintJob Viewer.</phrase>
</textobject>
<caption
><para
->A screenshot of the &kdeprint; PrintJob Viewer.</para
+>A screenshot of the &tdeprint; PrintJob Viewer.</para
></caption>
</mediaobject>
</screenshot>
@@ -139,7 +139,7 @@
</imageobject>
<textobject>
<phrase
->Here's a screenshot of the &kdeprint; PrintJob Viewer.</phrase>
+>Here's a screenshot of the &tdeprint; PrintJob Viewer.</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -151,7 +151,7 @@
>Modules for different print subsystems</title>
<para
->&kdeprint; uses different modules to realise the interface to the possible print subsystems. Not all the modules are yet developed fully, but you will have basic printing functionality with:</para>
+>&tdeprint; uses different modules to realise the interface to the possible print subsystems. Not all the modules are yet developed fully, but you will have basic printing functionality with:</para>
<itemizedlist>
<listitem>
@@ -198,25 +198,25 @@
> may be available later.</para>
<para
->&kdeprint; 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
+>&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
> style print subsystems. Now they can even use &CUPS;. In the future, there will be easy integration of new subsystems, as they appear on the scene.</para>
</sect1>
-<sect1 id="kdeprint-goodies">
+<sect1 id="tdeprint-goodies">
<title
->More &kdeprint; <quote
+>More &tdeprint; <quote
>Goodies</quote
></title>
<subtitle
>Benefitting all Print SubSystems.</subtitle>
<para
->Some specific features of &kdeprint; depend on the chosen print subsystem. This dependency might exist because those features are only implemented there; remember, &kdeprint; 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 features of all the subsystems.</para>
+>Some specific features of &tdeprint; depend on the chosen print subsystem. This dependency might exist because those features are only 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 &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 independent of the chosen print subsystem, and are available with all of them. At present there are <quote
+>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
@@ -243,7 +243,7 @@
></term>
<listitem>
<para
->Amongst these additional &kdeprint; features are a few <quote
+>Amongst these additional &tdeprint; features are a few <quote
>special</quote
> or <quote
>virtual</quote
@@ -322,7 +322,7 @@
></term>
<listitem>
<para
->&kdeprint; provides you with a framework to define and configure your own <quote
+>&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
@@ -362,7 +362,7 @@
>XML</acronym
> files. 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>
+> because of &tdeprint;!</para>
<variablelist>
<varlistentry>
@@ -372,7 +372,7 @@
></term>
<listitem>
<para
->This is a predefined filter that installs with &kdeprint;. 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>
+>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>
</listitem>
</varlistentry>
@@ -383,7 +383,7 @@
></term>
<listitem>
<para
->This is a predefined filter that installs with &kdeprint;. 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>
+>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>
</listitem>
</varlistentry>
@@ -421,16 +421,16 @@
</sect1>
<sect1 id="cups-plugin">
<title
->&CUPS; Support: the Most Important Module in &kdeprint;</title>
+>&CUPS; Support: the Most Important Module in &tdeprint;</title>
<para
->&kdeprint; contains a module for &CUPS;. &CUPS;, the <quote
+>&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 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>
+>, 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 &tdeprint; developer.</para>
<para
>Experienced &kde; users may already be familiar with Michael's utilities <application
@@ -472,10 +472,10 @@
<sect2>
<title
->&kdeprint; &mdash; The Heir</title>
+>&tdeprint; &mdash; The Heir</title>
<para
->The &CUPS; Module in &kdeprint; now contains all (and more) functions that were provided by <application
+>The &CUPS; Module in &tdeprint; now contains all (and more) functions that were provided by <application
>qtcups</application
> and <application
>kups</application
@@ -493,7 +493,7 @@
> from now on. </para>
<para
->The &kdeprint; module for &CUPS; also lets you fully administer the print subsystem, just like <application
+>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
@@ -508,7 +508,7 @@
>&kprinter; &mdash; Graphical Print Command</title>
<para
->&kdeprint;'s &CUPS; module gives you access to a <quote
+>&tdeprint;'s &CUPS; module gives you access to a <quote
>graphical print command</quote
>, like <application
>qtcups</application
@@ -636,14 +636,14 @@ format="PNG"/></imageobject>
>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 printing. You might even think that <quote
+>What you have now is the first, already very feature-rich 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 better job of <quote
+>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 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 legacy print system.</para>
+> your installed print subsystem 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 &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 completion of the <application
@@ -688,7 +688,7 @@ format="PNG"/></imageobject>
<para
>Please contact Michael Goffioul at <email
->kdeprint@swing.be</email
+>tdeprint@swing.be</email
> with any further user or developer suggestions.</para>
</sect1>