From 2b06a50140b7eb81eb55dcc1547fee4e8842e697 Mon Sep 17 00:00:00 2001 From: Sebastian Rasmussen Date: Fri, 14 Sep 2018 00:46:28 +0800 Subject: Update to OpenJPEG 2.3.0. There is a regression for 2325_-_JPX_image_with_padding_rejected.pdf. Object 3 in that document is a JPX-encoded image. Its EOC marker is preceded by two extra bytes of data, 0x80 0x80. This makes the file broken according to the JPEG 2000 specification. Acrobat Reader and the Kakadu JPX decoder accepts this file without issues, so OpenJPEG 2.1.0 added code to fix this (bug 226, commit 005e75bdc). That fix detects exactly two bytes of 0x80 0x80, a rather brittle fix. Adding more padding or changing the padding byte values is not accepted. Adding more padding is acceptable to Acrobat Reader and Kakadu. An unrelated fix for another problem has since broken OpenJPEG's support for this broken image. --- thirdparty/openjpeg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'thirdparty') diff --git a/thirdparty/openjpeg b/thirdparty/openjpeg index 19b3d33e..0c286d07 160000 --- a/thirdparty/openjpeg +++ b/thirdparty/openjpeg @@ -1 +1 @@ -Subproject commit 19b3d33e7547682364a36a51e61ae38e068262ab +Subproject commit 0c286d07292f780b2a154e9b47c2a675decf2045 -- cgit v1.2.3