{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Sandy Swan <[EMAIL PROTECTED]>
>{#} Replies are directed back to [EMAIL PROTECTED]
>{#} To reply to the author, write to Sandy Swan <[EMAIL PROTECTED]>
>
>>{#} Replies are directed back to [EMAIL PROTECTED]
>>{#} To reply to the author, write to RJ Auburn <[EMAIL PROTECTED]>
>>
>>On 03/26/2002 10:27, "Colter Reed" <[EMAIL PROTECTED]> wrote:
>>> I don't think this is a good idea. The fact that they're speaking *another
>>> language* entirely should be clue enough that there may be some
>>> miscommunications. Besides, even without Fire's help, miscommunications
>>> happen when someone is speaking a language in which one is not fluent.
>>> Miscommunications happen even when people are speaking the same language,
>>> native to both speakers.
>>>
>>> All that will be accomplished by echoing back the translated copy is the
>>> confusion of the remote user and and the convolution of the conversation.
>>> If a Spanish-speaker is using Fire to talk with me in English, having the
>>> Spanish translation of what I send them in English echoed back to me is
>>> going to be of no use to me. I don't speak Spanish, so being able to see
>>> how what I said translated is literally meaningless.
>>
>>I think it would be good to send the original message. If the translation
>>does not make sense the recipient can then use other resources to try and
>>translate it if needed. I would suggest a preference option to control this
>>setting.
>>
>> RJ
>>
>>--
>>RJ Auburn
>>Chief Network Architect
>>Voxeo Corporation
>>Bring your web application to the phone for free.
>>Find out how at http://community.voxeo.com
>>
>>
>>{#} ----------------------------------------------------+[ fire ]+---
>
>
>--
>unsubscribe
>
>{#} ----------------------------------------------------+[ fire ]+---
--
unsubscribe
{#} ----------------------------------------------------+[ fire ]+---
