-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Feature Request] Generate all possible Furigana from Kanji Name #39
Comments
Thank you for your request. I appreciate being able to understand what kind of features are needed. If I may suggest an alternative solution, namelti seems like it could meet your needs. |
Thank you so much for suggesting this package and taking the time to compile it! I tried for a few hours to compile it but was unsuccessful :( I was unable to compile the namelti_server. I wish using this library (like your package or Sudachipy) was easier. I liked the myoji-yurai website (which you have also linked) as it gave not just various furigana but also probably in the order of decreasing probability ( https://myoji-yurai.net/searchResult.htm?myojiKanji=%E5%A4%A7%E8%B0%B7 ) Although, I am not a very good programmer as you are, please let me know if I can help integrate the namelti package into your package (or create an easier-to-use fork of that package). |
First of all, thank you so much @rskmoi for making this package! I tried the demo on https://rskmoi-namedivider-python-examplesdemoexample-streamlit-x2ba84.streamlit.app/ and the results are amazing!
I intend to try it out in our business card management application to increase the accuracy of name dividing.
I have a request: Is it possible to get Kanji names Furigana too, especially all the possible candidates? OSS packages like Sudachi give only one candidate for the Furigana but I would like all possible suggestions for the Furigana.
For example, for the family name "大谷" Sudachi gives "オオヤ" as the output (please see attachment) but probably "オオタニ" is a more common Furigana of the name.
The text was updated successfully, but these errors were encountered: