[sarankumar1325]

Fixes #15819.

In a UTF-8 locale, WhitespaceMatcher splits fields on Unicode blanks such as U+3000, but cut_fields_whitespace_trimmed trimmed the ends of each line with a byte test that only knows SPACE and TAB. A leading Unicode blank therefore survived trimming and became a delimiter, which emptied field 1. A trailing one added an empty last field, and -s stopped dropping one-word lines:

$ printf '\343\200\200shutdown now\n' | LC_ALL=C.UTF-8 cut -w=trimmed -f1

$

The ends are now trimmed with the same WhitespaceMatcher that splits the fields: a blank run at offset 0 is skipped, and a blank run that ends at the end of the line is dropped. In the C locale the matcher only sees SPACE/TAB through its memchr2 fast path, so output there is unchanged.

The -w help text in en-US.ftl still said "Space/Tab", so it now mentions Unicode spaces in a UTF-8 locale.

Tests

• New test_whitespace_delimited_trimmed_unicode_blanks: leading U+3000, mixed leading/trailing SPACE + U+3000/U+2003, and -s with a one-word line padded by U+3000. It fails on main and passes with this change.
• cargo test --features cut --no-default-features test_cut: 81 passed; cargo test -p uu_cut: 22 passed.
• cargo fmt --check -p uu_cut and cargo clippy -p uu_cut --all-targets -- -D warnings are clean.

I used an AI assistant while working on this; I reviewed the change and the tests myself.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.