Closed ttasovac closed 5 years ago
This is an easy one to my view and you get a +1 immediately. My proposal would be to adapt the content model of <cit>
to contain model.segLike
, which would generalize your proposal nicely (having various types of seg-like object.
I agreed, we could probably make a TEI ticket on this.
Cool. I will implement this on our end later in the day and create a TEI ticket.
I will close this, but keep in mind that I've opened up a ticket for the Council on this: https://github.com/TEIC/TEI/issues/1891. You may want to go and give a 👍 to it to show support.
I'm working with Bulgarian and Serbian colleagues on encoding a Latin-Bulgarian and a Latin-Serbian dictionary this week. I just noticed something that seems like an obvious omission to me:
At the moment, in TEI Lex-0:
<pc>
is not allowed inside a<cit>
. This makes no sense because we fought to allow<pc>
within<entry>
(and we got the change through the TEI Council) because we argued that<pc>
is used in dictionaries as a structural delimiter or divider between different elements.<pc>
plays the same role in<cit>
— it separates the quote from the translation. Free text is not allowed in cit anyway, so we really should allow<pc>
.Can I get an amen for this?