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:

• updates espeak to the latest commit. The strategy to updating was to follow the updating espeak readme.

This seems to add support for 2 constructed languages from JRR Tolkien's LOTR.

Testing strategy:

• Diff the files as per the strategy above

git diff ab11439b18238b7a08b965d1d5a6ef31cbb05cbb 74068b91bcd578bd7030a7a6cde2085114b79b44 Makefile.am
git diff ab11439b18238b7a08b965d1d5a6ef31cbb05cbb 74068b91bcd578bd7030a7a6cde2085114b79b44 --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