Skip to content
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

Document --map argument #411

Open
Winterhuman opened this issue Oct 14, 2023 · 2 comments
Open

Document --map argument #411

Winterhuman opened this issue Oct 14, 2023 · 2 comments

Comments

@Winterhuman
Copy link

I noticed in some issues and pull requests that there's a --map option available which is "undocumented", however, I couldn't find an explanation for why this is. Is there a chance it could be included in the --help and man pages?

@kornelski
Copy link
Owner

It reads palette from the given file.

It's undocumented, because of tradition. It was undocumented in 1999 version of pngquant too! ;)

More seriously, I never implemented it properly by reading the palette out of the file, it applies pngquant to it, so it only uses palette for pixels in the file, not all (including unused) palette entries.

@Winterhuman
Copy link
Author

Winterhuman commented Oct 20, 2023

Yeah, I noticed using an indexed PNG for the palette image doesn't work (I didn't open an issue for that in case --map was being deprecated, hence this issue), it's cool to hear how long pngquant has been around!

Are there any plans for enhancing --map in the future? Maybe a way to export a palette from an existing image?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants