<B>MPlayer</B> ---> MPlayer

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7815 b3059339-0415-0410-9bf9-f77b7e298cf2

1 files changed, 40 insertions, 40 deletions

diff --git a/DOCS/video.html b/DOCS/video.html
index 204c2cd7a0..487ea982c3 100644
--- a/DOCS/video.html
+++ b/DOCS/video.html
@@ -123,9 +123,9 @@
 	(...etc...)
   </PRE>
     <P>It must support YUY2 packed, and YV12 planar pixel formats to be
-      usable with <B>MPlayer</B>.</P>
+      usable with MPlayer.</P>
   </LI>
-  <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support.
+  <LI>And finally, check if MPlayer was compiled with 'xv' support.
     ./configure prints this.</LI>
 </UL>
 
@@ -179,7 +179,7 @@
     refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or
     set refresh rate to n*(fps of the movie) Hz.</LI>
   <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version
-    4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can
+    4.1.0 doesn't. And no TV out support. Of course with MPlayer you can
     happily get <B>accelerated</B> display, with or without <B>TV output</B>, and
     no libraries or X are needed. Read <A HREF="#vidix">Vidix</A> section.</LI>
 </UL>
@@ -215,7 +215,7 @@
 <H5><A NAME="dga_summary">2.3.1.3.1 Summary</A></H5>
 
 <P>This document tries to explain in some words what DGA is in general and what
-  the DGA video output driver for <B>MPlayer</B> can do (and what it
+  the DGA video output driver for MPlayer can do (and what it
   can't).</P>
 
 
@@ -226,7 +226,7 @@
   Technically spoken this happens by mapping the framebuffer memory into
   the memory range of your process. This is allowed by the kernel only
   if you have superuser privileges. You can get these either by logging in
-  as root or by setting the SUID bit on the <B>MPlayer</B> executable (<B>not
+  as root or by setting the SUID bit on the MPlayer executable (<B>not
   recommended</B>).</P>
 
 <P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was
@@ -252,7 +252,7 @@
 
 <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>(II) Loading extension XFree86-DGA</CODE></P>
 
-<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! <B>MPlayer</B>'s DGA
+<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! MPlayer's DGA
   driver is autodetected on ./configure, or you can force it with
   --enable-dga.</P>
 
@@ -261,7 +261,7 @@
   the movie fits in. There is no converter right now :(</P>
 
 <P>Become root. DGA needs root access to be able to write directly to video
-  memory. If you want to run it as user, then install <B>MPlayer</B> SUID
+  memory. If you want to run it as user, then install MPlayer SUID
   root:</P>
 
 <P><CODE>
@@ -275,7 +275,7 @@
   <B>Warning: security risk</B><BR>
   This is a <B>big</B> security risk! <B>Never</B> do this on a server or on
   a computer that can be accessed by other people because they can gain root
-  privileges through SUID root <B>MPlayer</B>.
+  privileges through SUID root MPlayer.
 </BLOCKQUOTE>
 
 <P>Now use the <CODE>-vo dga</CODE> option, and there you go (hope so :))!
@@ -303,10 +303,10 @@
 
 <H5><A NAME="dga_mplayer">2.3.1.3.5 DGA &amp; MPlayer</A></H5>
 
-<P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to
+<P>DGA is used in two places with MPlayer: The SDL driver can be made to
   make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above
   said is true for both; in the following sections I'll explain how the DGA
-  driver for <B>MPlayer</B> works.</P>
+  driver for MPlayer works.</P>
 
 
 <H5><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></H5>
@@ -352,7 +352,7 @@
 
 <P>Generally spoken, DGA framebuffer access should be at least as fast as using
   the X11 driver with the additional benefit of getting a fullscreen image. 
-  The percentage speed values printed by <B>MPlayer</B> have to be interpreted
+  The percentage speed values printed by MPlayer have to be interpreted
   with some care, as for example, with the X11 driver they do not include the
   time used by the X-Server needed for the actual drawing. Hook a terminal to a
   serial line of your box and start top to see what is really going on in your
@@ -426,7 +426,7 @@
 <H5><A NAME="dga_bug_reports">2.3.1.3.B Bug Reports</A></H5>
 
 <P>If you experience troubles with the DGA driver please feel free to file
-  a bug report to me (e-mail address below). Please start <B>MPlayer</B> with
+  a bug report to me (e-mail address below). Please start MPlayer with
   the -v option and include all lines in the bug report that start with
   vo_dga:</P>
 
@@ -446,7 +446,7 @@
   (for example) video driver to use with the SDL_VIDEODRIVER environment
   variable. Well, in theory.</P>
 
-<P>With <B>MPlayer</B>, we used its X11 driver's software scaler ability for
+<P>With MPlayer, we used its X11 driver's software scaler ability for
   cards/drivers that doesn't support XVideo, until we made our own (faster,
   nicer) software scaler. Also we used its aalib output, but now we have ours
   which is more comfortable. Its DGA mode was better than ours, until
@@ -494,7 +494,7 @@
 <H4>Installation</H4>
 
 <P>You'll have to install svgalib and its development package in order for
-  <B>MPlayer</B> build its SVGAlib driver (autodetected, but can be forced),
+  MPlayer build its SVGAlib driver (autodetected, but can be forced),
   and don't forget to edit /etc/vga/libvga.config to suit your card &amp;
   monitor.</P>
 
@@ -506,7 +506,7 @@
 
 <H4>EGA (4bpp) support</H4>
 
-<P>SVGAlib incorporates EGAlib, and <B>MPlayer</B> has the possibility to
+<P>SVGAlib incorporates EGAlib, and MPlayer has the possibility to
   display any movie in 16 colors, thus usable in the following sets:</P>
 
 <UL>
@@ -575,7 +575,7 @@
 </UL>
 
 <P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer,
-  and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P>
+  and don't ask for it, since it's not an MPlayer limitation.</P>
 
 
 <H4><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></H4>
@@ -608,9 +608,9 @@
       under <CODE>/lib/modules/&lt;kernel version&gt;/somewhere</CODE>.</P>
     <P>Then run</P>
     <P><CODE>depmod -a</CODE></P></LI>
-  <LI>Now you have to (re)compile <B>MPlayer</B>, <CODE>configure</CODE> will
+  <LI>Now you have to (re)compile MPlayer, <CODE>configure</CODE> will
     detect <CODE>/dev/mga_vid</CODE> and build the 'mga' driver. Using it from
-    <B>MPlayer</B> goes by <CODE>-vo mga</CODE> if you have matroxfb console,
+    MPlayer goes by <CODE>-vo mga</CODE> if you have matroxfb console,
     or <CODE>-vo xmga</CODE> under XFree86 3.x.x or 4.x.x.</LI>
 </OL>
 
@@ -630,7 +630,7 @@
 
 <H4><A NAME="opengl">2.3.1.9 OpenGL output</A></H4>
 
-<P><B>MPlayer</B> supports displaying movies using OpenGL, but if your
+<P>MPlayer supports displaying movies using OpenGL, but if your
   platform/driver supports xv as should be the case on a PC with Linux, use xv
   instead, OpenGL performance is considerably worse. If you have an X11
   implementation without xv support, OpenGL is a viable alternative.</P>
@@ -650,7 +650,7 @@
 
 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful
   ASCII renderer. There are LOTS of programs already supporting it, like Doom,
-  Quake, etc. <B>MPlayer</B> contains a very usable driver for it.
+  Quake, etc. MPlayer contains a very usable driver for it.
   If ./configure detects aalib installed, the aalib libvo driver will be
   built.</P>
 
@@ -663,7 +663,7 @@
   <TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR>
   <TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR>
   <TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR>
-  <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and <B>MPlayer</B> control)</TD></TR>
+  <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and MPlayer control)</TD></TR>
 </TABLE>
 
 <P><B>The following command line options can be used:</B></P>
@@ -782,7 +782,7 @@
 
 <UL>
   <LI>If you have installed <B>NLS</B> font on your Linux box and run VESA
-    driver from text-mode then after terminating <B>MPlayer</B> you will have
+    driver from text-mode then after terminating MPlayer you will have
     <B>ROM font</B> loaded instead of national. You can load national font again
     by using <B><I>setsysfont</I></B> utility from the Mandrake distribution
     for example.<BR>
@@ -867,11 +867,11 @@ Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>.
     AAlib for that).<BR>
     <I>Note: Everyone can try this trick by commenting out mode switching in
     vo_vesa driver.</I></LI>
-  <LI><B>MPlayer</B>'s video output driver should know active video mode and be
+  <LI>MPlayer's video output driver should know active video mode and be
     able to tell to VIDIX subdevice some video characteristics of server.</LI>
 </UL>
 
-I hope that probably every video output driver of <B>MPlayer</B> will
+I hope that probably every video output driver of MPlayer will
 recognize <CODE>:vidix</CODE> subdevice.
 
 <H4>USAGE METHODS</H4>
@@ -879,7 +879,7 @@ recognize <CODE>:vidix</CODE> subdevice.
 <P>When VIDIX is used as <B>subdevice</B> (<CODE>-vo vesa:vidix</CODE>) then
   video mode configuration is performed by video output device
   (<B>vo_server</B> in short). Therefore you can pass into command line of
-  <B>MPlayer</B> the same keys as for vo_server. In addition it understands
+  MPlayer the same keys as for vo_server. In addition it understands
   <CODE>-double</CODE> key as globally visible parameter. (I recommend using
   this key with VIDIX at least for ATI's card).<BR>
   As for <CODE>-vo xvidix</CODE>: currently it recognizes the following
@@ -897,7 +897,7 @@ recognize <CODE>:vidix</CODE> subdevice.
   But it's dangerous, and you shouldn't do that. In this case given driver will
   be forced and result is unpredictable (it may <B>freeze</B> your
   computer). You should do that ONLY if you are absolutely sure it will work,
-  and <B>MPlayer</B> doesn't do it automatically. Please tell about it to the
+  and MPlayer doesn't do it automatically. Please tell about it to the
   developers. The Right Way is to use VIDIX without arguments to enable driver
   autodetection.</P>
 
@@ -910,14 +910,14 @@ recognize <CODE>:vidix</CODE> subdevice.
   <B>Warning: security risk</B><BR>
   Unfortunately you <B>must</B> have <B>root</B> privileges to use VIDIX
   due to direct hardware access. At least the <B>SUID</B> bit on the
-  <B>MPlayer</B> executable must be set.
+  MPlayer executable must be set.
 </BLOCKQUOTE>
 
 <H4>VIDEO EQUALIZER</H4>
 
 <P>This is a video equalizer implemented especially for VIDIX. You can use
   it either with <B>1-8</B> keys as described in the man page, or
-  by command line arguments. <B>MPlayer</B> recognizes the
+  by command line arguments. MPlayer recognizes the
   following options:</P>
 
 <DL>
@@ -1044,13 +1044,13 @@ recognize <CODE>:vidix</CODE> subdevice.
 
 <P>Finally an important remark: Do not start or stop XawTV on the playback
   device during playback, it will crash your computer. It is, however, fine to
-  <B>FIRST</B> start XawTV, <B>THEN</B> start <B>MPlayer</B>, wait for
-  <B>MPlayer</B> to finish and <B>THEN</B> stop XawTV.</P>
+  <B>FIRST</B> start XawTV, <B>THEN</B> start MPlayer, wait for
+  MPlayer to finish and <B>THEN</B> stop XawTV.</P>
 
 
 <H4><A NAME="dvb">2.3.1.15 DVB</A></H4>
 
-<P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like
+<P>MPlayer supports cards with the Siemens DVB chipset from vendors like
   Siemens, Technotrend, Galaxis or Hauppauge.  The latest DVB drivers are
   available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you
   want to do software transcoding you should have at least a 1GHz CPU.</P>
@@ -1153,7 +1153,7 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
 
 <H4><A NAME="dxr3">2.3.1.16 DXR3/Hollywood+</A></H4>
 
-<P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3
+<P>MPlayer supports hardware accelerated playback with the Creative DXR3
   and Sigma Designs Hollywood Plus cards. These cards both use the em8300 MPEG
   decoder chip from Sigma Designs.</P>
 
@@ -1169,10 +1169,10 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
   <DD><CODE>noprebuf</CODE> turns off prebuffering. Prebuffering is a feature
     of the em8300 chip that enables it to hold more than one frame of video at
     a time. This means that when you are running with prebuffering (default)
-    <B>MPlayer</B> will try to keep the video buffer filled with data at all
-    times. If you are on a slow machine <B>MPlayer</B> will probably use close
+    MPlayer will try to keep the video buffer filled with data at all
+    times. If you are on a slow machine MPlayer will probably use close
     to, or precisely 100% of CPU. This is especially common if you play pure MPEG
-    streams (like DVDs, SVCDs a.s.o.) since <B>MPlayer</B> will not have to
+    streams (like DVDs, SVCDs a.s.o.) since MPlayer will not have to
     reencode it to MPEG it will fill the buffer very fast.<BR>
     With prebuffering video playback is <B>much</B> less sensitive to other
     programs hogging the CPU, it will not drop frames unless applications hog
@@ -1219,12 +1219,12 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
 <H4>Overlay</H4>
 
 <P>To get overlay run dxr3view that comes with the em8300 package before
-  starting <B>MPlayer</B>. You can set various options in dxr3view by pressing
+  starting MPlayer. You can set various options in dxr3view by pressing
   <CODE>T</CODE> while holding the mouse cursor above the window.</P>
 
 <H4>MPEG1, MPEG2, VCD and DVD Notes</H4>
 
-<P>MPEG1/2 content should now automatically be detected by <B>MPlayer</B> and
+<P>MPEG1/2 content should now automatically be detected by MPlayer and
   it will use the hardware acceleration of the DXR3 to play it. If not, you can
   force it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you
   plan to use postprocessing filters you must use <CODE>-vc mpeg12</CODE>.</P>
@@ -1234,7 +1234,7 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
   known bug. The em8300 will also improperly handle subtitles that are too big,
   and may hang for a second or two. At this time, the only workaround is to use
   <CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles. When running with
-  <CODE>-vc mpeg12</CODE> <B>MPlayer</B> will reencode video to MPEG (even if it
+  <CODE>-vc mpeg12</CODE> MPlayer will reencode video to MPEG (even if it
   already is MPEG). This means that it will need more CPU power, and you might
   loose some picture quality.</P>
 
@@ -1276,7 +1276,7 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
         <CODE>TVout/fbset</CODE> and type <CODE>make</CODE>. Install
         <CODE>fbset</CODE> into somewhere in your PATH.</LI>
       <LI>
-        Then enter into the <CODE>TVout/</CODE> directory in the <B>MPlayer</B>
+        Then enter into the <CODE>TVout/</CODE> directory in the MPlayer
         source, and execute <CODE>./modules</CODE> as root. Your text-mode console
         will enter into framebuffer mode (no way back!).</LI>
       <LI>Next, EDIT and run the <CODE>./matroxtv</CODE> script. This will present you
@@ -1339,7 +1339,7 @@ for 16:9 TV:  -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
     <A HREF="http://gatos.sf.net">gatos</A>.</LI>
   <LI><B>ASIC Radeon VIVO</B>: supported by
   <A HREF="http://gatos.sf.net">gatos</A>.</LI>
-  <LI><B>Radeon</B> and <B>Rage128</B>: supported by <B>MPlayer</B>!
+  <LI><B>Radeon</B> and <B>Rage128</B>: supported by MPlayer!
     Check <a href="#vesa">VESA driver</a> and <A HREF="#vidix">VIDIX</A>
     sections.</LI>
 </UL>