changeset 7814:988498df1996

<B>MPlayer</B> ---> MPlayer
author diego
date Sun, 20 Oct 2002 12:20:39 +0000
parents 76940a39405a
children c81e5a7f5862
files DOCS/bugreports.html DOCS/cd-dvd.html DOCS/codecs.html DOCS/documentation.html DOCS/encoding.html DOCS/faq.html DOCS/formats.html DOCS/mplayer.1 DOCS/skin.html DOCS/sound.html DOCS/users_against_developers.html DOCS/video.html
diffstat 12 files changed, 217 insertions(+), 217 deletions(-) [+]
line wrap: on
line diff
--- a/DOCS/bugreports.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/bugreports.html	Sun Oct 20 12:20:39 2002 +0000
@@ -16,7 +16,7 @@
   software project. But just like writing good software, good problem reports
   involve some work. Please realize that most developers are extremely busy and
   receive obscene amounts of email. So while your feedback is crucial in
-  improving <B>MPlayer</B> and very much appreciated, please understand that you
+  improving MPlayer and very much appreciated, please understand that you
   have to provide <B>all</B> of the information we request and follow the
   instructions in this document closely.</P>
 
@@ -26,14 +26,14 @@
 <P>If you feel have the necessary skills you are invited to have a go at fixing
   the bug yourself.  Or maybe you already did that?  Please read
   <A HREF="tech/patches.txt">this short document</A> to find out how to get
-  your code included in <B>MPlayer</B>. The people on the
+  your code included in MPlayer. The people on the
   <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A>
   mailing list will assist you if you have questions.</P>
 
 
 <H2>How to report bugs</H2>
 
-<P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug
+<P>First of all please try the latest CVS version of MPlayer as your bug
   might already be fixed there. Development moves extremely fast, most problems
   in official releases are reported within days or even hours, so please use
   <B>only CVS</B> to report bugs. CVS instructions can be found at the bottom of
@@ -46,7 +46,7 @@
 <P>Please do not send bug reports privately to individual developers.  This is
   community work and thus there might be several people interested in it.
   Sometimes other users already experienced your troubles and know how to
-  circumvent a problem even if it is a bug in <B>MPlayer</B> code.</P>
+  circumvent a problem even if it is a bug in MPlayer code.</P>
 
 <P>Please describe your problem in as much detail as possible. Do a little
   detective work to narrow down the circumstances under which the problem
@@ -164,7 +164,7 @@
 
 <H4>For playback problems</H4>
 
-<P>Please include the output of <B>MPlayer</B> at verbosity level 1, but
+<P>Please include the output of MPlayer at verbosity level 1, but
   remember to <B>not truncate the output</B> when you paste it into your mail.
   The developers need all of the messages to properly diagnose a problem. You
   can direct the output into a file like this:</P>
@@ -179,7 +179,7 @@
 <P>Also upload a small text file having the same base name as your file
   with a .txt extension. Describe the problem you are having with the
   particular file there and include your email address as well as the output
-  of <B>MPlayer</B> at verbosity level 1. Usually the first 1-5 MB of a file are
+  of MPlayer at verbosity level 1. Usually the first 1-5 MB of a file are
   enough to reproduce the problem, but to be sure we ask you to:</P>
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;dd if=yourfile of=smallfile bs=1024k count=5</CODE></P>
@@ -220,12 +220,12 @@
 
 <H4>How to conserve information about a reproducible crash</H4>
 
-Recompile <B>MPlayer</B> with debugging code enabled:
+Recompile MPlayer with debugging code enabled:
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR>
   &nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P>
 
-and then run <B>MPlayer</B> within gdb using:
+and then run MPlayer within gdb using:
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb ./mplayer</CODE></P>
 
@@ -254,7 +254,7 @@
 <H2>I know what I am doing...</H2>
 
 <P>If you created a proper bug report following the steps above and you are
-  confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken
+  confident it is a bug in MPlayer, not a compiler problem or broken
   file, you have already read the documentation and you could not find a
   solution, your sound drivers are OK, then you might want to subscribe to the
   mplayer-advusers list and send your bug report there to get a better and
@@ -263,7 +263,7 @@
   in the manual there, you will be ignored or flamed instead of getting an
   appropriate answer.<BR>
   So do not flame us and  subscribe to -advusers only if you really know
-  what you are doing and feel like being an advanced <B>MPlayer</B> user or
+  what you are doing and feel like being an advanced MPlayer user or
   developer.  If you meet these criteria it should not be difficult to find
   out how to subscribe...</P>
 
--- a/DOCS/cd-dvd.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/cd-dvd.html	Sun Oct 20 12:20:39 2002 +0000
@@ -60,9 +60,9 @@
 
 <H2><A NAME="dvd">4.2 DVD playback</A></H2>
   
-<P><B>MPlayer</B> uses <CODE>libdvdread</CODE> and <CODE>libdvdcss</CODE> for
+<P>MPlayer uses <CODE>libdvdread</CODE> and <CODE>libdvdcss</CODE> for
   DVD decryption and playback. These two libraries are contained in the
-  <CODE>libmpdvdkit2/</CODE> subdirectory of the <B>MPlayer</B> source tree, you
+  <CODE>libmpdvdkit2/</CODE> subdirectory of the MPlayer source tree, you
   do not have to install them separately. We opted for this solution because
   we had to fix a libdvdread bug, and apply a patch which adds
   <B>cracked CSS keys caching support</B> to libdvdcss. This results in a large
@@ -70,7 +70,7 @@
   playing. The cracked keys are stored in the
   <CODE>~/.mplayer/DVDKeys</CODE> directory.</P>
 
-<P><B>MPlayer</B> can also use system-wide <CODE>libdvdread</CODE> and
+<P>MPlayer can also use system-wide <CODE>libdvdread</CODE> and
   <CODE>libdvdcss</CODE> libraries, but this solution is <B>not</B> recommended,
   as it can result in bugs, library incompatibilities, and slower speed.</P>
 
@@ -80,7 +80,7 @@
 <H4>Old-style DVD support - OPTIONAL</H4>
 
 <P>Useful if you want to play encoded VOBs from hard disk. Compile and
-  install <B>libcss</B> 0.0.1 (not newer) for this (If <B>MPlayer</B> fails to
+  install <B>libcss</B> 0.0.1 (not newer) for this (If MPlayer fails to
   detect it, use the <CODE>-csslib /path/to/libcss.so</CODE> option).</P>
 
 <P>For the complete list of available options, please read the man page.</P>
--- a/DOCS/codecs.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/codecs.html	Sun Oct 20 12:20:39 2002 +0000
@@ -47,7 +47,7 @@
 <P>This section contains information about the DivX4 and DivX5 codecs of
   <A HREF="http://www.projectmayo.com">Project Mayo</A>. Their first available
   alpha version was OpenDivX 4.0 alpha 47 and 48. Support for this was included
-  in <B>MPlayer</B> in the past, and built by default. We also used its
+  in MPlayer in the past, and built by default. We also used its
   postprocessing code to optionally enhance visual quality of MPEG1/2 movies.
   Now we use our own, for all file types.</P>
 
@@ -67,7 +67,7 @@
 <P><B>Note:</B> Do <B>not</B> forget adding <CODE>/usr/local/lib</CODE> to your
   <CODE>/etc/ld.so.conf</CODE> and running <CODE>ldconfig</CODE>!</P>
 
-<P><B>MPlayer</B> autodetects DivX4/DivX5 if it is properly installed, just
+<P>MPlayer autodetects DivX4/DivX5 if it is properly installed, just
   compile as usual. If it does not detect it, you did not install or configure
   it correctly.</P>
 
@@ -76,7 +76,7 @@
 <DL>
   <DT><CODE>-vc odivx</CODE></DT>
   <DD>Uses the codec in OpenDivX fashion. In this case it
-    produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
+    produces YV12 images in its own buffer, and MPlayer does colorspace
     conversion via libvo. (<B>Fast, recommended!</B>)</DD>
 
   <DT><CODE>-vc divx4</CODE></DT>
@@ -107,22 +107,22 @@
   variants:
   DivX 3, DivX 4, DivX 5, Windows Media Video 7 (WMV1)</P>
 
-<P>If you use an <B>MPlayer</B> release you have libavcodec right in the
-  package, just build as usual. If you use <B>MPlayer</B> from CVS you have to
+<P>If you use an MPlayer release you have libavcodec right in the
+  package, just build as usual. If you use MPlayer from CVS you have to
   extract libavcodec from the FFmpeg CVS tree as FFmpeg 0.4.5 does <B>not</B>
-  work with <B>MPlayer</B>. In order to achieve this do:</P>
+  work with MPlayer. In order to achieve this do:</P>
 
 <OL>
   <LI><CODE>cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg login</CODE></LI>
   <LI><CODE>cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg co ffmpeg</CODE></LI>
   <LI>Move the <CODE>libavcodec</CODE> directory from the FFmpeg sources to the
-    root of the <B>MPlayer</B> CVS tree. It should look like this:
+    root of the MPlayer CVS tree. It should look like this:
     <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>main/libavcodec</CODE></P>
     Symlinking is <B>not</B> enough, you have to copy or move it!</LI>
   <LI>Compile. Configure should detect problems before compilation.</LI>
 </OL>
 
-<P><B>Note:</B> <B>MPlayer</B> from CVS does contain a libavcodec
+<P><B>Note:</B> MPlayer from CVS does contain a libavcodec
   subdirectory, but it does <B>not</B> contain the source for libavcodec!
   You must follow the steps above to obtain the source for this library.</P>
 
@@ -140,7 +140,7 @@
   action against anyone for codec-related issues.
 </P>
 
-<P><B>MPlayer</B> is capable of employing the XAnim codecs for decoding. Follow
+<P>MPlayer is capable of employing the XAnim codecs for decoding. Follow
   the instructions to enable them:</P>
 
 <OL>
@@ -157,7 +157,7 @@
 </OL>
 
 <P>XAnim is video codec family number 10, so you may want to use the <CODE>-vfm 10</CODE>
-  option to tell <B>MPlayer</B> to use them if possible.</P>
+  option to tell MPlayer to use them if possible.</P>
 
 <P>Tested codecs include: <B>Indeo 3.2</B>, <B>4.1</B>, <B>5.0</B>, <B>CVID</B>,
   <B>3ivX</B>, <B>h263</B>.</P>
@@ -165,7 +165,7 @@
 
 <H4><A NAME="vivo_video">2.2.1.4 VIVO video</A></H4>
 
-<P><B>MPlayer</B> can play Vivo (1.0 and 2.0) videos. The most suitable codec
+<P>MPlayer can play Vivo (1.0 and 2.0) videos. The most suitable codec
   for 1.0 files is FFmpeg's H263 decoder, you can use it with the <CODE>-vc
   ffh263</CODE> option (default). For 2.0 files, use the
   <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">ivvideo.dll</A>
@@ -176,7 +176,7 @@
 <H4><A NAME="mpeg">2.2.1.5 MPEG 1/2 video</A></H4>
 
 <P>MPEG1 and MPEG2 are decoded by the multiplatform native <B>libmpeg2</B>
-  library, whose source code is included in <B>MPlayer</B>. We handle buggy
+  library, whose source code is included in MPlayer. We handle buggy
   MPEG 1/2 video files by catching sig11 (segmentation fault), and quickly
   reinitializing the codec, continuing exactly from where the failure occurred. 
   This recovery technique has no measurable speed penalty.</P>
@@ -192,14 +192,14 @@
 
 <H4><A NAME="cinepak">2.2.1.7 Cinepak CVID</A></H4>
 
-<P><B>MPlayer</B> uses its own open source, multiplatform Cinepak decoder by
+<P>MPlayer uses its own open source, multiplatform Cinepak decoder by
   default. It supports YUV outputs, so that hardware scaling is possible if the
   video output driver permits it.</P>
 
 
 <H4><A NAME="realvideo">2.2.1.8 RealVideo</A></H4>
 
-<B>MPlayer</B> supports decoding all versions of RealVideo:
+MPlayer supports decoding all versions of RealVideo:
 
 <UL>
   <LI>RealVideo 1.0 (fourcc RV10) - en/decoding supported by <B>libavcodec</B></LI>
@@ -207,8 +207,8 @@
 </UL>
 
 <P>It is recommended to download and install RealPlayer8 or RealONE, because
-  <B>MPlayer</B> can use their libraries to decode files with RealVideo 2.0 -
-  4.0 video. The <B>MPlayer</B> configure script should detect the
+  MPlayer can use their libraries to decode files with RealVideo 2.0 -
+  4.0 video. The MPlayer configure script should detect the
   RealPlayer libraries in the standard locations of a full installation. If it
   does not, tell configure where to look with the
   <CODE>--with-reallibdir</CODE> switch.</P>
@@ -258,7 +258,7 @@
   <LI><CODE>make -f Makefile.linux</CODE></LI>
   <LI>Get <CODE>encore2.h</CODE> and <CODE>decore.h</CODE> from the DivX4Linux
     package, and copy them to <CODE>/usr/local/include/</CODE>.</LI>
-  <LI>Recompile <B>MPlayer</B> with <CODE>--with-xvidcore=/path/to/libcore.a</CODE>.</LI>
+  <LI>Recompile MPlayer with <CODE>--with-xvidcore=/path/to/libcore.a</CODE>.</LI>
 </OL>
 
 
@@ -354,13 +354,13 @@
   VIVO/2.0 file. VIVO/1.0 files have <B>g.723</B> audio, and VIVO/2.0 files
   have <B>Vivo Siren</B> audio. Both are supported. You can grab the
   <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/vivog723.acm">g.723/Siren</A>
-  Win32 DLL from the <B>MPlayer</B> site,
+  Win32 DLL from the MPlayer site,
   then copy it into the <CODE>/usr/lib/win32</CODE> directory.</P>
 
 
 <H4><A NAME="realaudio">2.2.2.5 RealAudio</A></H4>
 
-<B>MPlayer</B> supports decoding nearly all versions of RealAudio:
+MPlayer supports decoding nearly all versions of RealAudio:
 
 <UL>
   <LI>RealAudio DNET - decoding supported by <B>liba52</B></LI>
@@ -379,7 +379,7 @@
 
 <P>VFW (Video for Windows) is the old Video API for Windows. Its codecs have
   the .DLL or (rarely) .DRV extension.
-  If <B>MPlayer</B> fails at playing your AVI with this kind of message:</P>
+  If MPlayer fails at playing your AVI with this kind of message:</P>
 
 <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>UNKNOWN video codec: HFYU (0x55594648)</CODE></P>
 
@@ -435,7 +435,7 @@
 
 <P><B>Note:</B> If there is no <CODE>Filename</CODE> entry and <CODE>DisplayName</CODE>
   contains something like <CODE>device:dmo</CODE>, then it is a DMO-Codec, which are
-  currently not supported by <B>MPlayer</B>.</P>
+  currently not supported by MPlayer.</P>
 
 <P><B>Old Method:</B> Take a deep breath and start searching the registry...</P>
 
--- a/DOCS/documentation.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/documentation.html	Sun Oct 20 12:20:39 2002 +0000
@@ -307,33 +307,33 @@
 <H1><A NAME="introduction">1. Introduction</A></H1>
 
 
-<P><B>MPlayer</B> is a movie player for LINUX (runs on many other Unices, and
+<P>MPlayer is a movie player for LINUX (runs on many other Unices, and
   <B>non-x86</B> CPUs, see the <A HREF="#ports">ports section</A>). It plays most
   MPEG, VOB, AVI, OGG, VIVO, ASF/WMV, QT/MOV, FLI, RM, NuppelVideo, yuv4mpeg,
   FILM, RoQ, PVA files, supported by many native, XAnim, RealPlayer, and
   Win32 DLL codecs. You can watch <B>VideoCD</B>, <B>SVCD</B>, <B>DVD</B>,
   <B>3ivx</B>, <B>RealMedia</B>, and <B>DivX</B> movies too (and you don't need
   the avifile
-  library at all!). Another big feature of <B>MPlayer</B> is the wide range of
+  library at all!). Another big feature of MPlayer is the wide range of
   supported output drivers. It works with X11, Xv, DGA, OpenGL, SVGAlib, fbdev,
   AAlib, DirectFB, but you can also use GGI and SDL (and this way all their
   drivers) and some lowlevel card-specific drivers (for Matrox, 3Dfx and Radeon,
   Mach64, Permedia3) too! Most
   of them supports software or hardware scaling, so you can enjoy movies in
-  fullscreen. <B>MPlayer</B> supports displaying through some hardware MPEG
+  fullscreen. MPlayer supports displaying through some hardware MPEG
   decoder boards, such as the <B><A HREF="video.html#dvb">DVB</A></B> and
   <B><A HREF="video.html#dxr3">DXR3/Hollywood+</A></B>. And what about the nice big antialiased
   shaded subtitles (<B>10 supported types</B>) with European/ISO 8859-1,2
   (Hungarian, English, Czech, etc), Cyrillic, Korean fonts, and the onscreen
   display (OSD)?</P>
 
-<P><B>MPlayer</B> is under GPL v2 license.</P>
+<P>MPlayer is under GPL v2 license.</P>
 
 <P>The player is rock solid playing damaged MPEG files (useful for some VCDs),
   and it plays bad AVI files which are unplayable with the famous
   windows media player. Even AVI files without index chunk are playable, and
   you can temporarily rebuild their indexes with the <CODE>-idx</CODE> option, or
-  permanently with <B>MEncoder</B>, thus enabling seeking!
+  permanently with MEncoder, thus enabling seeking!
   As you see, stability and quality are the most important things,
   but the speed is also amazing.</P>
 
@@ -390,7 +390,7 @@
 <H2><A NAME="installation">1.2 Installation</A></H2>
 
 <P>In this chapter I'll try to guide you through the compiling and
-  configuring process of <B>MPlayer</B>. It's not easy, but it won't necessarily
+  configuring process of MPlayer. It's not easy, but it won't necessarily
   be hard. If you experience a different behavior than what I explain, please
   search through this documentation and you'll find your answers. If you
   see links, please follow them and read carefully what they contain. It
@@ -412,7 +412,7 @@
     runtime problems). If you vote for 3.x.x, try to use the latest version,
     early releases had various bugs, so be sure you use at least 3.1, it's
     tested and working. For detailed information about gcc 2.96's bugs (that are
-    still NOT fixed, they have been WORKED AROUND in <B>MPlayer</B>!), see the
+    still NOT fixed, they have been WORKED AROUND in MPlayer!), see the
     <A HREF="users_against_developers.html#gcc">gcc 2.96</A> section and the
     <A HREF="faq.html">FAQ</A>.</LI>
   <LI><B>XFree86</B> - suggested version is <B>always the newest (4.2.1)</B>.
@@ -429,9 +429,9 @@
     video cards that lag strangely with the xv driver). Always use the newest
     (beginning from 1.2.x).</LI>
   <LI><B>libjpeg</B> - optional JPEG decoder, used by -mf and some QT MOV files.
-    Useful for both <B>MPlayer</B> and <B>MEncoder</B> if you plan to work with jpeg files.</LI>
+    Useful for both MPlayer and MEncoder if you plan to work with jpeg files.</LI>
   <LI><B>libpng</B> - recommended and default (M)PNG decoder. Required for GUI.
-    Useful for both <B>MPlayer</B> and <B>MEncoder</B>.</LI>
+    Useful for both MPlayer and MEncoder.</LI>
   <LI><B>lame</B> - recommended, needed for encoding MP3 audio with MEncoder,
     suggested version is <B>always the newest</B> (at least 3.90).</LI>
   <LI><B>libogg</B> - optional, needed for playing OGG file format.</LI>
@@ -455,9 +455,9 @@
         other MPEG4 types. Recommended!</LI>
     </UL>
   </LI>
-  <LI><B>Win32 codecs</B>: If you plan to use <B>MPlayer</B> on x86
+  <LI><B>Win32 codecs</B>: If you plan to use MPlayer on x86
     architecture, you will possibly need them. Download and unzip w32codecs.zip
-    to /usr/lib/win32 <B>BEFORE</B> compiling <B>MPlayer</B>, otherwise no Win32
+    to /usr/lib/win32 <B>BEFORE</B> compiling MPlayer, otherwise no Win32
     support will be compiled!<BR>
     <B>Note:</B> the avifile project has a similar codecs package, but it differs
     from ours. If you want to use all supported codecs, then install our package
@@ -498,14 +498,14 @@
     screen, hardware YUV zoom) for decoding <B>3ivx</B> and Indeo 3/4/5 movies,
     and some old formats. And they are multiplatform, so this is the only way to
     play Indeo on non-x86 platforms (well, apart from using XAnim:). But for
-    example Cinepak movies are best played with <B>MPlayer</B>'s own Cinepak
+    example Cinepak movies are best played with MPlayer's own Cinepak
     decoder!</LI>
   <LI>For <B>Ogg Vorbis</B> audio decoding you need to install
     <CODE>libvorbis</CODE> properly. Use deb/rpm packages if available, or
     compile from
     <A HREF="http://ogg.org/ogg/vorbis/download/vorbis_nightly_cvs.tgz">source</A>
     (this is a nightly updated tarball of Vorbis CVS).</LI>
-  <LI><B>MPlayer</B> can use the libraries of RealPlayer 8 or RealONE to play
+  <LI>MPlayer can use the libraries of RealPlayer 8 or RealONE to play
     files with <B>RealVideo 2.0 - 4.0</B> video, and Sipro/Cook audio. See
     <A HREF="formats.html#real">RealMedia file format</A> section for
     installation instructions and more information.</LI>
@@ -528,14 +528,14 @@
     to use the mga_vid kernel module instead, for it works much better.
     Please see the <A HREF="video.html#mga_vid">mga_vid</A> section about its
     installation and usage. It is important to do these steps <I>before</I>
-    compiling <B>MPlayer</B>, otherwise no mga_vid support will be built. Also
+    compiling MPlayer, otherwise no mga_vid support will be built. Also
     check out the <A HREF="video.html#tv-out_matrox">Matrox TV-out</A> section.
     <U><B>If you don't use Linux</B></U>, your only possibility is the VIDIX
     driver: read the <A HREF="video.html#vidix">VIDIX</A> section.</LI>
   <LI><B>3Dfx Voodoo3/Banshee cards</B>: please see the
     <A HREF="video.html#tdfxfb">tdfxfb</A> section in order to gain big
     speedup. It is important to do these steps <B>before</B> compiling
-    <B>MPlayer</B>, otherwise no 3Dfx support will be built. Also see the <A
+    MPlayer, otherwise no 3Dfx support will be built. Also see the <A
     HREF="video.html#tv-out_voodoo">3dfx TV-out section</A>. If you use X, use
     <B>at least 4.2.0</B>, as the 3dfx Xv driver was broken in 4.1.0 and earlier
     releases.</LI>
@@ -636,7 +636,7 @@
   <LI><B>C-Media with SP/DIF out</B>: hardware AC3 passthrough is possible
     with these cards, see
     <A HREF="codecs.html#hardware_ac3">Hardware AC3 decoding</A> section.</LI>
-  <LI>Features of <B>other cards</B> aren't supported by <B>MPlayer</B>.
+  <LI>Features of <B>other cards</B> aren't supported by MPlayer.
     <U>It's very recommended to read the <A HREF="sound.html">sound card
     section</A>!</U></LI>
 </UL>
@@ -646,14 +646,14 @@
 <UL>
   <LI>Decide if you need GUI. If you do, see the <A HREF="#gui">GUI section</A>
     before compiling.</LI>
-  <LI>If you want to install <B>MEncoder</B> (our great all-purpose encoder),
+  <LI>If you want to install MEncoder (our great all-purpose encoder),
     see the <A HREF="encoding.html">MEncoder section</A>.</LI>
   <LI>If you have a V4L compatible <B>TV tuner</B> card, and wish to watch/grab
-    and encode movies with <B>MPlayer</B>, read the <A HREF="#tv">TV input</A>
+    and encode movies with MPlayer, read the <A HREF="#tv">TV input</A>
     section.</LI>
 </UL>
 
-<P>Then build <B>MPlayer</B>:</P>
+<P>Then build MPlayer:</P>
 
 <PRE>
     ./configure
@@ -661,17 +661,17 @@
     make install
 </PRE>
 
-<P>At this point, <B>MPlayer</B> is ready to use. The directory
+<P>At this point, MPlayer is ready to use. The directory
   <CODE>$PREFIX/share/mplayer</CODE> contains the <CODE>codecs.conf</CODE>
   file, which is used to tell the program all the codecs and their
   capabilities.  This file should always be kept up to date together with the
   main binary.<BR>
   Check if you have <CODE>codecs.conf</CODE> in your home directory
-  (<CODE>~/.mplayer/codecs.conf</CODE>) left from old <B>MPlayer</B> versions, and remove it.</P>
+  (<CODE>~/.mplayer/codecs.conf</CODE>) left from old MPlayer versions, and remove it.</P>
 
 <P><B>Debian users</B> can build a <CODE>.deb</CODE> package for themselves,
   it's very simple. Just exec <CODE>fakeroot debian/rules binary</CODE> in
-  <B>MPlayer</B>'s root directory. See
+  MPlayer's root directory. See
   <A HREF="documentation.html#debian">Debian packaging</A> for detailed
   instructions.</P>
 
@@ -712,12 +712,12 @@
 <P>Currently you can't use the <CODE>-gui</CODE> option on the command line,
   due to technical reasons.</P>
 
-<P>As <B>MPlayer</B> doesn't have a skin included, you have to download them if
+<P>As MPlayer doesn't have a skin included, you have to download them if
   you want to use the GUI. See the
   <A HREF="http://www.mplayerhq.hu/homepage/dload.html">download page</A>.
   They should be extracted to the usual system-wide directory
   (<CODE>$PREFIX/share/mplayer/Skin</CODE>), or to
-  <CODE>$HOME/.mplayer/Skin</CODE>. <B>MPlayer</B> by default looks in these
+  <CODE>$HOME/.mplayer/Skin</CODE>. MPlayer by default looks in these
   directories for a directory named <I>default</I>, but you can use the
   <CODE>-skin newskin</CODE> option, or the <CODE>skin=newskin</CODE> config
   file directive to use the skin in <CODE>*/Skin/newskin</CODE> directory.</P>
@@ -726,7 +726,7 @@
 <H2><A NAME="subtitles_osd">1.4 Subtitles and OSD</A></H2>
 
 <P>
-  <B>MPlayer</B> can display subtitles along with movie files. Currently the following 
+  MPlayer can display subtitles along with movie files. Currently the following 
   formats are supported:</P>
 <UL>
   <LI>VobSub</LI>
@@ -779,7 +779,7 @@
   the subtitle file are different.<BR> Please note that the MicroDVD subtitle
   format uses absolute frame numbers for its timing, and therefore the
   <CODE>-subfps</CODE> option cannot be used with this format. As
-  <B>MPlayer</B> has no way to guess the frame rate of the subtitle file, you
+  MPlayer has no way to guess the frame rate of the subtitle file, you
   have to manually convert the frame rate. There is a little perl script in the
   <CODE>contrib</CODE> directory of the MPlayer FTP site to do this conversion
   for you.</P>
@@ -789,7 +789,7 @@
 
 <H3><A NAME="mpsub">1.4.1 MPlayer's own subtitle format (MPsub)</A></H3>
 
-<P><B>MPlayer</B> introduces a new subtitle format called <B>MPsub</B>. It was
+<P>MPlayer introduces a new subtitle format called <B>MPsub</B>. It was
   designed by me (Gabucino). Basically its main feature is being
   <I>dynamically</I> time-based (although it has frame-based mode too). Example
   (from
@@ -821,11 +821,11 @@
 
 <H3><A NAME="install_osd">1.4.2 Installing OSD and subtitles</A></H3>
 
-<P>You need an <B>MPlayer</B> font package to be able to use OSD/SUB feature.
+<P>You need an MPlayer font package to be able to use OSD/SUB feature.
   There are many ways to get it:</P>
 
 <UL>
-  <LI>download ready-to-use font packages from <B>MPlayer</B> site.
+  <LI>download ready-to-use font packages from MPlayer site.
     Note: currently available fonts are limited for iso 8859-1/2 support,
     but there are some other (including Korean, Russian, 8859-8 etc) fonts
     at contrib/font section of FTP, made by users.<BR>
@@ -871,7 +871,7 @@
 
 <H2><A NAME="rtc">1.5 RTC</A></H2>
 
-There are three timing methods in <B>MPlayer</B>.
+There are three timing methods in MPlayer.
 
 <UL>
   <LI><B>To use the old method</B>, you don't have to do anything. It uses
@@ -880,7 +880,7 @@
   <LI><B>The new timer</B> code uses PC's RTC (Real Time Clock) for this task,
     because it has precise 1ms timers. It is automagically enabled when
     available, but requires root privileges, a <I>setuid root</I>
-    <B>MPlayer</B> binary or a properly set up kernel.
+    MPlayer binary or a properly set up kernel.
     <BR>
     If you are running kernel 2.4.19pre8 or later you can adjust the maximum
     RTC frequency for normal users through the <CODE>/proc</CODE> filesystem.
@@ -984,7 +984,7 @@
 
 <H2><A NAME="command_line">3.1 Command line</A></H2>
 
-<P><B>MPlayer</B> utilizes a complex playtree. It consists of global options
+<P>MPlayer utilizes a complex playtree. It consists of global options
   written as first (for example <CODE>mplayer -vfm 5</CODE>), and options
   written after filenames, that apply only to the given filename/URL/whatever
   (for example <CODE>mplayer -vfm 5 movie1.avi movie2.avi -vfm 4</CODE>).<BR>
@@ -1017,15 +1017,15 @@
 
 <H2><A NAME="control">3.2 Control</A></H2>
 
-<P><B>MPlayer</B> has a fully configurable, command driven, control layer which
-  lets you control <B>MPlayer</B> with keyboard, mouse, joystick or remote
+<P>MPlayer has a fully configurable, command driven, control layer which
+  lets you control MPlayer with keyboard, mouse, joystick or remote
   control (using LIRC). See the man page for the complete list of keyboard
   controls.</P>
 
 
 <H3><A NAME="controls_configuration">3.2.1 Controls configuration</A></H3>
 
-<P><B>MPlayer</B> allows you bind any key/button to any <B>MPlayer</B> command
+<P>MPlayer allows you bind any key/button to any MPlayer command
   using a simple config file.  The syntax consist of a key name followed by a
   command. The default config file location is
   <CODE>$HOME/.mplayer/input.conf</CODE> but it can be overridden using the
@@ -1115,7 +1115,7 @@
   <LI><B>audio_delay</B> (float) val
     <P>Adjust the audio delay of val seconds</P></LI>
   <LI><B>quit</B>
-    <P>Quit <B>MPlayer</B></P></LI>
+    <P>Quit MPlayer</P></LI>
   <LI><B>pause</B>
     <P>Pause/unpause the playback</P></LI>
   <LI><B>grap_frames</B>
@@ -1175,12 +1175,12 @@
   More about it at <A HREF="http://www.lirc.org">www.lirc.org</A>.</P>
 
 <P>If you have installed the lirc-package, configure will autodetect it. If
-  everything went fine, <B>MPlayer</B> will print a message like "Setting up
+  everything went fine, MPlayer will print a message like "Setting up
   lirc support..." on startup. If an error occurs it will tell you. If it
   doesn't tell you anything about LIRC there's no support compiled in. That's
   it :-)</P>
 
-<P>The application name for <B>MPlayer</B> is - oh wonder - 'mplayer'.
+<P>The application name for MPlayer is - oh wonder - 'mplayer'.
   You can use any mplayer commands and even pass more than one command by
   separating them with \n. Don't forget to enable the repeat flag in .lircrc
   when it make sense (seek, volume, etc). Here's an excerpt from my
@@ -1220,23 +1220,23 @@
 
 <H3><A NAME="slave">3.2.3 Slave mode</A></H3>
 
-<P>The slave mode allow you to build simple frontend to <B>MPlayer</B>. When
-  enabled (with the <CODE>-slave</CODE> switch) <B>MPlayer</B> will read
+<P>The slave mode allow you to build simple frontend to MPlayer. When
+  enabled (with the <CODE>-slave</CODE> switch) MPlayer will read
   commands separated by new line (\n) from stdin.</P>
 
 
 <H2><A NAME="streaming">3.3 Streaming from network or pipes</A></H2>
 
-<P><B>MPlayer</B> can play files from network, using the HTTP, MMS or RTSP/RTP
+<P>MPlayer can play files from network, using the HTTP, MMS or RTSP/RTP
   protocol.</P>
 
 <P>Playing goes by simply using adding the URL to the command line.
-  <B>MPlayer</B> also honors the http_proxy environment variable, and uses
+  MPlayer also honors the http_proxy environment variable, and uses
   proxy if available. Proxy usage can also be forced:</P>
 
 <P><CODE>mplayer http_proxy://proxy.micorsops.com:3128/http://micorsops.com:80/stream.asf</CODE></P>
 
-<P><B>MPlayer</B> can read from stdin (NOT named pipes). This can be for example
+<P>MPlayer can read from stdin (NOT named pipes). This can be for example
   used to play from FTP:</P>
 
 <P><CODE>&nbsp;&nbsp;wget ftp://micorsops.com/something.avi -O - | mplayer -</CODE></P>
@@ -1294,12 +1294,12 @@
 <P>To build the package you will need GNU make (gmake, /usr/ports/devel/gmake),
   native BSD make will not work.</P>
 
-<P>To run <B>MPlayer</B> you will need to re-compile the kernel with
+<P>To run MPlayer you will need to re-compile the kernel with
   "options USER_LDT" (unless you are running -CURRENT, where this is default).
   If you have a CPU with SSE also use "options CPU_ENABLE_SSE" to use it
   (FreeBSD-STABLE required, or use kernel patches).</P>
 
-<P>If <B>MPlayer</B> complains about "CD-ROM Device '/dev/cdrom' not found!" make a
+<P>If MPlayer complains about "CD-ROM Device '/dev/cdrom' not found!" make a
   symbolic link: <CODE>ln -s /dev/(your_cdrom_device) /dev/cdrom</CODE></P>
 
 <P>There's no DVD support for FreeBSD yet.</P>
@@ -1317,7 +1317,7 @@
   available. However, <B>DivX/OpenDivX</B> movies should work, when using
   libavcodec.</P>
 
-<P>On <B>UltraSPARC</B>s, <B>MPlayer</B> takes advantage of their <B>VIS</B>
+<P>On <B>UltraSPARC</B>s, MPlayer takes advantage of their <B>VIS</B>
   extensions (equivalent to MMX), currently only in <I>libmpeg2</I>,
   <I>libvo</I> and <I>libavcodec</I>, but not in mp3lib. You can watch a VOB
   file on a 400MHz CPU. You'll need
@@ -1402,7 +1402,7 @@
 
 <H2><A NAME="strongarm">6.4 StrongARM</A></H2>
 
-<P><B>MPlayer</B> is reported to compile on StrongARM. Use the following command line:</P>
+<P>MPlayer is reported to compile on StrongARM. Use the following command line:</P>
 
 <PRE>
   ./configure --target=arm-linux --disable-css --with-x11libdir=/usr/arm/lib
@@ -1419,7 +1419,7 @@
 <H2><A NAME="qnx">6.6 QNX</A></H2>
 
 <P>Works. You'll need to download SDL for QNX, and install it. Then run
-  <B>MPlayer</B> with <CODE>-vo sdl:photon</CODE> and <CODE>-ao sdl:nto</CODE>
+  MPlayer with <CODE>-vo sdl:photon</CODE> and <CODE>-ao sdl:nto</CODE>
   options, and it should be fast.</P>
 
 <P>The <CODE>-vo x11</CODE> output will be even slower than on Linux, since
@@ -1437,10 +1437,10 @@
   in PATH and do a '<CODE>gmake -k</CODE>', then make sure that the native
   version is used and do '<CODE>gmake</CODE>'.</P>
 
-<P>To use Win32 DLLs with <B>MPlayer</B> you will need to re-compile the
+<P>To use Win32 DLLs with MPlayer you will need to re-compile the
   kernel with "<CODE>option USER_LDT</CODE>".</P>
 
-<P>If <B>MPlayer</B> complains about not finding '/dev/cdrom' or
+<P>If MPlayer complains about not finding '/dev/cdrom' or
   '/dev/dvd' make a symbolic link, e.g. <CODE>ln -s
   /dev/rcd0c /dev/dvd</CODE></P>
 
@@ -1450,16 +1450,16 @@
 
 <H2><A NAME="cygwin">6.8. Cygwin</A></H2>
  
-<P>You will have to go to the <B>MPlayer</B> directory, and copy or symlink
+<P>You will have to go to the MPlayer directory, and copy or symlink
   <CODE>etc/cygwin_inttypes.h</CODE> to <CODE>/usr/include/inttypes.h</CODE> to
-  make <B>MPlayer</B> compile. Otherwise it will complain about missing
+  make MPlayer compile. Otherwise it will complain about missing
   <CODE>intypes.h</CODE>.</P>
 
 
 
 <H1><A NAME="mailing_lists">Appendix A - Mailing lists</A></H1>
 
-<P>There are some public mailing lists on <B>MPlayer</B>. Unless explicitly
+<P>There are some public mailing lists on MPlayer. Unless explicitly
   stated otherwise the language of these lists is <B>English</B>. Please do
   not send messages in other languages or HTML mail! Message size limit is 80k.
   If you have something bigger put it up for download somewhere. Click the
@@ -1474,7 +1474,7 @@
 <UL>
   <LI>MPlayer developers list:
     <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng</A><BR>
-    This list is about <B>MPlayer</B> development! Talking about interface/API
+    This list is about MPlayer development! Talking about interface/API
     changes, new libraries, code optimization, configure changes is ontopic
     here. Send patches but <B>not</B> bug reports, user questions, feature
     requests or flames here to keep the list traffic low.</LI>
@@ -1511,13 +1511,13 @@
   </LI>
   <LI>MPlayer CVS-log:
     <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog">http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog</A><BR>
-    All changes in <B>MPlayer</B> code are automatically sent to this list. Only
+    All changes in MPlayer code are automatically sent to this list. Only
     questions about these changes belong here (if you do not understand why a
     change is required or you have a better fix or you have noticed a possible
     bug/problem in the commit).</LI>
   <LI>MPlayer Cygwin-porting list:
     <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-cygwin">http://mplayerhq.hu/mailman/listinfo/mplayer-cygwin</A><BR>
-    List for discussion about <B>MPlayer</B>'s Cygwin port.</LI>
+    List for discussion about MPlayer's Cygwin port.</LI>
 </UL>
 
 <P><B>Note:</B> You can reach the searchable mailing list archives at
--- a/DOCS/encoding.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/encoding.html	Sun Oct 20 12:20:39 2002 +0000
@@ -12,7 +12,7 @@
 
 <H2><A NAME="encoding">2.4 Encoding with MEncoder</A></H2>
 
-<P><B>MEncoder</B> (<B>MPlayer</B>'s Movie Encoder) is a simple movie encoder,
+<P>MEncoder (MPlayer's Movie Encoder) is a simple movie encoder,
   designed to encode MPlayer-playable movies
   (<B>AVI/ASF/OGG/DVD/VCD/VOB/MPG/MOV/VIV/FLI/RM/NUV/NET/PVA</B>) to other
   MPlayer-playable formats (see below). It can encode with various codecs, like
@@ -24,7 +24,7 @@
 <H3><A NAME="compilation">2.4.1 Compilation</A></H3>
 
 <UL>
-  <LI><B>OPTIONAL</B> - read <B>MPlayer</B>'s compilation instruction.</LI>
+  <LI><B>OPTIONAL</B> - read MPlayer's compilation instruction.</LI>
   <LI><B>OPTIONAL (LINUX ONLY)</B> - download the newest <B>DivX4linux</B> libs
     from <A HREF="http://avifile.sourceforge.net/download.htm">avifile.sourceforge.net</A>,
     and have them PROPERLY installed. You need them if you want DivX4
@@ -53,13 +53,13 @@
 </UL>
 
 <P>You are ready. As you probably know, other encoding tools need the
-  <I>avifile</I> library installed. <B>MEncoder</B> doesn't need it at all.</P>
+  <I>avifile</I> library installed. MEncoder doesn't need it at all.</P>
 
 
 <H3><A NAME="features">2.4.2 MEncoder features</A></H3>
 
 <UL>
-  <LI>encoding from the wide range of fileformats and decoders of <B>MPlayer</B></LI>
+  <LI>encoding from the wide range of fileformats and decoders of MPlayer</LI>
   <LI>encoding to all the codecs of ffmpeg's
     <A HREF="codecs.html#libavcodec">libavcodec</A></LI>
   <LI>video encoding from <B>V4L compatible TV tuners</B></LI>
@@ -68,7 +68,7 @@
   <LI>1, 2 or 3 pass encoding</LI>
   <LI><B>VBR</B> MP3 audio - <B>IMPORTANT NOTE:</B> VBR MP3 audio doesn't
     always play nicely on Windows players! On the other hand, currently
-    <B>MEncoder</B>'s CBR encoding is totally broken on Win32 players :)</LI>
+    MEncoder's CBR encoding is totally broken on Win32 players :)</LI>
   <LI>PCM audio</LI>
   <LI>stream copying</LI>
   <LI>input A/V synchronizing (PTS-based, can be disabled with -mc 0 option)</LI>
@@ -122,20 +122,20 @@
     <P><CODE>mencoder &lt;file/DVD&gt; -ovc frameno -oac mp3lame -lameopts vbr=3:more_options -o frameno.avi</CODE></P>
     <P>An audio-only avi file will be created, containing
       <B>only</B> the requested audio stream. Don't forget <CODE>-lameopts</CODE>,
-      if you need to set it. If you were encoding a long movie, <B>MEncoder</B>
+      if you need to set it. If you were encoding a long movie, MEncoder
       prints the recommended bitrate values for 650Mb, 700Mb, and 800Mb
       destination sizes, after this pass finishes.</P></LI>
   <LI>Second pass:
     <P><CODE>mencoder &lt;file/DVD&gt; -oac copy -pass 1
       -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=&lt;bitrate&gt;</CODE></P>
     <P>Alias the first pass of DivX4 video encoding. 
-      Optionally specify the video bitrate <B>MEncoder</B> printed at the end of
+      Optionally specify the video bitrate MEncoder printed at the end of
       the previous pass.</P></LI>
   <LI>Third pass:
     <P><CODE>mencoder &lt;file/DVD&gt; -oac copy -pass 2
       -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=&lt;bitrate&gt;</CODE></P>
     <P>Alias the second pass of DivX4 video encoding. 
-      Optionally specify the video bitrate <B>MEncoder</B> printed at the end of
+      Optionally specify the video bitrate MEncoder printed at the end of
       the previous pass. In this pass, audio from <CODE>frameno.avi</CODE> will
       be inserted into the destination file.. and it's all ready!</P></LI>
 </OL>
@@ -187,7 +187,7 @@
 
 <P>The scaling process is handled by the <I>'scale'</I> video filter:
   <CODE>-vop scale=X:Y</CODE>. Its quality can be set with the
-  <CODE>-sws</CODE> option. If it's not specified, <B>MEncoder</B> will use 0:
+  <CODE>-sws</CODE> option. If it's not specified, MEncoder will use 0:
   fast bilinear.</P>
 
 <P>Usage:<BR>
@@ -198,14 +198,14 @@
 
 <H4><A NAME="copying">2.4.2.3 Stream copying</A></H4>
 
-<P><B>MEncoder</B> can handle input streams in two ways: <B>encode</B> or
+<P>MEncoder can handle input streams in two ways: <B>encode</B> or
   <B>copy</B> them. This section is about <B>copying</B>.</P>
 
 <UL>
   <LI><B>Video stream</B> (option <CODE>-ovc copy</CODE>): nice stuff can be
     done :)<BR>
     Like, putting (not converting) FLI or VIVO or MPEG1 video into
-    an AVI file. Of course only <B>MPlayer</B> can play such files :) And it
+    an AVI file. Of course only MPlayer can play such files :) And it
     probably has no real life value at all. Rationally: video stream copying
     can be useful for example when only the audio stream has to be encoded
     (like, uncompressed PCM to MP3).</LI>
@@ -220,7 +220,7 @@
 <H4><A NAME="fixing">2.4.2.4 Fixing AVIs with broken index or interleaving</A></H4>
 
 <P>Easiest thing. We simply copy the video and audio streams, and
-  <B>MEncoder</B> generates the index. Of course this cannot fix possible bugs
+  MEncoder generates the index. Of course this cannot fix possible bugs
   in the video and/or audio streams. It also fixes files with broken
   interleaving, thus the <CODE>-ni</CODE> option won't be needed for them
   anymore.</P>
@@ -255,17 +255,17 @@
 
 <H4><A NAME="image_files">2.4.2.6 Encoding from multiple input image files (JPEGs, PNGs or TGAs)</A></H4>
 
-<P><B>MEncoder</B> is capable of creating movies from one or more JPEG, PNG or TGA
+<P>MEncoder is capable of creating movies from one or more JPEG, PNG or TGA
   files. With simple framecopy it can create MJPEG (Motion JPEG), MPNG
   (Motion PNG) or MTGA (Motion TGA) files.</P>
 
 Explanation of the process:
 
 <OL>
-  <LI><B>MEncoder</B> <I>decodes</I> the input image(s) with
+  <LI>MEncoder <I>decodes</I> the input image(s) with
     <CODE>libjpeg</CODE> (when decoding PNGs, it will use <B>libpng</B>).</LI>
 
-  <LI><B>MEncoder</B> then feeds the decoded image to the chosen video compressor
+  <LI>MEncoder then feeds the decoded image to the chosen video compressor
     (DivX4, Xvid, ffmpeg msmpeg4, etc...). Watch for the PNG decoder, as
     currently it can output only to RGB formats, thus can't be used with codecs
     that require YUV as input, like DivX4 or ffmpeg's msmpeg4.</LI>
@@ -303,10 +303,10 @@
 
 <H4><A NAME="vobsub">2.4.2.7 Extracting DVD subtitles to Vobsub file</A></H4>
 
-<P><B>MEncoder</B> is capable of extracting subtitles from a DVD into
+<P>MEncoder is capable of extracting subtitles from a DVD into
   Vobsub fomat files. They consist of a pair of files ending in
   <CODE>.idx</CODE> and <CODE>.sub</CODE> and are usually packaged in a single
-  <CODE>.rar</CODE> archive. <B>MPlayer</B> can play these with the
+  <CODE>.rar</CODE> archive. MPlayer can play these with the
   <CODE>-vobsub</CODE> and <CODE>-vobsubid</CODE> options.</P>
 
 <P>You specify the basename (i.e without the <CODE>.idx</CODE> or
@@ -344,7 +344,7 @@
 
 <H3><A NAME="options">2.4.3 Available options</A></H3>
 
-<P>For the complete list of available <B>MEncoder</B> options and examples,
+<P>For the complete list of available MEncoder options and examples,
   please see the man page.</P>
 
 </BODY>
--- a/DOCS/faq.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/faq.html	Sun Oct 20 12:20:39 2002 +0000
@@ -145,7 +145,7 @@
 
   <DT>Q: It doesn't compile, and it misses uint64_t inttypes.h and similar
     things ...</DT>
-  <DD>A: Copy etc/inttypes.h to the <B>MPlayer</B> directory
+  <DD>A: Copy etc/inttypes.h to the MPlayer directory
     (<CODE>cp etc/inttypes.h .</CODE>) and try again ...</DD>
   <DD>&nbsp;</DD>
 
@@ -159,7 +159,7 @@
   <DD>A: Read the <A HREF="video.html#mga_vid">mga_vid documentation</A>.</DD>
   <DD>&nbsp;</DD>
 
-  <DT>Q: Are there rpm/deb/... packages of <B>MPlayer</B>?</DT>
+  <DT>Q: Are there rpm/deb/... packages of MPlayer?</DT>
   <DD>A: You can make a .deb package for yourself, check the
     <A HREF="documentation.html#debian">Debian packaging</A> section.
     There are links to official Red Hat RPM packages available on our
@@ -198,10 +198,10 @@
     <CODE>Warning: loading mga_vid.o will taint the kernel: no license</CODE></DT>
   <DD>A: The latest kernel modutils require a flag indicating the license
     (mainly to avoid kernel hackers debugging closed source drivers).
-    Upgrade your kernel, modutils and <B>MPlayer</B>.</DD>
+    Upgrade your kernel, modutils and MPlayer.</DD>
   <DD>&nbsp;</DD>
   
-    <DT>Q: When compiling <B>MEncoder</B>, it segfaults at linking!</DT>
+    <DT>Q: When compiling MEncoder, it segfaults at linking!</DT>
     <DD>A: This is a linker problem. Upgrading binutils should help (2.11.92.*
       or newer should be good). Since it is not our fault, please do <B>not</B>
       report!</DD>
@@ -211,7 +211,7 @@
     <DD>A: chmod 644 /usr/lib/libc.so</DD>
     <DD>&nbsp;</DD>
   
-    <DT>Q: I'd like to compile <B>MPlayer</B> on Minix!</DT>
+    <DT>Q: I'd like to compile MPlayer on Minix!</DT>
     <DD>A: Me too. :)</DD>
 
 </DL>
@@ -221,18 +221,18 @@
 
 <DL>
 
-  <DT>Q: How do I create a proper patch for <B>MPlayer</B>?</DT>
+  <DT>Q: How do I create a proper patch for MPlayer?</DT>
   <DD>A: We made a <A HREF="tech/patches.txt">short document</A> describing
     all the necessary details. Please follow the instructions.</DD>
   <DD>&nbsp;</DD>
 
-  <DT>Q: How can I support <B>MPlayer</B> development?</DT>
+  <DT>Q: How can I support MPlayer development?</DT>
   <DD>A: We are more than happy to accept your hardware and software
     <A HREF="http://www.mplayerhq.hu/homepage/donations.html">donations</A>.
-    They help us in continuously improving <B>MPlayer</B>.</DD>
+    They help us in continuously improving MPlayer.</DD>
   <DD>&nbsp;</DD>
 
-  <DT>Q: How can I become an <B>MPlayer</B> developer?</DT>
+  <DT>Q: How can I become an MPlayer developer?</DT>
   <DD>A: We always welcome coders and documenters.  Read the
     <A HREF="tech/">technical documentation</A> to get a first grasp. Then you
     should subscribe to the
@@ -240,7 +240,7 @@
     mailing list and start coding.</DD>
   <DD>&nbsp;</DD>
 
-  <DT>Q: Can I run multiple instances of <B>MPlayer</B>?</DT>
+  <DT>Q: Can I run multiple instances of MPlayer?</DT>
   <DD>A: Yes. Some video out drivers like xv, dga or (x)mga are exclusive, some
     are exclusive in combination with certain graphics boards and drivers. You
     will not be able to run more than one instance of MPlayer with one of those
@@ -398,16 +398,16 @@
     </PRE>
   </DT>
   <DD>A: Probably the audio uses a codec not natively supported by
-    <B>MPlayer</B>. Install the Win32 codec package as described in the README
+    MPlayer. Install the Win32 codec package as described in the README
     or in the <A HREF="documentation.html#installation">Installation</A> section.</DD>
   <DD>&nbsp;</DD>
 
   <DT>Q: ... works with avifile/aviplay but doesn't with MPlayer.</DT>
-  <DD>A: <B>MPlayer</B> is not avifile.
+  <DD>A: MPlayer is not avifile.
     The only common thing between these players is the Win32 DLL loader.
     The codecs (DLL) set, synchronization, demultiplexing etc is totally
     different and shouldn't be compared.
-    If something works with aviplay it doesn't mean that <B>MPlayer</B> will
+    If something works with aviplay it doesn't mean that MPlayer will
     work and vice versa.</DD>
   <DD>&nbsp;</DD>
 
@@ -426,7 +426,7 @@
     forces loading libraries to very low addresses.
     Because l3codeca.acm is a non-relocatable DLL, it must be loaded to
     0x00400000, we can't change this. You should use a non-patched kernel,
-    or use <B>MPlayer</B>'s <CODE>-afm 1</CODE> option to disable using
+    or use MPlayer's <CODE>-afm 1</CODE> option to disable using
     l3codeca.acm.</DD>
   <DD>&nbsp;</DD>
 
@@ -439,10 +439,10 @@
 
   <DT>Q: MPlayer dies with "MPlayer interrupted by signal 4 in module:
     decode_video".</DT>
-  <DD>A: Try running <B>MPlayer</B> on the machine you compiled on. Or recompile
+  <DD>A: Try running MPlayer on the machine you compiled on. Or recompile
     with runtime CPU detection
     (<CODE>./configure --enable-runtime-cpudetection</CODE>). Don't
-    use <B>MPlayer</B> on a CPU different from the one it was compiled on,
+    use MPlayer on a CPU different from the one it was compiled on,
     without using the feature mentioned just now.</DD>
   <DD>&nbsp;</DD>
 
@@ -467,7 +467,7 @@
     want to use arts sound, specify audio output via our native arts audio
     driver (<CODE>-ao arts</CODE>). If it fails or isn't compiled in, try SDL
     (<CODE>-ao sdl</CODE>) and make sure your SDL can handle arts sound. Yet
-    another option is to start <B>MPlayer</B> with artsdsp.</DD>
+    another option is to start MPlayer with artsdsp.</DD>
   <DD>&nbsp;</DD>
 
   <DT>Q: I have an AVI that produces a gray screen when played with
@@ -481,7 +481,7 @@
   <DD>A: This can have multiple reasons.
     <UL>
       <LI>Your CPU <B>and/or</B> video card <B>and/or</B> bus is too slow.
-        <B>MPlayer</B> displays a message if this is the case (and the dropped
+        MPlayer displays a message if this is the case (and the dropped
         frames counter goes up fast).</LI>
       <LI>If it is an AVI, maybe it has bad interleaving. Try the
         <CODE>-ni</CODE> option.</LI>
@@ -560,7 +560,7 @@
   </DT>
   <DD>A: Are you running KDE or GNOME with the arts or esd sound daemon? Try
     disabling the sound daemon, or use the <CODE>-ao arts</CODE> switch to make
-    <B>MPlayer</B> use arts.</DD>
+    MPlayer use arts.</DD>
   <DD>&nbsp;</DD>
 
   <DT>Q: What about the DGA driver? I can't find it!</DT>
@@ -575,7 +575,7 @@
     permissions. Help me!</DT>
   <DD>A: It works only if running as root! It's a DGA limitation.
     You should become root (<CODE>su -</CODE>), and try again.
-    Another solution is making <B>MPlayer</B> SUID root, but it's
+    Another solution is making MPlayer SUID root, but it's
     <B>not recommended!</B><BR>
     &nbsp;&nbsp;&nbsp;&nbsp;<CODE>chown root /usr/local/bin/mplayer</CODE><BR>
     &nbsp;&nbsp;&nbsp;&nbsp;<CODE>chmod 755 /usr/local/bin/mplayer</CODE><BR>
@@ -584,7 +584,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 you do not control completely because other users can
-      gain root privileges through SUID root <B>MPlayer</B>. <B>You have been
+      gain root privileges through SUID root MPlayer. <B>You have been
       warned.</B>
     </BLOCKQUOTE>
   </DD>
@@ -670,7 +670,7 @@
   <DD>A: Who knows ... It's said to work, so please test it and send feedback.
     Refer to the documentation of libdvdread and its homepage as well. We're not
     the authors of libdvdread. Use <B>libmpdvdkit2</B>, which is present in
-    <B>MPlayer</B> source, and used by default.</DD>
+    MPlayer source, and used by default.</DD>
   <DD>&nbsp;</DD>
 
   <DT>Q: What about subtitles? Can MPlayer display them?</DT>
@@ -713,8 +713,8 @@
 
 <DL>
 
-  <DT>Q: If <B>MPlayer</B> is paused and I try to seek or press any key at all,
-    <B>MPlayer</B> ceases to be paused. I would like to be able to seek in the
+  <DT>Q: If MPlayer is paused and I try to seek or press any key at all,
+    MPlayer ceases to be paused. I would like to be able to seek in the
     paused movie.</DT>
   <DD>A: This is very tricky to implement without losing A/V synchronization.
     All attempts have failed so far, but patches are welcome.</DD>
@@ -740,7 +740,7 @@
 <DL>
 
   <DT>Q: How can I encode?</DT>
-  <DD>A: Read the <B>MEncoder</B> <A HREF="encoding.html">documentation</A>.</DD>
+  <DD>A: Read the MEncoder <A HREF="encoding.html">documentation</A>.</DD>
   <DD>&nbsp;</DD>
 
   <DT>Q: How can I create VCDs?</DT>
--- a/DOCS/formats.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/formats.html	Sun Oct 20 12:20:39 2002 +0000
@@ -74,7 +74,7 @@
   encourages ASF/WMV. Not that anybody cares.</P>
 
 <P>There is a hack that allows AVI files to contain an Ogg Vorbis audio
-  stream, but makes them incompatible with standard AVI. <B>MPlayer</B>
+  stream, but makes them incompatible with standard AVI. MPlayer
   supports playing these files. Seeking is also implemented but severely
   hampered by badly encoded files with confusing headers. Unfortunately the
   only encoder currently capable of creating these files, NanDub, has this
@@ -82,14 +82,14 @@
 
 <P><B>Note:</B> DV cameras create raw DV streams that DV grabbing utilities
   convert to two different types of AVI files. The AVI will then contain either
-  separate audio and video streams that <B>MPlayer</B> can play or the raw DV
+  separate audio and video streams that MPlayer can play or the raw DV
   stream for which support is under development.</P>
 
 <P>There are two kinds of AVI files:</P>
 <UL>
   <LI><B>Interleaved:</B> Audio and video content is interleaved. This is the
     standard usage. Recommended and mostly used. Some tools create 
-    non-interleaved AVIs with bad sync. <B>MPlayer</B> detects these as
+    non-interleaved AVIs with bad sync. MPlayer detects these as
     interleaved, and this climaxes in loss of A/V sync, probably at seeking.
     These files should be played as non-interleaved (with the <CODE>-ni</CODE>
     option).</LI>
@@ -98,7 +98,7 @@
     CD-Rom difficult. (should be played with the <CODE>-ni</CODE> option)</LI>
 </UL>
 
-<P><B>MPlayer</B> supports two kinds of timings for AVI files:</P>
+<P>MPlayer supports two kinds of timings for AVI files:</P>
 <UL>
   <LI><B>bps-based</B>: It is based on the bitrate/samplerate of the video/audio stream. This
     method is used by most players, including <A HREF="http://avifile.sourceforge.net">avifile</A>
@@ -125,7 +125,7 @@
   variants of ASF, v1.0 and v2.0. v1.0 is used by their media tools (Windows
   Media Player and Windows Media Encoder) and is very secret. v2.0 is published
   and patented :). Of course they differ, there is no compatibility at all (it
-  is just another legal game). <B>MPlayer</B> supports only v1.0, as nobody has
+  is just another legal game). MPlayer supports only v1.0, as nobody has
   ever seen v2.0 files :). Note that ASF files nowadays come with the extension
   .WMA or .WMV.</P>
 
@@ -147,7 +147,7 @@
 
 <H4><A NAME="vivo">2.1.1.5 VIVO files</A></H4>
 
-<P><B>MPlayer</B> happily demuxes VIVO file formats. The biggest disadvantage
+<P>MPlayer happily demuxes VIVO file formats. The biggest disadvantage
   of the format is that it has no index block, nor a fixed packet size or sync
   bytes and most files lack even keyframes, so forget seeking!</P>
 
@@ -163,7 +163,7 @@
 <H4><A NAME="fli">2.1.1.6 FLI files</A></H4>
 
 <P><B>FLI</B> is a very old file format used by Autodesk Animator, but it is a
-  common file format for short animations on the net. <B>MPlayer</B> demuxes
+  common file format for short animations on the net. MPlayer demuxes
   and decodes FLI movies and is even able to seek within them (useful when
   looping with the <CODE>-loop</CODE> option). FLI files do not have keyframes,
   so the picture will be messy for a short time after seeking.</P>
@@ -171,7 +171,7 @@
 
 <H4><A NAME="real">2.1.1.7 RealMedia (RM) files</A></H4>
 
-<P>Yes, <B>MPlayer</B> can read (demux) RealMedia (.rm) files. Seeking works,
+<P>Yes, MPlayer can read (demux) RealMedia (.rm) files. Seeking works,
   but you have to explicitly specify the <CODE>-forceidx</CODE> option
   (the format supports keyframes). Here are the lists of the supported
   <A HREF="codecs.html#realvideo">RealVideo</A>
@@ -181,11 +181,11 @@
 <H4><A NAME="nuppelvideo">2.1.1.8 NuppelVideo files</A></H4>
 
 <P><A HREF="http://mars.tuwien.ac.at/~roman/nuppelvideo">NuppelVideo</A>
-  is a TV grabber tool (AFAIK:). <B>MPlayer</B> can read its .NUV files (only
+  is a TV grabber tool (AFAIK:). MPlayer can read its .NUV files (only
   NuppelVideo 5.0). Those files can contain uncompressed YV12, YV12+RTJpeg
   compressed, YV12 RTJpeg+lzo compressed, and YV12+lzo compressed frames.
-  <B>MPlayer</B> decodes them all (and also <B>encodes</B> them with
-  <B>MEncoder</B> to DivX/etc!). Seeking works.</P>
+  MPlayer decodes them all (and also <B>encodes</B> them with
+  MEncoder to DivX/etc!). Seeking works.</P>
 
 
 <H4><A NAME="yuv4mpeg">2.1.1.9 yuv4mpeg files</A></H4>
@@ -213,7 +213,7 @@
 <P>This is a new file format from <A HREF="http://www.xiph.org">Xiphophorus</A>.
   It can contain any video or audio codec, CBR or VBR. You will need to
   have <CODE>libogg</CODE> and <CODE>libvorbis</CODE> installed
-  before compiling <B>MPlayer</B> to be able to play it.</P>
+  before compiling MPlayer to be able to play it.</P>
 
 
 <H4><A NAME="sdp">2.1.1.13 SDP files</A></H4>
@@ -226,15 +226,15 @@
 
 <H3><A NAME="audio_formats">2.1.2 Audio formats</A></H3>
 
-<P><B>MPlayer</B> is a <B>Movie</B> and not a <B>Media</B> player, although
+<P>MPlayer is a <B>Movie</B> and not a <B>Media</B> player, although
   it can play some audio file formats (they are listed in the sections below).
-  This is not a recommended usage of <B>MPlayer</B>, you better use
+  This is not a recommended usage of MPlayer, you better use
   <A HREF="http://www.xmms.org">xmms</A>.</P>
 
 
 <H4><A NAME="mp3">2.1.2.1 MP3 files</A></H4>
 
-<P>You may have problems playing certain MP3 files that <B>MPlayer</B> will
+<P>You may have problems playing certain MP3 files that MPlayer will
   misdetect as MPEGs and play incorrectly or not at all. This cannot be fixed
   without dropping support for certain broken MPEG files and thus will remain
   like this for the foreseeable future. The <CODE>-demuxer</CODE> flag
--- a/DOCS/mplayer.1	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/mplayer.1	Sun Oct 20 12:20:39 2002 +0000
@@ -582,7 +582,7 @@
 
 .I NOTE:
 .br
-Mplayer doesn't accept colons so type dots instead in the device ID
+MPlayer doesn't accept colons so type dots instead in the device ID
 (e.g.\& hw.0,0 instead of hw:0,0).
 .br
 Be advised that although you can select any samplerate when using ALSA,
--- a/DOCS/skin.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/skin.html	Sun Oct 20 12:20:39 2002 +0000
@@ -55,7 +55,7 @@
 
 <h2><a name="intro">1 Introduction</a></h2>
 
-The purpose of this document is to describe the <b>MPlayer</b> skin format.
+The purpose of this document is to describe the MPlayer skin format.
 The information contained here might be wrong, for
 
 <ol type="a">
@@ -78,7 +78,7 @@
 <h2><a name="overview">2 Overview</a></h2>
 
 It does not really have anything to do with the skin format, but you should
-know that <b>MPlayer</b> has <b>no</b> builtin skin, so <b>at least one skin
+know that MPlayer has <b>no</b> builtin skin, so <b>at least one skin
 must be installed in order to be able to use the GUI.</b>
 
 
@@ -92,7 +92,7 @@
 </pre>
 
 <p>
-Note that the first path may vary according to the way <b>MPlayer</b> was
+Note that the first path may vary according to the way MPlayer was
 configured (see the <code>--prefix</code> and  <code>--datadir</code> arguments
 of the <code>configure</code> script).
 </p>
@@ -112,7 +112,7 @@
 <p>
 In the main window (see below) you can use images with `transparency':
 Regions filled with the color #FF00FF (<font color="#FF00FF">magenta</font>)
-are fully transparent when viewed by <b>MPlayer</b>. This means that you can even
+are fully transparent when viewed by MPlayer. This means that you can even
 have shaped windows if your X server has the XShape extension.
 </p>
 
@@ -131,7 +131,7 @@
 
 <ul>
 <li>
-The <b>main window</b> is where you can control <b>MPlayer</b>. The background of
+The <b>main window</b> is where you can control MPlayer. The background of
 the window is an image. Various items can (and must) be
 placed in the window: <em>buttons</em>, <em>potmeters</em> (sliders) and
 <em>labels</em>. For every item, you must
@@ -179,7 +179,7 @@
 </li>
 
 <li>
-The <b>skin menu</b> is just a way to control <b>MPlayer</b> by means of
+The <b>skin menu</b> is just a way to control MPlayer by means of
 menu entries. Two images are required for the menu: one of them is the base
 image that shows the menu in its normal state, the other one is used to
 display the selected entries. When you pop up the menu, the first image is
@@ -195,7 +195,7 @@
 
 <p>
 There is an important thing not mentioned yet: For buttons, potmeters and
-menu entries to work, <b>MPlayer</b> must know what to do if they are clicked.
+menu entries to work, MPlayer must know what to do if they are clicked.
 This is done by <a href="#guimsg">messages</a> (events). For these items
 you must define the messages to be generated when they are clicked.
 </p>
@@ -205,7 +205,7 @@
 You need the following files to build a skin:
 <ul>
 <li>
-The configuration file named <a href="#skin">skin</a> tells <b>MPlayer</b> how
+The configuration file named <a href="#skin">skin</a> tells MPlayer how
 to put different parts of the skin together and what to do if you click
 somewhere in the window.
 </li>
@@ -315,7 +315,7 @@
 <p>
 The name of an image file must be given without leading directories - images are
 searched for in the <code>Skin</code> directory. You may (but you need not)
-specify the extension of the file. If the file does not exist, <b>MPlayer</b>
+specify the extension of the file. If the file does not exist, MPlayer
 tries to load the file <code>&lt;filename&gt;.&lt;ext&gt;</code>, where
 <code>tga</code>, <code>TGA</code>, <code>bmp</code>, <code>BMP</code>,
 <code>png</code> and <code>PNG</code> is tried for <code>&lt;ext&gt;</code>
@@ -350,7 +350,7 @@
 </pre>
 </blockquote>
 
-<b>MPlayer</b> tries to load <code>main</code>, <code>main.tga</code>,
+MPlayer tries to load <code>main</code>, <code>main.tga</code>,
 <code>main.TGA</code>, <code>main.bmp</code> etc, so that <code>main.png</code>
 will be found.
 <br>
@@ -361,7 +361,7 @@
 </pre>
 </blockquote>
 then <code>main.bmp</code>, <code>main.bmp.tga</code>, <code>main.bmp.TGA</code>,
-<code>main.bmp.bmp</code> would be searched for and <b>MPlayer</b> would finally
+<code>main.bmp.bmp</code> would be searched for and MPlayer would finally
 give up because there is no <code>main.bmp</code> in the directory, only
 <code>main.png</code>.
 </td></tr></table>
--- a/DOCS/sound.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/sound.html	Sun Oct 20 12:20:39 2002 +0000
@@ -12,7 +12,7 @@
 
 <H3><A NAME="audio">2.3.2 Audio output devices</A></H3>
 
-<P><B>MPlayer</B>'s audio interface is called <I>libao2</I>. It currently
+<P>MPlayer's audio interface is called <I>libao2</I>. It currently
   contains these drivers:</P>
 
 <TABLE BORDER=0>
@@ -128,17 +128,17 @@
 
 <P>Sharing your sound card with another application like XMMS is <B>strongly
   discouraged</B>!  If the other sound application is using ESD, start
-  <B>MPlayer</B> with the <CODE>-vo sdl:esd</CODE> option to combine both
+  MPlayer with the <CODE>-vo sdl:esd</CODE> option to combine both
   sound streams. In fact, the option <CODE>-vo sdl:esd</CODE> could be used
-  with ESD even when playing <B>Mplayer</B> alone.</P>
+  with ESD even when playing MPlayer alone.</P>
 
-<P>Feedback to this document is welcome. Please tell us how <B>MPlayer</B>
+<P>Feedback to this document is welcome. Please tell us how MPlayer
   and your sound card(s) worked together.</P>
 
 
 <H4><A NAME="plugins">2.3.2.2 Audio plugins</A></H4>
 
-<P><B>MPlayer</B> has support for audio plugins. Audio plugins can be used for
+<P>MPlayer has support for audio plugins. Audio plugins can be used for
   changing the properties of the audio data before the sound reaches the sound
   card. They are enabled using the <CODE>-aop</CODE> switch which takes a
   <CODE>list=plugin1,plugin2,...</CODE> argument. The <CODE>list</CODE> argument
@@ -161,12 +161,12 @@
 <P>would set the output frequency of the resample plugin to 44100Hz and the
   output format of the format plugin to AFMT_U8.</P>                         
 
-<P>Currently audio plugins can not be used in <B>MEncoder</B>.</P>
+<P>Currently audio plugins can not be used in MEncoder.</P>
 
 
 <H5><A NAME="resample">2.3.2.2.1 Up/Downsampling</A></H5>
 
-<P><B>MPlayer</B> fully supports up/downsampling of the sound. This plugin can
+<P>MPlayer fully supports up/downsampling of the sound. This plugin can
   be used if you have a fixed frequency sound card or if you are
   stuck with an old sound card that is only capable of max 44.1kHz.
   Limitations in your hardware are not auto detected, so you have to specify
@@ -186,7 +186,7 @@
 
 <H5><A NAME="surround_decoding">2.3.2.2.2 Surround Sound decoding</A></H5>
 
-<P><B>MPlayer</B> has an audio plugin that can decode matrix encoded
+<P>MPlayer has an audio plugin that can decode matrix encoded
   surround sound. Dolby Surround is an example of a matrix encoded format.
   Many files with 2 channel audio actually contain matrixed surround sound.
   To use this feature you need a sound card supporting at least 4 channels.</P>
@@ -222,7 +222,7 @@
 
 <P>This plugin is a software replacement for the volume control, and
   can be used on machines with a broken mixer device. It can also be
-  used if one wants to change the output volume of <B>MPlayer</B>
+  used if one wants to change the output volume of MPlayer
   without changing the PCM volume setting in the mixer. It has one
   switch <CODE>volume</CODE> that is used for setting the initial
   sound level. The initial sound level can be set to values between 0
--- a/DOCS/users_against_developers.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/users_against_developers.html	Sun Oct 20 12:20:39 2002 +0000
@@ -43,7 +43,7 @@
   <A HREF="http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html">
   Linux kernel news flash about kernel 2.4.17</A> and
   <A HREF="http://www.voy.com/3516/572.html">Voy Forum</A>.
-  <B>MPlayer</B> also suffered from intermittent problems that were all solved by
+  MPlayer also suffered from intermittent problems that were all solved by
   switching to a different version of GCC. Several projects started implementing
   workarounds for some of the 2.96 issues, but we refused to fix other people's
   bugs, especially since some workarounds may imply a performance penalty.</P>
@@ -77,7 +77,7 @@
 <OL>
   <LI>Go to the <A HREF="http://gcc.gnu.org/mirrors.html">GCC mirrors page</A>
     page and download <CODE>gcc-core-3.1.tar.gz</CODE>.  This includes the
-    complete C compiler and is sufficient for <B>MPlayer</B>. If you also want
+    complete C compiler and is sufficient for MPlayer. If you also want
     C++, Java or some of the other advanced GCC features
     <CODE>gcc-3.1.tar.gz</CODE> may better suit your needs.</LI>
   <LI>Extract the archive with<BR>
@@ -100,12 +100,12 @@
 <H2><A NAME="binary">Binary distribution</A></H2>
 
 <P>This was the second big problem but has been solved as of version
-  0.90-pre1. <B>MPlayer</B> previously contained source from the OpenDivX project,
+  0.90-pre1. MPlayer previously contained source from the OpenDivX project,
   which disallows binary redistribution. This code has been removed and you are now
   welcome to create binary packages as you see fit.</P>
 
 <P>Another impediment to binary redistribution was compiletime optimizations
-  for CPU architecture.  <B>MPlayer</B> now supports runtime CPU detection
+  for CPU architecture.  MPlayer now supports runtime CPU detection
   (specify the <CODE>--enable-runtime-cpudetection</CODE> option when
   compiling). It is disabled by default because it implies a small speed
   sacrifice, it is now possible to create binaries that run on different
@@ -138,12 +138,12 @@
 
 <P>Joe Barr became infamous by writing a less than favorable
   <A HREF="http://www.linuxworld.com/site-stories/2001/1214.mplayer.html">
-  <B>MPlayer</B> review</A>. He found <B>MPlayer</B> hard to install, but then
+  MPlayer review</A>. He found MPlayer hard to install, but then
   again he is not very fond of
   <A HREF="http://www.linuxworld.com/linuxworld/lw-2000-06/lw-06-exam.html">reading documentation</A>.
   He also concluded that the developers were unfriendly and the documentation
   incomplete and insulting. You be the judge.
-  He went on to mention <B>MPlayer</B> negatively in his
+  He went on to mention MPlayer negatively in his
   <A HREF="http://www.linuxworld.com/site-stories/2001/1227.predictions.html">10 Linux predictions for 2002</A>
   In a followup
   <A HREF="http://www.linuxworld.com/site-stories/2002/0125.xine.html">review of xine</A>
@@ -153,7 +153,7 @@
 
 <BLOCKQUOTE>
   However, he also went on to say that he was "surprised" by my column about
-  Mplayer and thought it was unfair, reminding me that it is a free software
+  MPlayer and thought it was unfair, reminding me that it is a free software
   project. "If you don't like it," Bartsch said, "you're free not to use it." 
 </BLOCKQUOTE>
 
--- a/DOCS/video.html	Sun Oct 20 11:34:06 2002 +0000
+++ b/DOCS/video.html	Sun Oct 20 12:20:39 2002 +0000
@@ -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 @@
     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 @@
 <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 @@
   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 @@
   <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 @@
 
 <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 @@
 
 <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 @@
   <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 @@
 <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 @@
   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 @@
         <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 @@
     <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>