Hi Hans-Peter,
the behaviour that you describe looks like somewhere in your platform there
is some character-backspace-character detector active that replaces the
characters displayed when they are being overstruck.
I wrote such character-backspace-character detectors myself in the 1980s
as part
Hi Jürgen,
thank you for comment.
I am quite sure it's not an APL-character problem.
The characters in question are defined within the APL-keyboard layout as
normal UTF-8 characters.
The "overlay" I experience is different from APL-Character over strike:
An APL over strike is character-bac
