<DIV>Dear Louis-Felix, SW list, and other linguists.</DIV>
<DIV> </DIV>
<DIV>I appreciate you bringing up the French translations of "text processors" as an example of where technology might get in the way of mutual understanding when a single term will do for both signed and spoken languages.</DIV>
<DIV> </DIV>
<DIV>However, when I speak of spoken languages I use phonemes for the smallest recognizable unit of an utterance, for signed languages I use chereme because the parsing of the language is so different. For speech it is only sounds that occur, for signs the entire body may be involved and the division of those articulations, in SW or in Hamnosys is different. </DIV>
<DIV> </DIV>
<DIV>For the word "hello" in English there are four phonemes "h" + "e" + "l" = "o". The "o" may be a diphthong depending on the dialect. The same ASL sign is four cheremes, "the facial contact point," "the hand on edge", "the hand held at an angle" and "the movement forward." There is no way that I could call any of these signed parsings "phonemes" though both sets could be called "morphemes" as "units of meaning."</DIV>
<DIV> </DIV>
<DIV>The science of one is phonetics, the science of the other cheremics. Related, but not the same terminology. We will need to work through our common languages until we find analogous terms that are not confusing for "sign processing" , "sign editing" , and other terms.</DIV>
<DIV><BR><B><I>Valerie Sutton <sutton@SIGNWRITING.ORG></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">SignWriting List<BR>June 17, 2004<BR><BR>Dear SW List, and Louis-Felix!<BR>Thanks for this message, and it was interesting reading for me...As you <BR>know, I am not a linguist, and although I did start SignWriting at the <BR>University of Copenhagen, because researchers asked me to write some <BR>Danish signs (and some hearing persons' gestures)....even so....after <BR>that...I worked directly with Deaf people. There were 10 Deaf people <BR>who worked as Sign Language reporters for the SignWriter Newspaper, and <BR>wrote their articles directly in SignWriting in ASL, without any spoken <BR>language...no translations from spoken language to signed <BR>languages...instead the translations were reversed and the spoken <BR>language came after the signed language articles were written...After <BR>that, more and more Deaf people became involved and in 1988, Lucinda <BR>O'Grady Batch
suggested starting a Deaf Action Committee for <BR>SignWriting, the DAC...and that had a profound influence on the writing <BR>system...<BR><BR>You probably wonder why I am rambling on like this about Deaf <BR>influence, and not linguistic-research influences...but there is a <BR>reason...Reading what you say below, and following the linguistics <BR>terminology that all units of languages are called words...which is <BR>logical, I can see that....this would mean that the name Sign Language, <BR>would have to be changed to Word Language, and the term SignWriting <BR>would have to be changed to WordWriting...and would deaf people really <BR>recognize that we are talking about signed languages, when we say Word <BR>Language? No...I don't think so! And if we call SignWriter DOS a word <BR>processor..that is only ok as long as you say: .....word processor for <BR>signed languages...if you don't add that information, they will think <BR>you are talking about English or French...so I was
just using the term <BR>Sign, as the unit of Sign Languages...and for the everyday person who <BR>signs, I don't think that is illogical at all! it is faster, and less <BR>dependent on the spoken language terminology...<BR><BR>Recently there are more and more linguists using SignWriting in their <BR>research, and so now, as the everday world of writing, and the detailed <BR>analysis of researchers combine, there may be more terminology <BR>confusion...but in time, as you say, it will work its way out...<BR><BR>And ironically, in the past, I was criticized for calling SignWriting <BR>text...it is, and you are right, but computer programmers did not treat <BR>it as text - it was only text inside the SignWriter environment, and <BR>when it left SGN or DIC or DIN files, and was used in other computer <BR>programs, it was considered graphics, not text...so there is an example <BR>of how terminology is different, depending on the profession that uses <BR>it...<BR><BR>Val
;-)<BR><BR><BR><BR><BR><BR>On Jun 17, 2004, at 6:06 AM, Louis-F }_ ix Bergeron wrote:<BR><BR>> I'm glad that we don't have that "word processor" terminology problem <BR>> in<BR>> french.<BR>><BR>> We call it "text processor" (traitement de texte)... And a text is a <BR>> text,<BR>> either it is written in spoken language or in sign language.<BR>><BR>> For the word definition, I think "word" is generally considered as a<BR>> structure level in linguistics. Like the structure levels in chemistry<BR>> (quark, electrons-protons-neutrons, atoms, molecules, etc.), language <BR>> has<BR>> its structure levels too (phonologic features, phonemes, syllables,<BR>> morphemes, words, phrase, sentence, etc.). Even if some level names <BR>> were<BR>> created for spoken language structure levels, I don't think it is <BR>> really<BR>> useful to have different names for sign language structure levels, just<BR>> because some names (like phonemes,
for example) could include a "sound<BR>> related" meaning. And it doesn't seem useful for me especially when we <BR>> are<BR>> talking about writing.<BR>><BR>> But maybe we are rushing things... Terminology have been gradually <BR>> designed<BR>> with years of reflexion, usage and convention. As it has been said in <BR>> this<BR>> list, written forms for spoken language and relfexion on spoken <BR>> languages<BR>> have centuries of history. Sign language research and written forms for<BR>> sign language have a history of just only very few decades... Even if <BR>> we<BR>> try to have the best terminology, usage and time will make their way. <BR>> And<BR>> this way may be different that what we wish it could be.<BR>><BR>> Louis-Felix<BR>><BR></BLOCKQUOTE>