Comment 11 for bug 1447968

Ok, I came across this open thread thinking that it was abandoned (it's from 2015!), but apparently there have been a few messages in the past few days, so at least I know I'm not insane... as the OP said, I was assuming that IM on Ubuntu (even on my old 16.04.6 LTS Xenial) came with the JP2 coder built-in, and, indeed, I *thought* that this was the case:

# convert -list coder | grep JP2
J2C JP2
J2K JP2
JPC JP2
JPM JP2
JPT JP2
JPX JP2
PGX JP2

But clearly this is *not* true, since on ImageMagick 6.8.9-9 Q16 x86_64 built in 2019-11-12 I get:

Delegates: bzlib cairo djvu fftw fontconfig freetype jbig jng jpeg lcms lqr ltdl lzma openexr pangocairo png rsvg tiff wmf x xml zlib

(well, I have added a lot of stuff, thus Cairo etc. are listed)

I also have installed *both* jasper (lib and runtime) as well as libopenjp2-7 (and libopenjpeg-dev & libjpeg62-dev & openjpeg-tools for good measure...).

I'm not really familiar with IM — I thought, for instance, that you could just tweak the .xml files and get 'instant' results without needing to recompile it — so I guess that my only choice is to install IM from the sources to get JPEG-2000 support?... I have little faith that, after 5 years, there are still developers with free time and willingness to 'fix' this bug, especially because I can very well imagine that the latest Ubuntu versions have fixed this somehow...

There *is* a PPA listing imagemagick-jp2 which *does* have working JPEG-2000 support, but they haven't applied the latest security patches...