[BRLTTY] Clickable links, virtual consoles etc. (Was Re: Footsteps towards better accessibility in Linux)
Samuel Thibault
samuel.thibault at ens-lyon.org
Fri May 9 17:25:32 UTC 2025
Hello,
Sébastien Hinderer, le ven. 09 mai 2025 19:16:23 +0200, a ecrit:
> Dave Mielke (2025/05/09 12:48 -0400):
> I am a bit surprised that the vcsa interface was not designed to
> represent screens that actually can be displayed, but I guess it's jsut
> that the two date from different times.
>
> If we wanted to change the vcsa, I assume that would create backward
> compatibility issues and it would thus be better to introduce a new
> interface?
linux/drivers/tty/vt/vc_screen.c says:
* /dev/vcsN: the screen of /dev/ttyN (1 <= N <= 63)
* [minor: N]
*
* /dev/vcsaN: idem, but including attributes, and prefixed with
* the 4 bytes lines,columns,x,y (as screendump used to give).
* Attribute/character pair is in native endianity.
* [minor: N+128]
*
* /dev/vcsuN: similar to /dev/vcsaN but using 4-byte unicode values
* instead of 1-byte screen glyph values.
* [minor: N+64]
*
* /dev/vcsuaN: same idea as /dev/vcsaN for unicode (not yet implemented).
So it's probably just a matter of adding vcsuaN support (with 16b or
even 32b numbers.
(apparently the comment saying vcsu is like vcsa is just wrong: vcsu
doesn't have the heading attributes)
Samuel
More information about the BRLTTY
mailing list