Clarified what is treated as an acronym. #316
Conversation
| "HTML".Humanize() => "HTML" | ||
| ``` | ||
|
|
||
| Note that a string that contains only upper case letters, and consists only of one word, is always treated as an acronym (regardless of its length). |
There was a problem hiding this comment.
Thanks for the PR. Maybe provide an example of what you mean. Also provide the workaround for how to deal with them when we want a different treatment, as discussed in #287.
There was a problem hiding this comment.
Happy to add an example, just wasn't sure how big you wanted that readme to get.
Would you say this is the most appropriate method of ensuring an arbitrary string will be transformed to title case?
"HUMANIZER".Humanize(LetterCasing.LowerCase).Humanize(LetterCasing.Title) => "Humanizer"
This does seem a bit clunky to me, at least from the perspective of someone working with data that's already mostly human readable (as opposed to acronyms and techy things). I wonder if you think some sort of global switch to ignore all acronyms would be appropriate?
There was a problem hiding this comment.
You can use transforms for that; e.g. "HUMANIZER".Transform(To.LowerCase | To.TitleCase).
But you have a good point there. Maybe we should allow that to be treated differently with a config or param.
Additional examples of strings treated as acronyms, with workaround using Transform() method.
|
I've expanded the explanation of the acronym handling and added the workaround as discussed. When I get time I'll look into adding some sort of switch. Perhaps if there was a property such as MaxAcronymLength, with a default of say 20, then the existing functionality was used for strings up to that length. Setting this to zero would effectively turn off the acronym behaviour. |
Clarified what is treated as an acronym.
|
Thanks for the addition and the suggestion. Looking forward to seeing your solution for the switch. |
No description provided.