[NUT-devel] [nut]: r507 - docs/draft-niedermayer-nut-00.xml

[Michael Niedermayer]

On Sun, Oct 28, 2007 at 02:34:36AM +0200, lu_zero wrote:
> Author: lu_zero
> Date: Sun Oct 28 02:34:35 2007
> New Revision: 507
> 
> Log:
> yet another update

this is not a acceptable svn log message


> 
> Modified:
>    docs/draft-niedermayer-nut-00.xml
> 
> Modified: docs/draft-niedermayer-nut-00.xml
> ==============================================================================
> --- docs/draft-niedermayer-nut-00.xml	(original)
> +++ docs/draft-niedermayer-nut-00.xml	Sun Oct 28 02:34:35 2007
> @@ -101,8 +101,8 @@ providing citations here. -->
>              synchronous 1-in-1-out decoder.
>              </t>
>              <t hangText="frame"> Minimal unit of information that can be
> -            decoded completely, it is usually holds a full frame video frame,
> -            a group of audio samples or a subtitle line.
> +            decoded, it is usually holds a part of video frame, a group of
> +            audio samples or a subtitle line.

huh? a frame is part of a (video) frame ?


>              </t>
>              <t hangText="Keyframe"> A keyframe is a frame from which you can
>              start decoding.
> @@ -212,10 +212,89 @@ providing citations here. -->

>  
>      <section title="NUT file layout">
>  
> -      <t></t>
> -    
> +      <t>Every NUT file starts with an identification string, main (global)
> +      headers and per stream headers follow, frame data is interleaved with
> +      syncpoint packets. Optional info packets and index packet MAY be present,
> +      in multiple copies, in order to improve resilience</t>

this is unclear if not outright wrong
it makes it look as if only index and info packets may be repeated
also the "may" is not correct headers at least have strict repeation rules

[...]

> +        <t>The structure of an undamaged file SHOULD consist in the
> +        file_id_string, the main header, the stream headers, the optional
> +        info packets, the optional index, frames intermixed with syncpoints.

i dont think this is an english sentence


> +        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
> +        and unknown headers.</t>

s/be able to deal with/ignore/
or something like that
same for nut.txt if thats containing this as well

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/nut-devel/attachments/20071028/89b317b4/attachment.pgp>