<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Steve,<br>
Here are some comments about the technical document.<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>
<pre class="western">Copyright Notice</pre>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<p>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<pre><span
style="background: transparent none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">Code Components extracted from this document must include Simplified BSD License text as
described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
</span></pre>
<p><span
style="background: transparent none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">Does
this include implementing the SignWriting Script or just code lifted
from the document? Why the BSD? If I recall it is the first time we
are using this license. Just curious. <br>
</span></p>
<p>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>
<pre class="western">1.1.1. Grapheme</pre>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
A:link { so-language: zxx }
-->
</style>
<pre><span
style="background: transparent none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">The graphemes do not change size or shape when combined in a visual pattern.</span></pre>
Do you mean that only one font size will be available? I am
implementing SignWriter Studio to change the size of each individual
grapheme within the sign. Am I to understand that the SignWriting
Script will not support this feature? Or at least not within the
script directly? How would you modify the size of one grapheme and not
another if it is not part of the script? It would be problematic to
qualify the size of anything more than a full sign. If you meant that
size is not affected directly by combining the graphemes, then how is
font size to be specified, it didn't notice it in any other part of the
document.<br>
</p>
<p>Something else I didn't notice was custom coloring of the
graphemes. How will this be supported?<br>
</p>
<pre><meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1"><title></title><meta
name="GENERATOR" content="OpenOffice.org 3.2 (Win32)"><style
type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>
<h3 class="western">2. ISWA 2010 Design
</h3></pre>
</p>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<pre>A symbol ID is a unique combination of 6 numbers connected by
dashes(-) as numbered by 11-22-333-44-55-66.
</pre>
Are the dashes for better readability? For computing purposes I
personally prefer a fixed length string without the dashes as it is a
bit more compact and would already have concatenated numbers for
searches on indexed columns. Otherwise the dashes need to be removed
first to do the same which isn't a problem but adds to the computing
cost. Being that you have fixed length anyways why use both methods?<br>
<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>
<pre class="western">2.2. Symbol</pre>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<pre><span
style="background: transparent none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">The fill modifier can best be understood through the hand symbols. The first 3 fills are understood from the expressive viewpoint: signs as seen by the
signer. The last 3 fills are understood from the overhead viewpoint: signs as seen when looking down on the signer. </span></pre>
<p></p>
You might want to mention that there are 6 different fills. That they
represent the palm facing. This paragraph has a drastic jump from the
previous ones and should be more explicit for people not well aquainted
with SignWriting. Or consider briefly presenting the fills, put the
table then this paragraph.<br>
<br>
<pre>Rotations Table </pre>
<table width="322" border="0" cellpadding="2" cellspacing="0">
<tbody>
<tr>
<th width="62">
<p align="LEFT">Rotation</p>
</th>
<th width="126">
<p align="LEFT">Direction</p>
</th>
<th width="122">
<p align="LEFT">Degrees from top</p>
</th>
</tr>
</tbody>
</table>
<br>
Consider mentioning that rotations 09-16 are mirrored. Otherwise it
would seem like repeated graphemes but only in another order.<br>
<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<pre>A string of x-bsw3 characters must be well formed to be valid.
Validity can be determined with regular expressions. Validity can be
verified with a left to right parser, one character at a time.
Validity can be defined with <span
style="background: rgb(255, 0, 0) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">ABNF</span>.
</pre>
What is ABNF?<br>
<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>
<pre class="western">B.3.1. Format</pre>
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<pre><span
style="background: transparent none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;">Alternately, a space can be
used every 72 characters to chunk Binary SignWriting into fixed width
character strings. </span>
</pre>
<br>
Why is chunking important? I there any risk that a sign might be
broken up by one of these spaces?<br>
<br>
<b>General comments.</b><br>
<br>
Short concise examples could help make the concepts clearer to
readers. The text is well written and generally has sufficiently
concrete explanations while still covering the full spectrum of the
problems at hand. <br>
<br>
It seems that there are several distinct formats of the script
discussed in the document. It might be useful to explain the
difference between them and introduce them more distinctively when
going from one to the other.<br>
<br>
The ones I noticed: <br>
<ol>
<li>Symbol/Grapheme code (has dashes)</li>
<li>Coded Character Set (256-929) </li>
<li>
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>Combined
Character Sequence</li>
<li>
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>Unicode
Integration (Shift of Combined Character Sequence for use as Unicode)</li>
<li>
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
-->
</style>Interchange
(Another shift. Why if we already did a shift in the previous step?)
</li>
</ol>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.cjk { font-family: "SimSun" }
H3.ctl { font-family: "Mangal" }
--> </style><br>
It would be useful to explain what each one has in common with the
previous and in which way it differs. Maybe a short example throughout
the whole document would be helpful.<br>
<br>
<br>
Good work Steve<br>
<br>
<br>
Wish you the best when you present it. <br>
<br>
Looking forward to your comments.<br>
<br>
<br>
Jonathan<br>
<br>
<br>
<br>
On 12/23/2010 7:44 PM, Jonathan wrote:
<blockquote cite="mid:4D13FAFC.1020108@yahoo.ca" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<br>
On 12/23/2010 7:10 AM, Steve Slevinski wrote:
<blockquote cite="mid:4D134A48.3040907@signpuddle.net" type="cite">Hi
List, <br>
<br>
I'm about to submit a technical document on encoding the graphemes of
the SignWriting script. I will be submitting the document New Years
Day. Although there are a lot of technical details, I'd appreciate any
feedback. <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.signpuddle.net/draft-slevinski-iswa-2010-pre.html">http://www.signpuddle.net/draft-slevinski-iswa-2010-pre.html</a>
<br>
<br>
The main body includes sections on the SignWriting script, the
International SignWriting Alphabet 2010, the x-ISWA-2010 coded
character set, and Unicode integration. <br>
<br>
Appendix A is table data for the ISWA 2010 categories, groups, and
bases. <br>
<br>
Appendix B is the Binary SignWriting revision 3 reference with sections
on design, validity, and processing. <br>
<br>
Regards, <br>
-Steve <br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
No virus found in this incoming message.
Checked by AVG - <a moz-do-not-send="true"
class="moz-txt-link-abbreviated" href="http://www.avg.com">www.avg.com</a>
Version: 9.0.872 / Virus Database: 271.1.1/3334 - Release Date: 12/23/10 13:34:00
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<pre
style="font-size: 3pt; color: rgb(0, 0, 0); font-weight: 900; font-family: 'Courier New',Courier,monospace;"> _ ____
/\ | | (| \
| | __ _ _ __, _|_ | | __, _ _ | | _ _ __ __, _ _
| | / \_/ |/ | / | | |/ \ / | / |/ | _| || | / |/ | / / | / |/ |
\_|/\__/ | |_/\_/|_/|_/| |_/\_/|_/ | |_/ (/\___/ \_/|_/ | |_/\___/\_/|_/ | |_/
/|
\| </pre>
<p> email: <a moz-do-not-send="true"
href="mailto:duncanjonathan@yahoo.ca">duncanjonathan@yahoo.ca</a><br>
<a moz-do-not-send="true" href="mailto:joyoduncan@gmail.com">joyoduncan@gmail.com</a><br>
Cel: 9784-9775<br>
Tel: 213-5285<br>
Skype: yojoduncan<br>
<br>
<a moz-do-not-send="true" href="http://www.signwriterstudio.com/">SignWriter
Studio</a></p>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<pre
style="font-size: 3pt; color: rgb(0, 0, 0); font-weight: 900; font-family: 'Courier New',Courier,monospace;"> _ ____
/\ | | (| \
| | __ _ _ __, _|_ | | __, _ _ | | _ _ __ __, _ _
| | / \_/ |/ | / | | |/ \ / | / |/ | _| || | / |/ | / / | / |/ |
\_|/\__/ | |_/\_/|_/|_/| |_/\_/|_/ | |_/ (/\___/ \_/|_/ | |_/\___/\_/|_/ | |_/
/|
\| </pre>
<p> email: <a href="mailto:duncanjonathan@yahoo.ca">duncanjonathan@yahoo.ca</a><br>
<a href="mailto:joyoduncan@gmail.com">joyoduncan@gmail.com</a><br>
Cel: 9784-9775<br>
Tel: 213-5285<br>
Skype: yojoduncan<br>
<br>
<a href="http://www.signwriterstudio.com/">SignWriter Studio</a></p>
</div>
</body>
</html>