GNOME Bugzilla – Bug 688172
Orca speaks in a different pitch when coming across upper-case characters
Last modified: 2015-11-06 06:36:51 UTC
When reading web content or any other content with a mix of upper-case and lower-case letters, orca changes pitch and will not go back to its default pitch unless orca settings are reloaded or the no-setup command is run in a terminal. To reproduce this, load any web page or text that contains upper-case characters. You will notice that Orca starts speaking in a higher pitch.
I've not been able to reproduce this bug in Fedora. Do you have a very specific test case or string?
(In reply to comment #1) > I've not been able to reproduce this bug in Fedora. > > Do you have a very specific test case or string? I just typedShe went to the Store in gedit and started arrowing character by character. As soon as it came across the upper case S in the text the bug happened. In fact its still speaking in the upper case pitch now. This happens with both espeak and voxin under speech-dispatcher. I hope this helps.
Ok, I can reproduce it now. Thanks!
I have nearly all of it fixed. But something odd is happening regarding the letter immediately next to the capital. As a test I set my uppercase pitch to 8.6 and then arrowed around this text: ssSss I would expect that either all the S's would be the same regardless of case (i.e. this bug). Or that the capital S would be in upper case, but all the lowercase s's would be in the default pitch (i.e. this bug has been fixed). What I am finding, however, is that the pitch seems to step down, with the capital S in uppercase pitch, the s encountered next in a lower pitch (but not the default), and the s after that in the default pitch. So far, I don't see where in Orca's code this could be happening. So I need to experiment a bit in the speech-dispatcher code outside of Orca. In the meantime, this commit will get you out of permanent upper case: http://git.gnome.org/browse/orca/commit/?id=6f94c02f84f2e9b9e12d5a8fd4964344de29cd9c
With respect to the oddity in comment 4, see https://its.freebsoft.org/its/issues/31653 Since the originally-reported issue is fixed as far as Orca is concerned, I am closing this bug.