-
Notifications
You must be signed in to change notification settings - Fork 1
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
Finding all "Early Print"-IDs for Shakespeare plays #1
Comments
Bestand: 27 Dramen (4 Suchergebnisse waren Gedichte) |
What's with the rest of the 37 canonic Shakespeare plays? Are they just not there? If so, why are 10 missing? |
An Early Print query with "author" = "Shakespeare, William" returns 31 hits (27 plays, including the First Folio of 1623 [A11954], which in turns contains 36 plays). The metadata list provided by Ingo has 36 hits for Shakespeare or "W.S.", but some of them refer to the Shakespearean apocrypha (e.g. The Puritan [A11264]). A follow-up question would be: are we planning to eventually merge ShakeDraCor into EngDraCor, or keep it as a separate corpus? In the second option, Shakespearean texts might be excluded from EngDraCor. |
Oh, interesting, thanks! Would be good to know which plays of the Shakespeare canon are missing (of if they just have wrong author information). As for the other question, I'd say we keep ShakeDraCor separate as it's a whole other edition with other encoding. In parallel, we established GerShDraCor for a parallel corpus of the German Shakespeare translations by Schlegel/Tieck. It's still in beta, but not much left to do to release it officially, see here. |
In principle, all plays in ShakeDraCor (with the exception of Pericles) are also included in EarlyPrint via the First Folio (https://texts.earlyprint.org/works/A11954.xml). |
Thanks for looking up the details! We had the same problem with GerDraCor when we tried to understand how to cut out plays from TextGrid Repository, see here. Files containing multiple plays were identified by the |
No description provided.
The text was updated successfully, but these errors were encountered: