[tei-council] TEI P5 1.9.0
bansp at o2.pl
Wed Feb 16 17:47:39 EST 2011
That I understand, but I'm just not sure this is the message we want to
send to the user. Since colour coding is now being introduced, looking
from the user's perspective, green means "good to copy", yellow means
"copy and elaborate" (if I read this correctly).
My point is that in , the user gets a clear "good to copy" signal. A
"user" may mean a student being introduced to the TEI, not really being
able to tell TEI markup from other markup at first glance. I wouldn't
like to colour it yellow, I'd rather not colour it at all, if possible.
Of course this is the point when, as the "user" complains on TEI-L,
we'll say "relax, it's not really TEI, ignore the green". But the user
may never get to the stage of asking at TEI-L. And furthermore he should
never need to go that far.
In other words, it seems to me that there is a conflict here: on the one
hand, we're sending clear visual signals now, thus making one more step
on the way to greater user-friendliness, which is definitely the way to
go. On the other hand, we lure the newbie into a trap here, ironically
by means of the newly established user-friendly colour system.
On 2011-02-16 23:31, Lou Burnard wrote:
> The first example in DIFR is tagged as an example from the TEI examples
> namespace, and the markup within it is all escaped i.e. tagged using
> entity references. As far as the validator is concerned, it is therefore
> a pure text fragment with no tags in it, which is ipso facto valid TEI.
> To make it yellow, you'd have to turn the entity references < and >
> characters, and then wrap it in a CDATA marked section.
> On 16/02/11 22:21, Piotr Bański wrote:
>> I may have missed something concerning the nice way the examples are now
>> handled: I thought the valid ones were green and the 'feasibly valid'
>> ones were yellow, as in .
>> But if so, then in  the first example should be neither green nor
>> yellow, or I simplified my interpretation of colours. I'd be most happy
>> with it being colourless, as a piece of non-TEI markup. (I realise that
>> the true TEI markup has a degree of syntax colouring, which this
>> particular example lacks; but I don't think that that is enough of a
>> signal, given that we now use colours as primary signals).
More information about the tei-council