-
Notifications
You must be signed in to change notification settings - Fork 94
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
Stricter deinflection conditions #644
Conversation
CodSpeed Performance ReportMerging #644 will not alter performanceComparing Summary
|
✔️ No visual differences introduced by this PR. View Playwright Report (note: open the "playwright-report" artifact) |
I think the way the "name": "progressive or perfect",
"rules": [
{"suffixIn": "ている", "suffixOut": "て", "conditionsIn": ["v1"], "conditionsOut": ["iru"]},
...
] which makes it look out of place on -shimau because it doesn't match anything: "name": "-shimau",
"rules": [
{"suffixIn": "てしまう", "suffixOut": "て", "conditionsIn": ["v5"], "conditionsOut": ["iru"]},
{"suffixIn": "でしまう", "suffixOut": "で", "conditionsIn": ["v5"], "conditionsOut": ["iru"]}
] Should |
I have also thought of this, in addition, "iru" is being used for adverb くて form as well:
(which is obviously semantically incorrect) I also dislike the term conjunctive as I think grammar in Japanese does not fit perfectly into the grammar model of Western languages, but at the same time I don't know enough about linguistics to have a formal opinion. Open to change. |
Agree. I think いる performs too many distinct semantic functions to give it a name like that, I think just "iru" is fine. |
b3d5888
b3d5888
to
b5b5cf1
Compare
Add more conditions to transformations to avoid matching other words in the transformation process. (For example, prevents こうて from matching 斯くて)
also relocates the kansai-ben transformations so that verb transformations stay together