-
Notifications
You must be signed in to change notification settings - Fork 967
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
Single word casing not working as expected #287
Comments
This is the expected behavior. All caps is considered an extreme case and is usually left untouched. The reason for this is that all-caps is usually an indication of acronym (e.g. HTML) in which case you really don't want to mess with it. The only transformation that does change that is I hope this answers your question. Going to close this now; but happy to discuss further. |
The combination you provided worked perfectly! [image: Inline images 1] On 29 May 2014 14:24, Mehdi Khalili notifications@github.com wrote:
|
This puzzled me too. I'm using Humanizr to prettify addresses that have been stored entirely capitalised, some of these will be single word strings and some won't. Might be worth adding a note to the documentation that any capitalised upper case string of any length is considered an acronym. Other than that, great library! |
Good point. You know you can send me a PR for that, right? :) |
You got it! |
I've noticed that single word casing isn't working. For example
The text was updated successfully, but these errors were encountered: