37 karma · joined April 1, 2025
Yeah, there is such a problem with the naming "text" suggests something different than just a "string".
I guess handling these nuances falls under the broader categories of internationalization (i18n) and localization (l10n).
I guess handling these nuances falls under the broader categories of internationalization (i18n) and localization (l10n).
I appreciate your suggestion regarding the name, but unfortunately this name was already taken, so "textcase" was chosen.
I also have ideas for adding dictionary key conversion and other features in the future that will handle more than just strings. In addition, you can use this library to convert cases of Iterable[str] using textcase.pattern
It does not support non-English title casing. From the documentation:
> It also works non-ascii characters. However, no inferences on the language itself is made. For instance, the digraph ij in Dutch will not be capitalized, because it is represented as two distinct Unicode characters. However, æ would be capitalized
It sounds like you had quite the adventure with text casing on your project. I'm happy this library can save you some time and hassle. Looking forward to see what can be built with it!
Right now, there's no such GH badge. Since the project will always have zero dependencies, I think we can simply use a static badge like this:
Actually, this library supports conversion of even such strings!
```python
>>> import textcase
>>> textcase.convert("HAppY ApRiL FoOLs!", textcase.case.SNAKE, (textcase.boundary.SPACE,))
'happy_april_fools!'
```
Thanks for the congratulations!
This library actually has zero dependencies! I'm glad you appreciate the no-dependency design.
It's great to hear that it fits well with your work!