Each Chrome tts voice currently has a name which gets used as a programmatic name.

Unfortunately, this imposes uniqueness requirements on the value (at least within the same engine).

The other issue this poses is the inability for an extension to localize the name.

This feature request is to add a new property to the voice representation called voiceDescription.

This value will contain the localized name of the voice.

An extension is then responsible for adding this value for every voice it supports. When the browser locale changes (e.g. via settings), the extension will be reloaded and new string resources populated.

This will impact all apis that set or get voices.

chrome.tts.getVoices
chrome.ttsEngine.updateVoices

are the most pertinent ones.

In addition, native win/mac/linux voices do not usually have a localization description, but this needs to be investigated to see if any new apis are available on those platforms.