This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tfs
Recipients serhiy.storchaka, tfs, vstinner
Date 2017-07-14.21:59:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500069541.06.0.209063274583.issue30660@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry for the late reply. I had to deal with stuff.

serhiy.storchaka:

> What tools did you use, optipng, advpng, pngcrush, pngnq, pngquant, or other? How much space is saved?

I had half a crate of whiskey that day so I'm going to say optipng and pngcrush were used and if my recollection is good the saved space was ≈ 5 to 50 % depending on the file.

> Note that some tools remove an information about palette that makes files displaying differently on different platforms and output devises.

I am aware of that. But if I understood correctly these files are rendered in documentation, and I don't think they're going to do this in a PlayStation 2. There may be complaints with Windows XP users because I remember for sure that optimized PNG files could not render very well back in those days.

haypo:

> I suggest to work on Sphinx to propose to implement this optimization on the HTML rendering, maybe with optional external tools. What do you think?

Like you I'm very fond of a long-term proper solution and that is, by the way, the solution you deserve.

Unfortunately, I do not have the skills for provide that. I can only give the solution you need (which is smaller files).
History
Date User Action Args
2017-07-14 21:59:01tfssetrecipients: + tfs, vstinner, serhiy.storchaka
2017-07-14 21:59:01tfssetmessageid: <1500069541.06.0.209063274583.issue30660@psf.upfronthosting.co.za>
2017-07-14 21:59:01tfslinkissue30660 messages
2017-07-14 21:59:00tfscreate