Page Comparison

...

#	Aptfile	Buildpack	Results
1	mediainfo imagemagick poppler-utils	heroku-community/apt https://github.com/machinio/heroku-buildpack-vips heroku/ruby	`vips-8.10.2-Mon Oct 12` `vips -l \| grep -i pdf` is blank - no poppler support, so PDFs don’t work (See note 1) TIFFS work	2	libvips-tools mediainfo imagemagick poppler-utils	heroku-community/apt heroku/ruby	`vips-8.9.1-Sun Feb 23 08:51:26 UTC 2020` Color TIFFs work B&W TIFFs do not work PDFs work
32	libvips-tools mediainfo imagemagick poppler-utils	heroku-community/apt heroku/ruby	`vips-8.9.1-Sun Feb 23 08:51:26 UTC 2020` PDFs work All TIFFS work Removing `--eprofile srgb_profile_path` from the arguments to `vipsthumbnail` in the code (docs) avoids the error described in issue 942 (See note 2)5.
3	mediainfo imagemagick poppler-utils	heroku-community/apt https://github.com/machinio/heroku-buildpack-vips heroku/ruby	`vips-8.10.2-Mon Oct 12 16:43:59 UTC 2020` At some point in 2021, `vips -l \| grep -i pdf` started returning blank - no `poppler` support, so PDFs don’t work. All TIFFS work
4	mediainfo imagemagick libglib2.0-0 libglib2.0-dev libpoppler-glib8	heroku-community/apt https://github.com/brandoncc/heroku-buildpack-vips heroku/ruby	`vips-8.10.6-Tue Mar 23 20:52:58 UTC 2021` PDFs work All TIFFS work

Note 1: Eddie believes option 1 did work for much of the evaluation period for Heroku, but as of summer 2021 it didn’t.Note 2: Solution 3 is : Row 2 was a band-aid; it violates violated the rule implicit in the code that all TIFF derivatives should have their derivatives encoded as srgb, including the derivatives of B&W originals. I interpret the documentation as meaning that the icc profile of originals is reused in their derivatives, but further research is needed.
identify -verbose graphics_file.tiff | grep Colorspace can be used to elucidate what happens to various types of original after being processed by vipsthumbnail.

Versions Compared