[tei-council] Values of @xml:lang on <exemplum>

[Lou Burnard]

I think it's clear that there are two things being confused here.
1. There is the language used by the example itself.
2. There is the language used by the text in which the example is embedded.

xml:lang on <exemplum> should be the latter
xml:lang on <egXML> should be the former

Of course, usually the latter is embedded in the former. Whence the 
confusion.

But there's no reason why you shouldn't have

<exemplum xml:lang="fr">
<p>Voici un exemple d'interet profonde:
<egXML xml:lang="la">Caesar adsum jam forte</egXML>
qui pourrait s'exprimer en anglais comme:
<egXML xml:lang="en">Caesar I  am here at last</egXML>
ou peut etre..
</p>
</exemplum>

I haven't looked, but is there really no official language code for 
"mixed" or "macaronic" or "unidentified"?


James Cummings wrote:
> Sebastian and I were just discussing this in relationship to examples 
> and my desire to decouple them.  In implementation it is fine where the 
> Guidelines point to a particular example by @xml:id, you just include 
> it.  But sometimes the elementSpec might have an example in another 
> language that you wish to appear in the English (or another language's) 
> element reference page.  So the logic, I think, is to include all 
> exemplum in the target language, and possibly all those with no 
> language, and only if those don't exist provide the English example. 
> the problem comes when the Chinese want to include a French example. 
> The solution we thought of was basically as you have below, but we 
> worried about abusing the semantics of exemplum/@xml:lang ... having a 
> @targetLang or something might solve this.  So you might get:
>
> <exemplum targetLang="fr">
> <!-- XInclude an example by @xml:id whose own @xml:lang is 'lat' -->
> </exemplum>
> <exemplum targetLang="zh">
> <!-- XInclude the same example -->
> </exemplum>
>
> Not sure...which is why I wanted to avoid talking about implementation. ;-)
>
> -James
>
> David Sewell wrote:
>   
>> This is do-able within the next month. I don't mind taking it on as my
>> project, as I've been working with similar issues with our UVa Press
>> material.
>>
>> Incidentally, I realized there is a perfectly straightforward (if
>> somewhat hack-ish) solution to handling exempla in Latin, etc.:
>>
>>   <exemplum xml:lang="">
>>     <egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="la">
>>       <p>GALLIA est omnis divisa in partes tres</p>
>>     </egXML>
>>   </exemplum>
>>
>> which asserts "this exemplum is language-neutral, but the sample code it
>> contains is in Latin".
>>
>> David
>>
>> On Thu, 30 Apr 2009, Sebastian Rahtz wrote:
>>
>>     
>>> Excellent to get this sorted.
>>>       
>>>> I would suggest, then, that we merge cases in #2 with #3 and assign them
>>>> all @xml:lang="". Those exempla are then considered language-neutral for
>>>> purposes of display. I assume that's more important to us than enabling
>>>> people to search for <exemplum>s that happen to be in Old English or
>>>> Arabic or whatever?
>>>>
>>>>         
>>> I am ambivalent about this. But on the whole I think your suggestion
>>> is the only practical one. We can change the schema for the Guidelines
>>> to make xml:lang compulsory on <exemplum>, by the way.
>>>
>>> the processing _will_ have to change. Can we get this done
>>> in the next month? how close are you to a listing all the
>>> exempla which need an xml:lang=""? I assume we just assign "en" to
>>> all the others which have no xml:lang at present.
>>>
>>>
>>>       
>
>
>