-
Notifications
You must be signed in to change notification settings - Fork 66
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 appears to refuse to modify certain Expressions #305
Comments
Since this is problem that only started happening to me recently, and I haven't changed my morphman settings recently, I'm guessing that this is a bug introduced by one of the last few updates (alpha 2, 3, or 4). This is just a guess, though. |
I tested with other morphemizers. When I tried the CJK characters morphemizer, it modified a few more of the cards, but many were still not being touched. When I tried the "languages with spaces" morphemizer, it modified some more, but still didn't modify every card. I don't believe ankiweb allows you to install old versions of addons, so I can't test if this issue still happens in alpha 1, but it didn't happen when I was using it before. |
I figured out how to install alpha 1 from source, and I can now confirm that it's an issue with the later versions. Alpha 1 appears to work fine. It recognizes and modifies all notes. |
Did you figure out a solution? Have the same problem for my decks (Latin-based) |
@Moriander |
I noticed this start happening for some reason for many new cards that I create recently. I don't know what the cause is. As an example, the expression "驚いて飛び上がった私は、恐る聞き返す。" when put as the expression of a card, doesn't seem to ever get modified by Morphman, but if I split the card into multiple smaller expressions, those will get modified and tagged appropriately. For example, I tested adding "驚いて飛び上がった私は、" and "恐る聞き返す。" and both of them were handled properly by Morphman, but in their original combined form they weren't.
I tested with both the default "Japanese support" morphemizer and the MecabUnidict one. The problem occurs with both. I also looked at the raw html of the expression field, and it's just the text in all 3 cases, so it couldn't be html that's messing up Morphman.
The text was updated successfully, but these errors were encountered: