# HG changeset patch
# User gpoirier
# Date 1120636601 0
# Node ID 154b64188f8eb1466fa2c121046c174b22282210
# Parent  ad2a3e29c0d1cf3a426de6306ce7ad0fe77ca06e
Few fixes and suggestions by Jeff and Diego

diff -r ad2a3e29c0d1 -r 154b64188f8e DOCS/xml/en/mencoder.xml
--- a/DOCS/xml/en/mencoder.xml	Tue Jul 05 22:11:23 2005 +0000
+++ b/DOCS/xml/en/mencoder.xml	Wed Jul 06 07:56:41 2005 +0000
@@ -2726,25 +2726,27 @@
     The quality of the encode yielded by this option highly depends
     on personal preferences and on the type and monitor settings
     used to watch it (typically, it will not look as good if it is
-    bright or if it is a TFT monitor.
+    bright or if it is a TFT monitor).
 </para></listitem>
 
 <listitem><para>
   <emphasis role="bold">qpel</emphasis>
-    Increases the precision of the motion estimation from halfpel to
+    Raise the number of candidate motion vectors's by increasing
+    the precision of the motion estimation from halfpel to
     quarterpel.
     The idea is to find better motion vectors which will in return
     reduce bitrate (hence increasing quality).
-    However, quarterpel precision motion vectors are coded in the
-    bitstream with a few bits, so if the content do not feature
-    enough possibilities to find better motion vectors through
-    <option>qpel</option>, it will in fact hurt compressibility.
+    However, motion vectors with quarterpel precision require a
+    few extra bits to code, but the candidate vectors do not always
+    give (much) better results.
+    Quite often, the codec still spends bits on the extra precision,
+    but little or no extra quality is gained in return.
     Unfortunately, there is no way to foresee the possible gains of
     <option>qpel</option>, so you need to actually encode with and
     without it to know for sure.
   </para><para>
     <option>qpel</option> can be almost double encoding time, and
-    requires as much as 30-60% more processing power to decode.
+    requires as much as 25% more processing power to decode.
     It is not supported by all standalone players.
 </para></listitem>
 
@@ -2752,12 +2754,12 @@
   <emphasis role="bold">gmc</emphasis>
     Tries to save bits on panning scenes by using a single motion
     vector for the whole frame.
-    This almost always raise PSNR, but significant slows down
-    encoding (and also needs more processing power to decode).
+    This almost always raise PSNR, but significantly slows down
+    encoding (significantly slows down encoding).
     Therefore, you should only use it when you have turned
     <option>vhq</option> to the maximum.
-    <systemitem class="library">XviD</systemitem>'s GMC (which are
-    more sophisticated than DivX's are not supported by all
+    <systemitem class="library">XviD</systemitem>'s GMC is more
+    sophisticated than DivX's, but is only supported by few
     standalone players.
 </para></listitem>