Version 9 13-Jan-2013 ---------------------- Add cjpeg -rgb1 option to create an RGB JPEG file, and insert a simple reversible color transform into the processing which significantly improves the compression. The recommended command for lossless coding of RGB images is now cjpeg -rgb1 -block 1 -arithmetic. As said, this option improves the compression significantly, but the files are not compatible with JPEG decoders prior to IJG v9 due to the included color transform. The used color transform and marker signaling is compatible with other JPEG standards (e.g., JPEG-LS part 2). Remove the automatic de-ANSI-fication support (Automake 1.12). Thank also to Nitin A Kamble for suggestion. Add remark for jpeg_mem_dest() in jdatadst.c. Thank to Elie-Gregoire Khoury for the hint. Support files with invalid component identifiers (created by Adobe PDF). Thank to Robin Watts for the suggestion. Adapt full buffer case in jcmainct.c for use with scaled DCT. Thank to Sergii Biloshytskyi for the suggestion. Add type identifier for declaration of noreturn functions. Thank to Brett L. Moore for the suggestion. Correct argument type in format string, avoid compiler warnings. Thank to Vincent Torri for hint. Add missing #include directives in configuration checks, avoid configuration errors. Thank to John Spencer for the hint.
+*jpeg-9 (14 Jan 2013) + + 14 Jan 2013; Samuli Suominen <ssuominen@gentoo.org> +jpeg-9.ebuild: + Version bump wrt #452008 by Lars Wendler. With empty KEYWORDS while waiting + for libjpeg-turbo to catch up.
(In reply to comment #1) > +*jpeg-9 (14 Jan 2013) > + > + 14 Jan 2013; Samuli Suominen <ssuominen@gentoo.org> +jpeg-9.ebuild: > + Version bump wrt #452008 by Lars Wendler. With empty KEYWORDS while > waiting > + for libjpeg-turbo to catch up. https://sourceforge.net/p/libjpeg-turbo/feature-requests/18/ and also posted to their forums
So it seems libjpeg-turbo upstream doesn't really want the new SmartScale feature from IJG's jpeg and even discredited the group with the backing of jpeg-6b author. It may be jpeg-9 never gets KEYWORDS.
see also http://digikam.1695700.n4.nabble.com/libjpeg-8-requirement-considered-harmful-td4661294.html where red-hat and arch developers suggest >=libjpeg-8 NOT 9 is to be avoided. disclaimer, I'm just a messenger, not analyzed the situation of jpeg API and ABI in the various version.
using libjpeg-turbo with jpeg8 abi enabled is safe, it just skips the smartscale that ijg's jpeg8 has we are certainly not falling back to jpeg6 without real need for doing so but i'm inclined to hold back jpeg9 for long as jpeg-turbo doesn't adapt to the latest smartscale features, and it propably doesnt
Thanks Samuli, actually *after* commenting here I've read the libjpeg-turbo ebuild and realized it's using JPEG_ABI=8 , I've also commented on that thread with the resulting toughts. Should have looked at the ebuild sooner.
