mirror of
https://github.com/ddidderr/wuffs.git
synced 2026-11-18 00:32:11 +01:00
test/3pdata: add more commentary about djpeg diffs
This commit is contained in:
1 parent
bffbad69a4
commit
ca50faaa92
1 file changed
+15
@@ -26,6 +26,21 @@ a3cecef6](https://github.com/google/wuffs/commit/a3cecef69aa04f1145f0c84b92481e8
|
||||
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:
|
||||
|
||||

|
||||

|
||||
|
||||
Here's the decodings on the same input by Wuffs:
|
||||
|
||||

|
||||

|
||||
|
||||
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.
|
||||
|
||||
---
|
||||
|
||||
`test/3pdata/blinksuite/large-size-image-crash.jpeg` is simply a very large
|
||||
|
||||
Reference in new issue
Block a user