From: John H. Jenkins (jenkins@apple.com)
Date: Tue Jun 01 2010 - 10:53:13 CDT
First of all, as Michael says, this isn't character encoding. You're not interchanging plain text. This is essentially machine language you're writing here, and there are entirely different venues for developing this kind of thing.
Secondly, I have virtually no idea what problem this is attempting to solve unless it's attempting to embed a text rendering engine within plain text. If so, it's both entirely superfluous (there are already projects to provide for cross-platform support for text rendering) and woefully inadequate and underspecified. Even if this were sufficient to be able to draw a currently unencoded script, the fact of the matter is that it doesn't allow for doing anything with the script other than drawing. (Spell-checking? Sorting? Text-to-speech?)
Unicode and ISO/IEC 10646 are attempts to solve a basic, simply-described problem: provide for a standardized computer representation of plain text written using existing writing systems. That's it. Any attempt to use the two to do something different is not going to fly. Creating new writing systems, directly embedding language, directly embedding mathematics or machine language--all of these are entirely outside of Unicode's purview and WG2's remit. They simply will not be adopted.
Your enthusiasm may be commendable, but you're spending your energy developing something which is not appropriate for inclusion within Unicode.
This archive was generated by hypermail 2.1.5 : Tue Jun 01 2010 - 10:55:11 CDT