From 6184059c0568b05d5d17831fabfd6f0a53480b15 Mon Sep 17 00:00:00 2001 From: Nigel Tao Date: Wed, 27 Sep 2023 22:31:37 +1000 Subject: [PATCH] test/3pdata: tweak blinksuite JPEG commentary --- .../nia-checksums-of-blinksuite.commentary.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/test/3pdata/nia-checksums-of-blinksuite.commentary.md b/test/3pdata/nia-checksums-of-blinksuite.commentary.md index 8f4178fa..0d1dbe23 100644 --- a/test/3pdata/nia-checksums-of-blinksuite.commentary.md +++ b/test/3pdata/nia-checksums-of-blinksuite.commentary.md @@ -27,17 +27,17 @@ performance trade-offs if Wuffs were to try to exactly match on all input, not just on well-formed JPEGs. As pointed out by the a3cecef6 commit message, matching libjpeg-turbo exactly -doesn't necessarily give better output. Here's two decodings of JPEG images -(one sequential, one progressive, both truncated to 1 KiB) by libjpeg-turbo: - -![Decoding by djpeg](../data/peacock.default.truncated.decoded-by-djpeg.png) -![Decoding by djpeg](../data/peacock.progressive.truncated.decoded-by-djpeg.png) - -Here's the decodings on the same input by Wuffs: +doesn't necessarily give better output. Here's two JPEG images (one sequential, +one progressive, both truncated to 1 KiB) decoded by Wuffs: ![Decoding by Wuffs](../data/peacock.default.truncated.decoded-by-wuffs.png) ![Decoding by Wuffs](../data/peacock.progressive.truncated.decoded-by-wuffs.png) +Here's the same input, this time decoded by libjpeg-turbo: + +![Decoding by djpeg](../data/peacock.default.truncated.decoded-by-djpeg.png) +![Decoding by djpeg](../data/peacock.progressive.truncated.decoded-by-djpeg.png) + Zoom in on all four images (in four different tabs, if viewing in a browser), and the first pair isn't obviously better or worse than the second pair.