EBB> For right now, it seems a higher priority to resolve the
EBB> release-blocking problems on dev connected with simplePrint.odd
EBB> ..., doesn't it?
Well, yes, but the question is whether *I* should be tackling the
nesting-<TEI> issue (for which I will find the schema changes easy,
but the prose changes will take me a long time because I'm slow at
that sort of stuff), or the stylesheet problems. (If someone else is
already 1/2-way to fixing it, speak up! :-)
HC> It would be a bit of a shame to lose it. I could work on it when
HC> I’m back home this weekend. Or on the plane on Friday for that
HC> matter...
Thanks. Might be a good idea. Although to be fair, we would not be
losing it, just not tucking it in until next release. (When,
honestly, it might make a bit more sense, anyway.)
MS> ... my understanding was that we already decided on the nesting
MS> TEI element, regardless of the deprecation of teiCorpus.
Right; I'm just talking about timing, not whether-or-not. (And in
part, timing so we can get feedback from community.)
MS> I am aware that we agreed on having LR propose this to the list,
MS> but on second thought my feeling is that such a suggestion should
MS> better be coming from the Council. I would therefore suggest that
MS> I draft an email to the list and circulate it to you.
My thought is "go, girl!". But perhaps the right thing to do is for
you to write up a draft, and send it to LR as well as to us so that
he can chime in, too?
EBB> It isn’t looking as if this sent, so I am trying again...
I had gotten it just fine.
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council