Re: Package proposal: greader, an audio emacs reader for blind and dislexic people

[Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]



On Wed, 30 Jan 2019, Tim Cross wrote:

> nIn addition to emacspeak, there is also a package called speechd.el, which also does a similar thing, but uses speech-dispatcher. 
> My question would be why create yet another package which appears to do the same thing rather than contribute to one of the other packages - what is it about your package that is fundamentally different to either emacspeak (very
> comprehensive, robust and powerful, with a well developed underlying philosophy/approach) and speechd.el (minimalist, simple and lower learning curve)?
> 
Hi,
Greader is not an accessibility tool for emacs. It is specialized on 
reading contents of buffers, not in providing information about emacs 
sessions.
Greader is based on back-ends architecture, so does not depend on a 
single package (eg. on speech-dispatcher) that is known to be buggy, and 
back-ends for espeak and speech-dispatcher are already provided.
Greader has the possibility to make "audiobooks", switable to be listened 
with mobile devices.
In other words, greader serves a different purpose if compared to 
emacspeak and speechd-el, that are indeed great packages.
Yes, i considered the iidea of integrating greader into one of those 
packages, but it can result in a confusion, because as i sayd, that 
packages are semantically different.
> 
> On Tue, 29 Jan 2019 at 20:15, Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com> wrote:
>       Hi All,
>       I would to propose a package that reads countinuously a buffer, using
>       speech synthesis.
>       It exists a package called emacspeak that makes emacs accessible, but my
>       package is somewhat different:
>       It does not depend on emacspeak, and can use espeak or speech-dispatcher
>       to perform reading.
>       It is my first package for emacs, and apart to make it available to all,
>       i'm interested on suggestions on how to make my code better.
>       The project is at very earl stage of development, though it works already.
>       So, what is the next step?
>       thanks to all for feedback.
>       Michelangelo Rodriguez
> 
> 
> 
> 
> --
> regards,
> 
> Tim
> 
> --
> Tim Cross
> 
> 
>