GNOME Bugzilla – Bug 591734
[testing required] "No break space" character not spoken
Last modified: 2009-11-09 21:35:17 UTC
From http://mail.gnome.org/archives/orca-list/2009-August/msg00196.html: "Probably this is related to thunderbird but I decided to report so that someone can confirm. To reproduce try the following: 1. Create a new message using thunderbird. 2. In the body of the message type the following text: "This is a test" Without the quotations. You must type 3 (three) blanks between each word. 3. Try to review the text using the left and right keys. Note that some spaces are not announced."
I was able to reproduce this using the HTML-mode of Thunderbird for entering text. The problem is indeed the no-break space character. Adding the following to chnames.py resolves the problem: chnames[u'\u00a0'] = _("no break space") I think there is value in letting someone know there is a no-break space there, since it provides different behavior when it comes to wrapping. But, I'm willing to acquiesce if people would rather hear "space" than "no break space". It would also prevent the need for me to send out a string change notice.
Note that the fix for this should probably also translate all no-break space characters to spaces in the string just before it is sent to the synthesis engine. Otherwise, the synthesis engine may interpret the no-break space character as something else.
Created attachment 140821 [details] [review] Patch This patch does two things (hopefully): 1) When reviewing by character, you will hear "no break space" 2) When reviewing by any other means (say all, line, etc.), it should substitute a normal space for the no break space character In no case (hopefully) should the no break space character itself be sent to the synthesis engine. Please test by navigating by character, navigating by line, doing a SayAll, etc.
Tested and approved, works fine. Many many thanks for this fix. Finally I can stop fighting with my friend Ciro. He always sends me messages with more than one blank between the words and it was difficult to read them.
Hi Will. This works perfectly! It also solves the related 'double speaking of punctuation symbols' problem. thanks.
When reviewing the message line by line, lines with only one space are read as NoBreakSpace. Doesn't happen when reading the entire document.
Comment on attachment 140821 [details] [review] Patch Committed to git master for 2.27.91. Thanks for testing!
*** Bug 591724 has been marked as a duplicate of this bug. ***
Resolves all the pronunciation issues I had using the ibmtts speech engine. Thanks