espeak-ng@groups.io

Github push to espeak-ng:espeak-ng #github

espeak-ng@groups.io Integration <espeak-ng@...>

#1

2 New Commits:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
a48576a3640f: Return ENS_SPEECH_STOPPED from Synthesize when the speech callback returns >1 to stop the audio.

Modified: src/include/espeak-ng/espeak_ng.h
Modified: src/libespeak-ng/espeak_api.c
Modified: src/libespeak-ng/speech.c

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
bc674081cd0e: Check the return from synth_callback in the second call to that function in Synthesize.

Modified: src/libespeak-ng/speech.c

Github push to espeak-ng:espeak-ng #github

espeak-ng@groups.io Integration <espeak-ng@...>

#2

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
d2478cc45375: Flush the audio if speech has stopped, drain the audio if speech is still active.

Modified: src/libespeak-ng/speech.c

Pull Request Updated #github

espeak-ng@groups.io Integration <espeak-ng@...>

#3

[espeak-ng/espeak-ng] Pull request updated by ValdisVitolins:

#161 Support for Arabic language merged from https://github.com/linuxscout/espeak-ng
Reece, I contacted https://github.com/linuxscout/ about merging his fork into mainstream eSpeak NG, but merging his old fork into current version was too complicated for him. If yo can, can you also change author of changes to Taha Zerrouki taha_zerrouki@... and skip/rebase yet another merging commit https://github.com/espeak-ng/espeak-ng/pull/161/commits/601beaa1289b786957d59c46d57b9fc6e3b4455d (this exercise was too complicated for me too...)

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>

#4

[espeak-ng:master] New Issue Created by rhdunn:
#176 Add support for Arabic

There is Arabic support in https://github.com/linuxscout/espeak-ng. This needs cleaning up to:

Simplify the history to not include small changes with non-descriptive commit messages.
Not add the Arabic MBROLA voice binary files to the espeak-ng repository.

[espeak-ng:master] New Comment on Pull Request #161 Support for Arabic language merged from https://github.com/linuxscout/espeak-ng
By rhdunn:

I am closing this as the branch contains other things than just the Arabic support. I have raised issue 176 to track enabling Arabic support.

[espeak-ng/espeak-ng] Pull request closed by rhdunn:

#161 Support for Arabic language merged from https://github.com/linuxscout/espeak-ng
Reece, I contacted https://github.com/linuxscout/ about merging his fork into mainstream eSpeak NG, but merging his old fork into current version was too complicated for him. If yo can, can you also change author of changes to Taha Zerrouki taha_zerrouki@... and skip/rebase yet another merging commit https://github.com/espeak-ng/espeak-ng/pull/161/commits/601beaa1289b786957d59c46d57b9fc6e3b4455d (this exercise was too complicated for me too...)

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>

#5

[espeak-ng/pcaudiolib] Pull request closed by rhdunn:

#2 A couple of changes for alsa.

3 New Commits:

[pcaudiolib:master] By Christopher Brannon <chris@...>:
bcc3b30db8cb: alsa: put PCM in prepared state after drain and drop. This keeps us from having to make an extra trip through the loop in alsa_object_write to prepare the handle, and we know the handle is in a state ready to play when alsa_object_drain or alsa_object_drop return.

Modified: src/alsa.c

[pcaudiolib:master] By Christopher Brannon <chris@...>:
df8df892a260: alsa: handle suspend state in write.

Modified: src/alsa.c

[pcaudiolib:master] By Reece H. Dunn <msclrhd@...>:
5cefeb9e01c2: alsa: move the unistd.h include into the have-alsa #if block to only include it when building alsa support.

Modified: src/alsa.c

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>

#6

1 New Commit:

[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f9ab812e0054: issue 172: fix sluggish speech for stopped speech. This restores the behaviour removed in commit ca831d236a4eed5648254329554affac143a1740. When using eSpeak for audio and eSpeak in a server, using the async speech requests, that code stopped the audio as soon as possible from a cancel request. This allows servers like brltty to be more responsive.

Modified: src/libespeak-ng/fifo.c
Modified: src/libespeak-ng/speech.c
Modified: src/libespeak-ng/speech.h

[espeak-ng:master] New Comment on Issue #172 sluggish speech interruption
By rhdunn:

This has now been fixed.

@sthibaul commit f9ab812e00549640ebf7d6f9416e151827ce5294 is all you need patch-wise to fix this issue.

[espeak-ng:master] Issue #172 sluggish speech interruption closed by sthibaul.

Sending out an official invitation to the ESpeak-NG mailing list to other groups

Bhavya shah

#7

Dear all,
To the few of us who are already part of this new discussion platform
for ESpeak-NG, there are a few essential tasks we may need to
discharge in order for this list to truly replace the older
SourceForge list, which includes attempting to transfer members from
the old list to this new one, inviting all those who are members of
the old list, sending out official invitation messages to the old
list, and lists of screen readers that use ESpeak-NG by default  and
other e-groups, etc.
having had past Groups.io administration experience (for maintaining
the NVDACon Asia e-group), I believe I would be capable of handling
some of the afore mentioned to-do things which require administrative
rights, along with Reece and others. However, even as a group member,
I would be equally willing to send out official invitations to the old
list, the NVDA forums the Orca list as well as a few others without
being promoted to moderator.
All in all, since the group settings seem in tune (with ideal
defaults, Github integration established and fundamentals in
foundation), I believe the above are pointers we may need to discuss
and act upon for a proper list succession.
Thanks.

-- 
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

Current Group Status, E-mail Addresses & Basic Information

Bhavya shah

#8

Dear all,
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 for those who have already joined
this ESpeak-NG e-group for their prompt transition.

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
build a stable community of its beneficiaries, in the form of this
mailing list.
In subsequent mails, I will be explicating our ways forward in
shifting those still on the old mailing list to this new one, as well
as cordially inviting screen reader users and vendors utilizing ESpeak
to our next generation platform, and spreading the word about this
community to other ESpeak contributors and beneficiaries.
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.

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. It is worth noting
that all messages would be sent to the list directly henceforth.

-- 
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

Roadmap - List Growth and Vision Ahead

Bhavya shah

#9

Dear all,
In sequence to my previous e-mail, I would like to share about the
roadmap we have lying in front of us towards a proliferating and
progressing e-group for ESpeak-NG that I conceptualize.
For now, we must work on asking, inviting and welcoming those who are
part of the old SourceForge list over to our Groups.io based e-group.
As a group moderator, I will be shortly sending an official invite to
40 e-mail addresses who have sent a message to the SourceForge list in
the past several months, since we seemingly do not have access to the
members list in the case of the old list. Also, I will be posting
regular reminders on the SourceForge list requesting folks to
unsubscribe from there and join here, with subscription details
included. Post those activities, I will also be sharing about this
next generation mailing list dedicated to the next generation of the
ESpeak TTS on screen reader lists and other assistive technology
related forums.
Regardless of my personal efforts, this cannot remain an
individualistic outreach initiative, but it must be a community-driven
one. I will be requiring your support and collaboration as we lay the
foundation of this e-group for the successor of a very popular and
influential text to speech program. 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 sending a
blank reply to the confirmation prompt subsequently received.

Best Regards,
Bhavya Shah

-- 
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

espeak-ng for windows

mattias <mjonsson1986@...>

#10

i downloaded the msi file for windows x86

but hm? no sapi?

Updated Wikipedia article about eSpeakNG

Valdis Vitolins

#11

After loosing battle with bureaucratic bots and moderators with two
Wikipedia articles: eSpeak and eSpeakNG,

I renamed original eSpeak article to eSpeakNG and updated it, to
reflect relevant information about eSpeakNG project.

https://en.wikipedia.org/wiki/ESpeakNG

Reviews and updates are welcome.

Valdis

Re: espeak-ng for windows

Reece H. Dunn

#12

SAPI support is currently experimental and not exposed in the installers. Issue #7 is being used to track the implementation. This is mentioned in the README file of the eSpeak NG project in the Windows Build section.

Kind regards,

Reece

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>

#13

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. This should include: 1. referring to external versions of the SAPI libraries; 2. not including generated files from midl, etc.; 3. using a more modern project format (MSBuild) than Visual Studio 6!; 4. avoid using pre-compiled headers (see #6).

The rewrite should also look to improve the SAPI binding in general.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [ ] Not including generated files from midl, etc. - [ ] Use a more modern project format (MSBuild) than Visual Studio 6! - [ ] Avoid using pre-compiled headers (see #6). - [ ] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Not including generated files from midl, etc. - [ ] Use a more modern project format (MSBuild) than Visual Studio 6! - [ ] Avoid using pre-compiled headers (see #6). - [ ] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [ ] Use a more modern project format (MSBuild) than Visual Studio 6! - [ ] Avoid using pre-compiled headers (see #6). - [ ] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [ ] Avoid using pre-compiled headers (see #6). - [ ] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [ ] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [x] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [ ] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [x] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [x] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [x] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [x] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [ ] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [x] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [x] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [x] ISpObjectWithToken - [ ] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [ ] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

[espeak-ng:master] New Issue Created by rhdunn:
#7 Reimplement the SAPI bindings.

The SAPI bindings should be rewritten to avoid the Copyright assignments to Microsoft. The rewrite should also look to improve the SAPI binding in general.

General Infrastructure: - [x] Refer to external versions of the SAPI libraries. - [x] Don't include generated files from midl, etc. - [x] Use a more modern project format (MSBuild) than Visual Studio 6! - [x] Avoid using pre-compiled headers (see #6). - [x] Implement the SAPI COM interfaces in libespeak-ng.dll, not in a separate DLL. - [x] Don't depend on the ATL library -- only use the Windows headers.

SAPI Interfaces: - [x] ISpObjectWithToken - [x] ISpTTSEngine

ISpTTSEngine:Speak SPVTEXTFRAG state actions: - [x] SPVA_Speak - [ ] SPVA_Silence - [ ] SPVA_Pronounce - [ ] SPVA_Bookmark - [ ] SPVA_SpellOut - [ ] SPVA_ParseUnknownTag

Voice Management: - [ ] Select and install voices from the MSI installer -- language+accent. - [ ] Select the voice variant from an eSpeak SAPI configuration/properties page.

Re: Updated Wikipedia article about eSpeakNG

turkiabdelwaheb@...

#14

Dear Sir,

I did not tell you that I am one of the 2000 most contributing users in the English Wikipedia. I am a founding member of Wikimedia TN, Wikipedia Library, WikiProject Maghrebi Arabic, and Wikimedia Maghreb. My entries was featured four times in the main page of English Wikipedia. I must tell you that the work lacks of references. It includes some misleading information. For example, I ask if Mohamed and Brazil are languages. As well, blog posts are unfortunately not considered as a trustworthy reference by the editors of Wikipédia. It can be removed by one week if someone does not add references to it. Please send me references (journal items, researches...) about eSpeak. I will edit the work. I congratulate you for the work and I invite you to include Arabic dialects to it in the next years. Merry Christmas and Happy New Year 2017.

Yours Sincerely,

Houcemeddine Turki

De : espeak-ng@groups.io <espeak-ng@groups.io> de la part de Valdis Vitolins <valdis.vitolins@...>
Envoyé : dimanche 25 décembre 2016 17:26
À : espeak-ng@groups.io
Objet : [espeak-ng] Updated Wikipedia article about eSpeakNG

After loosing battle with bureaucratic bots and moderators with two
Wikipedia articles: eSpeak and eSpeakNG,

I renamed original eSpeak article to eSpeakNG and updated it, to
reflect relevant information about eSpeakNG project.

https://en.wikipedia.org/wiki/ESpeakNG

Reviews and updates are welcome.

Valdis

[espeak-ng:master] reported: sluggish speech interruption #github

espeak-ng@groups.io Integration <espeak-ng@...>

#15

[espeak-ng:master] New Comment on Issue #172 sluggish speech interruption
By sthibaul:

Hello,

Reece H. Dunn, on Sat 24 Dec 2016 01:1100 -0800, wrote: > [1]@sthibaul commit [2]f9ab812 is all you need patch-wise to fix this issue.

Ok, thanks, I have uploaded this to Debian, let's see bug submitters' report on it.

Samuel

[espeak-ng:master] new issue: Support for timing output #github

espeak-ng@groups.io Integration <espeak-ng@...>

#16

[espeak-ng:master] New Issue Created by cmrdt:
#173 Support for timing output

maybe options to output subtitle-subrip (.srt) format files with option to split lines by word or line or consonant-vowels maybe also IPA/phonetic output and syntax coloring/formatting(font,bold)

https://en.wikipedia.org/wiki/SubRip#SubRip_text_file_format https//en.wikipedia.org/wiki/SubStation_Alpha

[espeak-ng:master] reported: Support for timing output #github

espeak-ng@groups.io Integration <espeak-ng@...>

#17

[espeak-ng:master] New Comment on Issue #173 Support for timing output
By cmrdt:

one of possible uses if for media players (e.g. VLC) which support loading these subtitles and have it sync to text to speech

Re: Updated Wikipedia article about eSpeakNG

Valdis Vitolins

#18

Hello, Houcemeddine!

I've corrected list of supported languages by eSpeakNG, because previously I used list of supported voices, which are related to languages, but

sometimes are not the same.

I have no idea where we can get more prominent sources for references.

All I can say is that current page has some more references than before, so, if quality criteria are not risen much higher, it should pass.

All the best from me too.

Valdis

Show quoted text

Dear Sir,

I did not tell you that I am one of the 2000 most contributing users in the English Wikipedia. I am a founding member of Wikimedia TN, Wikipedia Library, WikiProject Maghrebi Arabic, and Wikimedia Maghreb. My entries was featured four times in the main page of English Wikipedia. I must tell you that the work lacks of references. It includes some misleading information. For example, I ask if Mohamed and Brazil are languages. As well, blog posts are unfortunately not considered as a trustworthy reference by the editors of Wikipédia. It can be removed by one week if someone does not add references to it. Please send me references (journal items, researches...) about eSpeak. I will edit the work. I congratulate you for the work and I invite you to include Arabic dialects to it in the next years. Merry Christmas and Happy New Year 2017.

Yours Sincerely,

Houcemeddine Turki

De : espeak-ng@groups.io <espeak-ng@groups.io> de la part de Valdis Vitolins <valdis.vitolins@...>
Envoyé : dimanche 25 décembre 2016 17:26
À : espeak-ng@groups.io
Objet : [espeak-ng] Updated Wikipedia article about eSpeakNG

After loosing battle with bureaucratic bots and moderators with two
Wikipedia articles: eSpeak and eSpeakNG,

I renamed original eSpeak article to eSpeakNG and updated it, to
reflect relevant information about eSpeakNG project.

https://en.wikipedia.org/wiki/ESpeakNG

Reviews and updates are welcome.

Valdis

Re: Updated Wikipedia article about eSpeakNG

abdelwaheb turki <turkiabdelwaheb@...>

#19

Dear Sir,

I thank you for your answer. It is better now. It can pass. I will add references to it.

Yours Sincerely,

Houcemeddine Turki

De : espeak-ng@groups.io <espeak-ng@groups.io> de la part de Valdis Vitolins <valdis.vitolins@...>
Envoyé : mardi 27 décembre 2016 09:09
À : espeak-ng@groups.io
Objet : Re: [espeak-ng] Updated Wikipedia article about eSpeakNG

Hello, Houcemeddine!

I've corrected list of supported languages by eSpeakNG, because previously I used list of supported voices, which are related to languages, but

sometimes are not the same.

I have no idea where we can get more prominent sources for references.

All I can say is that current page has some more references than before, so, if quality criteria are not risen much higher, it should pass.

All the best from me too.

Valdis

Show quoted text

Dear Sir,

I did not tell you that I am one of the 2000 most contributing users in the English Wikipedia. I am a founding member of Wikimedia TN, Wikipedia Library, WikiProject Maghrebi Arabic, and Wikimedia Maghreb. My entries was featured four times in the main page of English Wikipedia. I must tell you that the work lacks of references. It includes some misleading information. For example, I ask if Mohamed and Brazil are languages. As well, blog posts are unfortunately not considered as a trustworthy reference by the editors of Wikipédia. It can be removed by one week if someone does not add references to it. Please send me references (journal items, researches...) about eSpeak. I will edit the work. I congratulate you for the work and I invite you to include Arabic dialects to it in the next years. Merry Christmas and Happy New Year 2017.

Yours Sincerely,

Houcemeddine Turki

De : espeak-ng@groups.io <espeak-ng@groups.io> de la part de Valdis Vitolins <valdis.vitolins@...>
Envoyé : dimanche 25 décembre 2016 17:26
À : espeak-ng@groups.io
Objet : [espeak-ng] Updated Wikipedia article about eSpeakNG

After loosing battle with bureaucratic bots and moderators with two
Wikipedia articles: eSpeak and eSpeakNG,

I renamed original eSpeak article to eSpeakNG and updated it, to
reflect relevant information about eSpeakNG project.

https://en.wikipedia.org/wiki/ESpeakNG

Reviews and updates are welcome.

Valdis

[espeak-ng:master] closed: Turkish pronunciation problems#github

espeak-ng@groups.io Integration <espeak-ng@...>

#20

[espeak-ng:master] Issue #152 Turkish pronunciation problems closed by burakyuksek.