I agree with Piotr that if you want to fully document this, then
pointing up to a separate <langUsage> element in the header would
It would seem strange to me to offer specific markup to indicate
that something was originally written in a different language, or
has been translated into a particular language. That doesn't stop
it being whatever if it is (an <lg>, a <p>, a <div>). It is
merely an additional interpretative annotation on that object, so
a @decls, @ana, or whatever.
I tend to fall back to loose ID linking and using @type or @ana
for forms of classification.
<div type="original" xml:lang="de" ana="#originallyInGerman"
<div type="translation" xml:lang="fr" ana="#translatedIntoFrench"
On 18/05/15 09:50, Piotr Bański wrote:
> Hello Matija and all,
> What you are asking about sounds like @decls to me, pointing at the
> relevant parts of the header.
> Given the variety of possible interrelationships between texts, of which
> translation (but what kind of translation?, I would ask next) is only a
> sub-type, the header seems like the best place to describe the nuances,
> and then @decls would be the way for your <p>s to say, with minimal but
> useful indirection, “I am translated from ...” -- just as you ask.
> Best wishes,
> On 18/05/15 09:31, Matija Ogrin wrote:
>> Dear Laurent and others,
>> I wanted to point out that (as far as I can see) TEI does not offer any
>> markup for two (quite basic) textual structures/features:
>> - originally-written-in-language-xy
>> - translated-into-language-xy
>> Both 'xy' may be the same language, and yet, the @xml:lang does not
>> capture this semantic at all.
>> (It seems unusual that we have elements for so many detailed, minute
>> textual traits, and on the other hand, we lack some attribute to express
>> (non)originality of the text language -- even for stand-alone
>> translations without any <link> to some original source).
>> Dne 15. 05. 2015 ob 15:48 je Laurent Romary zapisal(a):
>>> Hi Matija,
>>> The general way to do this is probably to use <link> between pairs of
>>> source and translated objects. I could imagine using @corresp as well.
>>> I am not enthusiastic at the idea that you use @corresp to point to a
>>> source. My feeling would go for @source (if we manage to expand the
>>> scope of att.source; or you can think of customizing a little here…)
>>> or possibly use @decls (pointing to your various sources in sourceDesc
>>> in the header)
>>>> Le 15 mai 2015 à 15:22, Matija Ogrin <[log in to unmask]> a
>>>> écrit :
>>>> Hello. I have a question about 'translation'.
>>>> I have a multi-lingual ms. dramatic text, where in some part of the
>>>> edition, I wish to publish the translated portions of the text
>>>> (originally in Latin, German etc) along with the main text
>>>> (originally in Slovenian).
>>>> Now, how can I make it explicit that some <p> and <stage> etc. are
>>>> translations from some other language (then I can use @corresp to
>>>> determine the source).
>>>> To put it briefly: is there a direct way for a <p> or <stage> to say:
>>>> “I am translated from ...”
>>>> (Sorry if I missed something obvious; I browsed the G. for
>>>> “translation”, and found the cases of <derivation> in the linguistic
>>>> modules and @type='translation' , but obviously, a <p> cannot have a
>>>> @type , while a <stage> should have the values of @type with entirely
>>>> other meanings.)
>>>> Matija Ogrin, dr.
>>>> Neznani rokopisi slovenskega slovstva 17. in 18. stoletja (NRSS)
>>>> Inštitut za slovensko literaturo in literarne vede
>>>> ZRC SAZU
>>> Laurent Romary
>>> [log in to unmask]
Dr James Cummings, [log in to unmask]
Academic IT Services, University of Oxford