<html><head><base href="x-msg://33/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">SignWriting List<div>September 15, 2011</div><div><br></div><div>Hello Alan, Steve, Ingvild, Stefan, Charles, Adam, Bill and everyone -</div><div><br></div><div>Thank you, Alan, for your beautiful description of your need for stable software, and thanks to Steve, and his huge efforts, we can gladly say that YES...the software is stablized. Of course there are always little tweaks that can be done, and new features can always be added upon the central core of his code, but Steve has now provided us with stability. THANK YOU, Steve, for your planning and making this possible.</div><div><br></div><div>And the ISWA 2010, with all its flexibility and large number of symbols, gives us a tool to be able to write in whatever style of SignWriting we choose. Within the ISWA 2010, using the symbols there, people can build new symbols if they need to, without disturbing the older symbols that other people use daily. So there is stability from the symbol core as well. The ISWA 2010 is a tool to build sign language documents and dictionaries for the future.</div><div><br></div><div>As an example, Stefan, and his marvelous team in Germany, has already written 15,581 entries in the SignPuddle DGS Dictionary - An amazing and impressive amount of signs, all using the ISWA 2010, as do all the dictionaries and documents in SignPuddle.</div><div><br></div><div>Jonathan Duncan, in Honduras, is another programmer who is using the ISWA 2010 for his new software, SignWriter Studio, which is close to Beta testing. SignWriter Studio will also coordinate with SignPuddle, which will be very useful.</div><div><br></div><div>If there are any older documents, Ingvild, that you would like to have copied from old software or old print-outs, into SignPuddle 1.6 online, we can do that copy work for you. Tell me if you need that service...it is free to anyone with old documents that need to be copied into SignPuddle...Just contact me and send me your old documents, whether they are in SignWriter DOS or are pdf documents or whatever - we will copy the signs in one at a time without changing anything - you can then go in and edit them later.</div><div><br></div><div>I will answer everyone's other messages as soon as I can - I look forward to it, believe me...it will be fun!</div><div><br></div><div>Have a wonderful day everyone -</div><div><br></div><div>Val ;-)</div><div><br></div><div>---------</div><div><br><div><div>On Sep 15, 2011, at 2:23 AM, Ingvild Roald wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Arial; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; "><div dir="ltr">Thanks Steve,<br><br>now I dare do some more work on the Norwegian files. I have been puting it up for some time because of the changes and the need to do things over - now I hope that things will work steadily.<br>(Sorry I have to wait a little longer, because of other pressing work, but I look forward to seet myself down to re-enter hundreds of signs, and quite a few that I never entered before too).<br><br>Ingvild<span class="Apple-converted-space"> </span><br><br><div>> Date: Wed, 14 Sep 2011 13:02:37 -0500<br>> From:<span class="Apple-converted-space"> </span><a href="mailto:slevin@SIGNPUDDLE.NET">slevin@SIGNPUDDLE.NET</a><br>> Subject: Re: Put the blame on me ;-)<br>> To:<span class="Apple-converted-space"> </span><a href="mailto:SW-L@LISTSERV.VALENCIACOLLEGE.EDU">SW-L@LISTSERV.VALENCIACOLLEGE.EDU</a><br>><span class="Apple-converted-space"> </span><br>> Hi Alan,<br>><span class="Apple-converted-space"> </span><br>> Thanks for you comments.<br>><span class="Apple-converted-space"> </span><br>> On 9/14/11 9:32 AM, Alan Post wrote:<br>> > I have struggled just to keep up with the changes to SWIS and<br>> > ISWA--I've had to convert my database three or four times, which<br>> > sometimes takes me many months to get around to--during which I<br>> > don't use SignWriting. :-(<br>><span class="Apple-converted-space"> </span><br>> Yes, I understand this very well. Every time I put out a new standard,<span class="Apple-converted-space"> </span><br>> I make additional busy work for myself and others. Back in 2008, I was<span class="Apple-converted-space"> </span><br>> hoping that I had a stable standard, but every time that I tried to use<span class="Apple-converted-space"> </span><br>> the standard, I always found a serious flaw that could not be<span class="Apple-converted-space"> </span><br>> overlooked. I would find that my code libraries were becoming overly<span class="Apple-converted-space"> </span><br>> complicated and slow. The only way to address the various flaws was<span class="Apple-converted-space"> </span><br>> with a new encoding.<br>><span class="Apple-converted-space"> </span><br>> > I *love* SWIS2. I am producing documents with it that are so, so<br>> > beautiful compared to SWIS. I don't wish to complain about where<br>> > we are, but to articulate just how expensive changes are, to me.<br>> > Even seemingly minor issues can be major headaches for me--I would<br>> > much rather be in the business of *using* SignWriting!<br>> Agreed! I love SWIS 2 as well. The code is simple and clean. It does<span class="Apple-converted-space"> </span><br>> what I want it to do. I have plans to expand the code and there are no<span class="Apple-converted-space"> </span><br>> more serious flaws that will get in the way.<br>><span class="Apple-converted-space"> </span><br>> The ISWA 2010 has been stable since it's release in 2010 and the Unicode<span class="Apple-converted-space"> </span><br>> proposal will hopefully be approved next year.<br>><span class="Apple-converted-space"> </span><br>> There will not be any more changes to the encoding so you will not need<span class="Apple-converted-space"> </span><br>> to convert your database again. Any writing you do today will still be<span class="Apple-converted-space"> </span><br>> valid years from now.<br>><span class="Apple-converted-space"> </span><br>> Fortunately, the question of writing style is outside of the encoding.<br>><span class="Apple-converted-space"> </span><br>> Regards,<br>> -Steve<br>><span class="Apple-converted-space"> </span><br></div></div></div></span></blockquote></div><br></div></body></html>