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

addressing textual variants in the apparatus #328

Open
paregorios opened this issue Aug 24, 2017 · 1 comment
Open

addressing textual variants in the apparatus #328

paregorios opened this issue Aug 24, 2017 · 1 comment

Comments

@paregorios
Copy link
Member

paregorios commented Aug 24, 2017

The following was provided by @hermaion82 at the NYC workshop:

A typical variant case:

papyrus reads (ll. 1-2):

                                 —  —  —
            καὶ τὰς ε]ὖ̣ π̣[ολιτευομένας
                   πόλ]ε[ι]ς̣ π̣ε̣ρ̣ὶ̣̣ [τούτου μάλιστα

and we want to say that it follows part of the manuscript tradition:

(apparatus) 1-2  τὰς ε]ὖ̣ π̣[ολιτευομένας | πόλ]ε[ι]ς̣ fort. pap. cum Γ : τὰς πόλεις τὰς εὖ φιλοτίμους πολιτευομένας ΛΠΝit: τὰς πόλεις τὰς εὖ φιλοτίμως πολιτευομένας ΘΝ1sl

I would envision something like what follows at the Leiden+ level:

<:τὰς ε]ὖ̣ π̣[ολιτευομένας2.- πόλ]ε[ι]ς̣=pap. fort. cum Γ||var||τὰς πόλεις τὰς εὖ φιλοτίμους πολιτευομένα=ΛΠΝit|τὰς πόλεις τὰς εὖ φιλοτίμως πολιτευομένας=ΘΝ1sl:>

which should conceal the following XML (or the like):

<app type="variant"><lem resp="pap. fort. cum Γ">τὰς ε]ὖ̣ π̣[ολιτευομένας <lb n="2"/>πόλ]ε[ι]ς̣</lem><rdg resp="ΛΠΝit">τὰς πόλεις τὰς εὖ φιλοτίμους πολιτευομένα</rdg><rdg resp="ΘΝ1sl">τὰς πόλεις τὰς εὖ φιλοτίμως πολιτευομένας</rdg></app>

The HTML output should resemble the abovementioned apparatus.

@paregorios
Copy link
Member Author

I'm interested in aligning our approach to encoding this stuff with what the Digital Latin Library is doing, since they've thought about lemmata, manuscript families, etc. Their guidelines are here: https://github.com/DigitalLatin/guidelines

@paregorios paregorios added this to the Post merge projects milestone Aug 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant