Summer 2022 release thread

[ctschroeder]

Timeline

Primary editors work freezes 9/10-9/13. Publication ~9/20

Tentative Corpora

Shenoute Abraham (Arabic translations by Philippe Zaher)

Amélineau (@lancealanmartin)

• [x] shenoute.place.BV277-278
• [x] shenoute.thundered.GG19-28
• [x] shenoute.considering.BV283-284

Shenoute A22 (@bkrawiec)

• [x] do not check off until repo thread is complete

Check on Shenoute Abraham (Arabic translations )

• [x] whole corpus

AP

• [x] do not check off until repo thread is complete

Pistis Sophia Book 1 (align translation TS) & Pistis Sophia Book 2

• [x] chapter divisions by @lancealanmartin
• [x] do not check off until rep thread is complete https://github.com/CopticScriptorium/pistis-sophia-dev/issues/2
• [x] also see alignment issue

Wait until later release

• shenoute.listen.XO35-42
• shenoute.listen.FL15-28
• shenoute.true.BV119-122

Gospel of Thomas

Other Marcion

• Encomium on St John the Baptist
• Theophilus on Repentence & Continence (?)
• Resurrection of Jesus Christ

[ctschroeder]

@bkrawiec @cluckmarq @PhilippeZaher any work you're doing right now can be published in the next round if you get it done around the 10th of September. (Earlier is great.) If the summer server outages mean that you didn't get anything done just let me know.

[ctschroeder]

@lancealanmartin can you list the repos the Amélineau material are in and the corresponding works we will be publishing this round?

[lancealanmartin]

I created issues with rudimentary checklists in the repos and linked the docs to them.

[ctschroeder]

Are we publishing those Marcion docs this go around? @amir-zeldes If so, what repo are they in? should I be researching the metadata? Thanks!

[amir-zeldes]

I don't think we'll manage those marcions, they aren't really processed yet and PS is taking insane amounts of time due to checking identities and the absolute flood of names (with mangled tokenization) in this work.

But I thought we were planning to include shenoute.considering, does something speak against it?

[ctschroeder]

@amir-zeldes https://github.com/CopticScriptorium/shenoute-discourses5-dev/issues/51#issuecomment-1252810929

[ctschroeder]

Adding items here that I notice

shenoute.a22

• [x] in shenoute.a22 YA 303-304 diplomatic is wonky (legacy we didn't catch?); I fixed the pb_xml_id column in gitdox (it was named wrong and there were spaces between the YA and 303 or 304)
• [x] I cannot figure out what is going on with the diplomatic viz for YA 309-10 in shenoute.a22. 309 column 2 lines 13-16 the letters are all supposed to be small and there is not supposed to be a blank space/gap between lines 12 & 13

shenoute.thundered

• [x] why does thundered have a diplomatic viz? (we don't have manuscript line breaks or any manuscript info really except the page breaks; place and considering do not have diplomatic viz, which is probably a good thing)

[amir-zeldes]

OK, YA 309 was an issue where the CSS does not play nicely if hi_rend=small spans multiple lines. As an easy fix, I just gave each line its own hi_rend=small.

Thundered has lb_n annotations, so it assumed it should get dipl, but it's no problem turning it off. Should those be edition lines instead?

[ctschroeder]

Thanks. Ok let me check Thundered. I don't remember off the top of my head. I thought I fixed all those but perhaps not. Amélineau definitely does NOT mark manuscript line breaks.

I have a few other documents to check tonight, as well, so please hold off on further steps.

[bkrawiec]

Here are some errors/problems I have noted in A22 YA 311-16

DIPLOMATIC

1. The title says "YA 311-12" but should say "YA 311-16"
2. All the ekthetics are slightly to the left of margin but were not made large (I checked the XML and it says ekthetic large)
3. YA 312 col a line 11 needs to be indented.
4. YA 314 col a line 2 should end at the second ϥ; what follows on that line is line 3 (error in XML)
5. YA 314 col a line 24 should end at ⲏ; what follows is a separate line (error in XML)
6. YA 315 col a line 12 needs to be indented
7. YA 315 col b line 13 remove extra bracket

ANALYTIC:

In Ch. 958, (2) and (3) some boxes are highlighted in yellow. Is this correct?

NORMALIZED:

Here it seems the bound groups are not bound in the normalization but segmented along piping.

---

From: Caroline T. Schroeder @.***> Sent: Tuesday, September 27, 2022 11:48:53 AM To: CopticScriptorium/corpora Cc: Krawiec, Rebecca; Mention Subject: Re: [CopticScriptorium/corpora] Summer 2022 release thread (Issue #90)

CAUTION: This email was sent from outside of Canisius College. Do not open attachments or click on links from unknown senders or unexpected emails.

Thanks. Ok let me check Thundered. I don't remember off the top of my head. I thought I fixed all those but perhaps not. Amélineau definitely does NOT mark manuscript line breaks.

I have a few other documents to check tonight, as well, so please hold off on further steps.

— Reply to this email directly, view it on GitHubhttps://github.com/CopticScriptorium/corpora/issues/90#issuecomment-1259700641, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB7OGHCLNVHYU24W2GGYUJDWAMJOLANCNFSM5VYVUIRA. You are receiving this because you were mentioned.Message ID: @.***>

[ctschroeder]

@bkrawiec thanks so much for this detailed review of your document! I have a few questions and requests:

• [x] YA 312 col 1 line 11 is missing in Gitdox. (There are no spans -- there are three cells in the lb_n column that aren't merged). Can you check rows 249-251 in Gitdox against the manuscript and set the line breaks? I think that may fix your number 3.. Thanks!
• [x] re your numbers 4 & 5 I think you will need to check the line breaks against the manuscript and fix it in GitDox too. When you say that "what follows" is on ine three or the following line I don't know whether to add it to the following line or make a new line or what. Thanks!!
• [x] re 6 as with number 3 there is no span here. Could you check and fix in Gitdox also?
• [x] re 7 which bracket? in GitDox in the TOK layer there is a bracket after the ϥ and a bracket after the ⲏ. In orig_group there is only a bracket after the ⲏ. Which one is "extra"?
• [x] I don't understand what the problem is with the normalized view. The bound groups look correct to me. Can you add a bit more detail?

I have fixed the title issue in GitDox

[ctschroeder]

@amir-zeldes

• [x] I don't know how to fix Becky's second problem above with the ekthetics not visualizing as large. The hi_rend layer in GitDox consistently has "ekthetic large" in the correct field

[ctschroeder]

Also @amir-zeldes Thundered is fixed in Gitdox. I'm still looking at Pistis Sophia

[bkrawiec]

I made all these fixes as noted.

For the extra bracket, it was not in orig_group but was on the tok level, so I removed it and hope that does it. The extra is/was between the ϥ and ⲏ.

Whatever I was seeing in the normalized view is no longer there.

---

From: Caroline T. Schroeder @.***> Sent: Tuesday, September 27, 2022 7:13:50 PM To: CopticScriptorium/corpora Cc: Krawiec, Rebecca; Mention Subject: Re: [CopticScriptorium/corpora] Summer 2022 release thread (Issue #90)

CAUTION: This email was sent from outside of Canisius College. Do not open attachments or click on links from unknown senders or unexpected emails.

@bkrawiechttps://github.com/bkrawiec thanks so much for this detailed review of your document! I have a few questions and requests:

• YA 312 col 1 line 11 is missing in Gitdox. (There are no spans -- there are three cells in the lb_n column that aren't merged). Can you check rows 249-251 in Gitdox against the manuscript and set the line breaks? I think that may fix your number 3.. Thanks!
• re your numbers 4 & 5 I think you will need to check the line breaks against the manuscript and fix it in GitDox too. When you say that "what follows" is on ine three or the following line I don't know whether to add it to the following line or make a new line or what. Thanks!!
• re 6 as with number 3 there is no span here. Could you check and fix in Gitdox also?
• re 7 which bracket? in GitDox in the TOK layer there is a bracket after the ϥ and a bracket after the ⲏ. In orig_group there is only a bracket after the ⲏ. Which one is "extra"?
• I don't understand what the problem is with the normalized view. The bound groups look correct to me. Can you add a bit more detail?

— Reply to this email directly, view it on GitHubhttps://github.com/CopticScriptorium/corpora/issues/90#issuecomment-1260167277, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB7OGHEXND5S4BYNHKNE3W3WAN5S5ANCNFSM5VYVUIRA. You are receiving this because you were mentioned.Message ID: @.***>

[ctschroeder]

@lancealanmartin I am sorry to bother you -- are the line breaks in Pistis Sophia from Marcion or from the manuscript? Thanks so much.

[amir-zeldes]

I'm 99% sure the line breaks in Pistis are from the edition - Marcion doesn't have MS breaks, so I don't see where we would have gotten them from.

[amir-zeldes]

Large rendering is now fixed, you can take a look in ANNIS and I'll aim to have them in CTS later today too.

[lancealanmartin]

No problem whatsoever! The line breaks (lb_n, right?) match Marcion. I am not sure if the Marcion line breaks strictly follow the manuscript or not. The line breaks of the Brill edition are different.

[ctschroeder]

large rendering looks good. It appears that the line breaks are from the Petermann edtion, so I am now changing all the layer names from lb_n to ed_line_n. I should be done this afternoon.

[ctschroeder]

ok pistis sophia I think is ready

[amir-zeldes]

OK, everything is up to date in ANNIS and in CTS! If it all looks presentable I think we can announce end of day (I'll hold off on the GH release zip for a few more days, and still need to update CDO examples and tools)

[ctschroeder]

Thanks so much.

I’ll look into this more this afternoon and change the lb_n layer names as appropriate in all docs. It’s going to be a couple hours until I get to it and to check the large rendering.

[amir-zeldes]

I think this was fine in the release, no? If so I can make the release zip in GH.

[ctschroeder]

I gotta be honest — I have no idea if I did this or not. (I’m usually pretty good at following up though.) Either way the release is the release, and if it’s not fixed it will wait for the next one. Thanks for finishing this up, Amir!

[amir-zeldes]

Done! Closing...