Sen Jiang

I still need to update some libraries and I'll cut a new release after that. Do note that this is only parallel on the file level, so it only works...

What's ByteArray.c? That's not a source file in leanify. Maybe trying appending a space after Leanify.res in build_gcc.bat line 4? I haven't used that in a while it could be...

What's "═х єфрхЄё эрщЄш єърчрээ√щ Їрщы."? Looks like russian, could you translate that? But probably something wrong with your mingw setup. That error in build_gcc looks like it's caused by...

I think this information is stored in `pHYs` chunk, which is an optional chunk in png specification, and most png optimizer will remove this by default, we can definitely add...

Yes, it does remove some metadata by default, but every pixel should be exactly the same, please provide example if that's not the case for the file you tested.

Not currently possible, I'm open to suggestions on how such a feature should be implemented.

By default `lossy_transparent` option is enabled because there's no difference in the pixels we can see, it is possible to add an option to disable this, but I would like...

Currently it's not exposed in CLI, but you can remove [this line](https://github.com/JayXon/Leanify/blob/master/formats/png.cpp#L111) in the code

This is because even though leanify will keep all the apng chunks, zopflipng and lodepng doesn't have native apng support https://github.com/google/zopfli/issues/118 https://github.com/lvandeve/lodepng/issues/98 And in some cases an optimization will change...

Looks like that's caused by rdata being writable, not sure why leanify would cause upx to not set that section to readonly. Maybe I have to disable leanify for upx...