I coded in assembly language for many years using speech. Before that, I
used an Optacon to read the CRT screen. The coding was modifying the
operating system of our mainframe computers to add new functionality
(often real-time functions) and/or to enhance existing functionality.
This necessitated reading large amounts of assembly-language code (at
first via OPtacon; then with speech). Speech synthesizers back then were
somewhat primitive; they pronounced exactly what was sent to them -- or
tried to. Assembly-language made for some pretty weird pronunciations.
However, this was an advantage in that I got used to it and could handle
the code about as easily as I could hard-copy. To ascertain format, I
tended to use the "read cursor position" key copiously. However, I don't
know that I could have handled assembly-language coding with speech had I
not previously seen the screen layout with an Optacon.
I believe the method one uses for computer access is a rather personal
thing -- there's no one best method for everyone. Personally, I prefer
speech because I do not have to take my hands off the keyboard. Others
cannot *stand* that machine blatting at them all day. I know my
colleagues would crucify me if I did not use phones!
I think John's ideas for Braille formatting are interesting and deserve
serious consideration. Above all, I think he is right in insisting that
the reader should have full control over Braille format.
-- Mike Freeman | Internet: firstname.lastname@example.org Amateur radio: K7UIJ | GEnie: M.Freeman11 /* PGP2.6.2 PUBLIC KEY available via finger or PGP key server */ ... Ask not for whom the <^G> tolls.
This archive was generated by hypermail 2b29 : Sat Mar 02 2002 - 01:40:30 PST