Reported by nvdakor on 2015-06-27 03:20
Hi,
Spin-off from #5100:
Consider the following scenario: a user uses NvDA in a language other than English, such as Japanese, and uses synthe settings ring commands to manipulate voice settings. Normally, the user would hear only the translated portion of the message, but for some languages, the accelerator used in voice settings dialog is also spoken.

Problem: This is because commonly manipulated settings are stored in synth driver handler, and the translatable strings in there are also used in voice settings dialog.

Proposed solution: Modify i18nName function as follows:

1. Look up a dictionary which maps currently used translatable string to normalized string suitable for output when changing the setting via synth settings ring.
2. If possible, for synthesizers which exposes additional configuration options via voice settings, let them return a normalized string for synth settings ring.

Impact and use cases:

• Translators can translate a given setting differently - one for voice setting and synth settings rint.
• Allows Gettext contexts to be applied so the translators can understand where the message will be used.
• Allows synth driver developers to provide different messages for use in GUI and synth settings ring.

Additional comments are appreciated. Thanks.

Blocking #5100