From 41f0bf680b0b139417bafdd92ec96ae666d29a61 Mon Sep 17 00:00:00 2001 From: James Zern Date: Mon, 26 Sep 2022 17:28:54 -0700 Subject: [PATCH] webp-container-spec: update note on trailing data clarify that the data is after the size specified by the file size in the header; an alternate way to read the previous statement was that the data was after the 'WEBP' fourcc. based on comments from: https://datatracker.ietf.org/doc/draft-zern-webp/ballot/#draft-zern-webp_robert-wilton Bug: webp:448 Change-Id: I7c5c5440a94cb817da51fe07d1ccf45d6af0f001 --- doc/webp-container-spec.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/webp-container-spec.txt b/doc/webp-container-spec.txt index fba29b72..de17be46 100644 --- a/doc/webp-container-spec.txt +++ b/doc/webp-container-spec.txt @@ -166,10 +166,11 @@ File Size: 32 bits (_uint32_) A WebP file MUST begin with a RIFF header with the FourCC 'WEBP'. The file size in the header is the total size of the chunks that follow plus `4` bytes for -the 'WEBP' FourCC. The file SHOULD NOT contain anything after it. Readers MAY -parse such files, ignoring the trailing data. As the size of any chunk is even, -the size given by the RIFF header is also even. The contents of individual -chunks will be described in the following sections. +the 'WEBP' FourCC. The file SHOULD NOT contain any data after the data +specified by _File Size_. Readers MAY parse such files, ignoring the trailing +data. As the size of any chunk is even, the size given by the RIFF header is +also even. The contents of individual chunks will be described in the following +sections. Simple File Format (Lossy)