-
Notifications
You must be signed in to change notification settings - Fork 119
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
Bugs/issues listed at googlecode #50
Comments
What is already fix and what still need fixing? This is maybe mostly fine by now: This still needs a fix: |
I think that marking them as "fixed" was a way to indicate I'd copied them to here. Seems like a bad idea. |
Working from memory: The "incomplete constituent tree" is probably a bug deep in the constituent code, which I have no desire to fiddle with. |
10 58 and 63 are all fixed. |
Update: |
I'm going to close this as "stale". 34 - elegant normal form will never happen. 27 needs an example. The others are English dict issues, on which there has been much progress, and also clearly, plenty of existing examples of sentences that don't parse right. |
There are currently eleven open issues listed at googlecode:
https://code.google.com/p/link-parser/issues/list?cursor=link-parser%3A58&ts=1419717174
A cut-n-paste shows:
The text was updated successfully, but these errors were encountered: