Author: lu_zero Date: Sun Oct 28 10:23:53 2007 New Revision: 510 Log: Clarify the behaviour in case of unknown headers: ignoring them Modified: docs/draft-niedermayer-nut-00.xml docs/nut.txt Modified: docs/draft-niedermayer-nut-00.xml ============================================================================== --- docs/draft-niedermayer-nut-00.xml (original) +++ docs/draft-niedermayer-nut-00.xml Sun Oct 28 10:23:53 2007 @@ -275,7 +275,7 @@ providing citations here. --> syncpoints. Demuxers SHOULD be flexible and be able to deal with damaged headers so is RECOMMENDED to use a loop able to adapt to corruptions and misordering, the file scheme in figure <xref="file representation" /> - shows a possible parsing method. Demuxers MUST be able to deal with new + shows a possible parsing method. Demuxers MUST ignore new and unknown headers.</t> <figure anchor="file representation" title="File representation"> <artwork><![CDATA[file: Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Sun Oct 28 10:23:53 2007 @@ -168,7 +168,7 @@ file: The structure of an undamaged file should look like the following, but demuxers should be flexible and be able to deal with damaged headers so the above is a better loop in practice (not to mention it is simpler). -Note: Demuxers MUST be able to deal with new and unknown headers. +Note: Demuxers MUST ignore new and unknown headers. file: file_id_string