<application> attack

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

1 files changed, 32 insertions, 28 deletions

diff --git a/DOCS/xml/en/video.xml b/DOCS/xml/en/video.xml
index 5dcf686133..7e7302b47d 100644
--- a/DOCS/xml/en/video.xml
+++ b/DOCS/xml/en/video.xml
@@ -219,9 +219,10 @@ Complain to nVidia.
 </para>
 
 <para>
-However, MPlayer contains a <link linkend="vidix">VIDIX</link> driver for most
-nVidia cards. Currently it is in beta stage, and has some drawbacks.  For more
-information, see <link linkend="vidix-nvidia">nVidia VIDIX</link> section.
+However, <application>MPlayer</application> contains a
+<link linkend="vidix">VIDIX</link> driver for most nVidia cards. Currently it
+is in beta stage, and has some drawbacks. For more information, see
+<link linkend="vidix-nvidia">nVidia VIDIX</link> section.
 </para>
 </sect5>
 
@@ -288,8 +289,8 @@ support with the Cyberblade XP card.
 </para>
 
 <para>
-Alternatively, MPlayer contains a <link linkend="vidix">VIDIX</link> driver
-for the Cyberblade/i1 card.
+Alternatively, <application>MPlayer</application> contains a
+<link linkend="vidix">VIDIX</link> driver for the Cyberblade/i1 card.
 </para>
 
 </sect5>
@@ -1708,8 +1709,8 @@ for a 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1
 <title>Using your DVB card for watching Digital TV (DVB input module)</title>
 <para>
   First you need to pass the <literal>dvb_shutdown_timeout=0</literal>
-  parameter to the kernel module <filename>dvb-core</filename>, or MPlayer
-  will die after 10 seconds.
+  parameter to the kernel module <filename>dvb-core</filename>, or
+  <application>MPlayer</application> will die after 10 seconds.
 </para>
 </formalpara>
 
@@ -1733,8 +1734,8 @@ for a 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1
 
 <para>
   Make sure that you have have <emphasis>only</emphasis> Free to Air
-  channels in your <filename>channels.conf</filename> file, or MPlayer
-  will hang on the others.
+  channels in your <filename>channels.conf</filename> file, or
+  <application>MPlayer</application> will hang on the others.
 </para>
 
 <para>
@@ -1810,7 +1811,8 @@ decompression).
 
 <sect4 id="dxr2">
 <title>DXR2</title>
-<para>MPlayer supports hardware accelerated playback with the Creative DXR2 card.</para>
+<para><application>MPlayer</application> supports hardware accelerated playback
+  with the Creative DXR2 card.</para>
 <para>
 First of all you will need properly installed DXR2 drivers. You can find
 the drivers and installation instructions at the
@@ -1874,25 +1876,27 @@ that you have a properly configured overlay setup to work right. The easiest
 way to configure the overlay is to first run autocal. Then run mplayer with
 dxr3 output and without overlay turned on, run dxr3view. In dxr3view you can
 tweak the overlay settings and see the effects in realtime, perhaps this feature
-will be supported by the MPlayer GUI in the future. When overlay is properly set
-up you will no longer need to use dxr3view.
+will be supported by the <application>MPlayer</application> GUI in the future.
+When overlay is properly set up you will no longer need to use dxr3view.
 <option>prebuf</option> turns on 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 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 MPlayer will not
-have to reencode it to MPEG it will fill the buffer very fast.
+means that when you are running with prebuffering <application>MPlayer</application>
+will try to keep the video buffer filled with data at all times. If you are on
+a slow machine <application>MPlayer</application> 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 <application>MPlayer</application> will not have
+to reencode it to MPEG it will fill the buffer very fast.
 With prebuffering video playback is <emphasis role="bold">much</emphasis>
 less sensitive to other programs hogging the CPU, it will not drop frames unless
 applications hog the CPU for a long time.
 When running without prebuffering the em8300 is much more sensitive to CPU load,
-so it is highly suggested that you turn on MPlayer's <option>-framedrop</option>
-option to avoid further loss of sync.
+so it is highly suggested that you turn on <application>MPlayer's</application>
+<option>-framedrop</option> option to avoid further loss of sync.
 <option>sync</option> will turn on the new sync-engine. This is currently an
 experimental feature. With the sync feature turned on the em8300's internal clock
-will be monitored at all times, if it starts to deviate from MPlayer's clock it
-will be reset causing the em8300 to drop any frames that are lagging behind.
+will be monitored at all times, if it starts to deviate from
+<application>MPlayer's</application> clock it will be reset causing the em8300 to
+drop any frames that are lagging behind.
 <option>norm=x</option> will set the TV norm of the DXR3 card without the need
 for external tools like em8300setup. Valid norms are 5 = NTSC, 4 = PAL-60,
 3 = PAL. Special norms are 2 (auto-adjust using PAL/PAL-60) and 1 (auto-adjust
@@ -1948,11 +1952,11 @@ becomes stable. For now all we can do is accept this for a fact.
 <term><option>-vf expand=-1:-1:-1:-1:1</option></term>
 <listitem><para>
 Although the DXR3 driver can put some OSD onto the MPEG1/2/4 video, it has
-much lower quality than MPlayer's traditional OSD, and has several refresh
-problems as well. The command line above will firstly convert the input
-video to MPEG4 (this is mandatory, sorry), then apply an expand filter which
-won't expand anything (-1: default), but apply the normal OSD onto the picture
-(that's what the "1" at the end does).
+much lower quality than <application>MPlayer's</application> traditional OSD,
+and has several refresh problems as well. The command line above will firstly
+convert the input video to MPEG4 (this is mandatory, sorry), then apply an
+expand filter which won't expand anything (-1: default), but apply the normal
+OSD onto the picture (that's what the "1" at the end does).
 </para></listitem>
 </varlistentry>
 
@@ -2054,8 +2058,8 @@ participating in <emphasis>cinerama</emphasis> is four, so you can build a
 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
 <emphasis role="bold">FIRST</emphasis> start XawTV, <emphasis role="bold">THEN</emphasis>
-start MPlayer, wait for MPlayer to finish and <emphasis role="bold">THEN</emphasis>
-stop XawTV.
+start <application>MPlayer</application>, wait for <application>MPlayer</application>
+to finish and <emphasis role="bold">THEN</emphasis> stop XawTV.
 </para>
 </sect4>