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

Update bavet129 130 #2756

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Update bavet129 130 #2756

wants to merge 12 commits into from

Conversation

MassimoVilla
Copy link
Contributor

Revision of MSS BAVet129 (Harp of the Virgin, Hymn to Mary, Anaphora of John) and BAVet130 (collection of texts on the archangel Raphael)

@CarstenHoffmannMarburg
Copy link
Contributor

Cf. BetaMasaheft/Documentation#2733.

LondonBritishLibrary/orient/BLorient619.xml Outdated Show resolved Hide resolved
<msItem xml:id="ms_i2.2">
<locus from="106r"/>
<title type="complete" xml:lang="gez" ref="LIT6404Dersan4recA">Homily of John Chrysostom</title>
<incipit xml:lang="gez">በእንተ፡ ፬እንስሳ፡ ዓበይት፡ መንፈሳውያን፡ አመ፳ለወርኃ፡ ኅዳር፡</incipit>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contrary to my previous comments in another pull request, it is recommended to have a space between a number and a following word, as @thea-m pointed out to me recently, i.e. ፬ እንስሳ፡. Sorry for the confusion!

Cf. BetaMasaheft/Works#1357:

Thank you @CarstenHoffmannMarburg , I follow a past decision to always have a space after a numeral for better searchability (taken for the bodleian project and not necessarily relevant per se for bm, but I think it makes sense). I would not like to include word dividers where there are none in the manuscripts

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem, thank you for confirming that we add a space after the numeral

<!-- Data don't match.
The quire structure illustrated in the catalogues gives a total number of 133 ff., while the catalogues
state that the manuscript has 131 ff. In order to reconcile the two data, one can assume that the first
two folia are blank and were not counted by the cataloguers (MKr-MV) -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, this information should be given in a note. However, I do not understand, why they necessarily must be the first two folia, but not one or two at the end. My suggestion:
<note>The quire structure as given in the catalogues ends with a total of 133 folios, while the same catalogues state that the manuscript has 131 folios. In order to reconcile the two data, it can be assumed that two folios either before or after the text block are blank and have not been counted.</note>
For me, it is OK not to give a for each quire, unless it would be nice to give loci here as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the suggestion about <note/>. Regarding the loci, in principle I try to give them every time the quire sequence is clear or can be easily reconstructed, but in this very case I preferred not to give loci because data are inconsistent and we do not know exactly the origin of the divergence.

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

Successfully merging this pull request may close these issues.

2 participants