[MPlayer-dev-eng] [PATCH] DOCS/tech/codecs.conf.txt

[compn]

hows this then? lets see if my mail client is worth a damn.

>You are not allowed to post to this mailing list, and your message has
>been automatically rejected.  If you think that your messages are
>being rejected in error, contact the mailing list owner at
>mplayer-docs-owner at mplayerhq.hu.

bah.
-------------- next part --------------
? codecs.conf.txt.patch
Index: codecs.conf.txt
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/tech/codecs.conf.txt,v
retrieving revision 1.5
diff -u -r1.5 codecs.conf.txt
--- codecs.conf.txt	15 Sep 2002 01:39:42 -0000	1.5
+++ codecs.conf.txt	20 Nov 2004 03:59:29 -0000
@@ -13,7 +13,8 @@
 users to access, or in the .mplayer directory in a user's home
 directory. When MPlayer starts, it first looks for a codecs.conf file in a
 user's home directory. Failing that, it searches for the shared file. If
-it can't find a codecs.conf file, MPlayer will refuse to run.
+the file is edited incorrectly, mplayer will fail to start and report any
+errors.
 
 The codecs.conf file is really quite simple. It is simply a collection of
 codec definition blocks that define how different media types should be
@@ -63,17 +64,17 @@
 This is a particularly full-featured video codec. The "videocodec" keyword
 identifies the fact that this is the start of a new video
 codec. "indeo5ds" is MPlayer's unique name for the codec. You have to use
-this name with the -vd/-ad option.
+this name with the -vc/-ac option.
 
 The next line has the keyword "info" which specifies a human-readable
-comment accompanies this codec. This is printed by -vd help / -ad help.
+comment accompanies this codec. This is printed by -vc help / -ac help.
 
 The "status" keyword carries information about the codec's functional
 status. MPlayer currently recognizes 4 status levels: working, buggy,
 crashing, and untested. When it gets to codec auto-selection, it tries
 untested first (to force the users to test it for us and report result :)),
 then working and finally buggy ones. Codecs marked crashing won't be tried,
-unless explicitly (-vd/-ad) selected.
+unless explicitly (-vc/-ac) selected.
 
 The next line lists 4-character codes (FOURCCs) that are associated with
 this codec. There can be more than one FOURCC specified on a fourcc line
@@ -93,7 +94,7 @@
 they all manage communication with binary-only modules.
 
 The "guid" keyword identifies a 16-byte Microsoft GUID that some media
-files use to identify codecs. Used only for win32 dshow codecs.
+files use to identify codecs. Used only for win32 dshow and DMO codecs.
 
 The "out" keyword identifies which output format that the decoder is known
 to output. Just like the fourcc line, there can be multiple out lines or
@@ -101,7 +102,7 @@
 formats should be listed in order of preference.
 
 The outfmt values can be followed by one or more flags, like flip, noflip,
-static, query. Describe these in detail:
+static, query. The flags are defined as follows:
 
 "flip":
     If this flag is set for a given format, then o_bih->biHeight will NOT be
@@ -123,7 +124,7 @@
     
 "query":
     This flag is used to control VDCTRL_QUERY_FORMAT for vfw/vfewx codecs.
-    If thsi flag is set, the control() will query the codec for the csp
+    If this flag is set, the control() will query the codec for the csp
     support, otherwise it will assume constant csp table. Required for
     some DLLs (like huffyuv, CRAM).