fix issue "'Started-word' event does not work correctly #78" in sapi5 driver for win. #186
Conversation
… in sapi5 driver for win.
|
`starting fox Process finished with exit code 0 for sapi5 driver the first word is actually the stream_number and stream_position (e.g. word dog 1 82240 => stream_number=1 and stream_position=82240 ) |
| self._driver._proxy.notify( | ||
| 'started-word', location=char, length=length) | ||
| 'started-word', location=stream_number, length=stream_position) |
There was a problem hiding this comment.
should probably be 'started-utterance' not 'started-word'. Location and length no longer make sense for StartStream.
There was a problem hiding this comment.
You are probably right. It has been a while since I look at the code.
|
See PR #329 - this fixes this now and the None issue |
No description provided.