Re: [EXTERNAL] [PNG] Upcoming meeting topics (Fourth Edition)

Cosmin, I can somewhat understand your position in the context of browsers, where users are simply consuming content authored by others….but in the case of authoring tools (e.g., Photoshop), then the considerations are quite different and may even be business/competitive decisions.

So without really understanding what direction(s) you might be trying to head towards – it’s difficult to offer more constructive feedback at this time.

Leonard

From: Cosmin Truta <ctruta@gmail.com>
Date: Sunday, April 27, 2025 at 7:30 AM
To: public-png@w3.org <public-png@w3.org>
Subject: Re: [EXTERNAL] [PNG] Upcoming meeting topics (Fourth Edition)

EXTERNAL: Use caution when clicking on links or opening attachments.


Speaking about the list of topics to discuss for Fourth Edition, I would like to add in my own: a list of non-normative Recommendations for Decoders on what to do when they stumble upon broken PNG files. In many instances, there's one obvious way to resolve it. It's how I'm resolving it (in optipng), it's how Chrome and Safari resolve it (in their rendering), and it's how libpng should at least facilitate the resolution, so that other browser implementers don't complain to us (libpng) that we're being unfair to them by not giving them a way to gracefully degrade.

And then, there's the issue of editors, from Gimp to Adobe and everything else in between. Load an incorrect PNG file, save a corrected PNG file, and the output may or may not match, depending on what editor is handling what broken image. I think that if we can reach a consensus here as well, and put it in libpng with little effort (really!) then we can improve the situation of all of those broken PNG images out there.

I'm volunteering to design and implement the proposal.

Sincerely,
Cosmin