You know that loop you have that resets every widget's accessible name to it's variable name? Maybe use that *only* during LDTP testing so that properly translated accessible names can be provided for users in the actual release by commenting out that loop.
Maco On Sep 23, 2011 5:31 AM, "Evan Dandrea" <[email protected]> wrote: > This was a purposeful change so that we can get at the widgets in LDTP without relying on knowing their text content beforehand: > http://bazaar.launchpad.net/~ev/+junk/ubiquity-ldtp-tests/view/head:/test_ubiquity.py > > Do you know a way to provide screen readable text while still exposing > each widget as a static string? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/781385 > > Title: > Ubiquity GTK should have useful accessible names set in the Glade .ui > files instead of using the variable names > > Status in “ubiquity” package in Ubuntu: > New > > Bug description: > Binary package hint: ubiquity > > Installing Ubiquity with Orca enabled results in things like "live > underscore installer" being read aloud instead of useful widget names. > Setting useful accessible names in Glade instead of assigning > accessible_name = variable_name in Python would be better. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/781385/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781385 Title: Ubiquity GTK should have useful accessible names set in the Glade .ui files instead of using the variable names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/781385/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
