Peter Prymmer <pvhp(_at_)forte(_dot_)com> writes:
Or one could use the source text "GGGG" to *really* indicate a "hex" value
that does not map to a character (I am being more than a little facetious
here ;-).
I quite like that idea.
How firmly established is the Tcl scheme?
Has not changed in a while.
I am not sure I want to keep it - the reasons for .enc files being there are:
0. They were to hand.
1. Known to work for Tcl/Tk so should "suffice" for perl/Tk which is
what I was working on at the time.
2. They are text so human and perl code can mess with them.
Is it still being hammered out?
I think the original Tcl folks have other fish to fry - but now Tcl itself
is a SourceForge project perhaps its new "owners" would accomodate our requests.
I do think that it would be nice to avoid yet another gratuitous file
format incompatability if possible. So how do the Tcl folks plan to
handle surrogates or truly unrecognized characters?
I am not sure the original Tcl/Tk project had that much vision on this regard.
I think the main reason they went UTF8 was for Japanese "market".
--
Nick Ing-Simmons
