@aral > And then: oh, and this charity is > paying for one person to work >on accessibility support to be >implemented now
Assuming it doesn’t fall through…
“We’re currently facing a major issue from the GNOME Foundation side. We hope it will be resolved before it impacts the coordination of the STF project, but if not, the future of parts of the project is uncertain.” https://thisweek.gnome.org/posts/2024/05/twig-149/
In LibreOffice, in the "View" menu, when "Field Shadings" is checked, non-breaking spaces (NBSP) appear grayed out, but narrow no-break spaces (NNBSP) do not. Is it possible to make narrow no-break spaces appear grayed out as well? And if yes, how ?
@aral Unless I'm mistaken, GNOME does not offer this functionality by default. Personally I use the "Dark Mode Switcher" extension and I have no problem (Fedora Silverblue 39). But I don't use any particular theme, I kept the default one.
@aral One of the missions financed by the Sovereign Tech Fund is precisely "Design and prototype a new accessibility stack". It's discussed almost every week in This Week in GNOME, for example https://thisweek.gnome.org/posts/2024/02/twig-135/.
@aral@la This is what the Langmap option in Vim is for. Where I have the t in my bepo, there is the j in qwerty, so I can request that a "j" be displayed when I press t. But when I press the dead key ^, the system waits for me to press a second key before sending the information to the software (^+e=ê, ^+^=^, ^+p=^p ), so I can't fully simulate a qwerty keyboard.
The solution might be to use key-codes instead of key-chars, but that would mean rewriting the entire base layer of the software?