[Kde-accessibility] KSpeech

[guenter]

Am 06.03.2014 17:13, schrieb Jeremy Whiting:
> On Thu, Mar 6, 2014 at 6:43 AM, Frederik Gladhorn <gladhorn at kde.org> wrote:
>> Onsdag 5. mars 2014 23.04.12 skrev Jeremy Whiting:
>>> Took a quick read through that just now and it looks pretty promising
>>> from what I saw. I guess I don't know my way around gerrit very well
>>> because I couldn't see a place to comment on the code like
>>> reviewboard.
>>> Really the only difference between jovie and that class are the following:
>>> 1. jovie has some old code and ui to control jobs at a fine grain that
>>> spd doesn't expose really well, so I left it out when I ported ktts to
>>> spd.
>> I would like to expose "voices" and "languages" in a sensible fashion. This is
>> tricky to get right cross-platform. I started with something on Linux but
>> decided to implement other backends first before attempting to implement voice
>> selection.
>> For language/locale I think qtspeech should default to the system locale and
>> let the user select a different one.
> Using the system locale as default makes sense. What do you mean by
> "voices" you mean something like spd's voice type (male1, male2,
> female1, etc.)
> Ktts had a complex system of specifying a voice with xml with
> language, voice type, speed, pitch, etc. attributes and if an
> attribute was empty it meant any voice with the other attributes was
> acceptable. I think that's a bit too fine-grained for most cases
> though, most uses I can think of just want to choose the voice type,
> or even just the gender, and let the user/defaults choose the rest.
> If more complex specification is wanted applications could always use
> ssml to change the voice as part of the text they send to qtspeech.
>
Hi folks,

although my locale is de_DE I'm reading often English and other
languages too. So I would vote for an easy way for users/applications of
switching the language.

Greetings,
  Günter

-- 
.