numfmt: --format width accounting diverges from GNU for multi-byte --suffix #11937 fix#11992
Merged
cakebaker merged 2 commits intouutils:mainfrom Apr 25, 2026
Merged
numfmt: --format width accounting diverges from GNU for multi-byte --suffix #11937 fix#11992cakebaker merged 2 commits intouutils:mainfrom
cakebaker merged 2 commits intouutils:mainfrom
Conversation
|
GNU testsuite comparison: |
Contributor
|
Thanks! |
This file contains hidden or 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
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.
This PR closes #11937.
Previously, uutils numfmt treated non-ascii characters as a few characters (equal to the bytes' count), there character counts were considered when using width in the precision flag.
for example 🔗 was treated as f0 9f 94 97 (4 characters). It will now treat it as a single character, just as GNU numfmt does.