You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently text-to-speech (TTS) support is pretty bad. It should be improved.
Specifically, it should
Use SpeechSynthesis API
"Polyfill" SpeechSynthesis API (which isn't supported by WebKitGTK) by posting messages to the GJS process, which will call speech-dispatcher.
Parse and handle assisting markups
SSML
PLS
CSS speech?
Segment text, with Intl.Segmenter
Highlight currently spoken word/sentence
There is a "boundary" event on SpeechSynthesisUtterance. AFAICT there is no such event in speech-dispatcher. Instead we need to add SSML marks and read the INDEX_MARK event notification from speech-dispatcher. This is how Calibre does it, judging by its source code. Also, not all synthesizers supports this (or even SSML).
Currently text-to-speech (TTS) support is pretty bad. It should be improved.
Specifically, it should
Use SpeechSynthesis API
"Polyfill" SpeechSynthesis API (which isn't supported by WebKitGTK) by posting messages to the GJS process, which will call speech-dispatcher.
Parse and handle assisting markups
Segment text, with
Intl.Segmenter
Highlight currently spoken word/sentence
There is a "boundary" event on
SpeechSynthesisUtterance
. AFAICT there is no such event in speech-dispatcher. Instead we need to add SSML marks and read theINDEX_MARK
event notification from speech-dispatcher. This is how Calibre does it, judging by its source code. Also, not all synthesizers supports this (or even SSML).UI for controlling playback and configuring voice, speed, etc., and make the features more discoverable (see Make text-to-speech feature more discoverable #672)
The text was updated successfully, but these errors were encountered: