<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:12pt"><DIV>I have just looked at the Wikipedia article on Hongul rendering using Unicode, and what the unicode font system has to do to assemble a word (merging more than one character in a set square). If Hongul can do it with a limited character set (around 240) then there is no reason that SignWriting cannot define itself with a character rendering. It doesn't stop Hongul from being rendered by computers and printed using them, nor transferring those character blocks into a newspaper printout. What is required is a defined drawing space, exactly similar to Hongul's rendering, and then that becoming the output to a printing space, or to transfer from what looks like a drawing in the SignPuddle lifted as an assembled block, directly into any printed page.</DIV>
<DIV> </DIV>
<DIV>Charles</DIV>
<DIV><BR> </DIV>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 12pt"><BR>
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt"><FONT size=2 face=Tahoma>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Charles Butler <chazzer3332000@yahoo.com><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> SignWriting List: Read and Write Sign Languages <SW-L@LISTSERV.VALENCIACC.EDU><BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Thu, May 27, 2010 11:47:34 AM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: Data exchange with SignPuddle Markup Language<BR></FONT><BR>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 12pt">
<DIV>How is Hongul (Korean) encoded. I thought it was spacial characters merged to look like graphics, not a corpus of words. There are only 20 letters in Korean, yet it does print looking like ideographs.</DIV>
<DIV> </DIV>
<DIV><BR> </DIV>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 12pt"><BR>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 13px"><FONT size=2 face=Tahoma>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Steve Slevinski <slevin@SIGNPUDDLE.NET><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> SW-L@LISTSERV.VALENCIACC.EDU<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Thu, May 27, 2010 11:10:44 AM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: Data exchange with SignPuddle Markup Language<BR></FONT><BR>MARIA AZZOPARDI wrote:<BR>> Dear Steve, Val and all the list,<BR>> I attended the LREC 2010 and I must say I was slightly disappointed at the<BR>> very low use of SignWriting in Computer Sign Language linguists. There<BR>> were some researchers that told me they considered SignWriting, but opted<BR>> for HanNoSys. It would be ideal if SignWriting were used, I thought, but I<BR>> probably can't understand the technicalities, as computers are not my<BR>> area.<BR>> Could you explain why the situation is so.<BR>> <BR><BR>Hi Maria,<BR><BR>The 2
main reasons for the low use of SignWriting in Computer Sign Language linguistics are conceptual and technological. Conceptually, SignWriting requires accepting a new paradigm, while HamNoSys is much more comfortable. Technologically, SignWriting presents unique challenges.<BR><BR>I'll try to explain how SignWriting is different and why there is a technology gap. Some of the details are simplified.<BR><BR><BR>Currently, in the computer world, there are 2 main types of script: one based on letters and the other based on pictographs. Both use a sequential list of characters, either "ABC" or "儷黑". A character is a very technical term that has many definitions, but simply put, a character is a number that can represents a letter or a pictograph. The letters "ABC" are sent by computer as the numbers 65, 66, and 67. The pictographs "儷黑" are sent as 2 numbers as well, such as 234452 and 222763.<BR><BR><BR>Now the question becomes how to encode
SignWriting. For the current technologies, the easiest way forward would be to label SignWriting as pictographic and analyze the corpus of each individual sign language. We could define a list of 20,000 signs for ASL. Stamp it as final and then create a font file (like Chinese) that could display those 20,000 signs. However, this list would never change and adding new signs would be laborious. And if this were to be done for all of the world's sign language, we would quickly run out of numbers for characters.<BR><BR><BR>When I look at SignWriting, I don't see pictographs, I see symbols on a 2 dimensional canvas. Current technology can not use characters in 2 dimensional space, only characters in a sequential list. This spatial nature of SignWriting is where the breakdown happens.<BR><BR><BR>Our current technique for SignWriting is to encode the script and not the individual languages. Once we encode the SignWriting script, we can write any sign
language. Since, the idea of a spatial script is outside of the current model, we are making our own model. The current SignWriting model is a collaboration between Valerie and myself.<BR><BR>The ISWA 2010 defines the alphabet (graphemes) of the script. An X,Y coordinate based writing style is used to combine the symbols to form signs. Binary SignWriting is the character encoding model that transforms the abstract symbols, structural markers, and numbers into a sequential list of characters.<BR><BR><BR>These developments represent the open standards of SignWriting. These standards were recently finalized and stabilized. With a 10 year freeze on these standards, I believe we are ready for wide spread adoption.<BR><BR>As we overcome the technological barriers, the conceptual barriers will drop as well. I'm predicting an explosion of acceptance for SignWriting. With all that we've done so far, I know we're
ready.<BR><BR>Regards,<BR>-Steve<BR><BR></DIV></DIV></DIV></DIV></DIV></div></body></html>