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

MorphMan marking some i+0 as i+1 #107

Open
kanjieater opened this issue Mar 29, 2020 · 1 comment
Open

MorphMan marking some i+0 as i+1 #107

kanjieater opened this issue Mar 29, 2020 · 1 comment

Comments

@kanjieater
Copy link

I'm seeing a fair amount of false focus cards pop-up. For example, in my 10k+ cards that have either "mm" (the tag to represent that I want morphman to control order) or "mmi" (the tag to represent I want morphman to ignore the order but respect that it as a know; if a note is mmi, it does not have it's modify box checked). My already known tag is "mmk".

For instance, I'm being told “ゴミに突っ込む” is an i+1 sentence, despite already having 5 other sentences containing ゴミ, like: ゴミを捨ててください。

Deck Settings:
image

Tags:
image

I'm guessing it has to do to my deck/tag set up. I did see one card containing ゴミ that had both mmk & mmi, i'm not sure if that could somehow remove the morpheme from the "known" list.

@illiiilli
Copy link

My first hunch was because MeCab viewed ゴミ as two different variations, and as a result, marked them as different words, which is often the case. However, when I analyzed it using the morph extractor, it described both instances as 普通名詞 (see the two screenshots). However, I still think that MorphMan/MeCab recognizing the two different uses of ゴミ as two different words might still be the case, as one attaches to the particle に and the other attaches to the particle を. Have you tried going into MorphMan preferences and checking Ignore grammar position and seeing if the same problem still arises? If it doesn't then it confirms my hypothesis and vice versa.

ゴミに突っ込む
image

ゴミを捨ててください。
image

Morphman Preferences
image

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