From 7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 6 Nov 2011 02:28:57 -0600 Subject: Additional kde to tde renaming --- doc/faq/install.docbook | 4 +- doc/faq/webbrowse.docbook | 2 +- doc/glossary/CMakeLists.txt | 2 +- doc/glossary/index.docbook | 4 +- doc/glossary/kdeprintingglossary.docbook | 16 +++--- doc/kcontrol/passwords/index.docbook | 4 +- doc/kdeprint/CMakeLists.txt | 2 +- doc/kdeprint/add-printer-wiz.docbook | 18 +++---- doc/kdeprint/cups-config.docbook | 14 ++--- doc/kdeprint/cupsoptions.docbook | 16 +++--- doc/kdeprint/extensions.docbook | 2 +- doc/kdeprint/final-word.docbook | 12 ++--- doc/kdeprint/getting-started.docbook | 24 ++++----- doc/kdeprint/highlights.docbook | 76 +++++++++++++------------- doc/kdeprint/index.docbook | 24 ++++----- doc/kdeprint/lprng.docbook | 2 +- doc/kdeprint/tech-overview.docbook | 74 ++++++++++++------------- doc/kdeprint/theory.docbook | 4 +- doc/kdesu/CMakeLists.txt | 2 +- doc/kdesu/index.docbook | 80 +++++++++++++-------------- doc/kdesu/man-kdesu.1.docbook | 38 ++++++------- doc/kioslave/index.docbook | 2 +- doc/kioslave/print.docbook | 10 ++-- doc/konqueror/faq.docbook | 2 +- doc/konqueror/filemanager.docbook | 2 +- doc/userguide/base-kde-applications.docbook | 4 +- doc/userguide/kde-as-root.docbook | 6 +-- doc/userguide/kde-for-admins.docbook | 84 ++++++++++++++--------------- doc/userguide/konsole-intro.docbook | 4 +- 29 files changed, 267 insertions(+), 267 deletions(-) (limited to 'doc') diff --git a/doc/faq/install.docbook b/doc/faq/install.docbook index d428f0ae5..a0edad92d 100644 --- a/doc/faq/install.docbook +++ b/doc/faq/install.docbook @@ -167,7 +167,7 @@ server. -kdegames +tdegames Optional Various games like &kmahjongg;, &ksnake;, &kasteroids;, and @@ -206,7 +206,7 @@ download manager &kget;, and several other network-related programs. -kdepim +tdepim Optional Personal information management tools. Contains the email client &kmail;, the newsreader &knode; and other related programs. diff --git a/doc/faq/webbrowse.docbook b/doc/faq/webbrowse.docbook index b80c7ae1a..94315dcf9 100644 --- a/doc/faq/webbrowse.docbook +++ b/doc/faq/webbrowse.docbook @@ -19,7 +19,7 @@ url="http://www.konqueror.org">http://www.konqueror.org where a Can I run &konqueror; without running &kde;? -Yes. Just install &Qt;, kdelibs and kdebase, and from your favorite window manager just launch &konqueror;. It should work just fine, but if it doesn't (&kde; developers don't test that case often), report it to http://bugs.kde.org and try running "kdeinit" before running &konqueror;, it usually helps. +Yes. Just install &Qt;, kdelibs and kdebase, and from your favorite window manager just launch &konqueror;. It should work just fine, but if it doesn't (&kde; developers don't test that case often), report it to http://bugs.kde.org and try running "tdeinit" before running &konqueror;, it usually helps. This is of course the same for any other &kde; application. diff --git a/doc/glossary/CMakeLists.txt b/doc/glossary/CMakeLists.txt index decd03348..73a84f204 100644 --- a/doc/glossary/CMakeLists.txt +++ b/doc/glossary/CMakeLists.txt @@ -10,5 +10,5 @@ ################################################# tde_create_handbook( - FILES checkxrefs index.docbook kdeprintingglossary.docbook + FILES checkxrefs index.docbook tdeprintingglossary.docbook DESTINATION khelpcenter/glossary ) diff --git a/doc/glossary/index.docbook b/doc/glossary/index.docbook index 4aba44c53..f089c0bad 100644 --- a/doc/glossary/index.docbook +++ b/doc/glossary/index.docbook @@ -2,7 +2,7 @@ - + ]> @@ -10,7 +10,7 @@ -&glossary-kdeprinting; +&glossary-tdeprinting; Technologies diff --git a/doc/glossary/kdeprintingglossary.docbook b/doc/glossary/kdeprintingglossary.docbook index 7a9311c73..6a0f35a34 100644 --- a/doc/glossary/kdeprintingglossary.docbook +++ b/doc/glossary/kdeprintingglossary.docbook @@ -5,7 +5,7 @@ "customization/dtd/kdex.dtd" [ - + ]> @@ -170,7 +170,7 @@ Authentication BSD-style printing IPP - KDEPrint + KDEPrint LPR/LPD PPD @@ -184,7 +184,7 @@ is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. - KDEPrint Handbook + KDEPrint Handbook @@ -715,7 +715,7 @@ now. - + KDEPrint The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings @@ -736,16 +736,16 @@ now. BSD-style printing &CUPS; kprinter - KDEPrint Handbook + KDEPrint Handbook - + KDEPrint Handbook... ...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 KDEPrint website is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt @@ -1260,7 +1260,7 @@ now. has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time. - KDEPrint + KDEPrint kprinter printcap diff --git a/doc/kcontrol/passwords/index.docbook b/doc/kcontrol/passwords/index.docbook index 3aa2ed0bc..b2be11f36 100644 --- a/doc/kcontrol/passwords/index.docbook +++ b/doc/kcontrol/passwords/index.docbook @@ -31,7 +31,7 @@ Introduction This module of the &kcontrol; gives you options for configuring the way in -which the &kdesu; program treats passwords. &kdesu; will ask you for a password +which the &tdesu; program treats passwords. &tdesu; will ask you for a password when you try to carry out some privileged actions, such as changing the date/time stored in your system clock, or adding new users on your computer. @@ -69,7 +69,7 @@ choose a time period in minutes using the spinner labeled and 1200 minutes, or use the arrows on the spinner.) If the Remember passwords option has been selected, -kdesu will not ask you for a password for the length +tdesu will not ask you for a password for the length of time specified, after you have given the password once. Keep in mind, however, that this makes your workstation less secure. diff --git a/doc/kdeprint/CMakeLists.txt b/doc/kdeprint/CMakeLists.txt index 30f7f022c..3a1f95d9e 100644 --- a/doc/kdeprint/CMakeLists.txt +++ b/doc/kdeprint/CMakeLists.txt @@ -9,4 +9,4 @@ # ################################################# -tde_create_handbook( DESTINATION kdeprint ) +tde_create_handbook( DESTINATION tdeprint ) diff --git a/doc/kdeprint/add-printer-wiz.docbook b/doc/kdeprint/add-printer-wiz.docbook index 6b6ada4ea..28d5791d2 100644 --- a/doc/kdeprint/add-printer-wiz.docbook +++ b/doc/kdeprint/add-printer-wiz.docbook @@ -20,7 +20,7 @@ your box. change a setting. -The &kdeprint; wizard introduction screen +The &tdeprint; wizard introduction screen decide which setting could be useful. -&kdeprint; wizard network scan +&tdeprint; wizard network scan -In the &kdeprint; wizard, you can enter network details +In the &tdeprint; wizard, you can enter network details directly, or you can scan the network automatically. @@ -115,14 +115,14 @@ printer with &IPP;), you have an option for scanning the network. Be careful when applying this; in some environments network scanning is considered to be hostile and harmful! -In the case of SMB, &kdeprint; will use the +In the case of SMB, &tdeprint; will use the Samba utilities nmblookup and smbclient (which need to be installed for this to work) to retrieve the information it presents in a tree structure. In the case of &IPP; (Port 631) and TCP -Network/AppSocket (Port 9100) &kdeprint; will try to open the port and, +Network/AppSocket (Port 9100) &tdeprint; will try to open the port and, if successful, send an ipp-get-printer-attribute request to the printer. For newer &HP; printers the latter usually works, because they support both AppSocket and &IPP;. @@ -137,13 +137,13 @@ timeout to use. your network, if you use the scanning technique. -&kdeprint; wizard network configuration dialog +&tdeprint; wizard network configuration dialog -In the &kdeprint; wizard, you can enter parameters to have the +In the &tdeprint; wizard, you can enter parameters to have the wizard scan parts of your network. @@ -163,7 +163,7 @@ 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 /usr/share/cups/model/. If you want your -driver to be found automatically by &CUPS; and &kdeprint;, place it in +driver to be found automatically by &CUPS; and &tdeprint;, place it in there. @@ -215,7 +215,7 @@ url="http://www.linuxprinting.org">http://www.linuxprinting.org And ask for help. At a later stage, a document detailing the differences between the different driver and &PPD; models will appear at http://kdeprint.sourceforge.net/ +url="http://tdeprint.sourceforge.net">http://tdeprint.sourceforge.net/ Watch out for this! Via the Other... button you are able to diff --git a/doc/kdeprint/cups-config.docbook b/doc/kdeprint/cups-config.docbook index 3196c9af3..304fe9514 100644 --- a/doc/kdeprint/cups-config.docbook +++ b/doc/kdeprint/cups-config.docbook @@ -15,7 +15,7 @@ configuration file for that daemon is normally located in ASCII file with a syntax similar to the configuration file of the Apache web server. It is a good idea to create a backup copy, just in case something goes wrong with the -configuration through &kdeprint;/&CUPS; Server Configuration +configuration through &tdeprint;/&CUPS; Server Configuration dialogs: cp /etc/cups/cupsd.conf /etc/cups/cupsd.conf.bak @@ -52,7 +52,7 @@ class="directory">/usr/share/doc/cups/ or always refer to the original &CUPS; documentation. &CUPS; is, much like &kde; in a rapid development process. There are constantly new features being added. New features might for times be only configurable by -directly editing the configuration files. The &kdeprint; &GUI; might not +directly editing the configuration files. The &tdeprint; &GUI; might not have caught up with &CUPS; development. Just in case you want to look at the original configuration files @@ -198,12 +198,12 @@ http://www.linuxprinting.org/newsportal/ -And finally, there will be a WebSite for &kdeprint; and related -documentation, at -http://kdeprint.sourceforge.net/ +And finally, there will be a WebSite for &tdeprint; and related +documentation, at +http://tdeprint.sourceforge.net/ In the next section I will step you through most of the -configuration options of &kdeprint; with &CUPS;. +configuration options of &tdeprint; with &CUPS;. @@ -442,7 +442,7 @@ to. By default &CUPS; will use root@hostname. Contrary to what the quickhelp suggests, it is also legal to send an email full of praise and enthusiasm about &CUPS; and -&kdeprint; to the server administrator. +&tdeprint; to the server administrator. diff --git a/doc/kdeprint/cupsoptions.docbook b/doc/kdeprint/cupsoptions.docbook index dc886d21c..bd0ba95a3 100644 --- a/doc/kdeprint/cupsoptions.docbook +++ b/doc/kdeprint/cupsoptions.docbook @@ -2,14 +2,14 @@ &CUPS; options presently not available through &kcontrol; This chapter gives you some hints about further configuration -possibilities which may not be available through the &kdeprint; &GUI; +possibilities which may not be available through the &tdeprint; &GUI; interface to &CUPS;. Overview of provided features All of the most often used features and functions &CUPS; provides -are supported in &kdeprint;. +are supported in &tdeprint;. @@ -38,13 +38,13 @@ a start. There you find a link to locally available &CUPS; documentation in HTML and PDF if you are new to &CUPS;. -&CUPS; is accessible through other means than &kdeprint;: +&CUPS; is accessible through other means than &tdeprint;: commandline and browser are two native &CUPS; interfaces. The many commandline utilities add up to the most complete control you have on &CUPS;. The web interface is only a subset of all available configuration or control options. -This is also true for &kdeprint;. Generally, as &CUPS; develops, +This is also true for &tdeprint;. Generally, as &CUPS; develops, most new features will first be implemented through the commandline. Be sure to check the latest versions of the man pages for &CUPS; to stay up-to-date with new features after you install a new version. @@ -103,7 +103,7 @@ filter (1) - cups file conversion filter interfaces -Outside &kdeprint;: Hints & Tips Tricks with &CUPS; on the +<title>Outside &tdeprint;: Hints & Tips Tricks with &CUPS; on the Commandline Here are a few examples of options that are presently only @@ -288,9 +288,9 @@ handy. -Troubleshooting &CUPS; in &kdeprint; +Troubleshooting &CUPS; in &tdeprint; -This section of the &kdeprint; Handbook will live from the +This section of the &tdeprint; Handbook will live from the readers' feedback. Here is just a small beginning. @@ -587,7 +587,7 @@ with the name lp. Maybe printers it sees on the network into a Class name lp. All jobs destined to lp are sent to this class and the first available member prints it. So if you had this nice fellow (who listened closely -when you raved about &CUPS; and &kdeprint;) install &CUPS; and poke +when you raved about &CUPS; and &tdeprint;) install &CUPS; and poke around the system...get the idea? Take my advice: choose a unique name for any network printer! diff --git a/doc/kdeprint/extensions.docbook b/doc/kdeprint/extensions.docbook index 3995272c2..c14691d51 100644 --- a/doc/kdeprint/extensions.docbook +++ b/doc/kdeprint/extensions.docbook @@ -1,5 +1,5 @@ -&kdeprint; Extensions To All Print Subsystems +&tdeprint; Extensions To All Print Subsystems <quote>Virtual</quote> Printers diff --git a/doc/kdeprint/final-word.docbook b/doc/kdeprint/final-word.docbook index ed2ae029a..175afb2f1 100644 --- a/doc/kdeprint/final-word.docbook +++ b/doc/kdeprint/final-word.docbook @@ -72,7 +72,7 @@ community. Not least within the &kde; project... ;-) Jean-Eric Cuendet for starting kups and qtcups, the predecessors of -&kdeprint; +&tdeprint; Michael Goffioul for doing all the hard work recently @@ -101,14 +101,14 @@ writing Caveats -&kdeprint; has been developed on a system using &CUPS; 1.1.6. -&kdeprint; has been tested on other versions of &CUPS; and so +&tdeprint; has been developed on a system using &CUPS; 1.1.6. +&tdeprint; has been tested on other versions of &CUPS; and so far no incompatibilities are known. By the time of writing this Handbook, &CUPS; 1.1.9 is out with a few new features -not yet supported by &kdeprint;. Of course you are able to -access these features, but you will need to bypass &kdeprint; +not yet supported by &tdeprint;. Of course you are able to +access these features, but you will need to bypass &tdeprint; and use the &CUPS; command-line tools or edit configuration -files manually. &kdeprint;'s development will go on and this +files manually. &tdeprint;'s development will go on and this Handbook strives to always be the best available user documentation resource for it. diff --git a/doc/kdeprint/getting-started.docbook b/doc/kdeprint/getting-started.docbook index cb360379f..9ef1500b7 100644 --- a/doc/kdeprint/getting-started.docbook +++ b/doc/kdeprint/getting-started.docbook @@ -1,11 +1,11 @@ Getting Started -This chapter of the &kdeprint; Handbook will walk you through most -of the configuration or selection options of &kdeprint;. It will mainly +This chapter of the &tdeprint; Handbook will walk you through most +of the configuration or selection options of &tdeprint;. It will mainly deal with &CUPS; in this version, as the author is most familiar with -it, and also because &kdeprint; started off with supporting &CUPS; -best. Later versions of the &kdeprint; software and editions of this +it, and also because &tdeprint; started off with supporting &CUPS; +best. Later versions of the &tdeprint; software and editions of this handbook will support and explore other printing systems more closely. @@ -13,7 +13,7 @@ systems more closely. Selecting Your Print Subsystem You need to define your print subsystem, before you are able to -install any printer with the &kdeprint; framework. There are two areas +install any printer with the &tdeprint; framework. There are two areas where you can define this: either in &kcontrol; (The Printing Manager section), or directly and on the fly from the print dialog. @@ -51,7 +51,7 @@ your box prior to your selection, or before it takes effect. -On it's first startup, &kdeprint; will try an autodetection. This +On it's first startup, &tdeprint; will try an autodetection. This only works for: @@ -78,13 +78,13 @@ your selection. The author's personal recommendation is subsystem will take effect for all &kde; applications. Different users may have different print subsystems in use, if those do exist on the computer and are compliant with each other. Their settings are -stored in the kdeprintrc. This file is unique to +stored in the tdeprintrc. This file is unique to every user, and is normally installed in -$HOME/.kde/share/config/kdeprintrc. +$HOME/.kde/share/config/tdeprintrc. This file is not intended to be directly editable, and all -available options can be set from the &kdeprint; &GUI;. +available options can be set from the &tdeprint; &GUI;. You may even select a different printer subsystem, on the fly, from @@ -97,7 +97,7 @@ the &kprinter; dialog box. Once you have chosen your preferred and installed print subsystem, you are ready to investigate, configure administer and work with this -system through the &kdeprint; framework. +system through the &tdeprint; framework. Navigate to K Menu Preferences System @@ -131,10 +131,10 @@ choices at your fingertips than with any other printing system. &CUPS; is new to most Linux users (even the senior hackers amongst us), and it is quite easy to use. But it is at the same time very different from other printing systems. -Therfor the &CUPS; part in the &kdeprint; Handbook is naturally +Therfor the &CUPS; part in the &tdeprint; Handbook is naturally the most detailed. -Future editions of the &kdeprint; handbook will describe in +Future editions of the &tdeprint; handbook will describe in more detail the other systems. --> 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 @@ - -&kdeprint;'s Highlights + +&tdeprint;'s Highlights -The new &kdeprint; system includes more than one highlight. +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; +the benefits that come with &tdeprint; The <quote>Add Printer</quote> Wizard -&kdeprint; has an Add Printer Wizard. The Add +&tdeprint; has an Add Printer Wizard. The Add Printer Wizard helps you with adding and configuring a new printer. Of course, you may do this manually as well. -&kdeprint; helps you discover printers. It is able +&tdeprint; helps you discover printers. It is able to scan the environment for available devices and queues. This works for network connections using TCP (AppSocket, aka &HP; -A screenshot of the &kdeprint; PrintJob Viewer shows the information +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). -A screenshot of the &kdeprint; PrintJob Viewer +A screenshot of the &tdeprint; PrintJob Viewer - + -Here's a screenshot of the &kdeprint; PrintJob Viewer. +Here's a screenshot of the &tdeprint; PrintJob Viewer. -A screenshot of the &kdeprint; PrintJob +A screenshot of the &tdeprint; PrintJob Viewer. @@ -106,7 +106,7 @@ to see this: -Here's a screenshot of the &kdeprint; PrintJob Viewer. +Here's a screenshot of the &tdeprint; PrintJob Viewer. @@ -116,7 +116,7 @@ to see this: Modules for different print subsystems -&kdeprint; uses different modules to realize the interface to the +&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: @@ -142,7 +142,7 @@ Modules for other print subsystems, such as PLP, PPR and PDQ may be available later. -&kdeprint; makes &kde; much more flexible. It gives freedom of +&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 LPD @@ -152,19 +152,19 @@ appear on the scene. - -More &kdeprint; <quote>Goodies</quote> + +More &tdeprint; <quote>Goodies</quote> Benefitting all Print SubSystems. -Some specific features of &kdeprint; depend on the chosen print +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. -Other features include benefits from &kdeprint; that are +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 special or virtual printers, and some generic @@ -183,7 +183,7 @@ displaying on screen using &kghostview;. Special Printers -Amongst these additional &kdeprint; features are a few +Amongst these additional &tdeprint; features are a few special or virtual printers: These special printers may: @@ -232,7 +232,7 @@ configurable on a per-user basis. Generic Pre-Filtering -&kdeprint; provides you with a framework to define and configure +&tdeprint; provides you with a framework to define and configure your own pre-filters. These pre-filters may take effect before they are passed to your print subsystem for further processing, but after the (&PostScript;, @@ -264,13 +264,13 @@ any one of those formats. 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 -XML because of &kdeprint;! +XML because of &tdeprint;! Multiple Pages Per Sheet Filter -This is a predefined filter that installs with &kdeprint;. It +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. @@ -280,7 +280,7 @@ paper. Enscript Text Filter -This is a predefined filter that installs with &kdeprint;. It +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. @@ -315,9 +315,9 @@ side. These can then be folded to make a pamphlet. -&CUPS; Support: the Most Important Module in &kdeprint; +&CUPS; Support: the Most Important Module in &tdeprint; -&kdeprint; contains a module for &CUPS;. &CUPS;, the +&tdeprint; contains a module for &CUPS;. &CUPS;, the Common &UNIX; Printing System (http://www.cups.org/), 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 IPP, 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. +Goffioul, the principal &tdeprint; developer. Experienced &kde; users may already be familiar with Michael's utilities qtcups and @@ -360,9 +360,9 @@ restart it. -&kdeprint; — The Heir +&tdeprint; — The Heir -The &CUPS; Module in &kdeprint; now contains all (and more) +The &CUPS; Module in &tdeprint; now contains all (and more) functions that were provided by qtcups and kups in former &kde; versions. @@ -372,7 +372,7 @@ functions that were provided by qtcups and kcmshell printers from now on. -The &kdeprint; module for &CUPS; also lets you fully administer +The &tdeprint; module for &CUPS; also lets you fully administer the print subsystem, just like kups did before. It can start, stop and configure your &CUPS; daemon. It can also start, stop, add and delete printers (&ie; printer @@ -385,7 +385,7 @@ different default setting of print options. &kprinter; — Graphical Print Command -&kdeprint;'s &CUPS; module gives you access to a graphical +&tdeprint;'s &CUPS; module gives you access to a graphical print command, like qtcups did before. @@ -469,16 +469,16 @@ for you. Read more about this in . Plans for Future Development 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 it was never so easy (not even back in the days when you had to use &Microsoft; &Windows;). - In the future, &kdeprint; will become even better. It will do a + In the future, &tdeprint; will become even better. It will do a better job of detecting 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. 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; print:/manager. -Please contact Michael Goffioul at kdeprint@swing.be +Please contact Michael Goffioul at tdeprint@swing.be with any further user or developer suggestions. diff --git a/doc/kdeprint/index.docbook b/doc/kdeprint/index.docbook index 79ef27770..977d9a6f4 100644 --- a/doc/kdeprint/index.docbook +++ b/doc/kdeprint/index.docbook @@ -20,7 +20,7 @@ - + ]> @@ -28,7 +28,7 @@ -The &kdeprint; Handbook +The &tdeprint; Handbook @@ -43,7 +43,7 @@ Michael Goffioul -
kdeprint@swing.be
+
tdeprint@swing.be
 Developer @@ -72,8 +72,8 @@ 1.00.04 -This handbook describes &kdeprint;. &kdeprint; is not a standalone -program. It is the new printing framework for &kde; 2.2. &kdeprint; +This handbook describes &tdeprint;. &tdeprint; is not a standalone +program. It is the new printing framework for &kde; 2.2. &tdeprint; is an intermediate layer between &kde; (or other) applications and the selected (and installed) print subsystem of your OS (&OS;). @@ -81,7 +81,7 @@ is an intermediate layer between &kde; (or other) applications and the selected KDE kdebase -kdeprint +tdeprint print printing CUPS @@ -93,8 +93,8 @@ is an intermediate layer between &kde; (or other) applications and the selected Introduction -This handbook describes &kdeprint;. &kdeprint; is not a standalone -program. It is the new printing framework for &kde; 2.2. &kdeprint; +This handbook describes &tdeprint;. &tdeprint; is not a standalone +program. It is the new printing framework for &kde; 2.2. &tdeprint; is an intermediate layer between &kde; (or other) applications and the selected (and installed) print subsystem of your OS (&OS;). @@ -104,7 +104,7 @@ printing system. At the time of writing, &CUPS; is the best supported printing subsystem, and it is the best documented. This handbook is a work in progress, and later versions of the -&kdeprint; software and editions of this handbook will support and +&tdeprint; software and editions of this handbook will support and explore more closely other printing systems. In the meantime, even if your printing subsystem is not yet well @@ -123,7 +123,7 @@ subsystem you use. To configure your printing subsystem from &kcontrol;, go to SystemPrinting Manager and select your subsystem. Or you can -let &kdeprint; try to determine it... +let &tdeprint; try to determine it... &CUPS; Printing Manager dialog: overview via &kcontrol; @@ -173,8 +173,8 @@ settings Credits And Licenses -&kdeprint; copyright 2001, Michael Goffioul -kdeprint@swing.be +&tdeprint; copyright 2001, Michael Goffioul +tdeprint@swing.be &underGPL; Documentation copyright 2001, Kurt Pfeifle, diff --git a/doc/kdeprint/lprng.docbook b/doc/kdeprint/lprng.docbook index 5117664e0..78db2615b 100644 --- a/doc/kdeprint/lprng.docbook +++ b/doc/kdeprint/lprng.docbook @@ -1,7 +1,7 @@ <application>LPRng</application> -An LPRng module for &kdeprint; is in +An LPRng module for &tdeprint; is in development, and hopefully available for the &kde; 2.3 release. diff --git a/doc/kdeprint/tech-overview.docbook b/doc/kdeprint/tech-overview.docbook index 96b3888e9..7a81a48a2 100644 --- a/doc/kdeprint/tech-overview.docbook +++ b/doc/kdeprint/tech-overview.docbook @@ -1,25 +1,25 @@ Technical Overview -This chapter aims to give a technical overview of &kdeprint; which +This chapter aims to give a technical overview of &tdeprint; which non-programmers can comprehend. -&kdeprint; is a new and revolutionary tool to give easy access to +&tdeprint; is a new and revolutionary tool to give easy access to printing services for both &kde; users and &kde; developers. -A Brief Description of &kdeprint; +A Brief Description of &tdeprint; -You can access the functions of &kdeprint; in different ways: +You can access the functions of &tdeprint; in different ways: through the Printing Manger in the &kcontrol;, through the kprinter command or through the dialog that pops up if you want to print. - + What it is <emphasis>not</emphasis> -&kdeprint; is not a replacement for the -printing subsystem itself. &kdeprint; does not +&tdeprint; is not a replacement for the +printing subsystem itself. &tdeprint; does not therefore give provision for spooling, and it does not do the basic processing of &PostScript; or other print data. @@ -28,15 +28,15 @@ other print data. What it <emphasis>is</emphasis> -&kdeprint; is an intermediate layer between the spooling and the +&tdeprint; is an intermediate layer between the spooling and the data processing print subsystem (as installed), and the application that -seeks to print. &kdeprint; provides a common interface for &kde; +seeks to print. &tdeprint; provides a common interface for &kde; developers and &kde; users, to various supported print subsystems. At the same time, it is customizable, and highly configurable. -&kdeprint; is easy to use for both &kde; developers and end-users. +&tdeprint; is easy to use for both &kde; developers and end-users. Developers can port their applications, with minimal changes, to use -&kdeprint; instead of the old &Qt; print system. Users +&tdeprint; instead of the old &Qt; print system. Users can easily choose and configure their print subsystem. For a reference to new &kde; users: &Qt; is the basic library and @@ -48,24 +48,24 @@ developed by TrollTech, a Norwegian software company. -&kdeprint; -- Different Usage for Different People +&tdeprint; -- Different Usage for Different People -&kdeprint; has different faces for different people. +&tdeprint; has different faces for different people. -What users and administrators can do with &kdeprint; +What users and administrators can do with &tdeprint; -&kdeprint; allows users and/or administrators, depending on their +&tdeprint; allows users and/or administrators, depending on their rights, access to printing subsystems (&CUPS;, LPD, RLPR, LPRng, PDQ &etc;) through a &kde; graphical user -interface (&GUI;). Using &kdeprint;, they can print, administer jobs, +interface (&GUI;). Using &tdeprint;, they can print, administer jobs, printers and the printing daemon, all in a comfortable manner. Experienced users will like the capability to plug any working filter for the print data between the output of their application and the input, into the chosen print subsystem. Some examples for this -already ship with plain vanilla &kdeprint;. Read +already ship with plain vanilla &tdeprint;. Read on. @@ -80,34 +80,34 @@ service was provided by the QPrinter class, a library function of the &Qt; Toolkit. The QPrinter class relied on the out-moded Line Printer Daemon (LPD). The -&kdeprint; library bases itself firmly on the more modern Common &UNIX; +&tdeprint; library bases itself firmly on the more modern Common &UNIX; Printing System (&CUPS;), while at the same time keeping backward compatibility with LPD and other legacy, or less elaborate, print systems. It also leaves the door open for any new development that might occur. -For &kde; developers to use the new &kdeprint; class in their +For &kde; developers to use the new &tdeprint; class in their applications, they require only minimal changes to their code: for every call of QPrinter, they just need to change this to KPrinter. Replacing one (!) letter in a few spots, and automatically they are done; their application can then use -all of the features of the new &kdeprint; library. +all of the features of the new &tdeprint; library. More ambitious developers, or ones with special requirements, can -do more: despite &kdeprint;'s feature-rich framework, they are still able +do more: despite &tdeprint;'s feature-rich framework, they are still able to customize the print dialog of their application by creating an additional Tab, where their -extensions to the standard &kdeprint; will feel right at home. +extensions to the standard &tdeprint; will feel right at home. This last mentioned feature has not been used widely inside -&kde; so far, as developers are not yet fully aware of &kdeprint;'s +&kde; so far, as developers are not yet fully aware of &tdeprint;'s power. Expect more of this in the near future. One example I discovered is the &kcron; application. It lets you edit the crontab through a &GUI;. The developers have implemented a printing feature that lets you (or root) choose if you want to print the whole of crontab (for all users) or -just the part that is marked. You can see the effects on &kdeprint; +just the part that is marked. You can see the effects on &tdeprint; in the following screenshots. This shot shows a sample from the &kcron; utility. @@ -127,22 +127,22 @@ cron table or just the marked part of it. The dialog to configure &kcron;'s printing options: the additional tab titled Cron Options is from inside -&kcron;, not &kdeprint;; it is a special extension added by the +&kcron;, not &tdeprint;; it is a special extension added by the &kcron; developers for printing purposes, not originating from, but -executed by &kdeprint;. Developers of other applications are free +executed by &tdeprint;. Developers of other applications are free to implement their own goodies, if they feel need for it. -&kcron;'s addition to the &kdeprint; dialog. +&kcron;'s addition to the &tdeprint; dialog. -&kcron;'s addition to the &kdeprint; dialog. +&kcron;'s addition to the &tdeprint; dialog. -&kcron;'s addition to the &kdeprint; dialog. +&kcron;'s addition to the &tdeprint; dialog. @@ -150,9 +150,9 @@ format="PNG"/> -What &kdeprint; offers to everybody... +What &tdeprint; offers to everybody... -&kdeprint;'s easy-to-use interface for all supported print subsystems +&tdeprint;'s easy-to-use interface for all supported print subsystems of course does not eliminate basic traditional weaknesses of some of those systems. But it smooths some rough edges. Different users may use different printing systems on the same box. A user is free to even @@ -169,7 +169,7 @@ working remotely over any distance (like every TCP/IP based protocol), LPD lacks bi-directional communication, authentication, access control and encryption support. -&kdeprint; can use &CUPS; to support: +&tdeprint; can use &CUPS; to support: @@ -188,14 +188,14 @@ eavesdropping, or at least make it much more difficult. -This makes &kdeprint; a much more robust and reliable solution +This makes &tdeprint; a much more robust and reliable solution than using the venerable LPD. -How to access &kdeprint; +How to access &tdeprint; -You get access to &kdeprint;, or parts of it, in four different +You get access to &tdeprint;, or parts of it, in four different ways: @@ -214,14 +214,14 @@ window: this also opens the printing dialog. fileref="kcontrol-icon.png" format="PNG"/> button, starting &kcontrol;, and then go to SystemPrinting -Manager. This opens the &kdeprint; +Manager. This opens the &tdeprint; administration which is part of the &kcontrolcenter; and also lets you switch to other parts of the &kcontrol; from a command line (&konsole; or mini-CLI) type kcmshell . -This opens just the &kdeprint; part of &kcontrol; to change your settings +This opens just the &tdeprint; part of &kcontrol; to change your settings diff --git a/doc/kdeprint/theory.docbook b/doc/kdeprint/theory.docbook index a90aa2755..7b137f1c3 100644 --- a/doc/kdeprint/theory.docbook +++ b/doc/kdeprint/theory.docbook @@ -348,7 +348,7 @@ anything other than the originally supported &OS;s: &Microsoft; &Windows; and &MacOS;. Through its brilliant move to fully support and utilize the existing &PPD; specification, &CUPS; now gives the power to use all features of modern printers to users of &Linux; and &Linux;-like -systems. &kdeprint; makes its usage even more comfortable than the +systems. &tdeprint; makes its usage even more comfortable than the &CUPS; developers ever dreamed of. &CUPS; can use original &Windows; &PPD;s, distributed by the @@ -568,7 +568,7 @@ internet and printed. &CUPS; is the most advanced implementation of &IPP; on all &OS; platforms. That makes &CUPS; a crucial ally to help "conquer the -desktop" for projects like &kde;. &kdeprint; is the best utility to +desktop" for projects like &kde;. &tdeprint; is the best utility to make &CUPS; core functionality available to &kde; Desktop users. diff --git a/doc/kdesu/CMakeLists.txt b/doc/kdesu/CMakeLists.txt index e0a216477..9c562330f 100644 --- a/doc/kdesu/CMakeLists.txt +++ b/doc/kdesu/CMakeLists.txt @@ -9,4 +9,4 @@ # ################################################# -tde_create_handbook( DESTINATION kdesu ) +tde_create_handbook( DESTINATION tdesu ) diff --git a/doc/kdesu/index.docbook b/doc/kdesu/index.docbook index 800d20b10..81c71cf17 100644 --- a/doc/kdesu/index.docbook +++ b/doc/kdesu/index.docbook @@ -1,7 +1,7 @@ + @@ -10,7 +10,7 @@ -The &kdesu; handbook +The &tdesu; handbook &Geert.Jansen; &Geert.Jansen.mail; @@ -28,7 +28,7 @@ 1.00.00 -&kdesu; is a graphical front end for the &UNIX; +&tdesu; is a graphical front end for the &UNIX; su command. @@ -43,13 +43,13 @@ Introduction -Welcome to &kdesu;! &kdesu; is a graphical front end for the +Welcome to &tdesu;! &tdesu; is a graphical front end for the &UNIX; su command for the K Desktop Environment. It allows you to run a program as different user by supplying the -password for that user. &kdesu; is an unprivileged program; it uses +password for that user. &tdesu; is an unprivileged program; it uses the system's su. -&kdesu; has one additional feature: it can remember passwords +&tdesu; has one additional feature: it can remember passwords for you. If you are using this feature, you only need to enter the password once for each command. See for more information on this and a @@ -63,13 +63,13 @@ glue instead of a pure &GUI; program. - -Using &kdesu; + +Using &tdesu; -Usage of &kdesu; is easy. The syntax is like this: +Usage of &tdesu; is easy. The syntax is like this: -kdesu +tdesu @@ -89,7 +89,7 @@ user -kdesu +tdesu &kde; Generic Options Qt Generic Options @@ -101,7 +101,7 @@ user This specifies the program to run as root. It has to be passed in one argument. So if, for example, you want to start a new file manager, you -would enter at the prompt: kdesu @@ -110,10 +110,10 @@ would enter at the prompt: kdesu -This option allow efficient use of &kdesu; in -.desktop files. It tells &kdesu; to examine the +This option allow efficient use of &tdesu; in +.desktop files. It tells &tdesu; to examine the file specified by file. If this file is -writable by the current user, &kdesu; will execute the command as the +writable by the current user, &tdesu; will execute the command as the current user. If it is not writable, the command is executed as user user (defaults to root). file is evaluated like this: if @@ -121,7 +121,7 @@ current user. If it is not writable, the command is executed as user taken as an absolute filename. Otherwise, it is taken as the name of a global &kde; configuration file. For example: to configure the K display manager, kdm, you could issue -kdesu @@ -130,7 +130,7 @@ kdmrc just the name, without any extension. For instance to run kfmclient and show the &konqueror; icon in the password dialog: -kdesu kfmclient +tdesu kfmclient @@ -155,7 +155,7 @@ password checkbox in the password dialog. -Stop the kdesu daemon. See Stop the tdesu daemon. See . @@ -166,7 +166,7 @@ standard su instead. user -While the most common use for &kdesu; is to run a command as +While the most common use for &tdesu; is to run a command as the superuser, you can supply any user name and the appropriate password. @@ -183,12 +183,12 @@ password. X authentication The program you execute will run under the root user id and will -generally have no authority to access your X display. &kdesu; gets +generally have no authority to access your X display. &tdesu; gets around this by adding an authentication cookie for your display to a temporary .Xauthority file. After the command exits, this file is removed. -If you don't use X cookies, you are on your own. &kdesu; will +If you don't use X cookies, you are on your own. &tdesu; will detect this and will not add a cookie but you will have to make sure that root is allowed to access to your display. @@ -197,18 +197,18 @@ that root is allowed to access to your display. Interface to <command>su</command> -&kdesu; uses the sytem's su for acquiring -priviliges. In this section, I explain the details of how &kdesu; does +&tdesu; uses the sytem's su for acquiring +priviliges. In this section, I explain the details of how &tdesu; does this. Because some su implementations (&ie; the one from &RedHat;) don't want to read the password from -stdin, &kdesu; creates a pty/tty pair and executes +stdin, &tdesu; creates a pty/tty pair and executes su with it's standard filedescriptors connected to the tty. To execute the command the user selected, rather than an -interactive shell, &kdesu; uses the argument with +interactive shell, &tdesu; uses the argument with su. This argument is understood by every shell that I know of so it should work portably. su passes this argument to the target user's shell, and the @@ -216,9 +216,9 @@ shell executes the program. Example command: su . Instead of executing the user command directly with -su, &kdesu; executes a little stub program called -kdesu_stub. This stub (running as the -target user), requests some information from &kdesu; over the pty/tty +su, &tdesu; executes a little stub program called +tdesu_stub. This stub (running as the +target user), requests some information from &tdesu; over the pty/tty channel (the stub's stdin and stdout) and then executes the user's program. The information passed over is: the X display, an X authentication cookie (if available), the PATH and the @@ -231,7 +231,7 @@ command line. Password Checking -&kdesu; will check the password you entered and gives an error +&tdesu; will check the password you entered and gives an error message if it is not correct. The checking is done by executing a test program: /bin/true. If this succeeds, the password is assumed to be correct. @@ -241,25 +241,25 @@ password is assumed to be correct. Password Keeping -For your comfort, &kdesu; implements a keep +For your comfort, &tdesu; implements a keep password feature. If you are interested in security, you should read this paragraph. -Allowing &kdesu; to remember passwords opens up a (small) -security hole in your system. Obviously, &kdesu; does not allow +Allowing &tdesu; to remember passwords opens up a (small) +security hole in your system. Obviously, &tdesu; does not allow anybody but your user id to use the passwords, but, if done without caution, this would lowers root's security level to that of a normal user (you). A hacker who breaks into your account, would get -root access. &kdesu; tries +root access. &tdesu; tries to prevent this. The security scheme it uses is, in my opinion at least, reasonably safe and is explained here. -&kdesu; uses a daemon, called -kdesud. The daemon listens to a &UNIX; +&tdesu; uses a daemon, called +tdesud. The daemon listens to a &UNIX; socket in /tmp for commands. The mode of the socket is 0600 so that only your user id can connect to it. If -password keeping is enabled, &kdesu; executes commands through this +password keeping is enabled, &tdesu; executes commands through this daemon. It writes the command and root's password to the socket and the daemon executes the command using su, as describe @@ -271,7 +271,7 @@ not have to supply the password. To keep hackers who broke into your account from stealing passwords from the daemon (for example, by attaching a debugger), the daemon is installed set-group-id nogroup. This should prevent all normal users (including you) from -getting passwords from the kdesud +getting passwords from the tdesud process. Also, the daemon sets the DISPLAY environment variable to the value it had when it was started. The only thing a hacker can do is execute an application on your display. @@ -292,12 +292,12 @@ yourself if you want to use it or not. Author -&kdesu; +&tdesu; Copyright 2000 &Geert.Jansen; -&kdesu; is written by &Geert.Jansen;. It is somewhat based on -Pietro Iglio's &kdesu;, version 0.3. Pietro and I agreed that I will +&tdesu; is written by &Geert.Jansen;. It is somewhat based on +Pietro Iglio's &tdesu;, version 0.3. Pietro and I agreed that I will maintain this program in the future. The author can be reached through email at &Geert.Jansen.mail;. diff --git a/doc/kdesu/man-kdesu.1.docbook b/doc/kdesu/man-kdesu.1.docbook index b9c5ac4ca..fd99812fd 100644 --- a/doc/kdesu/man-kdesu.1.docbook +++ b/doc/kdesu/man-kdesu.1.docbook @@ -12,18 +12,18 @@ -kdesu +tdesu 1 -kdesu +tdesu Runs a program with elevated privileges -kdesu +tdesu @@ -43,7 +43,7 @@ user -kdesu +tdesu KDE Generic Options Qt Generic Options @@ -51,13 +51,13 @@ user Description -&kdesu; is a graphical front end for the +&tdesu; is a graphical front end for the &UNIX; su command for the K Desktop Environment. It allows you to run a program as different user by supplying the -password for that user. &kdesu; is an unprivileged program; it uses +password for that user. &tdesu; is an unprivileged program; it uses the system's su. -&kdesu; has one additional feature: it can optionally remember passwords +&tdesu; has one additional feature: it can optionally remember passwords for you. If you are using this feature, you only need to enter the password once for each command. @@ -73,7 +73,7 @@ from .desktop files. This specifies the program to run as root. It has to be passed in one argument. So if, for example, you want to start a new file manager, you -would enter at the prompt: kdesu @@ -82,10 +82,10 @@ would enter at the prompt: kdesu -This option allow efficient use of &kdesu; in -.desktop files. It tells &kdesu; to examine the +This option allow efficient use of &tdesu; in +.desktop files. It tells &tdesu; to examine the file specified by file. If this file is -writable by the current user, &kdesu; will execute the command as the +writable by the current user, &tdesu; will execute the command as the current user. If it is not writable, the command is executed as user user (defaults to root). file is evaluated like this: if @@ -93,7 +93,7 @@ current user. If it is not writable, the command is executed as user taken as an absolute filename. Otherwise, it is taken as the name of a global &kde; configuration file. For example: to configure the K display manager, kdm, you could issue -kdesu @@ -124,9 +124,9 @@ password checkbox in the password dialog. -Stop the kdesu daemon. This is the daemon that caches +Stop the tdesu daemon. This is the daemon that caches successful passwords in the background. This feature may also be disabled with - when &kdesu; is initially run. + when &tdesu; is initially run. @@ -136,7 +136,7 @@ standard su instead. user -While the most common use for &kdesu; is to run a command as +While the most common use for &tdesu; is to run a command as the superuser, you can supply any user name and the appropriate password. @@ -151,10 +151,10 @@ password. su(1) More detailed user documentation is available from help:/kdesu +url="help:/tdesu">help:/tdesu (either enter this URL into &konqueror;, or run khelpcenter -help:/kdesu). +help:/tdesu). @@ -163,13 +163,13 @@ url="help:/kdesu">help:/kdesu Run kfmclient as user jim, and show the &konqueror; icon in the password dialog: -kdesu kfmclient +tdesu kfmclient Authors -&kdesu; was written by +&tdesu; was written by GeertJansen jansen@kde.org and PietroIglio iglio@fub.it. diff --git a/doc/kioslave/index.docbook b/doc/kioslave/index.docbook index 6f70d6e23..d76ba7d0a 100644 --- a/doc/kioslave/index.docbook +++ b/doc/kioslave/index.docbook @@ -40,7 +40,7 @@ -KDEPrint"> +KDEPrint"> FerdinandGassauer'> f.gassauer@aon.at'> diff --git a/doc/kioslave/print.docbook b/doc/kioslave/print.docbook index 034eddab1..557636aab 100644 --- a/doc/kioslave/print.docbook +++ b/doc/kioslave/print.docbook @@ -13,7 +13,7 @@ The print KIOSlave gives quick access to browse -different &kdeprint; sections via virtual folders. +different &tdeprint; sections via virtual folders. These folders provide some information about and quick access to your print subsystem. @@ -116,7 +116,7 @@ or print:printers/printer_name print:/manager or print:manager -opens a page very similar to the &kdeprint; +opens a page very similar to the &tdeprint; Manager module inside the &kde; Control Center. Switch to a different printing system here or do every other administrative task. @@ -157,9 +157,9 @@ or print:printers/printer_name the Quick Command utility (started via &Alt;F2) -You can learn more about printing and &kdeprint;'s powerful abilities -by reading the &kdeprint; Handbook -locally or at the &kdeprint; +You can learn more about printing and &tdeprint;'s powerful abilities +by reading the &tdeprint; Handbook +locally or at the &tdeprint; Website where there are documents online (HTML and PDF),containing window manager, launch &konqueror;. It should work just fine, but if it doesn't (&kde; developers don't test that case often), report it to http://bugs.kde.org and try running -kdeinit before running &konqueror;; it usually +tdeinit before running &konqueror;; it usually helps. diff --git a/doc/konqueror/filemanager.docbook b/doc/konqueror/filemanager.docbook index c6fb880ba..b63fbfbb7 100644 --- a/doc/konqueror/filemanager.docbook +++ b/doc/konqueror/filemanager.docbook @@ -862,7 +862,7 @@ easier. ToolsExecute Shell Command... (&Ctrl; E) opens a small command line dialog window where -you can enter a shell command such as ps -ax | grep kdeinit +you can enter a shell command such as ps -ax | grep tdeinit . Note that it does not support full featured terminal control characters, so applications such as top and less will not work properly, but it is available immediately diff --git a/doc/userguide/base-kde-applications.docbook b/doc/userguide/base-kde-applications.docbook index 863271b37..917855c69 100644 --- a/doc/userguide/base-kde-applications.docbook +++ b/doc/userguide/base-kde-applications.docbook @@ -128,7 +128,7 @@ - + @@ -229,7 +229,7 @@ Related Information - See http://kontact.kde.org and http://kdepim.kde.org for more information. + See http://kontact.kde.org and http://tdepim.kde.org for more information. &kontact; Handbook diff --git a/doc/userguide/kde-as-root.docbook b/doc/userguide/kde-as-root.docbook index 7e6bb6fe9..c97f2e5f5 100644 --- a/doc/userguide/kde-as-root.docbook +++ b/doc/userguide/kde-as-root.docbook @@ -19,14 +19,14 @@ Some &Linux; distributions have tried to stress this point so much that they have disabled the root account altogether, and instead use the sudo model. Nevertheless, the basic security model in sudo is the same as su, and thus they share the same security strengths and weaknesses, essentially. -If you should ever need to run a program with Super User privileges, then it is always recommend that you use &kdesu;. From &konsole; or from hitting &Alt;F2, enter kdesu application, and the application will be run with the appropriate Super User privileges. +If you should ever need to run a program with Super User privileges, then it is always recommend that you use &tdesu;. From &konsole; or from hitting &Alt;F2, enter tdesu application, and the application will be run with the appropriate Super User privileges. -Even if you have set up your system to use sudo, or you are on a distribution that uses sudo, such as &kubuntu;, you should still use &kdesu;. The program will be appropriately modified by the developers to use the correct settings. You should not, however, ever use sudo application to run an application with root permissions; it can derange permissions of certain configuration files for a program. Running a graphical applications as root in general is not a good idea, but using &kdesu; will always be your safest bet with it. +Even if you have set up your system to use sudo, or you are on a distribution that uses sudo, such as &kubuntu;, you should still use &tdesu;. The program will be appropriately modified by the developers to use the correct settings. You should not, however, ever use sudo application to run an application with root permissions; it can derange permissions of certain configuration files for a program. Running a graphical applications as root in general is not a good idea, but using &tdesu; will always be your safest bet with it. Related Information -&kdesu; Handbook +&tdesu; Handbook diff --git a/doc/userguide/kde-for-admins.docbook b/doc/userguide/kde-for-admins.docbook index f5d98e019..6424ea965 100644 --- a/doc/userguide/kde-for-admins.docbook +++ b/doc/userguide/kde-for-admins.docbook @@ -833,22 +833,22 @@ are two very important lines in the startkde script: -LD_BIND_NOW=true kdeinit +kcminit +knotify and kwrapper +LD_BIND_NOW=true tdeinit +kcminit +knotify and kwrapper ksmserver $KDEWM -The first line starts the kdeinit master process. -The kdeinit master process is used to start all other +The first line starts the tdeinit master process. +The tdeinit master process is used to start all other &kde; processes. It show up in the output of ps - as kdeinit: -Running.... The arguments after kdeinit + as tdeinit: +Running.... The arguments after tdeinit are the names of additional processes to be started. The + -indicates that kdeinit needs to wait till the process has -finished. kdeinit also starts +indicates that tdeinit needs to wait till the process has +finished. tdeinit also starts dcopserver, klauncher and kded. -The second of the two lines asks kdeinit to start +The second of the two lines asks tdeinit to start the ksmserver session manager process. The session manager determines the lifetime of the session. When this process exits, the user is logged out. @@ -910,18 +910,18 @@ needed - -<command>kdeinit</command> -kdeinit is used to start all other &kde; -programs. kdeinit can start normal binary program files -as well as kdeinit loadable modules + +<command>tdeinit</command> +tdeinit is used to start all other &kde; +programs. tdeinit can start normal binary program files +as well as tdeinit loadable modules (KLMs). KLMs work just like binary program files but can be started more efficiently. KLMs live in $KDEDIR/lib/trinity The drawback is that programs started this way appear as -kdeinit in the output of +tdeinit in the output of top and ps. Use top or ps to see the actual program name: @@ -929,20 +929,20 @@ to see the actual program name: %ps -waba 23184 0.2 2.1 23428 11124 ? S 21:41 0:00 kdeinit: Running... -waba 23187 0.1 2.1 23200 11124 ? S 21:41 0:00 kdeinit: dcopserver --nosid -waba 23189 0.2 2.4 25136 12496 ? S 21:41 0:00 kdeinit: klauncher -waba 23192 0.7 2.8 25596 14772 ? S 21:41 0:00 kdeinit: kded -waba 23203 0.8 3.4 31516 17892 ? S 21:41 0:00 kdeinit: +waba 23184 0.2 2.1 23428 11124 ? S 21:41 0:00 tdeinit: Running... +waba 23187 0.1 2.1 23200 11124 ? S 21:41 0:00 tdeinit: dcopserver --nosid +waba 23189 0.2 2.4 25136 12496 ? S 21:41 0:00 tdeinit: klauncher +waba 23192 0.7 2.8 25596 14772 ? S 21:41 0:00 tdeinit: kded +waba 23203 0.8 3.4 31516 17892 ? S 21:41 0:00 tdeinit: knotify -kdeinit: Running... indicates the -master kdeinit process. The other processes listed are +tdeinit: Running... indicates the +master tdeinit process. The other processes listed are programs started as KLMs. -When kdeinit starts for the first time it will +When tdeinit starts for the first time it will launch dcopserver, klauncher, and kded, as well as any additional programs specified on its command line in the startkde script, normally @@ -1019,7 +1019,7 @@ startup problems. klauncher is a daemon which is responsible for service activation within &kde;. It operates in close connection with the -kdeinit master process to start new processes. &kde; +tdeinit master process to start new processes. &kde; applications communicate with klauncher over &DCOP; in order to start new applications or services. @@ -1029,7 +1029,7 @@ either indicates a serious problem with the dcopserver or that klauncher crashed. klauncher can be restarted by restarting -kdeinit from a console window. Make sure that +tdeinit from a console window. Make sure that $HOME, $DISPLAY and the various $KDEDIR(S) are set correctly when doing so! @@ -1205,7 +1205,7 @@ on a multi-head system. (Since &kde; 3.2.3) Set this variable to spawn KIO-slaves directly from the application process itself. By default KIO-slaves are spawned using -klauncher/kdeinit. This option is +klauncher/tdeinit. This option is useful if the KIO-slave should run in the same environment as the application. This can be the case with Clearcase. @@ -1228,7 +1228,7 @@ lookups. $KDE_IS_PRELINKED (Since &kde; 3.2) - Set this variable to indicate that you have prelinked your &kde; binaries and libraries. This will turn off -kdeinit. +tdeinit. @@ -1243,7 +1243,7 @@ locale. (Since &kde; 3.2) Automatically set to true by &kde; startup, it is used by ⪚ &konqueror; to know if it should consider remaining in memory for future re-use when being closed. If not set, &konqueror; will exit -after being closed (⪚ &kdesu; does that, it's also useful for +after being closed (⪚ &tdesu; does that, it's also useful for debugging). @@ -1314,21 +1314,21 @@ $KDEDIRS and profiles as well. Used by - -The kdeinit Mystery + +The tdeinit Mystery -kdeinit is used to start all other &kde; -programs. kdeinit can start normal binary program f iles -as well as kdeinit loadable modules +tdeinit is used to start all other &kde; +programs. tdeinit can start normal binary program f iles +as well as tdeinit loadable modules (KLMs). KLMs work just like binary program files but can be started more efficiently. KLMs live in $KDEDIR/lib/trinity The drawback is that programs started this way appear as -kdeinit in the +tdeinit in the output of top and ps. Use top or ps to see the actual program name: @@ -1336,14 +1336,14 @@ output of top and ps. Use % ps aux | grep bastian -bastian 26061 0.0 2.2 24284 11492 ? S 21:27 0:00 kdeinit: Running... -bastian 26064 0.0 2.2 24036 11524 ? S 21:27 0:00 kdeinit: dcopserver -bastian 26066 0.1 2.5 26056 12988 ? S 21:27 0:00 kdeinit: klauncher -bastian 26069 0.4 3.2 27356 16744 ? S 21:27 0:00 kdeinit: kded -bastian 26161 0.2 2.7 25344 14096 ? S 21:27 0:00 kdeinit: ksmserver -bastian 26179 1.1 3.4 29716 17812 ? S 21:27 0:00 kdeinit: kicker -bastian 26192 0.4 3.0 26776 15452 ? S 21:27 0:00 kdeinit: klipper -bastian 26195 1.0 3.5 29200 18368 ? S 21:27 0:00 kdeinit: kdesktop +bastian 26061 0.0 2.2 24284 11492 ? S 21:27 0:00 tdeinit: Running... +bastian 26064 0.0 2.2 24036 11524 ? S 21:27 0:00 tdeinit: dcopserver +bastian 26066 0.1 2.5 26056 12988 ? S 21:27 0:00 tdeinit: klauncher +bastian 26069 0.4 3.2 27356 16744 ? S 21:27 0:00 tdeinit: kded +bastian 26161 0.2 2.7 25344 14096 ? S 21:27 0:00 tdeinit: ksmserver +bastian 26179 1.1 3.4 29716 17812 ? S 21:27 0:00 tdeinit: kicker +bastian 26192 0.4 3.0 26776 15452 ? S 21:27 0:00 tdeinit: klipper +bastian 26195 1.0 3.5 29200 18368 ? S 21:27 0:00 tdeinit: kdesktop As you might have noticed, this has another side effect, making it @@ -1353,7 +1353,7 @@ difficult to kill a process that is causing trouble: kdesktop: no process killed You might be tempted to try killall -kdeinit, but killing all kdeinit processes will have +tdeinit, but killing all tdeinit processes will have the effect of shutting down all of &kde;. In effect, total destruction! diff --git a/doc/userguide/konsole-intro.docbook b/doc/userguide/konsole-intro.docbook index d42b4f59a..ec168ac22 100644 --- a/doc/userguide/konsole-intro.docbook +++ b/doc/userguide/konsole-intro.docbook @@ -81,8 +81,8 @@ action="simul">&Ctrl;&Alt;S and enter the new name. If you find the need to run any &kde; program with root privileges, you can use the &kdesu; command with the switch -from the command line like this: kdesu +class="username">root privileges, you can use the &tdesu; command with the switch +from the command line like this: tdesu , using the switch will prevent &kde; from remembering your passwords. -- cgit v1.2.3