<DIV>Hi Stuart and Sandy,</DIV>
<DIV>Only question on your defaults on a keyboard is the necessity of having a head and torso as default in the system. For a lot of signs in the dictionaries currently loaded to SignPuddle, the body is "assumed" and not visible. I'd prefer to not have the body if I don't want it so at least one of the default "edits" would be to take out the body lines and head unless they are absolutely necessary. I use them for facial expressions and particular locational signs but for "neutral space" I use only the hands (and elbows) and heads for contact when necessary. The following examples are from LIBRAS. </DIV>
<DIV><IMG alt=cachorro src="http://signbank.org/signpuddle/sgn-BR/dict/sl/cachorro.png" align=middle border=0>(cachorro/dog) <IMG alt=futuro src="http://signbank.org/signpuddle/sgn-BR/dict/sl/futuro.png" align=middle border=0>(futuro/future) <IMG alt=tres src="http://signbank.org/signpuddle/sgn-BR/dict/sl/tres.png" align=middle border=0>(tres/three)<BR><BR><B><I>Sandy Fleming <sandy@FLEIMIN.DEMON.CO.UK></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Stuart,<BR><BR>> Hi! Those of us who are linguists or who approach things from a<BR>> systematic approach will likely consider that to be a simple enough<BR>> process. However, I am not sure if the rank-and-file deaf person will<BR>> analyze (or want to analyze) their movements to that degree. I don't<BR>> have a problem (if it can work) to have the computer automatically<BR>> assemble a handshape or symbol from components when I request that<BR>> handshape. But to have the user type in all the components plus<BR>> positioning information may be too much to expect.<BR><BR>Using components would probably make typing easier. For example in inputting<BR>a handshape you might have the letter keys to input a palm - and there are<BR>really very few palms in the SW system, especially if you don't include all<BR>the "exotic" ones such as the Spock handshape!
. You can
then add fingers, for<BR>example the number keys 1, 2, 3, 4, 5 would add that number of straight<BR>fingers to the palm. Then you could, say, bend, claw &c all the fingers at<BR>once with a single keypress. Finally any further refinements to individual<BR>fingers and the thumb. This way, all the main handshapes can be built up<BR>with a few keypresses each, the more difficult ones may take up more<BR>keypresses but I'd hope that as a general rule simple handshapes are the<BR>norm in sign languages and a section of the keyboard could be reserved to<BR>cater especially for the few that are difficult to type in the user's<BR>selected language. So he should be able to type the majority of handshapes<BR>in any language very quickly, the more exotic ones with some extra<BR>keypresses, and still have some "macro" keypresses available for quick<BR>access to the "exotic" handshapes in his own language. Hopefully these<BR>hard-to-type handshapes will be few in number in any given!
- I'm<BR>thinking of things like the Portuguese SL "figure eight" handshape.<BR><BR>Remember also that if we're using an IMWA subset for a language we might<BR>have less than 100 handshapes at our disposal. The software could only offer<BR>the available handshapes, helpfully restricting the range of choices for the<BR>user.<BR><BR>I think this is an awful lot easier than having to sort of _know_ the<BR>grouping structure of the SSS and having to go down through a tree of<BR>handshape categories. There's also a fast and easy way to get to any of the<BR>six orientations for a given handshape, involving the use of three keyboard<BR>keys without repeated keypresses. Say we use the keyboard U, I and O keys to<BR>control orientation - then let "I" toggle between wall and floor plane, let<BR>"U" rotate left and "O" rotate right. Then between zero, one or two<BR>keypresses is enough to select any orientation. This is much better than<BR>having to cycle through things all the
time.<BR><BR>I've been experimenting with this (aiming at a complete keying system<BR>without using the mouse) and it's possible to get plenty of room on the<BR>keyboard for everything by giving the user keypresses to select different<BR>editing modes. In each mode there's a different keyboard layout though this<BR>doesn't mean it's difficult to learn - most are either very similar, very<BR>simple, or are just involve alphabetic typing on the normal QWERTY keyboard.<BR>Here's my current set of keyboard modes:<BR><BR>head<BR>torso<BR>arm<BR>hand<BR>hands (ie two hands as a unit)<BR>fingerspelling<BR>mundschrift<BR><BR>But the first three can all probably fit on one keyboard and hand+hands on<BR>another, giving only four keyboards. The fingerspelling mode would just<BR>involve typing the normal QWERTY letters, as would the Mundschrift, though<BR>the Mundschrift mode would cause a new head to be added for each keypress,<BR>with the appropriate mouth for that letter.<BR><BR>The!
punctuation mode as I would hope to be able to use the period,<BR>comma, spacebar etc keys for punctuation regardless of the mode.<BR><BR>I think it would be good to have a standard keyboard but to let programmers<BR>experiment with alternatives for a few years to let the users decide what<BR>they like best.<BR><BR>We can also do a lot to minimise the amount of positioning required. We can<BR>have some "templates" for say, the neutral sign postion, top view and<BR>anything else that acts as a positioning pattern for common types of signs.<BR>On selecting a template it could be displayed in light blue and the typist<BR>types stuff in over it - it helps them to see exactly where to position<BR>things and also shows where the head &c will be automatically placed when<BR>she types it. The default template to be displayed as they start typing a<BR>fresh sign could consist of the head, shoulders, hips, arms and a couple of<BR>squares representing the hands, all in light blue !
background to the<BR>actual typing - see the attached gif for examples.<BR><BR>Use of the mouse, eg for clicking and dragging is less important to<BR>standardise, I think - it's probably better for each programmer to do it the<BR>way it works best for each program. But we should have a standard<BR>keyboarding system (after experimenting with alternatives) for touch typists<BR>to be able to input continuously without the mouse.<BR><BR>Sandy<BR><BR><BR>> ATTACHMENT part 2 image/gif name=templates.gif<BR></BLOCKQUOTE>