Hi Tara,
This is not a bug. The reason it works this way is that the underlying
text you are reading is in computer braille. If you have your prefered
reading grade set to grade 2 the text on the braille display will be
showing in grade 2 as you are reading through with the thumb keys.
However, as soon as you press a cursor key above the a word, the display is
placed into editing mode and the word is displayed as it is actually stored
in the file, that is in computer braille. At that point the cursor is then
placed at the beginning of the word. If you then want to move to a
character within the word you can press the cursor key above the required
character.
Maurice
________________________
Maurice Sloane
Sales & Support Manager - Blindness
HumanWare
Direct Dial: +64 3 940 2223
Mobile: +64 21 528 374
email: [EMAIL PROTECTED]
Website: www.humanware.com
"Taraprakash"
<[EMAIL PROTECTED]
l.com> To
"Mike Schmitt"
09/07/2007 02:44 <[EMAIL PROTECTED]>,
PM <[EMAIL PROTECTED]>
cc
"braillenote"
<[email protected]>
Subject
problem with text files
Hi all.
I am wondering if someone else also has this problem. When I am working in
a
file other than in brf format in keyword, the cords on the display do not
behave the way they do in brf files. If, for instance, I press the cord
above the letter g in the word "English", the cursor will not jump to g but
will go to the beginning of that word, that is, the letter e.
Is it a known problem, or a specific one?
Any idea if it is going to be addressed in the future releases?
Regards
Tara
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Mike Schmitt" <[EMAIL PROTECTED]>
Cc: "braillenote" <[email protected]>
Sent: Thursday, September 06, 2007 10:05 PM
Subject: Re: [Braillenote] problem with saving braille file as rich text
format
> Hi Mike,
>
> We confirm that this is an issue, when saving a braille document to
> another
> format from within that document to a text document, be it an ASCII, RTF
> or
> MS Word file.
>
> Rhonda Clarke's suggestion of exporting the document via the Translation
> Menu is a good work-around. We will investigate what is causing this
> issue.
>
> Maurice
> ________________________
> Maurice Sloane
> Sales & Support Manager - Blindness
> HumanWare
>
>
> Direct Dial: +64 3 940 2223
> Mobile: +64 21 528 374
> email: [EMAIL PROTECTED]
> Website: www.humanware.com
>
>
>
> "Mike Schmitt"
> <[EMAIL PROTECTED]
> .net> To
> Sent by: "braillenote"
> braillenote-bounc <[email protected]>
> [EMAIL PROTECTED] cc
> .com
> Subject
> [Braillenote] problem with saving
> 09/07/2007 10:20 braille file as rich text format
> AM
>
>
>
>
>
>
>
>
>
> Hi all, I upgraded to keysoft 7.5 build 18 and am using mPower. I
created
> document in braille keyword format and then saved the file as rich text
> format. Several letters were not translated properly. For example, the
> in
> contraction was translated as number 9 when saved in rich text format.
> The
> braille code is set to USA. Does anyone have a suggestion regarding a
> work
> around. Thanks.
>
> Mike
> ___
> Replies to this message will go directly to the sender.
> If your reply would be useful to the list, please send a
> copy to the list as well.
>
> To leave the BrailleNote list, send a blank message to
> [EMAIL PROTECTED]
> To view the list archives or change your preferences, visit
> http://list.humanware.com/mailman/listinfo/braillenote
>
>
>
>
> ___
> Replies to this message will go directly to the sender.
> If your reply would be useful to the list, please send a
> copy to the list as well.
>
> To leave the BrailleNote list, send a blank message to
> [EMAIL PROTECTED]
> To view the list archives or change your preferences, visit
> http://list.humanware.com/mailman/listinfo/braillenote
>
___
Replies to this message will go directly to the sender.
If your reply would be useful to the list, please send a
copy to the list as well.
To leave the BrailleNote list, send a blank message to
[EMAIL PROTECTED]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
