-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
strings: Title function incorrectly handles word breaks #6801
Labels
Documentation
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
It's documented in the code: func Title(s string) string Title returns a copy of the string s with all Unicode letters that begin words mapped to their title case. BUG: The rule Title uses for word boundaries does not handle Unicode punctuation properly. Unlikely to be fixed. Instead, perhaps the documentation should refer to a proper implementation once it lands in go.text. Not exactly working as intended, but working about as well as it ever will. Labels changed: added priority-later, documentation, removed priority-triage. Status changed to Accepted. |
Owner changed to @robpike. |
quentinmit
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Oct 10, 2016
Not going to be fixed in 1.8. |
This is unplanned and will stay that way indefinitely. There are no plans to fix it. Please do not tag it for each Go release and do not assign it to me. |
robpike
removed
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Mar 21, 2017
seankhliao
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Jul 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Documentation
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
The text was updated successfully, but these errors were encountered: