ilrt / Beyond2022TeiTemplate

Work on creating a template for the TEI/XML that will be used in the Medieval Gold Seam and other seams
2 stars 0 forks source link

Which languages? #10

Closed MikeJ1971 closed 3 years ago

MikeJ1971 commented 3 years ago

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?

         <langUsage>
            <language ident="eng">English</language>
            <language ident="enm">English, Middle (1100–1500)</language>
            <language ident="lat">Latin</language>
            <language ident="gle">Irish</language>
            <language ident="mga">Irish, Middle (900–1200)</language>
            <language ident="fro">French, Old (842–ca. 1400)</language>
         </langUsage>

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

crooksp commented 3 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.

MikeJ1971 commented 3 years ago

Can we show the original versus the translation?

crooksp commented 3 years ago

Advice is to treat 'language' as a description of the language of the original, unless we can specify edition versus the original

MikeJ1971 commented 3 years ago

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 ?

crooksp commented 3 years ago

That seems very helpful -- and for our own internal documentation, we can record taht refers to the edition always (it could be an edition using original source language), whereas is always the original source language.

What happens if these are the same? Does one become redundant?

Anyway you have a solution here for present purposes.