From: Josh Coalson Date: Fri, 23 Jul 2004 05:08:30 +0000 (+0000) Subject: add table of contents X-Git-Tag: 1.2.0~835 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=00db21147a645ac56a2be536bb726f8c699744e2;p=platform%2Fupstream%2Fflac.git add table of contents --- diff --git a/doc/html/format.html b/doc/html/format.html index de993e1..7801f70 100644 --- a/doc/html/format.html +++ b/doc/html/format.html @@ -100,6 +100,88 @@

+ Table of Contents +

+

+

+

+

Scope

@@ -219,7 +301,7 @@ The FLAC format has reserved space for other coding methods. Some possiblities for volunteers would be to explore better context-modeling of the Rice parameter, or Huffman coding. See LOCO-I and pucrunch for descriptions of several universal codes.

- Format + Format

This section specifies the FLAC bitstream format. FLAC has no format version information, but it does contain reserved space in several places. Future versions of the format may use this reserved space safely without breaking the format of older streams. Older decoders may choose to abort decoding or skip data encoded with newer methods. Apart from reserved patterns, in places the format specifies invalid patterns, meaning that the patterns may never appear in any valid bitstream, in any prior, present, or future versions of the format. These invalid patterns are usually used to make the synchronization mechanism more robust. @@ -228,7 +310,7 @@ All numbers used in a FLAC bitstream are integers; there are no floating-point representations. All numbers are big-endian coded. All numbers are unsigned unless otherwise specified.

- A FLAC bitstream may be appended with ID3V1 data or prepended with ID3V2 data. FLAC has no knowledge of such data, but the reference decoder knows how to skip an ID3 tag. + A FLAC bitstream may be appended with ID3V1 data or prepended with ID3V2 data. FLAC has no knowledge of such data, but the reference decoder knows how to skip an ID3 tag.

Before the formal description of the stream, an overview might be helpful.