Bob Friesenhahn

This is an annoying problem. GraphicsMagick is passing the original string value as provided by the user. Thorough validation is hard. For example, "cblkheight" has a constraint in that it "Must be an integer power of two", and perhaps <= 0 is also not valid. Do we know how Jasper behaves for other options which do not meet constraints? Perhaps some options are not rejected, but cause it to crash?

configure + MSVC /MD build registers no coders: studio.h enables SupportMagickModules for any `_DLL` build

This issue is addressed by Mercurial changeset 18234:40e85cb59a50. Thank you for the bug report and the proposed fix.

configure + MSVC /MD build registers no coders: studio.h enables SupportMagickModules for any `_DLL` build

configure ignores pkg-config's PNG library name when it is `-llibpng16` (MSVC builds of libpng)

Addressed by Mercurial changeset 18233:6715475d25a6. Thanks for the bug report and the help.

configure ignores pkg-config's PNG library name when it is `-llibpng16` (MSVC builds of libpng)

While looking at the PNG issues with attached profiles and chunks, I am thinking that it is best to no longer pretend to support historical libpng versions, and to require at least libpng version 1.6.31 or the oldest which offers discrete helper functions for all the metadata. Indeed, the latest libpng is 1.6.59 and is what everyone should be using unless their libpng has security patches from a vendor. This approach would allow stripping out legacy code. If there is no API provided for something,...