@jcsteh: Would you think this makes sense if #4877 is there and language switching between synthesizers is supported?

In case of auto synth switching, I'd think that'd reduce the need for this even further. What's the use case for this?

@elliott94 This is a gentle request to respond to #2590 (comment).

Happy for this to be closed. :)

We don't have auto synth switching yet, so this request is still valid. Here are some use cases that I could think of:

• You read a text in a certain language and a certain synthesizer can pronounce the words much better, so you want to switch that on the fly
• In some applications you would like to use a synthesizer which recognizes languages automatically in a more reliable way for certain tasks, so you change the setting on the fly.

This feature assumes that the settings of the synthesizer can be adjusted and they will not be inherited to other synthesizers. This means if I set the speed for eSpeak to 80, when I choose onecore from synth settings ring, the specific settings for onecore should apply (i.e. different speed etc.).

In general, at least in my view, automatic switch synth would be a very good solution. The question is weather NVDA can provide a heuristic to assess which synthesizer is most suitable to pronounce a certain language. I guess it is very hard to implement such a heuristic for all synthesizers out there. So a manual solution might be worth to consider here.