[Accessibility] TTS API interface description + reqs update

Jonathan Duddington jsd at clara.co.uk
Sun May 7 16:09:17 PDT 2006


In article <200605071715.34168.garycramblitt at comcast.net>,
   Gary Cramblitt <garycramblitt at comcast.net> wrote:
> On Friday 05 May 2006 10:22, Jonathan Duddington wrote:
> > message_id defer(void);

> > say_deferred(message_id, position, position_type);
> >
> > If an application defers a message during speaking, then to resume,
> > it needs to specify a position from which to resume the speaking. 
> > There is no way to specify "continue from where it was deferred",
> > or "from the start of the sentence which was speaking".

> Yes, we should probably allow a zero for the position argument of
> say_deferred to mean "from last defer position".

I use KTTS regularly with eSpeak, and I dislike the way its Hold and
Resume continue speaking exactly from where it paused, even mid-word. 
(I expect it's just continuing playing a previously synthesized audio
file without knowing its contents). I'd prefer it to continue from the
start of the clause, or at least a few words previous to the pause, so
that I can better recall the context.

I'd assumed that zero would mean the beginning of the text, or do you
start counting words and sentences from 1 rather than 0 ?

Perhaps it needs a new "position_type" value?

-- 


More information about the accessibility mailing list