From e74f8a62b2bb0a7c839d6403a03f15775a6685aa Mon Sep 17 00:00:00 2001 From: James Zern Date: Sat, 14 May 2022 20:50:47 -0700 Subject: [PATCH] webp-lossless-bitstream-spec,cosmetics: normalize range syntax [N, M] -> [N..M] the latter is more common in this doc Bug: webp:551 Change-Id: I2d317c4b8bb31d313123e981f93cd1feb346a98a --- doc/webp-lossless-bitstream-spec.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/webp-lossless-bitstream-spec.txt b/doc/webp-lossless-bitstream-spec.txt index de300bf8..c67f96e5 100644 --- a/doc/webp-lossless-bitstream-spec.txt +++ b/doc/webp-lossless-bitstream-spec.txt @@ -866,7 +866,7 @@ stream. This may be inefficient, but it is allowed by the format. \[AMENDED2\] This variant is used in the special case when only 1 or 2 Huffman symbols are -in the range \[0, 255\] with code length `1`. All other Huffman code lengths +in the range \[0..255\] with code length `1`. All other Huffman code lengths are implicitly zeros. The first bit indicates the number of symbols: @@ -877,8 +877,8 @@ int num_symbols = ReadBits(1) + 1; Following are the symbol values. This first symbol is coded using 1 or 8 bits depending on the value of -`is_first_8bits`. The range is \[0, 1\] or \[0, 255\], respectively. -The second symbol, if present, is always assumed to be in the range \[0, 255\] +`is_first_8bits`. The range is \[0..1\] or \[0..255\], respectively. +The second symbol, if present, is always assumed to be in the range \[0..255\] and coded using 8 bits. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~