Samuel Thibault (2024/03/26 13:45 +0100):
> Sébastien Hinderer, le mar. 26 mars 2024 13:40:48 +0100, a ecrit:
> > I think what mislead me is that, although the braille rendering isdone
> > by BRLTTY, there continues to be a speech rendering which, I think, _is_
> > done by Orca.
>
> That's
Sébastien Hinderer, le mar. 26 mars 2024 13:40:48 +0100, a ecrit:
> I think what mislead me is that, although the braille rendering isdone
> by BRLTTY, there continues to be a speech rendering which, I think, _is_
> done by Orca.
That's entirely possible, since Orca doesn't even know that brltty
Hey Samuel,
Samuel Thibault (2024/03/26 13:34 +0100):
> AFAIK, the latest released versions of orca and brltty handle it
> correctly: usually Orca uses the default priority (50), except in flat
> review mode, in which case it uses a higher priority (70). On the brltty
> side, the a2 screen reader
Hello,
Sébastien Hinderer, le mar. 26 mars 2024 12:00:58 +0100, a ecrit:
> I think my graphical Mate terminals are rendered by Orca, whereas I do
> see a graphical BRLTTY process, run with the command
>
> /bin/brltty -b ba -s no -x a2 -N
>
> I assume there is a priroity issue between two BrlAPI
Dear all,
I think my graphical Mate terminals are rendered by Orca, whereas I do
see a graphical BRLTTY process, run with the command
/bin/brltty -b ba -s no -x a2 -N
I assume there is a priroity issue between two BrlAPI clients. HAs
anybody already encountered this problem? Is there a known
