Paul Eggert wrote:
On 2026-05-30 02:14, Lasse Collin wrote:
It blocks C0 control chars but not C1.
Thanks for mentioning that. I suppose I vaguely hoped C1 wasn't a problem.
Obviously I was mistaken.
FWIW, I think that treating C1 codes in the C locale as printable characters
(as Windows-1252 does) could help in getting the obsolete C1 redefined as
printable (and stop causing trouble) in common platforms.
https://en.wikipedia.org/wiki/C0_and_C1_control_codes#C1_controls
"Nowadays if these codes are encountered it is far more likely they are
intended to be printing characters from that position of Windows-1252 or Mac
OS Roman."
My 2 cents,
Antonio.
