From: Kenneth Whistler (firstname.lastname@example.org)
Date: Mon Aug 22 2005 - 17:57:35 CDT
This is getting really off-track.
> Surely the whole point of TUNE is that it work with basic Unicode support,
That translates to: "it can be displayed with a dumb rendering engine
and a simple font".
> without any awareness of Tamil as a distinct script. Having a special
In fact adding TUNE to Unicode "without any awareness of Tamil
as a distinct script" is a recipe for disaster. It would be
mixing encodings without applications being aware of equivalences.
Searches and matches will fail. The only way it comes close
to being viable would be to treat it like the Hangul multiple
representations in the standard: you have to make the software
*aware* of the Tamil script to establish the equivalences between the
existing Tamil encoding and the TUNE encoding. Otherwise, you
might as well write off New Tamil as an unencoded script in the
PUA, which is what it is now and will continue to be, if pushed
> charset defeats that purpose.
Encoding TUNE, whether in the PUA or elsewhere, *without any
awareness of Tamil as a distinct script*, defeats the purpose
of an encoding in the first place.
This archive was generated by hypermail 2.1.5 : Mon Aug 22 2005 - 17:58:42 CDT