I played a bit with the pngs in the tree.
findings:
- You can crunch ~20 MB off the current treesize, by "pngcrush"-ing all png files. (This keeps the pngs lossless as they were, yet optimizes their size.)
- Alot of png's are in fact jpg's and thus have the wrong extension.
134 MB files with png extension in the current tree
~20 MB can be crushed off this.
But alot of these are in fact jpegs, so:
201 MB after converting these jpegs to png, and then pngcrushing them all, is what I end up with. That is +70MB compared to the current size.
who can I send this if there's interest?
data4.x pngs and png size
Moderator: pyramid
-
klauss
- Elite
- Posts: 7243
- Joined: Mon Apr 18, 2005 2:40 pm
- Location: LS87, Buenos Aires, República Argentina
What exactly is this pngcrush?
Anyway... send it to me (klaussfreire at gmail) - just the pngs. Those with wrong extension, they'll get renamed for 0.5.x but not before (too much hassle to change all the references, but the 0.5.x engine - Ogre - needs the right extension, so there it will have to be done).
Anyway... send it to me (klaussfreire at gmail) - just the pngs. Those with wrong extension, they'll get renamed for 0.5.x but not before (too much hassle to change all the references, but the 0.5.x engine - Ogre - needs the right extension, so there it will have to be done).
-
pheldens
- Bounty Hunter
- Posts: 178
- Joined: Mon Sep 26, 2005 1:15 am
http://pmt.sourceforge.net/pngcrush/
It recompresses pngs that weren't properly compressed by export plugins of the gfx editor.
If you did compress the pngs properly while exporting, say, from gimp, then you can't reduce them much further with pngcrush either.
This process is lossless, (since png is lossless)
It recompresses pngs that weren't properly compressed by export plugins of the gfx editor.
If you did compress the pngs properly while exporting, say, from gimp, then you can't reduce them much further with pngcrush either.
This process is lossless, (since png is lossless)