Jon Callas writes:
We would like to have a modification to the literal packet, where there
is a type 'u' packet which is identical to the type 't' packet except
that in this packet the implementation is saying, "By gum, I *know*
this really, really contains UTF-8 in it. Trust me. Really."
So how would we define appropriate behavior with respect to the
't' and 'u' packets, on receipt and on creation? Are we deprecating
't' on creation, and we SHOULD use a 'u' (and UTF-8 of course)?
And then on receipt, what should (or SHOULD) we do?
Hal