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
speach hub should be aded to nvda sinth list #3267
Comments
Comment 1 by Animesh.mr on 2013-06-07 12:04 |
Comment 2 by Animesh.mr on 2013-07-23 04:28 |
Comment 3 by jteh on 2014-10-08 04:50 |
This is not yet added on https://github.com/nvaccess/nvda/wiki/ExtraVoices |
Is this project still alive. I know the original still runs, but not seen
anything from then in over a year.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Leonard de Ruijter" <notifications@github.com>
To: "nvaccess/nvda" <nvda@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Sent: Wednesday, July 19, 2017 7:33 PM
Subject: Re: [nvaccess/nvda] speach hub should be aded to nvda sinth list
(#3267)
… [This](http://www.speakon.org.uk/SpeechHub.html) is not yet added on
https://github.com/nvaccess/nvda/wiki/ExtraVoices
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#3267 (comment)
|
Regardless of whether or not this project is still alive, the original version of Speechhub for NVDA was quite popular and well-received. Could someone (CC at josephsl) please add a note about this on the Get Extra Voices page of the Github NVDA Wiki? This should be trivial to resolve. |
Hi, if the add-on is still being developed and if contacting the developer is still possible, then yes, it should be featured on our wiki. Thanks.
From: bhavyashah [mailto:notifications@github.com]
Sent: Saturday, August 19, 2017 12:42 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [nvaccess/nvda] speach hub should be aded to nvda sinth list (#3267)
Regardless of whether or not this project is still alive, the original version of Speechhub for NVDA was quite popular and well-received. Could someone (CC at josephsl) please add a note about this on the Get Extra Voices page of the Github NVDA Wiki? This should be trivial to resolve.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#3267 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkKvS4E7YUp2x3_Ln8yNQWSz5u6geks5sZpHXgaJpZM4OdH8J> .
|
I think development is over but the synth still works as indeed does Pico as
well
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <notifications@github.com>
To: "nvaccess/nvda" <nvda@noreply.github.com>
Cc: "Brian Gaff" <bglists@blueyonder.co.uk>; "Comment"
<comment@noreply.github.com>
Sent: Saturday, August 19, 2017 10:00 AM
Subject: Re: [nvaccess/nvda] speach hub should be aded to nvda sinth list
(#3267)
Hi, if the add-on is still being developed and if contacting the developer
is still possible, then yes, it should be featured on our wiki. Thanks.
From: bhavyashah [mailto:notifications@github.com]
Sent: Saturday, August 19, 2017 12:42 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [nvaccess/nvda] speach hub should be aded to nvda sinth list
(#3267)
Regardless of whether or not this project is still alive, the original
version of Speechhub for NVDA was quite popular and well-received. Could
someone (CC at josephsl) please add a note about this on the Get Extra
Voices page of the Github NVDA Wiki? This should be trivial to resolve.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3267 (comment)> , or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgLkKvS4E7YUp2x3_Ln8yNQWSz5u6geks5sZpHXgaJpZM4OdH8J>
.
…--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#3267 (comment)
|
It appears that SpeechHub can be downloaded from http://www.speakon.org.uk/SpeechHub.html. I am not sure if it is still being developed or not. I assume not. @Brian1Gaff do you know if this is still being developed? @josephsl do you think it is worth presenting this on the synth list on our community page if this addon is not being further developed? |
Hi, ultimately, it is up to developers to say if it is being developed, but given no updates (last time I checked), I think it is better to leave this out of synth page, especially once we start official Python 3 transition workflow. Thanks.
From: Ethan Holliger <notifications@github.com>
Sent: Friday, October 12, 2018 6:02 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] speach hub should be aded to nvda sinth list (#3267)
It appears that SpeechHub can be downloaded from http://www.speakon.org.uk/SpeechHub.html. I am not sure if it is still being developed or not. I assume not. @Brian1Gaff <https://github.com/Brian1Gaff> do you know if this is still being developed? @josephsl <https://github.com/josephsl> do you think it is worth presenting this on the synth list on our community page if this addon is not being further developed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3267 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkHNW2wxfcQecnJPJRxaalecmYbMAks5ukTt8gaJpZM4OdH8J> .
|
Given this synth has not had any updates lately, I am going to close this issue. |
Reported by Animesh.mr on 2013-06-07 12:02
speach hub is a tts server it may be used with nvda screenreader for more info go to
http://www.speechhub.org/index.html
The text was updated successfully, but these errors were encountered: