Clarify units #262
Merged
Clarify units #262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On the internet the usage of b and B for bits or bytes is inconsistent. Lowercase b seems to be used for either, and upperace B is more often used to mean bytes but usege for bits also exists. I am not aware of any standard that would mandate one or other use. Consequently, spelling out the whole word in the output or adding explanation in documentation is the only way to make sure the output is interpreted correctly. To save space on small screens only alter documentation and the bytes label without prefixes/suffixes. While at it change uppercase K to lowercase k to correctly spell the kilo- prefix. Fixes: #261 Signed-off-by: Michal Suchanek <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On the internet the usage of b and B for bits or bytes is inconsistent.
Lowercase b seems to be used for either, and upperace B is more often used to mean bytes but usege for bits also exists.
I am not aware of any standard that would mandate one or other use.
Consequently, spelling out the whole word in the output or adding explanation in documentation is the only way to make sure the output is interpreted correctly.
To save space on small screens only alter documentation and the bytes label without prefixes/suffixes.
While at it change uppercase K to lowercase k to correctly spell the kilo- prefix.
Fixes: #261