| Summary: | Typos in two kdebase docs, | ||
|---|---|---|---|
| Product: | [Websites] docs.kde.org | Reporter: | Natalie <nat> |
| Component: | general | Assignee: | Documentation Editorial Team <kde-doc-english> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Natalie
2006-11-23 19:58:00 UTC
SVN commit 607355 by annma: Thanks for your report! CCBUG=137785 M +24 -24 index.docbook --- branches/KDE/3.5/kdebase/doc/kompmgr/index.docbook #607354:607355 @@ -33,7 +33,7 @@ <para>&kappname; is a composite rendering engine to be used by &kwin;.</para> <para>This document is rather a general explanation of what it does, how it works and what the restrictions are than a documentation how to use -it (as it works in the background automatically)</para> +it (as it works in the background automatically).</para> </abstract> <keywordset> @@ -46,9 +46,9 @@ <chapter id="introduction"> <title>Introduction</title> -<para>&kappname; bases upon <application>xcompmgr</application>, Keith +<para>&kappname; is based upon <application>xcompmgr</application>, Keith Packards reference composing implementation for the use of the new X -features</para> +features.</para> <para>A composite manager catches the output of the X windows and renders them into a single picture that will be displayed on the screen. The advantage @@ -102,7 +102,7 @@ <title>Settings</title> <para>This chapter describes which parameters you can tweak, how they will -result visually and their performance impact</para> +result visually and their performance impact.</para> <sect1 id="translucency"> <title>Translucency</title> @@ -122,11 +122,10 @@ <variablelist> <varlistentry> <term><guilabel>Active windows</guilabel></term> -<listitem><para>It is suggested you deactivate active window -translucency for the active window. The main reason is for perfomance, -and secondly because to scan the content of a translucent window means your -brain has to strip the irritating throughshining information, which is -tiring.</para> +<listitem><para>It is suggested you deactivate translucency for the active +window. The main reason is for perfomance, and secondly because to scan the +content of a translucent window means your brain has to strip the irritating +throughshining information, which is tiring.</para> </listitem> </varlistentry> <varlistentry> @@ -136,7 +135,7 @@ value, you may have trouble to find an inactive window. If you choose very low values (< 20%) you may not be able to distinguish windows in their stack order - so you may accidently click the -<guibutton>Ok</guibutton> button of a dialog when you just wanted to +<guibutton>OK</guibutton> button of a dialog when you just wanted to activate a window. Optimal values are between 60% and 80%.</para> </listitem> @@ -172,7 +171,7 @@ using a composite manager. This may change in the future.</para> <para>On the other side, most gtk 1.x applications (⪚ <application>xmms</application>) set such an alpha mask, resulting in -almost unusable windows (as long as the sublying windows isn't black), so +almost unusable windows (as long as the sublying windows are not black), so you can disable the support for ARGB windows here to make use of gtk applications. There will hopefully be a patch for gtk in the near future to fix this.</para> @@ -184,7 +183,7 @@ <sect1 id="shadows"> <title>Shadows</title> <para>Why should anyone want his windows to throw shadows? Well, maybe just -it looks cute, or because it allows a better window separation, +because it looks cute, or because it allows a better window separation, or... because it looks cute!</para> <variablelist> <varlistentry> @@ -197,11 +196,11 @@ <term><guilabel>Active window size</guilabel></term> <term><guilabel>Inactive window size</guilabel></term> <term><guilabel>Dock window size</guilabel></term> -<listitem><para>You amy select different shadow sizes for different window +<listitem><para>You may select different shadow sizes for different window states/types. The values are not absolute, but will apply to your screen resolution.</para> <para>In principle, you can set every value you want (if you edit the config -file with a atext editor, far beyond the offered <quote>32</quote>), but +file with a text editor, far beyond the offered <quote>32</quote>), but bigger shadows cost more cpu/gpu power.</para> </listitem> </varlistentry> @@ -210,7 +209,7 @@ <term><guilabel>Horizontal offset</guilabel></term> <listitem><para>By default, the window would throw a <quote>all around equal</quote> shadow, implying a frontal light source. Users familiar with -&MacOS; users may like a vertical offset, &Windows; users may prefer a +&MacOS; may like a vertical offset, &Windows; users may prefer a slighter offset to the southeast. Experiment with the values until you are happy.</para> </listitem> @@ -226,7 +225,7 @@ <varlistentry> <term><guilabel>Remove shadows on move</guilabel></term> <listitem><para>Check this if you need more performance (especially when -using translucent moving windows)</para> +using translucent moving windows).</para> </listitem> </varlistentry> <varlistentry> @@ -257,7 +256,7 @@ <varlistentry> <term><guilabel>Fade-in speed</guilabel></term> <term><guilabel>Fade-out speed</guilabel></term> -<listitem><para>For the usability reasons mentioned under <guilabel>Fade in +<listitem><para>For the usability reasons mentioned under <guilabel>Fade-in windows</guilabel>, it is most practical to use a fast fade in speed and (for more eye candy) a slow fade out speed. This will provide you nice effects and a smooth feeling system as well as low latency before @@ -319,19 +318,20 @@ (⪚ from 1280x1024 to 1024x768).</para> <para>Please notice that the currently limiting factor for the Composite -extension seems to be the CPU cache size</para> +extension seems to be the CPU cache size.</para> </answer> </qandaentry> <qandaentry> <question> -<para>After enabling the Composite extension, i cannot run any -<acronym>GLX</acronym> applications anymore. I've got an <trademark>NVIDIA</trademark> card</para> +<para>After enabling the Composite extension, I cannot run any +<acronym>GLX</acronym> applications anymore. I've got an +<trademark>NVIDIA</trademark> card.</para> </question> <answer> -<para>For some problems, <trademark>NVIDIA</trademark> deactivated the GLX -support when Coposite is active. Reactivating is possible, but may cause +<para>To prevent some problems, <trademark>NVIDIA</trademark> deactivated the +GLX support when Coposite is active. Reactivating is possible, but may cause problems on some kernel/driver/GPU combinations.</para> <programlisting> Section "Device" @@ -399,8 +399,8 @@ mode, where the video content is written directly into the video card memory, bypassing X. Therefore the window seems to be static (colored background) and is not updated by the damage extension.</para> -<para> There will hopefully be a fix for this in the future. Currently i had -best results using <application>Xine</application> but displaying +<para> There will hopefully be a fix for this in the future. Currently I had +the best results using <application>Xine</application> but displaying translucent videos isn't fast anyway.</para> </answer> </qandaentry> SVN commit 607356 by annma: forward port of 607355 BUG=137785 M +24 -24 index.docbook --- trunk/KDE/kdebase/doc/kompmgr/index.docbook #607355:607356 @@ -33,7 +33,7 @@ <para>&kappname; is a composite rendering engine to be used by &kwin;.</para> <para>This document is rather a general explanation of what it does, how it works and what the restrictions are than a documentation how to use -it (as it works in the background automatically)</para> +it (as it works in the background automatically).</para> </abstract> <keywordset> @@ -46,9 +46,9 @@ <chapter id="introduction"> <title>Introduction</title> -<para>&kappname; bases upon <application>xcompmgr</application>, Keith +<para>&kappname; is based upon <application>xcompmgr</application>, Keith Packards reference composing implementation for the use of the new X -features</para> +features.</para> <para>A composite manager catches the output of the X windows and renders them into a single picture that will be displayed on the screen. The advantage @@ -102,7 +102,7 @@ <title>Settings</title> <para>This chapter describes which parameters you can tweak, how they will -result visually and their performance impact</para> +result visually and their performance impact.</para> <sect1 id="translucency"> <title>Translucency</title> @@ -122,11 +122,10 @@ <variablelist> <varlistentry> <term><guilabel>Active windows</guilabel></term> -<listitem><para>It is suggested you deactivate active window -translucency for the active window. The main reason is for perfomance, -and secondly because to scan the content of a translucent window means your -brain has to strip the irritating throughshining information, which is -tiring.</para> +<listitem><para>It is suggested you deactivate translucency for the active +window. The main reason is for perfomance, and secondly because to scan the +content of a translucent window means your brain has to strip the irritating +throughshining information, which is tiring.</para> </listitem> </varlistentry> <varlistentry> @@ -136,7 +135,7 @@ value, you may have trouble to find an inactive window. If you choose very low values (< 20%) you may not be able to distinguish windows in their stack order - so you may accidently click the -<guibutton>Ok</guibutton> button of a dialog when you just wanted to +<guibutton>OK</guibutton> button of a dialog when you just wanted to activate a window. Optimal values are between 60% and 80%.</para> </listitem> @@ -172,7 +171,7 @@ using a composite manager. This may change in the future.</para> <para>On the other side, most gtk 1.x applications (⪚ <application>xmms</application>) set such an alpha mask, resulting in -almost unusable windows (as long as the sublying windows isn't black), so +almost unusable windows (as long as the sublying windows are not black), so you can disable the support for ARGB windows here to make use of gtk applications. There will hopefully be a patch for gtk in the near future to fix this.</para> @@ -184,7 +183,7 @@ <sect1 id="shadows"> <title>Shadows</title> <para>Why should anyone want his windows to throw shadows? Well, maybe just -it looks cute, or because it allows a better window separation, +because it looks cute, or because it allows a better window separation, or... because it looks cute!</para> <variablelist> <varlistentry> @@ -197,11 +196,11 @@ <term><guilabel>Active window size</guilabel></term> <term><guilabel>Inactive window size</guilabel></term> <term><guilabel>Dock window size</guilabel></term> -<listitem><para>You amy select different shadow sizes for different window +<listitem><para>You may select different shadow sizes for different window states/types. The values are not absolute, but will apply to your screen resolution.</para> <para>In principle, you can set every value you want (if you edit the config -file with a atext editor, far beyond the offered <quote>32</quote>), but +file with a text editor, far beyond the offered <quote>32</quote>), but bigger shadows cost more cpu/gpu power.</para> </listitem> </varlistentry> @@ -210,7 +209,7 @@ <term><guilabel>Horizontal offset</guilabel></term> <listitem><para>By default, the window would throw a <quote>all around equal</quote> shadow, implying a frontal light source. Users familiar with -&MacOS; users may like a vertical offset, &Windows; users may prefer a +&MacOS; may like a vertical offset, &Windows; users may prefer a slighter offset to the southeast. Experiment with the values until you are happy.</para> </listitem> @@ -226,7 +225,7 @@ <varlistentry> <term><guilabel>Remove shadows on move</guilabel></term> <listitem><para>Check this if you need more performance (especially when -using translucent moving windows)</para> +using translucent moving windows).</para> </listitem> </varlistentry> <varlistentry> @@ -257,7 +256,7 @@ <varlistentry> <term><guilabel>Fade-in speed</guilabel></term> <term><guilabel>Fade-out speed</guilabel></term> -<listitem><para>For the usability reasons mentioned under <guilabel>Fade in +<listitem><para>For the usability reasons mentioned under <guilabel>Fade-in windows</guilabel>, it is most practical to use a fast fade in speed and (for more eye candy) a slow fade out speed. This will provide you nice effects and a smooth feeling system as well as low latency before @@ -319,19 +318,20 @@ (⪚ from 1280x1024 to 1024x768).</para> <para>Please notice that the currently limiting factor for the Composite -extension seems to be the CPU cache size</para> +extension seems to be the CPU cache size.</para> </answer> </qandaentry> <qandaentry> <question> -<para>After enabling the Composite extension, i cannot run any -<acronym>GLX</acronym> applications anymore. I've got an <trademark>NVIDIA</trademark> card</para> +<para>After enabling the Composite extension, I cannot run any +<acronym>GLX</acronym> applications anymore. I've got an +<trademark>NVIDIA</trademark> card.</para> </question> <answer> -<para>For some problems, <trademark>NVIDIA</trademark> deactivated the GLX -support when Coposite is active. Reactivating is possible, but may cause +<para>To prevent some problems, <trademark>NVIDIA</trademark> deactivated the +GLX support when Coposite is active. Reactivating is possible, but may cause problems on some kernel/driver/GPU combinations.</para> <programlisting> Section "Device" @@ -399,8 +399,8 @@ mode, where the video content is written directly into the video card memory, bypassing X. Therefore the window seems to be static (colored background) and is not updated by the damage extension.</para> -<para> There will hopefully be a fix for this in the future. Currently i had -best results using <application>Xine</application> but displaying +<para> There will hopefully be a fix for this in the future. Currently I had +the best results using <application>Xine</application> but displaying translucent videos isn't fast anyway.</para> </answer> </qandaentry> SVN commit 607358 by annma:
forward port
CCBUG=137785
M +50 -23 index.docbook
AM screenshot1.png
--- trunk/KDE/kdebase/doc/knetattach/index.docbook #607357:607358
@@ -1,5 +1,6 @@
<?xml version="1.0" ?>
-<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+"dtd/kdex.dtd" [
<!-- Define an entity for your application if it is not part of KDE
CVS -->
<!ENTITY kappname "&knetattach;">
@@ -65,7 +66,7 @@
The &knetattach; program, affectionately and hereafter known as the
Network Folder Wizard, allows easy addition and integration of various
network folders with your &kde; desktop. Please report any problems or
-feature requests for it to the &kde; mailing lists.
+feature requests for it to the &kde; bugs website.
</para>
</chapter>
@@ -73,10 +74,12 @@
<title>Using &knetattach;</title>
<para>
-As you will see in the screenshot below, the Network Folder Wizard currently allows
+As you will see in the screenshot below, the Network Folder Wizard currently
+allows
you to add four types of network folders: WebDav, FTP,
<trademark class="registered">Microsoft</trademark>
-<trademark class="registered">Windows</trademark> (Samba) network drives and SSH.
+<trademark class="registered">Windows</trademark> (Samba) network drives and
+SSH.
<screenshot>
<screeninfo>Here's a screenshot of &knetattach;</screeninfo>
@@ -99,22 +102,40 @@
<title>Adding network folders</title>
<para>
-Network folders show up in a special location of konqueror called a <emphasis>virtual folder</emphasis>.
-This virtual folder is accessed by typing <userinput>remote:/</userinput> in the
-<interface>Location bar</interface>. You will then be able to see any folders which have been
-previously added or use the wizard to add new ones.
+Network folders show up in a special location of &konqueror; called a
+<emphasis>virtual folder</emphasis>.
+This virtual folder is accessed by typing <userinput>remote:/</userinput> in
+&konqueror; <interface>Location bar</interface>. You will then be able to see
+any folders which have been previously added and you also will be able to use
+the wizard to add new ones.
+<screenshot>
+<screeninfo>Here's a screenshot of &knetattach;</screeninfo>
+<mediaobject>
+<imageobject>
+<imagedata fileref="screenshot1.png" format="PNG"/>
+</imageobject>
+<textobject>
+<phrase>Screenshot</phrase>
+</textobject>
+<caption>
+<para>The virtual folder with the Network Folder wizard</para>
+</caption>
+</mediaobject>
+</screenshot>
</para>
+
<para>
-Speaking of wizards, the Network Folder Wizard aims at being very easy to use. Don't worry if
-you are having some problems though, that's what we're here for. :-)
-After opening the wizard you must choose the type of network folder you would like to
-access. When you move on to the next screen you will just need to
-fill in the requested information and the worst will be over. The final step is entering your
-username and login password for the network share you've chosen to access.
+Speaking of wizards, the Network Folder Wizard aims at being very easy to use.
+After opening the wizard you must choose the type of network folder you would
+like to access. When you move on to the next screen you will just need to
+fill in the requested information. The final step is entering your username and
+login password for the network share you've chosen to access.
</para>
<para>
-Below is a list of the information needed by the wizard to create the network folders. If an option is not
-available for a particular folder it does not have to be entered. e.g. The Samba folders do not require a <guilabel>Port</guilabel> entry.
+Below is a list of the information needed by the wizard to create the network
+folders. If an option is not
+available for a particular folder it does not have to be entered. e.g. The Samba
+folders do not require a <guilabel>Port</guilabel> entry.
</para>
<para>
@@ -129,7 +150,7 @@
</listitem>
</varlistentry>
<varlistentry>
-<term>Server</term>
+<term>Server:</term>
<listitem>
<para>
This is the address of the server you are attempting to add. It can be an
@@ -169,8 +190,10 @@
but it will not be accessible from remote:/.
<note>
<para>
-The <guilabel>Recent connection:</guilabel> option allows you to re-connect to the
-last network mount point you connected to using the wizard whether an icon is created or not.
+The <guilabel>Recent connection:</guilabel> option allows you to re-connect to
+the
+last network mount point you connected to using the wizard whether an icon is
+created or not.
</para>
</note>
</para>
@@ -226,14 +249,16 @@
<para>
OK, so we (as in me) have chosen to add an FTP folder. Below you see
an example of the type of information you will need to add for your particular
-FTP server. After filling it in we press <guibutton>Save & Copy</guibutton>
+FTP server. After filling it in we press <guibutton>Save &
+Connect</guibutton>
and wait for the magic. Oh yes, if your server requires validation of some kind
you will be prompted at this point before being allowed to connect.
</para>
<para>
<screenshot>
-<screeninfo>Screenshot showing addition of FTP Folder &knetattach;</screeninfo>
+<screeninfo>Screenshot showing addition of FTP Folder
+using &knetattach;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot2.png" format="PNG"/>
@@ -264,13 +289,15 @@
</para>
<para>
-To get back to our network folders all that is necessary is typing <action>remote:/</action>
+To get back to our network folders all that is necessary is typing
+<action>remote:/</action>
in the <guilabel>Location:</guilabel> bar of &konqueror;.
</para>
<para>
<screenshot>
-<screeninfo>Screenshot of the remote:/ virtual folder</screeninfo>
+<screeninfo>Screenshot of the remote:/ virtual folder with the
+added connection</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot4.png" format="PNG"/>
** trunk/KDE/kdebase/doc/knetattach/screenshot1.png #property svn:mime-type
+ image/png
SVN commit 607357 by annma: Part of 137785 fix as well CCBUG=137785 M +36 -16 index.docbook M screenshot.png AM screenshot1.png M screenshot2.png M screenshot3.png M screenshot4.png --- branches/KDE/3.5/kdebase/doc/knetattach/index.docbook #607356:607357 @@ -65,7 +65,7 @@ The &knetattach; program, affectionately and hereafter known as the Network Folder Wizard, allows easy addition and integration of various network folders with your &kde; desktop. Please report any problems or -feature requests for it to the &kde; mailing lists. +feature requests for it to the &kde; bugs website. </para> </chapter> @@ -99,22 +99,39 @@ <title>Adding network folders</title> <para> -Network folders show up in a special location of konqueror called a <emphasis>virtual folder</emphasis>. -This virtual folder is accessed by typing <userinput>remote:/</userinput> in the -<interface>Location bar</interface>. You will then be able to see any folders which have been -previously added or use the wizard to add new ones. +Network folders show up in a special location of &konqueror; called a +<emphasis>virtual folder</emphasis>. +This virtual folder is accessed by typing <userinput>remote:/</userinput> in +&konqueror; <interface>Location bar</interface>. You will then be able to see +any folders which have been previously added and you also will be able to use +the wizard to add new ones. +<screenshot> +<screeninfo>Here's a screenshot of &knetattach;</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="screenshot1.png" format="PNG"/> +</imageobject> +<textobject> +<phrase>Screenshot</phrase> +</textobject> +<caption> +<para>The virtual folder with the Network Folder wizard</para> +</caption> +</mediaobject> +</screenshot> </para> + <para> -Speaking of wizards, the Network Folder Wizard aims at being very easy to use. Don't worry if -you are having some problems though, that's what we're here for. :-) -After opening the wizard you must choose the type of network folder you would like to -access. When you move on to the next screen you will just need to -fill in the requested information and the worst will be over. The final step is entering your -username and login password for the network share you've chosen to access. +Speaking of wizards, the Network Folder Wizard aims at being very easy to use. +After opening the wizard you must choose the type of network folder you would +like to access. When you move on to the next screen you will just need to +fill in the requested information. The final step is entering your username and +login password for the network share you've chosen to access. </para> <para> Below is a list of the information needed by the wizard to create the network folders. If an option is not -available for a particular folder it does not have to be entered. e.g. The Samba folders do not require a <guilabel>Port</guilabel> entry. +available for a particular folder it does not have to be entered. e.g. The Samba +folders do not require a <guilabel>Port</guilabel> entry. </para> <para> @@ -129,7 +146,7 @@ </listitem> </varlistentry> <varlistentry> -<term>Server</term> +<term>Server:</term> <listitem> <para> This is the address of the server you are attempting to add. It can be an @@ -226,14 +243,16 @@ <para> OK, so we (as in me) have chosen to add an FTP folder. Below you see an example of the type of information you will need to add for your particular -FTP server. After filling it in we press <guibutton>Save & Copy</guibutton> +FTP server. After filling it in we press <guibutton>Save & +Connect</guibutton> and wait for the magic. Oh yes, if your server requires validation of some kind you will be prompted at this point before being allowed to connect. </para> <para> <screenshot> -<screeninfo>Screenshot showing addition of FTP Folder &knetattach;</screeninfo> +<screeninfo>Screenshot showing addition of FTP Folder +using &knetattach;</screeninfo> <mediaobject> <imageobject> <imagedata fileref="screenshot2.png" format="PNG"/> @@ -270,7 +289,8 @@ <para> <screenshot> -<screeninfo>Screenshot of the remote:/ virtual folder</screeninfo> +<screeninfo>Screenshot of the remote:/ virtual folder with the +added connection</screeninfo> <mediaobject> <imageobject> <imagedata fileref="screenshot4.png" format="PNG"/> ** branches/KDE/3.5/kdebase/doc/knetattach/screenshot1.png #property svn:mime-type + image/png |