<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-mailStijl17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=NL link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello Tom,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Interesting point you make about sign-to-text interpreting. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For as far as I know that is unheard of in Belgium. Mostly it is
either sign language – spoken language (and vice versa) or spoken
language to text.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Can you provide me with examples of situations where sign
language-to-text interpreting is necessary or preferred?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thank you in advance,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Isabelle Heyerick<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
slling-l-bounces@majordomo.valenciacc.edu
[mailto:slling-l-bounces@majordomo.valenciacc.edu] <b>Namens </b>twflynn@aol.com<br>
<b>Verzonden:</b> maandag 25 februari 2008 6:09<br>
<b>Aan:</b> slling-l@majordomo.valenciacc.edu<br>
<b>Onderwerp:</b> [SLLING-L] Sign-To-Text Interpreting (Was Interpreters as
Typists)<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>I had a discussion on just this topic, about two years
ago, with an agency that has Deaf employees. <br>
<br>
The agency wanted me to provide ten or twelve workshops to help the Deaf
employees improve their written English. The agency has interpreters on staff,
so I tried to convince the agency to use the interpreters - let the Deaf
employees sign their texts, let the interpreters voice the text onto audio
tape, and let the secretaries transcribe the voicing onto paper.<br>
<br>
The agency no longer hires secretaries - each employee writes documents on
her/his own desktop computer.<br>
<br>
So I recommended that the interpreter watch the signed text (in real time)
and transcribe it onto the Deaf employee's desktop computer. <br>
<br>
My thought is that the interpreter's job is to convert text from source
language to target language, but the target language doesn't necessarily have
to be produced with the voice. Converting from signed ASL to written
English is just as much within the purview of "interpreting" as going
from signed ASL to spoken English. Technically, it might be defined more as
"translating", or somewhere on a continuum between translating and
interpreting, but all of that is a moot point to a Deaf individual who needs to
transcribe a spoken language. And there is probably more need
for sign-to-text interpreting than most people imagine - or there
will be as more and more Deaf individuals take mainstreamed jobs under the ADA
(here in the US). <br>
<br>
Some caveats: <br>
<br>
1. The interpreter may want or need to use the consecutive mode of interpreting
for this kind of work. Typing is generally slower than speaking. <br>
<br>
2. The interpreter ought not to be held responsible for formatting the document
- the Deaf employee should know the company/agency expectations for that sort
of thing.<br>
<br>
3. The interpreter should be held responsible for correct syntax, grammar,
vocabulary, spelling, and punctuation. Anna Whitter Merithew maintains that
interpreters need to know both languages (source and target) deeply; knowing
the syntax, grammar, vocabulary, spelling, and punctuation is simply part of
knowing the target language deeply.<br>
<br>
Tom Flynn<o:p></o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='margin-top:7.5pt;text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-top:7.5pt'>More new features than ever. Check
out the new <a
href="http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/text.htm?ncid=aolcmp00050000000003"
target="_blank">AOL Mail</a>!<o:p></o:p></p>
</div>
</div>
</body>
</html>