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

Stricter deinflection conditions #644

Merged
merged 4 commits into from
Feb 8, 2024

Conversation

Casheeew
Copy link
Collaborator

@Casheeew Casheeew commented Feb 5, 2024

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

@Casheeew Casheeew requested a review from a team as a code owner February 5, 2024 13:28
Copy link

codspeed-hq bot commented Feb 5, 2024

CodSpeed Performance Report

Merging #644 will not alter performance

Comparing Scrub1492:stricter-deinflections (b5b5cf1) with master (0e9c28f)

Summary

✅ 2 untouched benchmarks

Copy link

github-actions bot commented Feb 5, 2024

✔️ No visual differences introduced by this PR.

View Playwright Report (note: open the "playwright-report" artifact)

@StefanVukovic99
Copy link
Member

StefanVukovic99 commented Feb 5, 2024

I think the way the past (ta) and adv (ku) rules are used here is correct, the suffixIn and the conditionsIn match. However, iru is used in the opposite way, conditionsOut matching suffixIn:

"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 iru be renamed to te or conjunctive?

@Casheeew
Copy link
Collaborator Author

Casheeew commented Feb 5, 2024

I have also thought of this, in addition, "iru" is being used for adverb くて form as well:

{"suffixIn": "くて", "suffixOut": "", "conditionsIn": ["iru"], "conditionsOut": ["adj-i"]},

(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.

@djahandarie
Copy link
Collaborator

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.

djahandarie
djahandarie previously approved these changes Feb 7, 2024
@djahandarie djahandarie added this pull request to the merge queue Feb 8, 2024
Merged via the queue into themoeway:master with commit d0eb437 Feb 8, 2024
7 checks passed
@djahandarie djahandarie added the kind/bug The issue or PR is regarding a bug label Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug The issue or PR is regarding a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants