Link to issue number:

None

Summary of the issue:

It is helpful to run the latest version of espeak.

Description of how this pull request fixes the issue:

• Reverts Downgrade espeak to aafd2e720 #12495
• updates espeak to the latest commit. The strategy to updating was to follow the updating espeak readme.

Testing strategy:

• note that there has been no changes since the commit that was reverted to the build process (f6d092a9c13d864ede78c493f64a7d32cde41f09).

git diff f6d092a9c13d864ede78c493f64a7d32cde41f09 ab11439b18238b7a08b965d1d5a6ef31cbb05cbb Makefile.am
git diff f6d092a9c13d864ede78c493f64a7d32cde41f09 ab11439b18238b7a08b965d1d5a6ef31cbb05cbb --stat

• NVDA builds, ensure espeak continues to work as expected

Known issues with pull request:

May reintroduce #12465. If this is the case, espeak-ng/espeak-ng#950 will need to be updated. This may remain an issue when updating espeak in future.

As a short term solution I'll do a revert. However, since there is no test case that works for me and @valdisvi the bug might be reintroduced by accident later. [revert commit]

Originally posted by @jaacoppi in espeak-ng/espeak-ng#950 (comment)

Change log entries:

See changes.t2t diff

Code Review Checklist:

• Pull Request description is up to date.
• Unit tests.
• System (end to end) tests.
• Manual testing.
• User Documentation.
• Change log entry.
• Context sensitive help for GUI changes.
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers