Skip to content
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

"İ" does not behave the same as the Java version of Sudachi. #202

Open
katsutan opened this issue Jul 15, 2021 · 2 comments
Open

"İ" does not behave the same as the Java version of Sudachi. #202

katsutan opened this issue Jul 15, 2021 · 2 comments

Comments

@katsutan
Copy link

I have noticed that Sudachi Py and Sudachi behave differently because "İstanbul" is not recognized as a single token in SudachiPy, so I will report it.

$ echo "İstanbul" | sudachipy -a
İ       名詞,普通名詞,一般,*,*,*        I       I       アイ    0       []
        補助記号,一般,*,*,*,*   ̇       ̇               -1      []      (OOV)
stanbul 名詞,普通名詞,一般,*,*,*        stanbul stanbul         -1      []      (OOV)
EOS

$ echo "İstanbul" | sudachi -a
İstanbul        名詞,固有名詞,一般,*,*,*        Istanbul        Istanbul        Istanbul        0       [15600]
EOS

Apparently, the character normalization process is passing different input to each sudachi.

$ echo "İstanbul" | sudachipy -d
=== Inupt dump:
i(U+0307)stanbul

$ echo "İstanbul" | sudachi -d
=== Input dump:
istanbul

It seems that "İ (U + 0130)" is converted to "i (U + 0069)-◌̇ (U + 0307)" in python and "i (U + 0069)" in java.
This may be due to the lower specification of each programming language.

@eiennohito
Copy link
Collaborator

From the Unicode point of view, Python is correct here, Java is not.

@eiennohito
Copy link
Collaborator

İstanbul as a word is fixed in SudachiPy 0.6.1+, İ itself is not. Moving the issue to Sudachi.rs repo.

@eiennohito eiennohito transferred this issue from WorksApplications/SudachiPy Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants