Update espeak#7583
Merged
Merged
Conversation
michaelDCurran
approved these changes
Sep 13, 2017
feerrenrut
added a commit
that referenced
this pull request
Sep 13, 2017
Ensured that no changes to the voices available have been made.
michaelDCurran
approved these changes
Oct 18, 2017
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Continue to update Espeak. For the last set of changes that made it into master, see: #7385
Note:
If you notice a problem with Espeak on next (or master), please open a new issue to discuss this.
Summary of the issue:
In order to more quickly spot and report issues on Espeak, we are regularly updating espeak to the latest master on our next branch. When this gets to stable we can merge back to nvda master.
Description of how this pull request fixes the issue:
This updates the espeak submodule to the latest espeak-ng master commit and fixes any build errors.
Testing performed:
Known issues with pull request:
None
Change log entry:
For now none. But perhaps eventually: