eSpeak: Code for character mode is incorrect

[nvaccessAuto]

Reported by jteh on 2013-03-25 04:41
In the espeak synth driver, for character mode, we use . This actually does nothing with eSpeak and seems to be Microsoft specific. We should be using or perhaps which eSpeak documents as supported. Of course, we should check whether this has undesirable effects first.

References:

• For interpret-as="characters": http://www.w3.org/TR/ssml-sayas/
• For interpret-as="tts:char": http://lists.freedesktop.org/archives/accessibility/2006-March/000078.html

[nvaccessAuto]

Comment 1 by mdcurran on 2013-03-28 00:11
"characters" seems to do nothing at all for at least english and Chinese. But "tts:char" allows speaking numbers of generic group letters (e.g. Chinese letter might now be spoken as Chinese 3d4f). However, "tts:char" also raises the pitch of capital letters on its own, and adds the word "capital" to the start. Both of these features NVDA wants independent of the synth.
Are there settings in eSpeak to disable capital and pitch? if so then tts:char would be okay. If not, then we either go with "characters" as it may in some circomstances be more correct for a language "a b c" verses "a cat". Or we just remove say-as alltogether and leaving it as it was.

[nvaccessAuto]

Comment 2 by mdcurran on 2013-03-28 00:18
Actually, I made a typo. "characters" does exactly what we want.

[nvaccessAuto]

Comment 3 by mdcurran on 2013-03-28 01:03
Fixed in b5d33a2.
Changes:
Milestone changed from 2013.2 to 2013.1
State: closed

[nvaccessAuto]

Comment 4 by mdcurran on 2013-03-28 04:59
Backed out in 67c400a as this causes Chinese letters, when using an eSpeak chinese voice, to be also announced as values, rather than the correct Chinese pronunciation.
Changes:
State: reopened

[nvaccessAuto]

Comment 5 by mdcurran on 2013-03-28 05:00
Perhaps for 2013.2 I think. Unless we want to specifically check for Chinese and not do it... though there could be other languages.
Changes:
Milestone changed from 2013.1 to 2013.2

[nvaccessAuto]

Comment 6 by jteh on 2013-03-28 05:20
I'd say that problem is a bug in eSpeak, in which case it should be reported upstream.

[nvaccessAuto]

Comment 7 by jonsd on 2013-03-29 11:27

this causes Chinese letters, when using an eSpeak chinese voice, to be also announced as values, rather than the correct Chinese pronunciation.

Fixed now in eSpeak 1.47.03e in preparation for version 1.47.04.

[nvaccessAuto]

Comment 8 by mdcurran on 2013-04-02 23:27
Again fixed in 5e854e6. eSpeak 1.47.04 fixes the Chinese character issue.
Changes:
Milestone changed from 2013.2 to 2013.1
State: closed