Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Squash images (pngcrush version) #202
Conversation
|
How are you getting those sizes? I just checked out this branch, and I'm seeing about 1.5 MB of data in |
|
Good question! I also see 1,423,814 bytes (1.5 MB on disk) now. I must have initially tested pngcrush without resizing first. I'll update with/without |
|
Updated, sorry for the confusion! |
|
Thanks! As I'm not an expert in image processing, I'm inclined to go with the lossless compression for now (this PR). We can always swap in pngquant later if we need to squeeze the size even more. Does that sound reasonable to you? |
|
You're welcome! Sounds perfectly reasonable, it's already a good saving. |
|
OK, thanks. I'm going to rebase the branch locally to cut out all the regenerations of the images, and make a couple of other manual tweaks. |
|
Continued & merged in #203. |
For #165 and #200.
Like #201 but with lossless pngcrush instead of lossy pngquant.
(Edit: updated after script sizes)
The
-bruteoption doesn't save much space, but we're not time critical so might as well squeeze out the last few bytes.-brute-brute(Edit: updated)