diff options
Diffstat (limited to 'tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook')
| -rw-r--r-- | tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook b/tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook index 5124dddaa9a..1ece07bc322 100644 --- a/tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook +++ b/tde-i18n-en_GB/docs/kdebase/kdeprint/add-printer-wiz.docbook @@ -27,7 +27,7 @@ <screenshot> <screeninfo ->The &kdeprint; wizard introduction screen</screeninfo> +>The &tdeprint; wizard introduction screen</screeninfo> <mediaobject> <imageobject> <imagedata fileref="cupsaddprinterwizard1.png" @@ -125,14 +125,14 @@ format="PNG"/></imageobject> <screenshot> <screeninfo ->&kdeprint; wizard network scan</screeninfo> +>&tdeprint; wizard network scan</screeninfo> <mediaobject> <imageobject> <imagedata fileref="cupsaddprinterwizard3_networkscan.png" format="PNG"/></imageobject> <textobject> <phrase ->In the &kdeprint; wizard, you can enter network details directly, or you can scan the network automatically.</phrase +>In the &tdeprint; wizard, you can enter network details directly, or you can scan the network automatically.</phrase ></textobject> </mediaobject> </screenshot> @@ -152,7 +152,7 @@ format="PNG"/></imageobject> <para >In the case of <acronym >SMB</acronym ->, &kdeprint; will use the Samba utilities <command +>, &tdeprint; will use the Samba utilities <command >nmblookup</command > and <command >smbclient</command @@ -161,7 +161,7 @@ format="PNG"/></imageobject> <para >In the case of &IPP; (Port 631) and <acronym >TCP</acronym -> Network/AppSocket (Port 9100) &kdeprint; will try to open the port and, if successful, send an <command +> Network/AppSocket (Port 9100) &tdeprint; will try to open the port and, if successful, send an <command >ipp-get-printer-attribute</command > request to the printer. For newer &HP; printers the latter usually works, because they support both AppSocket and &IPP;.</para> @@ -177,14 +177,14 @@ format="PNG"/></imageobject> <screenshot> <screeninfo ->&kdeprint; wizard network configuration dialogue</screeninfo> +>&tdeprint; wizard network configuration dialogue</screeninfo> <mediaobject> <imageobject> <imagedata fileref="cupsaddprinterwizard4_networkscan_config.png" format="PNG"/></imageobject> <textobject> <phrase ->In the &kdeprint; wizard, you can enter parameters to have the wizard scan parts of your network.</phrase +>In the &tdeprint; wizard, you can enter parameters to have the wizard scan parts of your network.</phrase ></textobject> </mediaobject> </screenshot> @@ -204,7 +204,7 @@ format="PNG"/></imageobject> >database</quote > of available drivers on your system, select the manufacturer in the left part of the window first, then the device model in the right part. This split window shows all &PPD;s found by &CUPS; in its standard repository of installable &PPD;s. This repository normally is <filename class="directory" >/usr/share/cups/model/</filename ->. If you want your driver to be found automatically by &CUPS; and &kdeprint;, place it in there.</para> +>. If you want your driver to be found automatically by &CUPS; and &tdeprint;, place it in there.</para> <!-- Insert Screenshot here: --> @@ -260,8 +260,8 @@ url="http://www.linuxprinting.org" </itemizedlist> <para ->And ask for help. At a later stage, a document detailing the differences between the different driver and &PPD; models will appear at <ulink url="http://kdeprint.sourceforge.net" ->http://kdeprint.sourceforge.net/</ulink +>And ask for help. At a later stage, a document detailing the differences between the different driver and &PPD; models will appear at <ulink url="http://tdeprint.sourceforge.net" +>http://tdeprint.sourceforge.net/</ulink > Watch out for this!</para> <para |