From bec2c88a11a0e6308a4a237e332733038eaad98d Mon Sep 17 00:00:00 2001 From: James Zern Date: Mon, 1 Aug 2022 18:58:02 -0700 Subject: [PATCH] webp-container-spec.txt: move ChunkHeader to terminology this avoids presenting it in the description of a chunk where it could appear it was defining an element of the diagram Change-Id: I51b2c2a0dcecb4fc130711ad37c884a434920ecd --- doc/webp-container-spec.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/webp-container-spec.txt b/doc/webp-container-spec.txt index a6736de5..074b2d3c 100644 --- a/doc/webp-container-spec.txt +++ b/doc/webp-container-spec.txt @@ -92,6 +92,12 @@ _1-based_ : An unsigned integer field storing values offset by `-1`. e.g., Such a field would store value _25_ as _24_. +_ChunkHeader('ABCD')_ + +: This is used to describe the _FourCC_ and _Chunk Size_ header of individual + chunks, where 'ABCD' is the FourCC for the chunk. This element's size is 8 + bytes. + RIFF File Format ---------------- @@ -125,12 +131,6 @@ Chunk Payload: _Chunk Size_ bytes : The data payload. If _Chunk Size_ is odd, a single padding byte -- that SHOULD be `0` -- is added. -_ChunkHeader('ABCD')_ - -: This is used to describe the _FourCC_ and _Chunk Size_ header of individual - chunks, where 'ABCD' is the FourCC for the chunk. This element's - size is 8 bytes. - **Note:** RIFF has a convention that all-uppercase chunk FourCCs are standard chunks that apply to any RIFF file format, while FourCCs specific to a file format are all lowercase. WebP does not follow this convention.