[tei-council] concerns regarding <charDesc>

[Christian Wittern]

Lou Burnard wrote:
> I could live with this change. However:
>
> (a) I have an ousttanding action to make all listXXX things look the
> same, and I don't think that would work for listChar (which would
> presumably contain a mixture of char and glyph elements and wouldn'tt
> self-nest)
>   
Right. But it is still list-like enough to be called thus.

> (b) the pattern elsewhere in the header is to have a *decl including
> multiple *desc
> (c) each individual <char> or <glyph> is really a *desc
>   
In short, the change is unnecessary and the naming follows established
practice? In that case, it is fine with me:-)

> How about
>
> nonstandardChars containing (charDesc|glyphDesc)+
>   

No, please. This would cause too much confusion for current users of the
gaiji module.

> I dunno what the <desc> is doing inside the current <charDesc> --
> wouldnt it be more use be inside each <glyph> and <char> ?
>
>   
There is also one inside these. We felt there should be a place for an
overall description of the whole bunch. Given that note is presumably
now allowed here, we might get rid of this. On the other hand, I am
unconfortable making such changes at this point.

Christian


-- 

 Christian Wittern 
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN