[IAEP] New and revised chapters of "Make Your Own Sugar Activities!" ready for review, feedback

Jim Simmons nicestep at gmail.com
Thu Jan 21 18:23:31 EST 2010


I did consider mentioning the word tracking feature you put in your
example.  However, when I tried your example with actual book text
rather than letting it speak the source code of the program it seemed
to actually skip speaking some of the words.  The markup version was
more robust.

The machine I used for that test was running Fedora 10, and it may be
that in 11 or 12 it would work better.  I have another box running 11
and I could try it there.  I do have your examples in the Git project
for the book so readers could discover them on their own.

I could see word tracking being useful in the core Read Activity.
Actually highlighting text in place in PDF documents and scanned page
images is not as simple as what I'm doing with plain text, but perhaps
in Read you could have the spoken words appear in a text crawl at the
top of the screen.

Right now I want to work on collaboration examples but I may revisit
this chapter and add something on word tracking.

James Simmons

On Thu, Jan 21, 2010 at 4:53 PM, Aleksey Lim <alsroot at member.fsf.org> wrote:
> On Thu, Jan 21, 2010 at 10:41:59PM +0000, Aleksey Lim wrote:
>> Thanks for your efforts!
>> just minor cleanups you can consider to make code less verbose and
>> easily understandable(perhaps), see attached speech.py
> and also, could be useful to mention words tracking feature of espeak,
> like http://wiki.sugarlabs.org/go/Activity_Team/gst-plugins-espeak#Simple_TTS_example
> Yes, some espeak versions(at least old ones) could miss some words but
> its getting better(I didn't check last espeak version but at least
> espeak developers are working on track improvements) and in case of
> simple tts usage, just reusing espeak native feature would be more
> useful than coding marking stuff.

More information about the IAEP mailing list