[BRLTTY] What is the best way to deal with Unicode characters?

[Shérab]

Hi,

I missed Aura's initial message so I am responding to that one. Thanks
to both for your messages.

Dave Mielke (2019/09/19 10:54 -0400):
> [quoted lines by Aura Kelloniemi on 2019/09/19 at 14:33 +0300]
> 
> >In my opinion the best that can be done now is to use a custom contraction
> >table to get multi-cell characters. It is complicated to set up, but should
> >work. 
> 
> What's the complication? Is defining your own contraction table really that
> complicated, or is it actually something else like wanting to use computer
> braille text tables augmented by multi-cell (contraction) definitions (i.e. a
> text table that can include a contraction table)?

For me the issue would be more about realising that, for instance,
\alpha is actually just one character. For instance I can imagine myself
very well wanting to delete that all word and pressing backspace several
times automatically when one press is enough to get rid of it.

The other issue I can see is the loss of vertical alignment. For
instance, imagine one has:

\alhpa = 1
\beta = 2

but with the unicode representations. Then visually the equal signs are
aligned, which they won't be with our textual representaitons.

It is perhaps something one just has to live with, I don't know. Just
trying to share some thoughts here. Perhaps we should communicate
towards our sighted colleagues that these unicode characters are simply
not practical to use for us visually impaired. After all, the idea of
lines of code not longer than 80 characters because of braille displays
has become rather well known so why not do something similar about the
use of unicode characters in programming or so?

Shérab.