-
Notifications
You must be signed in to change notification settings - Fork 974
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
Updated Readme.md to make quality parameter better documented. #119
base: master
Are you sure you want to change the base?
Conversation
Added example of numbers that can be used for quality parameter and explained the current limit of numbers above the 83% quality threshold.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
I signed it! |
CLAs look good, thanks! |
"require modifying the code to go bellow the set threshold." - that can easily be interpreted as "require hacking the argument check to allow lower number" rather than "rewriting the compressor to tune it to lower values". The check isn't there to annoy people and make them compile source with a lower number. It's there to stop people from wasting their time on using quality that this compressor isn't good at. |
@pornel That's a very great point I had not thought of. Is there by chance a way we can change that sentence so that we can still give a user heads up about the limit, and inform them that the compressor should not be bellow that threshold for the reasons you outlined? Or Perhaps we should remove that section from the read me and leave in the example "(0 - 100)"? |
Perhaps something like this:
|
Readme.md text has been updated to give examples of passable values to the `--quality` parameter and also explains why the quality has an artificial limit of 84.
@pornel Thanks for the example. I think that the wording is much more elegantly in these terms. I updated my pull request to include the text in your example. Thanks again for the feedback! |
Added example of numbers that can be used for quality parameter and explained the current limit of numbers above the 83% quality threshold.
"equivalent to libjpeg quality" does not have inherent meaning to users without the context of the documentation.