Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade ESpeak to version 1.48.04 #4325

Closed
nvaccessAuto opened this issue Jul 25, 2014 · 22 comments
Closed

Upgrade ESpeak to version 1.48.04 #4325

nvaccessAuto opened this issue Jul 25, 2014 · 22 comments

Comments

@nvaccessAuto
Copy link

Reported by blindbhavya on 2014-07-25 11:23
Hi.
Espeak version 1.48.09 is available on espeak.sourceforge.net/
So, could you upgrade the ESpeak in NVDA as well?

@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2014-07-25 11:27
Hi,
1.48.09 is the latest development version. The latest stable version is 1.48.04, which may not be incorporated into NvDA core for a while. Thanks.

@nvaccessAuto
Copy link
Author

Comment 2 by blindbhavya on 2014-07-25 11:41
1.48.09 is the latest development version. The latest stable version is 1.48.04, which may not be incorporated into NvDA core for a while. Thanks.
Why wouldn't it be incorporated into NVDA for a while?
P.S. Thanks for clarifying the latest stable version.

@nvaccessAuto
Copy link
Author

Comment 3 by ateu on 2014-07-25 15:24
Hi blindbhavya,

1.48.09 is a development version, and may contain problems, as it's not stable.

@nvaccessAuto
Copy link
Author

Comment 4 by blindbhavya on 2014-07-25 15:39
Hi Athew,
Yes, NV Thakkar Sir told me that.
The latest stable version is 1.48.04. Why wouldn't that be incorporated into NVDA for a while, thats my question.
BTW, I find 09 as stable as 04, in fact better, but I can understand that NVDA cannot have it.

@nvaccessAuto
Copy link
Author

Comment 5 by ateu on 2014-07-25 17:24
As 1.48.09 is not stable, it may contain problems, as any program which is being developed.

@nvaccessAuto
Copy link
Author

Comment 6 by blindbhavya on 2014-07-25 18:17
Hi.
If you re-read my previous comments carefully, you will perceive that I have written that I understand why NVDA can't have an unstable program (ESpeak).
However, as Mr. NV Thakkar said, the ESpeak packages in NVDA can still be updated to a newer stable version of ESpeak. So I am requesting for that.

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2014-07-28 06:50
I didn't realise 1.48.04 had been released. We should upgrade, but this probably won't make it into NVDA 2014.3, as there isn't enough time before the release to ensure it doesn't cause regressions.
Changes:
Changed title from "request to upgrade ESpeak to version 1.48.09" to "Upgrade ESpeak to version 1.48.04"
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 8 by blindbhavya on 2014-07-28 11:58
Hi.
What does 'regressions' mean? How would regressions prevent the upgraded ESpeak from being in NVDA 2014.3?
Sorry for my ignorance.

@nvaccessAuto
Copy link
Author

Comment 9 by jteh on 2014-07-28 12:01
Regression means a bug that wasn't there before but got introduced because of something we changed. If we update to 1.48.04, it could introduce new bugs. There isn't enough time before the release to ensure it is thoroughly tested, so it'll have to wait until next release.

@nvaccessAuto
Copy link
Author

Comment 10 by blindbhavya on 2014-07-28 13:53
Hi.
When do you think approximately NVDA 2014.3 stable will be released?

@nvaccessAuto
Copy link
Author

Comment 11 by jteh on 2014-07-28 23:21
25 August. 2014.4 should be about three months after that.

@nvaccessAuto
Copy link
Author

Comment 12 by blindbhavya on 2014-07-29 07:01
Hi.
What does 25 August signify that you wrote that in your message?
How much time before the stable release should ESpeak upgradation request have been made?
Is it that always there are regressions with NVDA updates and ESpeak updates? Or are you just taking a precaution?
Just asking. Hope you wouldn't mind.

@nvaccessAuto
Copy link
Author

Comment 13 by jteh on 2014-07-29 10:30
Regarding release dates, see ReleaseProcess.

Historically, upgrading eSpeak has caused some major regressions, even when it only appears to be a minor update. I guess a couple of weeks ago would have been enough. It's just bad timing. :)

@nvaccessAuto
Copy link
Author

Comment 14 by blindbhavya on 2014-07-29 12:41
Ok.

@nvaccessAuto
Copy link
Author

Comment 15 by blindbhavya on 2014-09-05 04:46
Hi
Could ESpeak be upgraded now?
Hoping to hear from you soon.

@nvaccessAuto
Copy link
Author

Comment 16 by jteh on 2014-09-06 11:00
Changes:
Milestone changed from next to 2014.4

@nvaccessAuto
Copy link
Author

Comment 17 by blindbhavya on 2014-09-06 11:48
Thank you!

@nvaccessAuto
Copy link
Author

Comment 18 by jteh on 2014-09-06 12:10
Out of interest, is there actually something in 1.48.04 that you care about? That is, why do you care that we update so urgently?

@nvaccessAuto
Copy link
Author

Comment 19 by blindbhavya on 2014-09-06 15:22
Hi.
Well, I am not sure what to say.
I am not too keen for this version, because I am waiting for the next stable release of ESpeak, because that contains more fixes that I really need, such as fixes for foreign names and places, and minor fixes for Hindi.
Also, since I am new to NVDA (not new to NVDA perhaps, but certainly to ESpeak improving and NVDA issues) so I am curious to read some regressions reported due to upgradation of ESpeak.
I am not that urgent about upgradation of ESpeak in NVDA.
Hope I somewhat answered your question.

@nvaccessAuto
Copy link
Author

Comment 20 by jteh on 2014-11-20 08:05
These really should have been done for 2014.4, but we're out of time and they aren't absolutely critical. Still, we need to manage this better in future.
Changes:
Milestone changed from 2014.4 to 2015.1

@nvaccessAuto
Copy link
Author

Comment 21 by Michael Curran <mick@... on 2015-01-22 00:28
In [3c19acf]:

Merge branch 't4325' into next. Incubates #4325

Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

Comment 22 by Michael Curran <mick@... on 2015-02-05 00:23
In [5e3b3e5]:

Merge branch 't4325'. Fixes #4325

Changes:
Removed labels: incubating
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant