GNOME Bugzilla – Bug 658781
Some text not spoken at all since gobject introspection changes in orca 3.1.9x.
Last modified: 2011-09-14 17:18:56 UTC
Since the move to gobject introspection, I have foudn that some text does not get spoken, either when I navigate over it in flat review, or with the cursor if I am in for example gedit. The following text doesn't read for me, i.e when I use either flat review or move up/down in gedit to read the line, I get no speech: Granted, espeak doesn't actually pronounce the text, but reads out something related to the symbols in that author name string. Author: Мирослав Николић <miroslavnikolic@rocketmail.com> IT doesn't even get spoken whilst reviewing it in in firefox. Sed text is read perfectly ok with Orca 3.1.5. Some particulars: Orca: 3.1.91 pygobject: 2.90.3 GTK: 3.1.18 at-spi: 2.1.91 (atk, core), 2.1.90 (pyatspi)
Nice catch. Thanks!! Yeah, apparently in the brave new introspectiony world things have changed when attempting to encode or decode strings. Thus the proper solution is two-fold: 1. Figure out why python's unicode handling spits up in these sorts of cases. 2. Figure out why we are constantly going back and forth between UTF-8 and Unicode in the first place. I bet there's a good reason, but I'd sure like to know what it is along with how truly necessary it is. Given we're about to hit code freeze.... The short-term solution is to add (more) sanity checks to ensure we don't spit up due to "ascii codec" problems. Done. http://git.gnome.org/browse/orca/commit/?id=afc8a0d2990c517aa1e5f7927194a96997d8da5a