Nano-tiny (e.a) vs libslang-utf8
First of all I can confirm this happens with 1.0.6-2 as well.
In fact I tried doing this in all slang based editors I have installed.
I tried two tests
1. Loading the following file
/tmp/nano-1.1.5> LANG=C less /tmp/testje
"/tmp/testje" may be a binary file. See it anyway?
pond<A3>pond
The <A3> is the latin-1 UK currency symbol
gives
nano-tiny & jed : Only "pond" visible
ae : Shows "pondpond" (see also below) + keyboard shortcuts only partly visible.
2. Insert a high-bit character
nano-tiny & jed : show only characters upto high-bit character on that
line. Rest invisible (but cursor moves normally), saving the file
gives the expected results (with all the invisible characters)
ae: Displays as if the high-bit character was moved to the end and replaced
by space[1], i.e. if C represents the cursor then the file from 1 is shown as
pondpond C
I would suggest slang1-utf8 is broken (see also bug#128255 and bug#129415) and suggest
retitle 129694 UTF8 slang breaks editors
reassign 129694 slang1-utf8
merge 129694 128255 129415
Jan
P.S. Using unicode enabled shells or setting various locales does not make any difference.
Footnotes:
[1] i.e. it filters it out when displaying, but does let it count when doing cursor positioning.
Reply to: