It changes from " 0-9?a-z" to ".0-9a-z~". The default or placeholder
changes from " " to "." so it's now always visible. The wildcard changes
from "?" to "~" so it's now sorted last.
lo128.dat and hi128.dat were constructed manually, then the
256.bytes.two-concatenated-streams.xz file was constructed by:
xz --keep lo128.dat
xz --keep hi128.dat
cat lo128.dat.xz hi128.dat.xz > 256.bytes.two-concatenated-streams.xz
It was created wih a custom xz binary (built from the source at
https://github.com/tukaani-project/xz), with this command:
xz --compress --keep --stdout enwik5 > enwik5.lzma2-chunk-max-1-13.xz
after applying this patch to xz's src/liblzma/lzma/lzma2_encoder.h:
-#define LZMA2_CHUNK_MAX (UINT32_C(1) << 16)
+#define LZMA2_CHUNK_MAX (UINT32_C(1) << 13)
The resultant enwik5.lzma2-chunk-max-1-13.xz file has multiple LZMA2
chunks, unlike the existing enwik5.xz (created with the normal chunk
limit). Wuffs' std/xz currently does not decode this new file properly.
SPDX is an ISO standard for describing licenses in a computer readable
format, which is useful when applying license compliance tools and the
like to source code.
In addition to ensuring that the Wuffs C distribution is properly
annotated to the benefit of projects using Wuffs and SPDX-supporting
tools, add it everywhere else where there's a license in this repo for
consistency, too.
The LICENSE has changed from a single license (Apache2) to a dual
license (Apache2 or MIT, at your option).
If you've previously used Wuffs under the Apache2 license, you are able
to keep doing so. No further action required by you.
The two files listed below (previous releases) are exceptions, as they
are older snapshots, frozen in time. Their license has not changed:
release/c/wuffs-v0.2.c
release/c/wuffs-v0.3.c
Every name in the AUTHORS file, other than Google Inc., has signed
Google's CLA (Contributor License Agreement).
We now convert it from the BMP file, not the PNG file:
$ convert bricks-gray.bmp -auto-orient bricks-gray.tga
The bricks-gray.png file has some gamma correction metadata that meant
that the previous TGA file (when converted to NIA) didn't match the
other bricks-gray.* files. After this commit, they all match:
$ grep bricks-gray test/nia-checksums-of-data.txt
c2bce675 test/data/bricks-gray.bmp
c2bce675 test/data/bricks-gray.gif
c2bce675 test/data/bricks-gray.no-ancillary.png
c2bce675 test/data/bricks-gray.png
c2bce675 test/data/bricks-gray.tga
Updates #67
This re-ran imagemagick's convert program, but this time with an
"-auto-orient" option. See
https://issueexplorer.com/issue/ImageMagick/ImageMagick/3844
for i in {color,gray,nodither}; do \
convert bricks-$i.png -auto-orient bricks-$i.tga; \
done
The test/data/*.tga files only change in their 18th bytes, from 0x00
(bottom-to-top) to 0x20 (top-to-bottom).
Updates #67
RFC 1951 section 3.2.7. "Compression with dynamic Huffman codes
(BTYPE=10)" says, "If only one distance code is used, it is encoded
using one bit, not zero bits; in this case there is a single code length
of one, with one unused code."
I had previously mis-read that excerpt to also require that the sole
distance code was the shortest distance (code 0, a distance of 1).
Fixes#66