Activity for Scott DiGiulio
-
Scott DiGiulio modified ticket #170
Revise GL on subaudible
-
-
@ellimylonas and I will add a sentence or two into either supp-history.xml or supp-histmodern.xml to describe the use of <custodialhist> for specific custodial events like conservation or loans at the holding institution. @paregorios, if you feel that a more detailed description needs to be added to the EpiDoc guidelines beyond what the TEI provides, please share a couple of examples with us. We did find the following (https://github.com/papyri/idp.data/blob/master/DCLP/63/62962.xml), but we'd probably...
-
@ellimylonas and I will add a sentence or two into either supp-history.xml or supp-histmodern.xml to describe the use of <custodialhist> for specific custodial events like conservation or loans at the holding institution. @paregorios, if you feel that a more detailed description needs to be added to the EpiDoc guidelines beyond what the TEI provides, please share a couple of examples with us (we tried finding some in DCLP and couldn't find anything relevant).</custodialhist>
-
Marking transitions in language and/or script in the text
-
Perfect, thanks; copied into the file and will commit. If anything else needs tweaking, please feel free to clarify.
-
PR for space/gap
-
HC merged this in after testing, and all seemed to work well.
-
Re-engineer guidelines process to use tunnel parameters for examples
-
Update, format, correct, supplement examples in GL
-
page on EpiDoc and Linked Data
-
Incorporate EFES updates into EpiDoc release process
-
PR for space/gap
-
Will proof/test, and merge in if all seems well.
-
Text direction: GL and XSL need improving
-
Stylesheets default handling of tei:milestone not very useful
-
I can take a look at what Tom added above and then try to integrate them into what's already been worked up; this should be doable before 9.4.
-
tei:tag element not correctly displayed
-
After discussion, EDAG is happy to implement this fix as it stands.
-
Consider wrapping lines or line groups in HTML output
-
Wrote further guidance on handling languages and scripts in https://sourceforge.net/p/epidoc/code/2817/ and added a number of examples from the US Epigraphy Project; can use a look over from someone other than me to confirm that everything appears to be in order and that nothing is untoward, but should otherwise be ready to go for the upcoming release.
-
Revisions to address https://sourceforge.net/p/epidoc/feature-requests/154/
-
Looking at https://sourceforge.net/p/epidoc/code/HEAD/tree/trunk/guidelines/xml/trans-vacatotherunits.xml, I think I've already written some of this in as part of one of the other tickets I had been responsible for previously (in rev. 2739); I think we can consider this complete, but I'd appreciate it if someone could double-check the work to make sure that we're happy with what's there.
-
For the short term, will apply the provisional fix and will consider bigger picture changes in the future.
-
Stylesheets default handling of tei:milestone not very useful
-
Stylesheets default handling of tei:milestone not very useful
-
Stylesheets default handling of tei:milestone not very useful
-
I'll send an email to Markup to survey the needs of the community; once we have a sense of what kinds of values would be desirable, we can come back around to implementing all of the relevant changes at one time (rather than ad hoc).
-
Examples
-
We agreed that the recommended solution is to use <space> with a type attribute that indicates what the formatting element is; all that needs to be done is to add this to the documentation in the guidelines. I'll try to implement this in time for the next release.
-
Clarify and complete guidance on line placement/formatting
-
Clarify and complete guidance on line placement/formatting
-
Per discussion on 9/15, I feel like some of this may have been addressed in other conversations/tickets. I'll go back through briefly to see what, if anything, has been handled already and report back.
-
issues with release process
-
Added a couple of sentences addressing the html documentation, but I think the revisions to the release process should now be all set, unless there is something that stands out to others.
-
ReleaseProc
-
update to address questions of <space> and possible values for @types; added some prose to illustrate use.
-
Thinking quickly about the BM inscription that was raised as the example, and the ways in which <trailer> gets used in TEI, I'm not sure it actually carries the same semantic meaning as what we have on the stone. Based on the examples I've seen, <trailer> suggests a very particular convention of (especially) print and manuscript books, as opposed to the way that we conceptualize epigraphic texts and editorially present them. My instinct, then, is that we normally would not want <trailer> in the main...
-
Improve and consolidate GLs on verse and metre
-
Will add a little more prose to make this clearer, re-paragraph a bit more to help clarify what we actually mean by <space> in EpiDoc
-
Guidelines for space avoiding hole in support, etc.
-
General consensus, at Feb. 20 EDAG, is that having at least some suggested values would be valuable. Addtionally these values would help to resolve questions raisedabout how to indicate indentation, etc., at FR79, since <space> allows for a number of attributes that cannot be placed on <lb>.
-
Per EDAG discussion on Feb. 20 about the question of indenting, we generally agreed that the challenge of using <lb> for indent is the limitations on attributes (can't mark extent, e.g.), and <space> would be better to use for here. See related discussion at FR108.
-
Made slight tweaks, including removing the allowable TEI elements for clarity, as discussed at the Feb. 20 EDAG meeting, with commit r2721.
-
Minor modifications to discussion of unclear, per EDAG discussion on Feb. 20.
-
Only remaining points are documenting analytics (I'll handle this week), and documenting the HTML choice FR125, which is now closed.
-
Only remaining points are documenting analytics (I'll handle this week), and documenting the HTML choice [FR125]((https://sourceforge.net/p/epidoc/feature-requests/125/), which is now closed.
-
ReleaseProc
-
ReleaseProc
-
I think points 1, 2, and 3 are (at least partially) addressed by the changes made to address bugs:#170; still need to document the choice for 2.
-
Addressed points 2, 3, 4, 5, and 6 above; made relevant changes to release process guidelines page on sourceforge. Didn't address FR125 yet.
-
issues with release process
-
Addressed points 2, 3, 4, 5, and 6 above.
-
ReleaseProc
-
issues with release process
-
last updates to driver.xml and ReleaseNotes.txt for 9.0 release.
-
Home
-
LatestRelease
-
LatestRelease
-
LatestRelease
-
LatestRelease
-
release notes to 9.0
-
remove folder
-
new folder for 9.0 xslt
-
tagging as 9.0
-
-
-
upload final 9.0 schemata
-
update driver.xml for candidate release
-
9.0 candidate schema materials
-
release update
-
updated 9.0 ReleaseNotes.txt
-
Continued drafting 9.0 ReleaseNotes.txt
-
Updated the prose on <lb> to reflect our customized use of the element, per FR #87.
-
EpiDoc guidance on text direction is not TEI-conformant
-
Reassigning this back to Tom for the XSLT updates; I've also updated the prose of the guidelines to reflect the TEI usage of <lb> better.
-
-
Updated guidelines xml from @rend to @style as previously discussed to bring into conformity with TEI; I think there needs to be a corresponding change made in the XSLT, though I'm not sure precisely which files need changing.
-
(Very) short prose added to the Guidelines page for vacat (other), along with several suggested values there.
-
Inline editorial correction of previous edition
-
Consider and document EpiDoc customization of unclear
-
Improve handling for ligatured characters
-
EpiDoc guidance on text direction is not TEI-conformant
-
Guidelines for space avoiding hole in support, etc.
-
EpiDoc guidance on text direction is not TEI-conformant
-
Guidelines for space avoiding hole in support, etc.
-
As we discussed in the previous EDAG meeting, we're generally all in agreement that...
-
Based on our meeting last week, we agreed that changing the way we handle direction...
-
a) Generally speaking, the current TEI guidelines suggest (5.6) that the directionality...
-
a) Generally speaking, the current TEI guidelines suggest (5.6) that the directionality...
-
a) Generally speaking, the current TEI guidelines suggest (5.6) that the directionality...
1