On Sun, Jan 1, 2017 at 11:14 pm, Allan WKF wrote:

Hi Reece,

First of all thank you for taking the espeak-NG to your hand and
making the
project continue to grow. I would like to know, any work to port
espeak-NG
to Android?

Yes. I am working to bring the Android code into the mainline of
espeak-ng to keep it in step with the releases of espeak-ng.

Kind regards,

Reece Dunn

Happy New Year!

Bhavya,

Thank you for spreading the word and for your warm welcome to this new
group

Reece,

Thank you for your continued dedication to the development and support for
espeak

Russ


On Sun, Jan 1, 2017 at 10:02 AM, Bhavya shah <bhavya.shah125@gmail.com>
wrote:

Dear ESpeak-NG users, developers, and other beneficiaries,
At the outset, let me sincerely thank Reece for appointing me as a
moderator of this Groups.io based next generation mailing list for
official discussion regarding the ESpeak-NG speech synthesizer. Also,
I would like to express my gratitude towards everyone who joint the
e-mail list via invites sent out on different forums, direct invites,
word-of-mail (not mouth :D) and also for those who have begun
contributing by spreading the word about this project and its
community, and by participating in it.
Following are some fundamental statistics that highlight the current
status of this group:
Member Count: 11
Group Owner: Reece H. Dunn
Group Moderator: Bhavya Shah (Me)
Integrations: Github (https://github.com/espeak-ng/espeak-ng)

Also, following are integral e-mail addresses to perform various
activities on the group:
To Post: espeak-ng@groups.io
To Subscribe: espeak-ng+subscribe@groups.io
To Unsubscribe: espeak-ng+unsubscribe@groups.io
To Contact The Group Owner: espeak-ng+owner@groups.io

At the moment, we have no special hashtags in use (apart from Github),
no dedicated subgroups (due to lack of their requirement) and no Wiki
material (due to their inexistence). However, our vision for this
group must extend beyond not only encompassing this in ESpeak-NG’s
next generation e-group, but also having a prolific and proactive
community of users and developers in constant communication and
interaction via this list. ESpeak-NG powers the speech synthesis of
two popular screen readers by default - NVDA for Windows and Orca for
Linux – which in turn fuel computer access for tens of thousands of
visually impaired individuals across the globe. Let us recognize the
significance of this open source project, and accordingly strive to
mobilize its users, developers and other beneficiaries as part of this
e-mail platform.
Please do spread the word about this mailing list and ask your fellow
ESpeak users to join the list by sending a blank mail to
espeak-ng+subscribe@groups.io And send a blank reply to the
confirmation prompt subsequently received.
In conclusion, I hope to dutifully serve as a moderator of this
mailing list in a just manner, and I shall try to the best of my
abilities to assist Reece in ensuring smooth functioning of this
e-group, in constant anticipation of your continued collaboration.

Best Regards,
Bhavya Shah

P.S. Due to Groups.io policies, the first post of every group member
will require approval from a group administrator. All messages from
that e-mail will be delivered directly thereafter.

--
Best Regards
Bhavya Shah

Avid Enthusiast and User of the Free NVDA Screen Reader
(www.nvaccess.org)

Contacting Me
E-mail Address: bhavya.shah125@gmail.com
Follow me on Twitter @BhavyaShah125 or www.twitter.com/BhavyaShah125
Mobile Number: +91 7506221750

Hi guys.

Sorry i was just trying to help. Btw i have that version installed on my
current phone and i don't see any advertisements which you mentioned
over here. Do you know exactly when or in which situations they pop up?

Mario
On 12/31/2016 1:57 PM, Matěj Plch wrote:

Hi Mario,
I know about this port of eSpeak, but there is some in-app
advertisement, so I do not like this port.
It is established on the existing code and I found the crashes too.
Sincerely,
Matej


Dne 31.12.2016 v 13:49 Mario Perčinić napsal(a):

Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS
Engine from RedZoc apk. On his page he says that he optimised espeak
for android 6 and later.

Mario



On 12/31/2016 1:38 PM, Matěj Plch wrote:

Okay, Reece, thanks for your answer. I totaly understand. Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers, I am very happy, that this discussion
group was established and the next generation of eSpeak will come
in near future! Can you highlight some important changes, which
we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make
some engine optimizations, because I register quite often crashes
of latest available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The
focus on security and stability above should help reduce/remove
the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem
is noticeable especialy during fast typing on Google Keyboard or
sometimes, when I want to open several apps quickly. I posted
many crashing reports directly from the devices, but do not know,
if developers catched them.

I can see them, but as I have said, it is difficult to know what
the cause of the crash is. The work I have done already should
help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so
that the android code will be usable from the main releases
instead of requiring the android branch to be updated. This
should make it easier to perform new Android releases in the
future.

Kind regards,

Reece Dunn

Hi Mario,
I know about this port of eSpeak, but there is some in-app
advertisement, so I do not like this port.
It is established on the existing code and I found the crashes too.
Sincerely,
Matej


Dne 31.12.2016 v 13:49 Mario Perčinić napsal(a):

Hi Matej.

Have you tried using port of espeak for android called eSpeak TTS
Engine from RedZoc apk. On his page he says that he optimised espeak
for android 6 and later.

Mario



On 12/31/2016 1:38 PM, Matěj Plch wrote:

Okay, Reece, thanks for your answer. I totaly understand. Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers, I am very happy, that this discussion
group was established and the next generation of eSpeak will come
in near future! Can you highlight some important changes, which
we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make
some engine optimizations, because I register quite often crashes
of latest available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The
focus on security and stability above should help reduce/remove
the number of crashes on Android.

I tested it on many devices with this OS and the crashing problem
is noticeable especialy during fast typing on Google Keyboard or
sometimes, when I want to open several apps quickly. I posted
many crashing reports directly from the devices, but do not know,
if developers catched them.

I can see them, but as I have said, it is difficult to know what
the cause of the crash is. The work I have done already should
help, but there is still more to fix and improve.

I am working on merging the android code into the main branch, so
that the android code will be usable from the main releases
instead of requiring the android branch to be updated. This
should make it easier to perform new Android releases in the
future.

Kind regards,

Reece Dunn

Okay, Reece, thanks for your answer.
I totaly understand.
Regards,
Matej

Dne 31.12.2016 v 11:50 Reece H. Dunn napsal(a):

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers,
I am very happy, that this discussion group was established and the
next
generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some
engine optimizations, because I register quite often crashes of latest
available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The focus
on security and stability above should help reduce/remove the number of
crashes on Android.

I tested it on many devices with this OS and the crashing problem is
noticeable especialy during fast typing on Google Keyboard or
sometimes,
when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not
know, if developers catched them.

I can see them, but as I have said, it is difficult to know what the
cause of the crash is. The work I have done already should help, but
there is still more to fix and improve.

I am working on merging the android code into the main branch, so that
the android code will be usable from the main releases instead of
requiring the android branch to be updated. This should make it easier
to perform new Android releases in the future.

Kind regards,

Reece Dunn

On Sat, Dec 31, 2016 at 02:39 am, Matěj Plch wrote:

Dear users and developers,
I am very happy, that this discussion group was established and the
next
generation of eSpeak will come in near future!
Can you highlight some important changes, which we can expect?

The changes are described in the changelog
(https://github.com/espeak-ng/espeak-ng/blob/master/CHANGELOG.md).

My main focus so far has been:

1. Clean up the build process.

2. Simplify porting to other systems (BSD, Mac, Windows).

3. Clean up the codebase to make it easier to maintain.

4. Make the code more robust and secure.

I am highly interested in the port for Android operating system.
In this context, I would like to discuss, if is possible to make some
engine optimizations, because I register quite often crashes of latest
available version 1.48.15 on Android Marshmallow.

It is difficult to know where the crash is occurring and why. The focus
on security and stability above should help reduce/remove the number of
crashes on Android.

I tested it on many devices with this OS and the crashing problem is
noticeable especialy during fast typing on Google Keyboard or
sometimes,
when I want to open several apps quickly.
I posted many crashing reports directly from the devices, but do not
know, if developers catched them.

I can see them, but as I have said, it is difficult to know what the
cause of the crash is. The work I have done already should help, but
there is still more to fix and improve.

I am working on merging the android code into the main branch, so that
the android code will be usable from the main releases instead of
requiring the android branch to be updated. This should make it easier
to perform new Android releases in the future.

Kind regards,

Reece Dunn