Activity for EpiDoc: Epigraphic Documents in TEI XML
-
BODARD Gabriel modified a wiki page
MarkupList
-
MarkupList
-
Boilerplate
-
Schema
-
Emmanuelle Morlock modified a wiki page
Schema
-
Guidelines
-
Guidelines
-
Home
-
Guidelines
-
Home
-
LatestRelease
-
LatestRelease
-
Hugh A. Cayless modified a wiki page
Schema
-
Schema
-
metDecl
-
duplicate @id in html a/br elements
-
Dear Christian, thanks for getting in touch. The short answer is yes of course, we've very happy to hear from and engage with your new project. We look forward to it. Slightly longer answer is that this engagement would most usefully happen via the EpiDoc-Markup list list, since the number of people who look at this issue tracker is tiny. Please do keep in touch!
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
MarkupList
-
GitHub-actions
-
enury created ticket #193
duplicate @id in html a/br elements
-
Christian Oettinger created ticket #175
possible future collaboration
-
Thomas Kollatz modified ticket #174
Improve lb in GL
-
Indeed TEI is calling them beginnings I will make a suggestion in the XML and own this FR
-
Do TEI now call them line beginnings? w00t (We've been doing that for many years, but at the time there was stiff resistence in TEI Council against doing so.) 100% agree that we should make the text of the GL page reflect this language. Do you want to go ahead and make the changes in the xml? We have plenty of time to tweak and proofread it there between now and the next release.
-
Improve lb in GL
-
Great, let's discuss a bit on Markup, and then come back here with a plan of action!
-
Mike Sampson posted a comment on ticket #172
As advised, I posed this to the MARKUP list yesterday, and so we'll see if there is any community input. That query includes a bit more information about the role of the enotikon: "The enotikon serves is a lexical aid in scriptio continua, serving not to divide words from one another (for which purpose there is the diastole or hypodiastole) but instead to indicate that a single word is meant. A good example of a text that requires it is PSI 16 1594.6, where it indicates πρ]ο̣σγενό̣μ[ένοι] (instead...
-
I won't argue sematics on this one—because it looks like we're probably both arguing the same thing, that at least the hyphen case suggested by Mike should best be tagged as a <g/>? (I'm not sure what role the enotikon plays in papyrological text, but I assume it's not analogous to paragraphos or other features that we might also propose tagging with <milestone/>?)
-
I'd argue we are almost exclusively marking up symbols on the surface.
-
Nora White created ticket #173
Improve Paragraphos page in GL
-
It was a bit weird, but I'm not sure <g> would be less weird. :) I think the reasoning was by analogy with apex, which looks similar to a diacritic, but is clearly highlighting in exactly the same way as long i or similar. I suppose it depends if we think we're marking up symbols on the stone/papyrus, or qualitative features of a vowel, which diacritics (almost?) all are.
-
A not-inconsequential part of my brain thinks using <hi> to indicate combining characters was a category error in the first place.
-
There's nothing currently to prevent the use of <hi rend="breve"|"longum"> in the EpiDoc schema (I believe the values of hi/@rend are recommended, not constrained). Adding handling of this to the Stylesheets would be trivial. (Presumably under the ddbdp Leiden-style?) I think "enotikon"/"hyphen" needs a bit more discussion. (It might also be useful to raise this on the EpiDoc-Markup list, where you could explain why you think the slightly unintuitive <hi rend="hyphen"> is preferable?)
-
Add scribal indication of metrical quantity & scribal enotikon (=hyphen)
-
MarkupList
-
Agree this is a bug. I have reinstated <metDecl> in the dev version of the schema (should appear at https://epidoc.stoa.org/schema/dev/tei-epidoc.rng today). Will appear in the release version of the schema at next release (due to be announced approx January 2025).
-
Eleonora Santin created ticket #192
metDecl
-
Elli Mylonas created ticket #171
Improve Verse Lines page in GL
-
Home
-
Training
-
Training
-
Redundant angle brackets need omitting
-
Stylesheets default handling of tei:milestone not very useful
-
merged today
-
Scott DiGiulio modified ticket #170
Revise GL on subaudible
-
Martina Filosa created ticket #170
Revise GL on subaudible
-
Further, as far as respStmt is concerned, see what iSicily does: http://sicily.classics.ox.ac.uk/services/inscription/ISic000014.xml
-
ReleaseProc
-
Pull request created: https://github.com/EpiDoc/Stylesheets/pull/18 Note: same as described before, except for the spaces flanking the pipe '|' when not inword that was preserved in the final fix.
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
GitHub-actions
-
GitHub actions for the automation of the release process
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
ReleaseProc
-
Home
-
Home
-
Home
-
Example and documentation of chained ODD
-
Expansion to guidelines for "haplography"
-
Encoding permission/ethical metadata
-
Revise GL page on quotation marks
-
LatestRelease
-
LatestRelease
-
LatestRelease
-
Home
-
Stylesheets default handling of tei:milestone not very useful
-
I'm not ready. I think we should postpone it.
-
@asopracasa and @gethia are we ready to publish some examples of chained ODD for this release or should we postpone it to 9.7?
-
@asopracasa and @gethia are we ready to publish some examples of ODD for this release or should we postpone it to 9.7?
-
Expansion to guidelines for "haplography"
-
Done! 😊 It needs some proofreading, though.
-
Dear @sarcanon, should we tackle this for the 9.6 release?
-
It would also be interesting to have an element within acquisition where it is possible to tag the price at which an item was purchased, as often happens with seals and coins (but also Kleinkunst) sold at auction daily. However, I don't seem to have found anything in TEI that can be used for this purpose. Any ideas?
-
We could try to use following TEI elements: In titleStmt... - sponsor (sponsor) specifies the name of a sponsoring organization or institution. - funder (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. - principal (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. - respStmt (statement of responsibility) supplies a statement of responsibility for...
-
That's seems coherent to me. Here's how I would translate this solution in the XSL files: teimilestone.xsl display a pipe when @unit is 'fragment' or 'block' -- no spaces around if @n exists, displays as exposant <xsl:template match="t:milestone[@unit='block' or @unit='fragment']"> <!-- adds pipe for block or fragment--> <xsl:text>|</xsl:text> <xsl:if test="@n"> <sup><xsl:value-of select="@n"/></sup> </xsl:if> </xsl:template> instead of: <xsl:template match="t:milestone[@unit='block' or @unit='fragment']">...
-
That's seems coherent to me. Here's how I would translate this solution in the XSL files: teimilestone.xsl display a pipe when @unit is 'fragment' or 'block' -- no spaces around if @n exists, displays as exposant ~~~ <xsl:template match="t:milestone<span>[klzzwxh:0002='block' or klzzwxh:0003='fragment']</span>"> <xsl:text>|</xsl:text> <xsl:if test="@n"> <xsl:value-of select="@n"></xsl:value-of> </xsl:if> </xsl:template> ~~~ instead of: <xsl:template match="t:milestone[@unit='block'...
-
That's seems coherent to me. Here's how I would translate this solution in the XSL files: teimilestone.xsl display a pipe when @unit is 'fragment' or 'block' -- no spaces around if @n exists, displays as exposant ~~~ <xsl:template match="t:milestone<span>[klzzwxh:0002='block' or klzzwxh:0003='fragment']</span>"> <xsl:text>|</xsl:text> <xsl:if test="@n"> <xsl:value-of select="@n"></xsl:value-of> </xsl:if> </xsl:template> instead of: <xsl:template match="t:milestone<span>[klzzwxh:0022='block'...
-
That's seems coherent to me. Here's how I would translate this solution in the XSL files: teimilestone.xsl display a pipe when @unit is 'fragment' or 'block' -- no spaces around if @n exists, displays as exposant ~~~ <xsl:template match="t:milestone<span>[klzzwxh:0052='block' or klzzwxh:0053='fragment']</span>"> <xsl:text>|</xsl:text> <xsl:if test="@n"> <xsl:value-of select="@n"></xsl:value-of> </xsl:if> </xsl:template> instead of: <xsl:template match="t:milestone<span>[klzzwxh:0001='block'...
-
That's seems coherent to me. Here's how I would translate this solution in the XSL files: teimilestone.xsl display a pipe when @unit is 'fragment' or 'block' -- no spaces around if @n exists, displays as exposant ~~~ <xsl:template match="t:milestone<span>[klzzwxh:0052='block' or klzzwxh:0053='fragment']</span>"> <xsl:text>|</xsl:text> <xsl:if test="@n"> <xsl:value-of select="@n"></xsl:value-of> </xsl:if> </xsl:template> instead of: <xsl:template match="t:milestone<span>[klzzwxh:0001='block'...
-
Encoding permission/ethical metadata
1 >
