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

some questions that came up as I was converting <supplied> elements #155

Open
emylonas opened this issue Mar 13, 2021 · 3 comments
Open
Assignees

Comments

@emylonas
Copy link
Contributor

emylonas commented Mar 13, 2021

apol0100 has <supplied> elements in the diplomatic transcription. this seems strange. The <unclear> makes sense, but we don't usually put editorial markings in the diplomatic section.

mare0188 l. 135: there is a <space> element - should it be a <gap>?
bshe0022 l. 203 same things, <space> might be a <gap>

zoor0312 - l. 150: there is an <unclear> inside a supplied. I think it should be outside, in other words, the unclear letter would have an underdot, and the supplied part would be inside the square brackets. Is that correct?

caes0046 l. 134: I was checking something else, and noticed that the number was tagged as <num value="21"> but there was another roman numeral I after the <num> element. the translation also has 21, but is it perhaps 22? I put the <supplied> and the final roman numeral all inside the <num> but you should check it. Otherwise not clear what the extra I is. Haven't changed the value attribute.

caes0432 l. 136: there is a sequence of supplied elements with @lost and @Omitted attributes that may actually be encoding an abbreviation

caes0671 The diplomatic transcription doesn't match the word order of the edited transcription. Some of the words may be subaudible? It's not clear what is going on in this inscription. Also the abbreviation markup for the slash is odd.

nuse0001: I changed the supplied in the abbreviation in l. 129 so that the only supplied letter is the Θ, No need to include the expanded ε in the supplied element, as it's an editorial addition anyway.

hero0004 - there is an abbreviation on l. 135 that was broken into two <expan> elements in order to accommodate a <supplied> It's better in the case of partial words, to just put it inside the <abbr>, like this:

<expan><abbr><supplied reason="lost">καρποφ</supplied>ορησά</abbr><ex>ντων</ex></expan>

mtab0001 l.139: has supplied inside supplied. with a lot of subaudibles. They should probably be siblings

tdor0004 l. 204has a <note> element in the transcription. It's some kind of question that the encoder had, perhaps?

sena0001 and sena0003 have questions marks in the transcription. [there are more of these... 13 total]

.....MORE TO COME....

@zeichman
Copy link
Collaborator

Hi @emylonas ,
I don't know if these were part of the large commit from yesterday, but I think there was an error in correcting, namely that there is no closing quotation to reason="lost" (i.e., they all read reason="lost), which is rendering them all invalid. Is this something you can check on, because I've gone through a handful and they all seem to have that error introduced to them.

@zeichman
Copy link
Collaborator

Related to this, I see some strange new "supplied" information in some of the files, e.g., supplied reason="lost" that is nesting supplied reason="subaudible" that I have corrected when I've seen it (e.g., mtab0001 line 137 or so)

zeichman added a commit that referenced this issue Mar 14, 2021
Addressing issues #155 and #156 that Elli mentioned
@emylonas
Copy link
Contributor Author

emylonas commented Mar 14, 2021

didn't push my last set of changes last night. - where the missing quote was fixed. I had flagged the contained subaudible above, are there more? I'm probably going to find other strange bits here and there...

as I was merging confilcts just now, I noticed that in mare0506 there is an "L" to denote years. I think that should be an abbreviation. See jeru0321

<expan><abbr><am>L</am></abbr><ex>ἔτους</ex></expan>

zeichman added a commit that referenced this issue Mar 15, 2021
typo correction, including that identified by Elli in #155
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