[BRLTTY] can't read screen content
Sébastien Hinderer
sebastien.hinderer at ens-lyon.org
Thu May 21 10:53:36 UTC 2026
Hello,
Small status update on this. I think the escape sequence mentionned
previously, ^[%@, switches the console in non-UTF-8 mode. I assume this
changes the format of /dev/vcsa to something BRLTTY cannot read any
longer.
Is that correct? If so, is there a way to detect whether the
console is or is not in UTF-8 mode and for BRLTTY to cope with both
situations?
According to my findings: both the installer I use and the Debian
installer use newt, which requires the console to be in non-UTF-8 mode to
draw the dialog boxes, hence the need to print this escape sequence
before intializing newt.
So I fear if BRLTTY cannot read non-UTF-8 content on VCSA it will become
impossible to run these installers with recent kernels.
But maybe I am missing something?
Seb.
More information about the BRLTTY
mailing list