-
Notifications
You must be signed in to change notification settings - Fork 4
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
semi-colon vs colon #34
Comments
1. the issue-34.txt was transformed into a valid XML and renamed to issue-34.xml 2. the comment in the last line about the synset 04203889-n I had already applied in the data/ann/annotation-XX.jl 3. the synsets that I manually fixed in data/ann/annotation-XX.jl I removed from the issue-34.xml
@fcbond I converted the issue-34.txt to note also the comments in my last commit. From your file, I removed the last lines because that error I had already fixed.
Finally, the 3 or 4 cases that I manually fixed today I also removed from the |
I have added suggestions to all the sentences in https://github.com/own-pt/glosstag/blob/master/scripts/issue-34.xml I'm going to refer to this issue in Open English Wordnet: the cases @arademaker fixed manually are commit f3bdc66 and commit 59ed6d4 |
Hi @fcbond, maybe you forgot to make a PR or push the commits to GitHub? I can't see the changes. |
Small comment when implementing this for OEWN. For
|
we have cases were semi-colon were used instead of colon. The complete list of manually analyzed cases done by the @fcbond team is https://github.com/own-pt/glosstag/blob/master/scripts/issue-34.xml
The text was updated successfully, but these errors were encountered: