improvement in Use spelling functionality if supported documentation in NVDA User guide

[nvaccessAuto]

Reported by blindbhavya on 2014-09-29 17:23 The documentation given for Use spelling functionality if supported is not very clear, in my view. I can't understand what it does. This is because, the check box is checked, and I run ESpeak, but still ESpeak reads a as as ur and not ay when when reading by line. I think some detail should be given in this documentation, and if possible an example.

[nvaccessAuto]

Comment 1 by jteh on 2014-09-30 01:30 The documentation already explains what this does and gives an example. eSpeak just happens to have rules to try to handle the case of speaking a single letter even if it isn't told that it's being spelled. Not all synthesisers do. Changes: Added labels: worksforme State: closed

[nvaccessAuto]

Comment 2 by blindbhavya on 2014-09-30 03:47 Hi. Then I feel that in the User Guide you should mention that 'ESpeak does not support this well' or something like that. This is because Sapi 5 has been mentioned, and ESpeak being the default synth in NVDA has greater importance, therefore in my opinion it should be mentioned.

[nvaccessAuto]

Comment 3 by jteh on 2014-09-30 03:56 eSpeak does support it. It just happens that eSpeak also does this itself for "a" even when the option isn't enabled.

[nvaccessAuto]

Comment 4 by blindbhavya on 2014-09-30 05:20 Hi. I am getting confused here... At least for me this documentation is not clear enough... So, how and where does spelling functionality help? Please explain using the example of a being pronounced as ur or ay (ए) What about individual characters and everything here? Please be as detailed as possible. Sorry for my ignorance.

[nvaccessAuto]

Comment 5 by jteh on 2014-09-30 05:57 The example is exactly as given. Some synthesisers will pronounce the letter "a" in its short form instead of "eh" when reading by character if this option is disabled. eSpeak doesn't, but some others do. eSpeak may require this differentiation for other characters, but I'm not sure about that. Anyway, I believe this option was introduced for synthesisers other than eSpeak which don't cope well when this option is enabled.

[nvaccessAuto]

Comment 6 by blindbhavya on 2014-09-30 09:41 Hi. Can this example of 'a' as 'ur' and 'eh' be given in the User Guide? I now think that I understand the use of this option. May I ask on the NVDA Users list if they understand the use of this feature with the help of the documentation? And if they don't understand, then may I ask them to comment here?

[nvaccessAuto]

Comment 7 by jteh (in reply to comment 6) on 2014-09-30 10:30 Replying to blindbhavya:

Can this example of 'a' as 'ur' and 'eh' be given in the User Guide?

From the User Guide:

For example, in English, "a" is both a letter and a word. This option allows the synthesizer to differentiate between these two cases if the synthesizer supports this.

i don't follow how this doesn't communicate that there are two pronunciations of "a". Most users won't understand it if we write "ur", since "ur" sounds quite different to the short "a" sound.

[nvaccessAuto]

Comment 8 by jteh (in reply to comment 7) on 2014-09-30 10:31 Replying to jteh:

For example, in English, "a" is both a letter and a word.

i don't follow how this doesn't communicate that there are two pronunciations of "a".

I guess the only clarification we could provide is this: For example, in English, "a" is both a letter and a word and is pronounced differently in each case. Does that clarify it for you?

[nvaccessAuto]

Comment 9 by blindbhavya on 2014-10-01 11:47 At least this seems a bit better. But could I ask on the NVDA Users list please for opinions of others?

[nvaccessAuto]

Comment 10 by jteh on 2014-10-02 05:56 If you ask too many people an open question about a subjective issue, you will almost always receive feedback stating that it could be changed. No one has ever raised this as a problem before. That's not to say that it shouldn't be changed, but the point is that you're the one who has raised the issue, so you're the one the new content needs to satisfy. If the changed I'm proposing clarifies it for you, that is enough.

[nvaccessAuto]

Comment 11 by blindbhavya on 2014-10-02 07:31 Hi. Ok, then what clarifies this for me is your suggestion and a mention that ESpeak supports this without this feature as well. That would be good enough for me.

[nvaccessAuto]

Comment 12 by James Teh <jamie@... on 2015-02-02 06:04 In [2e445c55536a22e03fdc65c42937e24fa1fd862c]:

User Guide: Minor fixes.

Fixes #4506, #4513, #3775, #4176, #4123.

Changes: Removed labels: worksforme

[nvaccessAuto]

Comment 13 by jteh on 2015-02-02 06:05 Changes: Milestone changed from None to 2015.1