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

another typo #214

Open
dlschwartz opened this issue Feb 26, 2019 · 11 comments
Open

another typo #214

dlschwartz opened this issue Feb 26, 2019 · 11 comments
Assignees

Comments

@dlschwartz
Copy link

@jedwardwalters See https://syriaccorpus.org/57#Head-id.80 where ܐܡܕܡ should read ܐܡܕ. Compare https://archive.org/details/chronicaminorapa00guid/page/678 line 9.

@dlschwartz
Copy link
Author

@jedwardwalters And another: See https://syriaccorpus.org/57#Head-id.86 where ܘܗܼ،ܐ should read ܘܗܼܘܐ. Compare https://archive.org/details/chronicaminorapa00guid/page/678 line 29.

@jedwardwalters
Copy link
Contributor

Thanks for pointing these out, Dan! I'll try to get them taken care of soon.

@dlschwartz
Copy link
Author

@jedwardwalters Thank you for making the changes. One more, by the way. The very end is in bad shape. Compare our https://syriaccorpus.org/57#Head-id.106 with https://archive.org/details/chronicaminorapa00guid/page/674 lines 22ff.

@dlschwartz
Copy link
Author

@jedwardwalters And another. We've got a transposition of letters in the name Theodoret. Compare our https://syriaccorpus.org/57#Head-id.63 with https://archive.org/details/chronicaminorapa00guid/page/680 line 23.

@dlschwartz
Copy link
Author

@jedwardwalters
Copy link
Contributor

Are you still working through the text? I can wait until you're done looking over it and just correct them all at once.

@dlschwartz
Copy link
Author

Almost, should be done in about 15 minutes. Compare https://archive.org/details/chronicaminorapa00guid/page/674 line 30 on page 12 with what we have here https://syriaccorpus.org/57#Head-id.104. Seems we've got the addition of ܞ. Also,we have the repetition of ܫܝܢܐ, compare line 1 on page 13.

@dlschwartz
Copy link
Author

dlschwartz commented Feb 28, 2019

https://syriaccorpus.org/57#Head-id.106 has a number of errors. Compare https://archive.org/details/chronicaminorapa00guid/page/674 p. 13 ll 21-end. We have some typos and a missing chunk of text.

@dlschwartz
Copy link
Author

@jedwardwalters I want to apologize. I started out just thinking this would be a couple of little things but I obviously found a fair number of mistakes. I'm on a relatively new machine and still need to load a usable Syriac keyboard. Once I do that I could fix these.

I want to add that I haven't really worked through this in any kind of systematic way. I'm sure there are mistakes I've missed. Also, Guidi seems to have reproduced in this text the mss as it is and noted corrections in the footnotes rather than the other way around. Not sure how we want to deal with that kind of thing in the long run. In the short run I don't see any need to do this.

By the way, I started in on this because I'm preparing a copy of the text with persName, placeName, and orgName elements. Some folks at the prosopography hackathon in Vienna were doing some work on NER for non-Latin scripts and had some pretty good success with Arabic. They need something marked up for training the software. I'll put my marked up text on Github in a minute. Thanks Jamey!

@dlschwartz
Copy link
Author

@jedwardwalters Alright, I'm sorted on my keyboard situation now. I'll go ahead and make these changes unless you've already started.

@jedwardwalters
Copy link
Contributor

@dlschwartz No, I haven't started yet. I don't mind doing them, but I won't stop you either!

dlschwartz added a commit that referenced this issue Feb 28, 2019
@jedwardwalters Here is the commit that fixes the issues here: #214. I've also made the text in section 76 match the text of Guidi even though Guidi has a footnote indicating a correction to that text, see #213. I'll let you take a look at this, merge it to dev if you want to, and dismiss the linked issues when you want to do that. Thanks Jamey!
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

2 participants