[Mplayer-cvslog] CVS: main/DOCS formats.html,1.46,1.47 video.html,1.109,1.110

Diego Biurrun CVS diego at mplayerhq.hu
Wed Oct 30 00:37:48 CET 2002


Update of /cvsroot/mplayer/main/DOCS
In directory mail:/var/tmp.root/cvs-serv28572

Modified Files:
	formats.html video.html 
Log Message:
<B>MPlayer</B> --> MPlayer


Index: formats.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/formats.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- formats.html	22 Oct 2002 20:45:51 -0000	1.46
+++ formats.html	29 Oct 2002 23:37:45 -0000	1.47
@@ -89,7 +89,7 @@
 <UL>
   <LI><B>Interleaved:</B> Audio and video content is interleaved. This is the
     standard usage. Recommended and mostly used. Some tools create 
-    interleaved AVIs with bad sync. <B>MPlayer</B> detects these as
+    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>

Index: video.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/video.html,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -r1.109 -r1.110
--- video.html	29 Oct 2002 01:41:16 -0000	1.109
+++ video.html	29 Oct 2002 23:37:45 -0000	1.110
@@ -1178,7 +1178,7 @@
     programs hogging the CPU, it will not drop frames unless applications hog
     the CPU for a long time.<BR>
     When running without prebuffering the em8300 is much more sensitive to CPU
-    load, so it is highly suggested that you turn on <B>MPlayer's</B>
+    load, so it is highly suggested that you turn on MPlayer's
     <CODE>-framedrop</CODE> option to avoid further loss of sync.<BR>
     <CODE>sync</CODE> will turn on the new sync-engine. This is currently an
     experimental feature. With the sync feature turned on the em8300's internal
@@ -1318,7 +1318,7 @@
   configuration: the first CRTC chip (with much more features) on the first
   display (on monitor), and the second CRTC (no <B>BES</B> - for explanation 
   on BES, please see the G400 section above) on TV. So you can only use
-  <B>MPlayer's</B> <I>fbdev</I> output driver at the present.</P>
+  MPlayer's <I>fbdev</I> output driver at the present.</P>
 
 <P>The first CRTC can't be routed to the second head currently.
   The author of the kernel matroxfb driver - Petr Vandrovec - will maybe make




More information about the MPlayer-cvslog mailing list