<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">The Korean alphabet does not use XY coordinates for its construction of words. My understanding is that there are specific rules for how the characters combine and so those rules are built into the rendering system. Sometimes, like for Chinese, there are a limited set of helper characters that can be included in the Unicode stream that indicates how the various characters combine. The point being that spoken language writing systems are very restricted in the way their letters combine. Even Chinese has very limited sets of how they can combine their characters into a new character.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>SignWriting, on the other hand, is much more free in how various symbols combine. Part of my research will involve studying what restrictions are present in the system (for example, can a contact symbol connect with an arrow? Can a face and an arm symbol interact? etc.) Once we know what restrictions are present in how symbols interact with each other and where symbols do tend to connect and where symbols do not connect, we can begin to develop rules for SignWriting with Unicode. Remember, for Unicode, we have to consider how to take a 1D text string and represent it as a 2D SignWriting word. So we have to consider what needs to be present to make that transition successful so that the renderer knows how to select the appropriate symbols and display them properly.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>There are alternatives to XY coordinates and that will be what I will research to see if it will work.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Thanks,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Stuart</DIV><DIV><BR><DIV><DIV>On May 3, 2007, at 11:56, Charles Butler wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">I am curious as to why XY coordinates would not be well received with the Korean alphabet and its construction of words included in the corpus. That writing system requires every letter having its forms and space locatives available. <BR><BR>Arabian script has endings that have to be attached or moved depending on the appearance of the word. <BR><BR>When one works with Chinese, if one were working with the 32 possible brush strokes to construct a new symbol, one needs XY coordinates.<BR><BR>Same thing for Cree, apparently based on Gregg shorthand.<BR><BR>Charles Butler<BR><BR><BR><BR><B><I>Stuart Thiessen <<A href="mailto:sw@passitonservices.org">sw@passitonservices.org</A>></I></B> wrote:<BLOCKQUOTE class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> See my comments below ...<BR><BR>Stuart<BR><BR>On May 1, 2007, at 9:10, Steve Slevinski wrote:<BR><BR>> Unicode<BR>> -----------------------<BR>> MovementWriting in general needs a Unicode platter of 56 thousand <BR>> symbol places. Each symbol should get it's own space, or be <BR>> logically combined some how. It's going to be political to get a <BR>> new platter opened, but the existing 256 spaces in a nearly full <BR>> platter are not enough.<BR><BR>My contacts who work with non-Roman scripts assure me that there is <BR>no problem with getting space for SignWriting. That is not the main <BR>issuel. The biggest issue is deciding what should appear in the slots <BR>and what should be handled by the renderer. In addition to that, we <BR>will have to convince them of our method of rendering SignWriting <BR>(whatever that ends up being). I strongly believe we will have to do <BR>some unique things to make SignWriting work with Unicode compared to <BR>the way most spoken languages are rendered in Unicode today. So that <BR>will be a greater issue than the number of symbols. My conversations <BR>with my contacts indicate that x/y coordinates may not be well <BR>received. So I am exploring other alternatives to x/y coordinates for <BR>symbol placement. Also, whether it is on existing planes or a new <BR>plane, we will have to see what is available when our proposal is <BR>ready. My initial efforts will be focused on SignWriting proper. But <BR>I agree that a strong case exists for bringing in all of the Movement <BR>writing symbols.<BR><BR>><BR>> Unicode and SVG<BR>> -----------------------<BR>> Once each symbol has a unique number, we can create font files for <BR>> SignWriting. We may be able to have a single font file, or we may <BR>> need multiple font files. Since we'll already have the SVGs <BR>> completed, we can use the SVG style fonts. This whole process will <BR>> be repackaging. There should be automated tools that can help. <BR>> Maybe even font experts..<BR><BR>I believe that it should be no problem to contain all the symbols in <BR>one font file. After all, they have font files with nearly every <BR>writing system included that are several megabytes in size. It may be <BR>that our font file has very minimal support for spoken languages and <BR>only contains movement writing symbols.<BR><BR>Thanks,<BR><BR>Stuart<BR><BR></BLOCKQUOTE><BR></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>