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
This commit is contained in:
James Zern 2022-05-14 20:50:47 -07:00
parent 5a709ec0d7
commit e74f8a62b2

View File

@ -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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~