As to why Word was selected as the initial target, it's just a matter of
market share and perceived use. Most dictation users are generating
text, so it makes sense to work with a word processor, and Word has
the largest market share. But there's no reason it shouldn't be applied
to any program, including the native editor.
---------------------- Forwarded by Don Selesky/DIC/US/LHS on 07/07/98
05:11 PM ---------------------------
Susan Fulton <fulton@@nytimes.com> on 07/07/98 05:02:12 PM
To: voice-users@@voicerecognition.com
cc: (bcc: Don Selesky/DIC/US/LHS)
Subject: natural language commands
>From what I've seen on so-called natural language commands so far, they
appear to be just vastly larger groups of commands from which one can draw,
perhaps more flexible from the outset but not really natural. Is this
assessment correct? If so, in my opinion natural language commands are not
easy to use but harder than predefined commands that one can look up
easily. What I really want to know, though, is whether natural language
commands are just something that works in Microsoft Word? And if so, why is
that? Is it somehow connected to Active Accessibility? Can someone explain
why natural language commands are available in word and not in the speech
program's native editor, such as IBM's SpeakPad and NaturallySpeaking text
editor?
As for Active Accessibility, is this preventing menu accessibility in the
NaturallySpeaking interface with Microsoft Word? What is Active
Accessibility anyway?
------------------------------------------------------------
----SF/ using speech recognition software/forgive odd typos
![]() |