Plans for per-object locale?
I'm auditing the DBus interfaces for accessibility in at-spi2-core, and I have some questions about handling locale information. CC @mgorse for the details of the interfaces.
The current state of things is like this; please tell me if I missed something:
-
Orca does not query for the locale of applications/accessibles/documents at all. Is this planned?
-
(I suppose the intention is to tell the speech engine something like "say $string in $language" rather than setting the language at startup and then saying everything in that language?)
-
The
Locale
property in theAccessible
interface is supposed to be the canonical or most fine-grained way to query for locale/language information for each object. From what I have gleaned from git histories, things started with theApplication
iface having a way to query the app's locale, and alsoDocument
— but then things slowly moved to wanting a per-object locale in case you have things like a document with paragraphs in different languages. (Or an editor for translations, which displays multiple languages at the same time - etc.). -
There is
Application.GetLocale
(method),Image.ImageLocale
(property),Document.GetLocale
(method). Are all of these to be superseded byAccessible.Locale
? -
@ebassi GTK4 implements
Application.GetLocale
but as far as I can tell it never gets used upstream. -
atspi implements
Accessible.Locale
,Image.ImageLocale
, andDocument.GetLocale
, but it doesn't even have a method to queryApplication.GetLocale
. The counterpart in atk-adaptor always returns NULL. Can I just removeApplication.GetLocale
and the bits of C code related to it that don't really do anything? (I assume this will get superseded withAccessible.Locale
implemented for the application object at some point in the future.)