-
Notifications
You must be signed in to change notification settings - Fork 25
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
Formatting code for English nouns and verbs #39
Comments
Hey @andrewtavis, could you add the appropriate priority to this issue? Also, what formatter does Scribe-Data use? autopep8? |
Priority applied, @SaurabhJamadagni! And Scribe-Data uses black for formatting :) |
For the verbs formatting, @SaurabhJamadagni, the output I got from Wikidata would be for simple present, simple past and past perfect. Unless you really want to keep the model lean as on Wikidata, let’s make the full six conjugations per case in the formatting so the references would be easier. We also don’t need to do six versions of past perfect as this would just be conjugations of have with the past participle as we do for other languages :) :) |
Hey @andrewtavis, could you please list the six conjugation cases to include? I am a bit confused 😅 |
So would the list be: presFPS
presSPS
presTPS
presFPP
presSPP
presTPP
pastFPS
pastSPS
pastTPS
pastFPP
pastSPP
pastTPP
pastParticiple |
@SaurabhJamadagni, sure thing!
We’d need the above for present and past, and then for present perfect and past perfect we can just construct it with “have” conjugations: “have run” or “had run”, etc. |
Exactly, @SaurabhJamadagni! |
Awesome! Got it thanks! On it right now :) |
Hey @andrewtavis, I don't think the |
Ya you’re right, @SaurabhJamadagni 🤦♂️ Should have ran it and sent the file. I’ll be home in 20 min and will update it for you! |
Got held up, @SaurabhJamadagni. 2836dbb adds the new verbs with all their forms :) |
Awesome @andrewtavis! Thanks :) |
So the values for the key
|
I guess all of past ones, so:
Feels a bit weird to do it this way, but then we'd have to change the view. We do that for Russian, but that's explicitly because past tense works differently rather than in the case for English where there just isn't a change. I'd say we're fine to do the 3x2 view for English for now, and we can reevaluate later :) |
So if the following is one of the entries in {
"infinitive": "dialogue",
"presFPS": "dialogue",
"presTPS": "dialogues",
"simpPast": "dialoged",
"pastPart": "dialoged"
} then the formatted file would have: dialogue: {
"presFPS": "dialogue",
"presSPS": "",
"presTPS": "dialogues",
"presFPP": "",
"presSPP": "",
"presTPP": ""
"pastFPS": "dialoged",
"pastSPS": "dialoged",
"pastTPS": "dialoged",
"pastFPP": "dialoged",
"pastSPP": "dialoged",
"pastTPP": "dialoged",
"pastPart": "dialoged"
} is this correct @andrewtavis? |
We’d also want to apply |
Ohh, so something like this: "presFPS": "dialogue",
"presSPS": "dialogue",
"presTPS": "dialogues",
"presFPP": "dialogue",
"presSPP": "dialogue",
"presTPP": "dialogue" But how is "dialogues" third person singular? |
I think that dialogue is maybe not the best example @SaurabhJamadagni, but that is the structure we’ll need :) :) “He dialogues the steps in the code”? Seems ok-ish, and other verbs will be fine 😊 |
Ahhh got it! |
da6b5c4 finalizes this, @SaurabhJamadagni 😊 Maybe some minor changes will be needed during the next update process, but we can figure it out then :) |
Terms
Languages
English
Description
The issue focuses on adding the formatting scripts for nouns and verbs for the English language queried data.
Will tackle the issue in parts. Part of the GSoC project.
The text was updated successfully, but these errors were encountered: