From: Jan Engelhardt on

On Wednesday 2010-04-21 01:49, H. Peter Anvin wrote:
>> Alexander mentioned:
>> [quoting the gmane nntp posting which was stripped of To:s and Cc:s]
>>>
>>> Since KOI7 is not used by any glibc locale, your use case is now
>>> extinct. I think that, unless someone finds out a different use case,
>>> these SI and SO characters should be deactivated completely (and not
>>> just in unicode mode).
>>
>> Alan, do you agree that the entire SI/SO can/should be removed?
>
>VT line drawing characters are generally assumed to be accessible using
>SI/SO (as they are by default.)

Indeed 0x0e 0x71 0x0f generates the same output as U+2501.

I can't say when the last time was that I saw SISO in use, though.
At least UTF-8 programs just print U+2501, so it should
be fine to exclude SISO handling there.
With

echo -en "\e%@"; setfont r -u /usr/share/kbd/unimaps/cp437.uni;
LC_CTYPE=C mc

it would also output no SISO and use 0xc4 for U+2501.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: H. Peter Anvin on
On 04/22/2010 01:39 AM, Jan Engelhardt wrote:
>
> Indeed 0x0e 0x71 0x0f generates the same output as U+2501.
>
> I can't say when the last time was that I saw SISO in use, though.

Probably a lot more recently than you think, especially if you are
dealing with terminal input from other hosts.

-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/