[kde-doc-english] [Bug 137785] Typos in two kdebase docs,
Anne-Marie Mahfouf
annma at kde.org
Fri Nov 24 10:38:45 CET 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=137785
annma kde org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From annma kde org 2006-11-24 10:38 -------
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>
More information about the kde-doc-english
mailing list