Text To Speech in Read Etexts improved again

[Hemant Goyal]

Hi James,

Absolutely not a problem at all. I am also working on finding a fix for the
problems that developers can have while using speechd api with pyGTK as
described here : http://www.mail-archive.com/pygtk@daa.com.au/msg15868.html

I discussed a solution to the problem with tomeu and erikos, and have been
making changes in the API implementation to make speechd support
asynchronous socket communication so that we can avoid  a thread to perform
network communication. We've figured out an approach to avoid threads in the
API, and hopefully I'll have the alternate solution ready in 2-3 days. I'll
be depending upon you to use the modified API in your application for
testing purposes :)

Best,
Hemant

On Mon, Jun 16, 2008 at 10:25 PM, James Simmons <jim.simmons at walgreens.com>
wrote:

>  Hemant,
>
> The RPM's and instructions you posted to the Wiki before *almost* worked.
> Can we assume that you'll do something similar with your debugged RPMs while
> awaiting sponsorship?  Having my activity do TTS on a real XO would make a
> big difference to my project.  Not to mention that I could finally show my
> wife why I've been spending so much time in the basement programming.
>
> Thanks,
>
> James Simmons
>
>
> Hemant Goyal wrote:
>
> Hi Michael,
>
> The basic package is ready to use, and a few more Q/A issues as described
> in the bug report need to be resolved.
>
> The major Q/A issues to be resolved at the moment are :
>
>    1. Conversion of CS language info file to UTF-8 encodings. I am having
>    trouble finding the encoding of the file and then converting it correctly
>    using iconv.
>     2. Also I am working on an init script so that the speech-dispatcher
>    daemon can be auto-started when the Operating System loads. The script is
>    ready and has been included in the package. The init script has a few bugs
>    in that it deletes the wrong pid file when the daemon has to be stopped. I
>    will be fixing this bug in the next release.
>
> Hopefully, there wont be any more issues at the package review level after
> I resolve the above issues.
>
> Since this is my first package the next step for me is to get *sponsored*.
> I wrote 2 informal reviews for this purpose.
>
> The reviews I wrote can be found at :
> https://bugzilla.redhat.com/show_bug.cgi?id=448292 &
> https://bugzilla.redhat.com/show_bug.cgi?id=448458
>
> Best,
> Hemant
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080616/941e849c/attachment.html>