What is the level of tagging that will happen in a
translation? practice will differ, but what do we
expect the xslt to do, and what do we recommend?
Logged In: YES
This surely needs addressing in Guidance, but I don't think it's a big deal. My feeling is that editors will in general only need to tag very basic elements in translation (supplied, gap, abbr), and that these will be handled more or less as in the edition. The only difference in InsAph was that line-breaks were rendered as '|' rather than carriage returns. Are there enough other differences that we need to consider a translation Leiden-style? I would have thought not...
I would say that (a) anything that can appear in a text can appear in a translation, and except in rare cases (none currently) we should expect the XSLT to do the same things with it; (b) in practice far fewer things will be tagged in the translation than in the text. In IRT, for example, we restrict translation markup to: supplied-lost, supplied-subaudible, gap-lost, abbreviation, notes.
I would suggest that an appendix on translations would basically make this point, with a slimmed down list of the most commonly useful markup pages.
This is handled here, extensively, since that time. [http://www.stoa.org/epidoc/gl/dev/supp-translation.html]
Log in to post a comment.