[Athen] Warning on Duxbury/Word problem

[Gaeir Dietrich]

And what is the fix?

****************************************************** 
Gaeir (rhymes with "fire") Dietrich 
High Tech Center Training Unit of the 
California Community Colleges 
De Anza College, Cupertino, CA 
www.htctu.net 
408-996-6043 

  _____  

From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org] On
Behalf Of Manning, Melissa Ann
Sent: Wednesday, February 07, 2007 8:17 AM
To: athen at athenpro.org
Subject: [Athen] Warning on Duxbury/Word problem

 

I know this may affect only a small number of folks who use Duxbury for
translating foreign languages into Braille, but for those who do I think you
really need to know about this problem.  

When we use Duxbury to put in a foreign language, we highlight the portion
to be translated into a foreign language, and thus into grade 1 exact
Braille for that language.  We have just discovered that Microsoft WORD goes
into the file if it is in WORD, and puts in its own foreign language codes,
which are wrong most of the time. It will put in a little shaded code in
parens (e.g., (lng~it)that change the language and then mess up the grade 1
and grade 2 Braille.  In the last WORD document we were using to explore
this, which should have been Italian/English combination, WORD even put in
Danish! There is a simple fix for this, you can pull all that trash WORD
code out with one operation, but if you don't know about it, it can really
mess you up.  I talked to Peter Sullivan, the VP of software development at
Duxbury, and he said Duxbury had made an actual decision to honor the WORD
foreign language code, possibly mistakenly.  I would add, that was very
mistakenly.  

Thanks, 
Melissa 

 

Melissa Manning 
Disability Resources 
University of Kansas 
manning at ku.edu 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20070207/5999cc04/attachment.html>