Menu
▾
▴
#87 EpiDoc guidance on text direction is not TEI-conformant
Current EpiDoc Guidance for Direction of Text suggest the selective use of the "rend" attribute on the "lb" element to indicate text direction. The TEI Guidelines (Section 5.6 Writing Modes) prescribes the use of the "style" attribute and the CSS Writing Modes Module.
EpiDoc Guidelines and XSLTs need to be brought into conformance with the TEI.
Ticket moved from /p/epidoc/bugs/135/
Moved this to feature requests, because I think we need to (a) assess the new TEI section on text directionality; (b) revise existing EpiDoc usage and guidance; (c) consider shorthand versions for left-to-right, right-to-left, boustrophedon on a whole div, etc.
(Also it's not really a bug, because TEI usage has only just recently changed on us.)
I'm not going to get the analysis done for this in time for the release. Pulling it out of 8.21 milestone.
Scott DiGiulio will work on the analysis and report back in sf
a) Generally speaking, the current TEI guidelines suggest (5.6) that the directionality as a rule is bound up in the script itself; in cases where you want to indicate it, they seem to be suggesting @style in the xml referring to CSS values, and the attributes "writing-mode" and "text-orientation" in the CSS. An example of boustrophedon is also given, in 5.9, which relies on the style attribute as well. The directionality of the text seems to be given primarily in a <seg>.</seg>
b) We currently use @rend for handling such directionality. This might be brought into agreement with TEI simply using @style instead, and updating the CSS accordingly (if I've understood the TEI discussion correctly). While TEI's examples generally mark the directionality of a <seg>, <lg>, etc., we currently indicate this on the <lb>; does this make sense to keep and only change the attribute? The boustrophedon example in the TEI marks this on a <seg> after each <lb>, though I'm fairly certain we don't normally include the <seg> in EpiDoc. I think we could add the directionality attribute to whole divs, too, as a possibility.</seg></lb></seg></lb></lg></seg>
c) l-to-r; r-to-l; boust? But this can be sorted out easily enough.
Last edit: Scott DiGiulio 2017-01-16
Based on our meeting last week, we agreed that changing the way we handle direction to <lb style="text-direction:l-to-r"> vel sim. should align with the new TEI standard, while still keeping the nuances that are particular to epigraphic texts.</lb>
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.
This may be a case for assigning this ticket to Tom (and I would categorize this as now a BUG, since GL and XSLT practice are out of sync—so fixing after today's feature freeze is acceptable) who I think have examples of text direction to encode and handle in his projects...
Yep, I can take the XSLT aspect, for sure.
--
Tom Elliott, Ph.D.
Associate Director for Digital Programs and Senior Research Scholar
Institute for the Study of the Ancient World (NYU)
http://isaw.nyu.edu/people/staff/tom-elliott
Humanities Commons: @paregorios https://hcommons.org/members/paregorios/
OrcID: 0000-0002-4114-6677 http://orcid.org/0000-0002-4114-6677
On Mon, Dec 4, 2017 at 5:45 AM, BODARD Gabriel gabrielbodard@users.sf.net
wrote:
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.</lb>
The strings "left-to-right" and "right-to-left" only appear in htm-teiab.xsl, so that's where I'm going to make the changes.
I've made, committed, and pushed the XSL changes to GitHub: https://github.com/EpiDoc/Stylesheets/commit/9343bef07b99c87ae6cc0415997d8c56ea358487
Closing this ticket as "done."