alhudz opened a new pull request, #1728:
URL: https://github.com/apache/commons-lang/pull/1728

   Repro: capitalise any word that begins with a supplementary cased letter, 
e.g. `WordUtils.capitalize("𐐨bc")` where `𐐨` is Deseret small long-i `U+10428`.
   Cause: `capitalize`, `capitalizeFully`, `uncapitalize` and `swapCase` 
iterate one `char` at a time and call 
`Character.toTitleCase`/`toUpperCase`/`toLowerCase` on each unit. The two 
surrogate halves of a supplementary code point carry no case mapping, so the 
letter is left as-is and the result diverges from 
`StringUtils.capitalize`/`swapCase`, which already work on code points 
(`capitalize` yields `U+10428` instead of `U+10400`, `swapCase` leaves 
`U+10400` unchanged).
   Fix: iterate with `Character.codePointAt` and write the mapped code point 
back with `Character.toChars`. A case mapping never changes the UTF-16 length, 
so the existing buffer is reused; BMP input and lone surrogates are untouched.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [ ] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [ ] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute?
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to