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

Some codes don't parse correctly #4

Open
scruffian opened this issue Sep 3, 2019 · 10 comments
Open

Some codes don't parse correctly #4

scruffian opened this issue Sep 3, 2019 · 10 comments

Comments

@scruffian
Copy link
Contributor

scruffian commented Sep 3, 2019

Some example codes from the morphhb repo that don't parse correctly:

  • HVqrmsa, HVprmsa, HVqrmpc, HVqrmsc
  • HPp3fs

I'll add more as I find them

@jag3773
Copy link
Member

jag3773 commented Sep 4, 2019

@scruffian Can you note where you've found these?

@scruffian
Copy link
Contributor Author

@scruffian
Copy link
Contributor Author

Any thoughts on why this is and what we can do to fix it?

@joeldruark
Copy link

@scruffian I'm taking a look at this, but I'm not following you when you say that "the codes don't parse correctly." Can you explain the problem a little more specifically?

@scruffian
Copy link
Contributor Author

scruffian commented Nov 12, 2019

Sure, I'm using the parsing code in this repo, and calling this: parser.Parse(HVqrmsa) and it returns undefined for part of the morphology. For example:

var parser = new MorphParse();
parser.Parse('HVqrmsa');
"Verb qal participle active undefined undefined undefined"```

@joeldruark
Copy link

joeldruark commented Nov 13, 2019

OK, I think I understand. This is not a problem with the parsing data itself (i.e. where Hebrew forms are incorrectly parsed in the OSHB). This is a problem in the programming code that displays itself when trying to manipulate certain aspects of the parsing data. Have I understood you correctly, @scruffian ?

@scruffian
Copy link
Contributor Author

I'm not sure where the problem is, which is why I haven't submitted a patch. It could be that the parsing code needs updating to accommodate these forms, or it could be that the forms themselves are incorrect.

For example HVqrmsa fails to parse because it doesn't have a Person element. Either we need to make sure that all these forms are updated to have a Person, or we need to change the code to allow it to parse forms with missing elements. What do you think?

@joeldruark
Copy link

@scruffian Ah, I understand what you're saying. The HVqrmsa form is a participle, and participles do not indicate person. Likewise, finite verbs do not indicate construct/absolute state, nouns do not indicate stem formation, etc. Not all morphological forms have the same parsing elements, so we need to change the code to allow it to parse forms according to the specific elements that are applicable.

@joeldruark
Copy link

@jag3773 has indicated to me that he thinks this is David Troidl's code.

@scruffian
Copy link
Contributor Author

Makes sense. I'll work up a fix if I have time :)

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

3 participants