zobweyt

7 ms·

1. 1.▲
   Show HN: Native-feeling charts for Obsidian Bases, built with Deno(github.com)

   3 points by zobweyt 4mo ago|0 comments
2. 2.▲
   by zobweyt 1y ago

   Thanks for the feedback! I'm glad you found a use case for this library!
3. 3.▲
   by zobweyt 1y ago

   Thank you for the update! I’ve added a badge to the GitHub repository to reflect its availability on AUR.
4. 4.▲
   by zobweyt 1y ago

   Thanks for the clarification! 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 internationalizat
5. 5.▲
   by zobweyt 1y ago

   Thank you for the clarification! I appreciate your input. I've updated the wording to "feature-rich" to better convey the intended meaning. Your feedback is valuable!
6. 6.▲
   by zobweyt 1y ago

   Thanks for your feedback! You're right; I should clarify that the library assumes English-language strings for casing. I'll update the documentation to make this limitation clear. I appreciate you pointing it out!
7. 7.▲
   by zobweyt 1y ago

   I understand your perspective, and it's a valid concern. However, this library is designed to support not only simple use cases but also more advanced scenarios, providing a comprehensive solution for various needs. Additionally, it ha
8. 8.▲
   by zobweyt 1y ago

   Thank you for your suggestion! Adding a preserve option to maintain leading, trailing, and duplicate delimiters while normalizing them to the target delimiter is a great idea. I’ll consider implementing this feature. Thanks again!
9. 9.▲
   by zobweyt 1y ago

   Thank you for the clarification! I understand that title capitalization can be quite complex, especially with specific rules in languages like German where capitalization can change the meaning of a word. I guess handling these nuances fall
10. 10.▲
    by zobweyt 1y ago

    Thank you for the feedback! 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
11. 11.▲
    by zobweyt 1y ago

    I appreciate your perspective! It's interesting to consider how the built-in libraries of a language can influence its ecosystem. Python does have a rich standard library that often reduces the need for external dependencies. In contra
12. 12.▲
    by zobweyt 1y ago

    That's a great observation! Instead of seeing it as a limitation, it can be treated as a feature. Users can handle Unicode normalization using Python's built-in unicodedata module to ensure proper case conversion. Thanks for point
13. 13.▲
    by zobweyt 1y ago

    Thanks! 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, bec
14. 14.▲
    by zobweyt 1y ago

    Thank you for the kind words! I'm glad you appreciate the effort put into covering all those edge cases. It sounds like you had quite the adventure with text casing on your project. I'm happy this library can save you some time an
15. 15.▲
    by zobweyt 1y ago

    Thanks for the suggestion! 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: https://img.shields.io/badge/dependencies-0-
16. 16.▲
    by zobweyt 1y ago

    Happy April! Actually, this library supports conversion of even such strings! ```python >>> import textcase >>> textcase.convert("HAppY ApRiL FoOLs!", textcase.case.SNAKE, (textcase.boundary.SPACE,)) 'happy_
17. 17.▲
    by zobweyt 1y ago

    Thanks for the kind words! 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!
18. 18.▲
    Show HN: Textcase: A Python Library for Text Case Conversion(github.com)

    71 points by zobweyt 1y ago|41 comments