One of the unfixed bugs I reported in the beta release has to do with the
Grade 2 translator. The bug can be suppressed, but at a price.
When you turn Grade 2 on, several symbols include dot 7 along with the
proper dots. These symbols include at least:
o w, e r, o u, dot 4, dots 4 5, and dots 4 5 6.
This effect can be eliminated by going to 6-dot Braille. If, like me, you
are primarily a computer Braille user, you can even add this to the
BrailleGrade2Translation script. However, this means that there is no way to
determine capitalization when the current word is expanded. You can turn
word expansion off in Config Manager or by using a script. It takes a little
getting used to, because no matter which routing button you push the cursor
goes to the beginning of the word and thus effectively eliminates what could
be a useful feature. If they could only change those darn square brackets to
curly brackets, backslashes to vertical bars, carets to tildes, ats to
graves and underscores to - um - the fly in the ointment? - ANSI 127s, then
we would have both accurately expanded words and accurate Grade 2.
Another feature which would be very useful would be to allow text to flow
from the next line onto this one. Short Braille lines slow down reading, and
some of these lines are very short indeed. There would have to be a toggle
for this since sometimes we read columns in Grade 2, though a smart flow
facility might be derived.
Some Europeans object to the American-style use of the capital indicator. It
would be nice if we could turn that off also. I'm sure none of this is under
the direct control of Henter-Joyce, but they can put pressure on the
developer or get a free product. But it's actually much easier to proofread
in Grade 2 since many mistakes are much more visible, including
capitalization errors.
Lee
-
Visit the jfw ml web page: http://jfw.cjb.net
