Emacspeak discussion list

["T.V Raman" <raman AT google.com>]

Robert Melton <lists AT robertmelton.com> writes:


As usual, I've done the simple/easy thing, The lisp layer doesn't know
anything about available languages.

See the code for espeak and outloud (server code) to see how they each
introspect the relevant engine to discover available languages and
implement next/prev lang; the lisp layer is intentionally unaware of the
details.

And in general, dont equate voice to language, that is  the first step
toward creating a truly tangled mess.

And do spend some time thinking of atomicity and multithreaded systems,
e.g. ask yourself the question "how many threads of execution are active
at any given time"; Hint: the answer isn't as simple as "just one
because my server doesn't use threads". > Raman--
>
> Thanks so much, that clarifies a bunch. A few questions on the 
> language / voice support.
>
> Does the TTS server maintain an internal list and switch through 
> it or does it send the list the lisp in a way I have missed? 
>
> Would it be useful to have a similar feature for voices, being 
> first you pick right language, then you pick preferred voice 
> then maybe it is stored in a defcustom and sent next time as 
> (set_lang lang:voice t)
>
>
>> On Apr 5, 2024, at 13:10, T.V Raman <raman AT google.com> wrote:
>> 
>> If your TTS supports more than one language, the TTS API exposes these
>> as a list; these calls loop through the list (dectalk,espeak, outloud)
>
> --
> Robert "robertmeta" Melton
> lists AT robertmelton.com
>

--