Closed MikeJ1971 closed 4 years ago
Yes, I think we could usefully clarify this in the sense of specifying an English-language calendar of Latin (and sometimes French and Middle English original material).
It would be worth thinking through some other examples of how this could play out with other Beyond 2022 materials.
Can we show the original versus the translation?
Advice is to treat 'language' as a description of the language of the original, unless we can specify edition versus the original
Ok. In the profileDesc I've gone for English, since that is the language in the encoded edition:
<langUsage>
<language ident="eng">English</language>
</langUsage>
However, we describe in msContents under the sourceDesc that the original document was mainly Latin:
<msContents>
<textLang mainLang="la">Latin</textLang>
</msContents>
Does this seem like a reasonable solution @crooksp ?
That seems very helpful -- and for our own internal documentation, we can record taht
What happens if these are the same? Does one become redundant?
Anyway you have a solution here for present purposes.
The tag allows us to 'describes the languages, sublanguages, registers, dialects, etc. represented within a text'. I think this refers to the electronic version we are creating and, often, this will be an English-language translation of the source material. However, I'm guessing certain words from the original will be encoded if they are of particular interest or the translation is uncertain?
Note: I need to check the language codes as there are several.
See https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-langUsage.html