Samuel,
I am not being provocative, just curious, but why?
By which I mean, why should a company who, and I may be wrong, likely
developed these voices for other goals, choose to create something to
work with speakup?
again, drawing on far from Linux related experience, but to insure a
screen reader functioned fully with a specific source of speech, those
developing the screen reader wrote configuration files to match the needs
of that synthesizer, not the other way around.
It is how, again for me personally, I can have one synthesizer, but have
more than one screen reader on my computer. as installed, I located the
specific config file associated with my synthesizer, including it in the
install process.
that way a screen reader could insure performance integrity across the
board, while allow individuals to use the best synthesizers for their
personal needs.
Granted there is, to my mind, a great difference between text to Speech,
and a screen reader working well with various types of speech synthesizers,
but that is me.
Kare
On Mon, 11 Jul 2022, Samuel Thibault wrote:
Samuel Thibault, le lun. 11 juil. 2022 05:58:22 +0200, a ecrit:
Karen Lewellen, le dim. 10 juil. 2022 18:09:41 -0400, a ecrit:
I have personally never encountered synthesis that could not be
paused.
Yes, but the question here is whether the *pipes* between speakup and
the synthesis (here, voxinup and voxin) actually support that.
Put another way: the problem has to be addressed by voxin people,
speakup cannot do anything about it.
Samuel
