Re: help wanted in porting espeak fixes over to windows

Brian's Mail list account

Please do not insult things that others find fine.
It may be rubbish to you but everyone has their favourite voice or synth. That is just a personal thing.
I have always used Espeak with few problems. it is going through a rocky patch just now but so many people I talk to in the flesh so to speak have never ever tried any of the variants or played around with the settings to customise it.
We do not really want another flame war on here about synths do we?
please pretty please?
Discussions of how to try to correct some of the recent changes are fine, but just coming in and saying xxx synth is rubbish helps nobody at all, in my view.
Oh and Happy 2018
Try not to break it before next year!


Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Peter Beasley" <pjbeasley23@...>
To: <>
Sent: Sunday, December 31, 2017 8:27 PM
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows

Espeak is rubbish.

-----Original Message-----
From: Shaun Everiss
Sent: Sunday, December 31, 2017 6:56 PM
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows

To be honest, and I know all the devs will shoot me down for this, but I
have sceen no real reason that we shouldn't drop back to the last real
version of espeak by default, have espeak ng as an optional or include
both synths they have seperate directorys for data and so I see no real
reason we can't have both installed, true espeak ng's espeak.dll will
have to be espeakng.dll or something but to be honest.

The espeak ng screwups don't worry me that much but I do know for bidden
is not fir bidden.

pir cent is not purcent.

or whatever it is.

Its almost like spaces in some words are being added when they were
coded in.

At any rate, mr espeak robot is not to be understood.

Its a crappy low powered synth used for admin work and other generalness.

If I wanted my voices understood I'd use my slow good quality but
resource hungry synth I have about.

Its not a big issue but the fact the list is growing.

They have fixed most of the accent issues but even so.

I really do hope that things continue to work.

On 31/12/2017 8:51 p.m., Brian's Mail list account via Groups.Io wrote:
I had always understood that the engine in nvda is updated regularly to take account of fixes, but recently there seem to have been a number of nasty bugs and silly mispronunciations added during code clean up. I'm speaking about UK English here and so have gone back to Speech Player in Espeak add on to get to an older version of Espeak which does not have these issues.
In my view there seems to be a focus in the team to attempt to make the code understandable, by moving stuff about. I guess this makes sense if they want to understand it, but its not really doing anything to fix crashes inimogees, bad pronunciations or other strange funnies, in fact its already broken language dictionaries and some other bits on the latest nvda meaning that Nvda team had to make work around to help them use the latest code.

Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: <coffeekingms@...>
To: <>
Sent: Sunday, December 31, 2017 4:18 AM
Subject: [nvda] help wanted in porting espeak fixes over to windows

Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http// I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Kendell Clark

Sent from my Vizio Ultrabook


Join to automatically receive all group messages.