From: Steve Slevinski (slevin@signpuddle.net)
Date: Fri Jan 07 2011 - 09:23:07 CST
On 1/7/11 2:06 AM, William_J_G Overington wrote:
> I notice that the Unicode proposal is for some characters in plane 1.
>
> I notice that there is also some encoding of characters into plane 15, which is a Private Use Area plane.
For the purpose of standardization and the widest agreement possible,
I've stratified my document and split my encoding model into 2 parts:
symbol encoding (sections 2 - 4) and script encoding (appendix B).
http://tools.ietf.org/html/draft-slevinski-iswa-2010-00#section-1.3
Symbol encoding uses the x-ISWA-2010 coded character set, proposed for
plane 1. A lite markup will be required to represent structure and layout.
The script encoding described in section 5.2 and appendix B represents
structure and layout using the x-BSW3 coded character set, a superset of
the x-ISWA-2010. For data interchange, it is possible to send plain
SignWriting text only using characters from plane 15.
All of the characters proposed on plane 1 are mirrored on plane 15. The
additional characters on plane 15 include the 4 structural markers and
the number characters.
> Please correct me if I have misunderstood, yet it seems to me that the idea is to use those characters with a plane 15 encoding on a permanent basis, rather than to propose that they be encoded into regular Unicode.
In the future, there may be a second Unicode proposal to handle the
script encoding issues of structure and layout.
The split between symbol encoding and script encoding is stark. I
believe the symbol encoding can be universally accepted by the writers
of the script, the academic researchers, and the Unicode consortium.
Standardized symbolset - http://www.signbank.org/iswa
Standardized symbol encoding - http://signpuddle.net/sw_unicode
Standardization of the symbol encoding is the focus of the initial
Unicode proposal. This standard will lay the foundation for the
discussions about the script encoding model.
http://www.signpuddle.net/mediawiki/index.php/Unicode#Encoding_Model_Issues
Thanks for the input,
-Steve
This archive was generated by hypermail 2.1.5 : Fri Jan 07 2011 - 09:27:23 CST