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

Chapters repeat in the same book in stoa0054.stoa006.perseus-lat1.xml #572

Open
bolner opened this issue Aug 10, 2024 · 8 comments
Open

Comments

@bolner
Copy link
Contributor

bolner commented Aug 10, 2024

In file: stoa0054.stoa006.perseus-lat1.xml

(Note: Chapter 15 also repeats in that book.)

The texts are different though. Someone with access to the source could compare.

@lcerrato
Copy link
Contributor

@bolner
Thank you. A point of clarification, What is the issue with the Book 4 and Book 5 notations? Are they wrong? As this has not yet been updated, these sorts of structural inconsistencies are generally captured and corrected when texts are made compliant for the new software. (A duplicate chapter would be rejected, for instance.)

@bolner
Copy link
Contributor Author

bolner commented Aug 12, 2024

@lcerrato
The issue is that in Book 4 the chapters come in this order:
..., 13, 14, 15, 14, 15, 16, ...

So 14 and 15 are repeated.

@lcerrato
Copy link
Contributor

@bolner
Thank you. I was confused by the pointers to where Book 4 and Book 5 start. As I said, this type of issue will fail any checks upon conversion to Epidoc/CTS compliance as a duplicate section would be flagged.
I can take a look now but no corrections will be visible apart from the source file itself.

@bolner
Copy link
Contributor Author

bolner commented Aug 13, 2024

@lcerrato
I see :) This comes from the sources. This is a print of the Charles Plummer edition:
https://www.digitale-sammlungen.de/de/view/bsb11817355?page=422,423

Some chapters are missing in some sources.
But it would be nice if the numbering in the markup would not follow the source if that has a non-regular numbering.
So then we could pair the chapters in the English translation.

@lcerrato
Copy link
Contributor

@bolner The source editions should always linked in the header of the file, I believe. This is the case with most files. The pdfs are also linked via the Perseus Catalog.

As I said, since this is not yet transitioned, I did not look at the issue in the print. (We have many errors where the numbering is just applied incorrectly). I do see the long footnote here: https://archive.org/details/venerabilisbaeda01bede/page/232/mode/2up?view=theater

First, were I editing the file, I would have noted the parenthetical chapter numbering (that between the brackets) in the markup. Second, to address this particular issue, we will probably do something like chapter 14 and then chapter 14a.

In a case where there is a duplicate in the print, we have to modify to make it compliant with CTS as that requires unique containers. This current markup would simply not be permitted.

Are you in need of the file for your research or other work? If so, I will prioritize the conversion so that it can be published in the Scaife Viewer.

@bolner
Copy link
Contributor Author

bolner commented Aug 13, 2024

It's just for a hobby project, no worries :) And I see that the English version only has books 1-3, so book 4 would not cause any problem:
https://github.com/PerseusDL/canonical-latinLit/blob/master/data/stoa0054/stoa006/stoa0054.stoa006.perseus-eng1.xml#L47

(Because I'm pairing the Latin/English chapters.)

Thanks for the quick answer!

@lcerrato
Copy link
Contributor

@bolner
Well, that's interesting! I should also look into completing the English, now that you've noted it.
I do not see it on any pick lists or to do lists. I am wondering if there is an untagged file somewhere or if it was just neglected. I will open an issue to see that it is completed.
Please let me know if you do want the work converted. I can usually complete within in a day or two depending on other deadlines and scheduling.

@bolner
Copy link
Contributor Author

bolner commented Aug 13, 2024

My code can parse both formats, so it's okay for now. Thanks again!

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