I don't think so, not necessarily, though you're right to note that this
would remove the ambiguity.
The one thing I hope we all agree would be bad news is
<p><hi rend="italic">blah blah</hi> bling <hi
since this encoding does not make significant the real thing of interest
in the source: the fact that the bling is visually distinct from its
On 06/01/12 10:34, Franz Fischer wrote:
>> Consider<p rend="italic">blah blah<emph rend="roman">bling</emph>
>> blah</p> for example. The intent here surely is that the bling 's
>> roman-ness replaces its italic-ness; it doesn't complement it.
> But accurate encoding should then be as follows:
> <p><hi rend="italic">blah blah<hi> <emph rend="roman">bling</emph> <hi
> shouldn't it?
>> On 06/01/12 09:55, Barry Cornelius wrote:
>>> On Fri, 6 Jan 2012, Sebastian Rahtz wrote:
>>>> I suspect I know what people will think, but let me try anyway.
>>>> <tei:hi rend="subscript">b,<tei:hi rend="italic">i</tei:hi></tei:hi>;
>>>> mean that the inner "i" is subscripted or not?
>>> Do you need to distnguish between the TEI document and its processing?
>>> When looking at the TEI, I'm not sure if inheritance is relevant. I mean
>>> as far as the TEI is concerned the letter i is inside a hi-rend-italic and
>>> that is inside a hi-rend-subscript. That's the end of the story.
>>> When processing this TEI, e.g., by a XSL script, it's up to your XSL as to
>>> what you want to do with characters that are inside a hi-rend-italic that
>>> is itself inside a hi-rend-subscript. Most people would want the
>>> If the opposite of italic is normal then how about:
>>> <tei:hi rend="normal">b,<tei:hi rend="italic">i</tei:hi></tei:hi>;
>>> Presumably this is valid TEI but your XSL might produce an error.