-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix skull png #100
fix skull png #100
Conversation
Hi @advaith1, thanks for reporting this! Usually we run the PNGs through ImageOptim at the highest compression, then confirm the compressed & original PNGs visually match. Happy to merge this once you've done that, and I assume you'll need a patch version to be published on NPM too? |
Thanks, compressed! re npm, it looks like the png files are not published to npm? We pull them from our GitHub fork. |
They aren't, but they're referenced in the code through a CDN that pulls from GitHub tags. If you just pull the images alone from your own fork/don't use the referencing code, it should be fine (unless you also rely on the tags somehow). I'll merge this now (from mobile). Let me know if you need anything else. |
Actually, the png was correct, it's the svg that is wrong here. |
This reverts commit 9b03e52.
This reverts commit 9b03e52.
Hi, I'm Advaith from Discord. I got a report from a user that the skull emoji appears differently on Android vs desktop, particularly the eyes are different shapes. It seems to be because the PNG image is different from the SVG image. On desktop we use the SVGs but on Android we use the PNGs.
I used rsvg-convert to convert the skull's SVG to PNG so they are consistent now. However, this seems to have increased the file size significantly - is there a preferred way of optimizing the PNG?