-
Notifications
You must be signed in to change notification settings - Fork 6
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
Publish 1.1 to the app store #46
Comments
@djphoenix I was about to ask the very same question. Please kindly either publish V1.1 to the App Store or at least make a newer Test Flight version available. |
I am having the same issue, and I relay on the sinth daily so it's quithe te situation... |
I think there will be a next version in TestFlight with, at least, updated dictionaries and maybe some fixes related to core. It will take 1-2 days. Perhaps. |
@djphoenix Thanks for keeping an eye on the project. Looking forward to it. |
Yep, what @amirsol81 said, thanks for all you've done. I'll be keeping my eye on the testflight app then. |
Speaking of fix, can we make it possible to control the punctuation level of espeak? Currently, it seems espeak has it very own punctuation level and completely ignores the one from VO. If you go in VO punctuation setting, you can see that in the most punctuations there's the |
@xogium please open separate issue for it. It is possible to control espeak own punctuation list, but I should take a look on it separately. |
Is the new beta out? If so I'd like to try it, I only heard about it after the first one expired. Thanks. |
@dparker21 1.1-3 is available, link is still here |
Hello,
A couple days ago, Testflight version 1.1 of EspeakNG expired after the 90-day period. As a result, now the only precompiled available version is the very first 1.0 that was submitted to the store. This version, although works, is missing some useful features that were added later like #40.
Do you have any plans to either submit the app in its current state to the store or release a new version in testflight?
The text was updated successfully, but these errors were encountered: