On Sun, 11 Jan 2026, Mouse wrote: >> For the case of declared latin1, contains utf-8, you could do a >> rather evil thing of temporarily switching the display charset to >> latin1 and â??Raw 8-bitâ?? to ON. > >That *is* evil!
I said so :þ >> That might just work, if you use lynx in the C.UTF-8 locale and >> donâ??t have any nÅ?n-ASCII UI strings. > >It also depends on the UTF-8 to not use any 0x80-0x9f octets (which “Raw 8-bit” ought to handle that, no? But yes, this is… only something of last resort. >It will also cause the terminal to advance by one character position >per UTF-8 character when lynx is expecting it to advance by one >position per octet. This may or may not break anything, depending on >various factors, probably including some I'm not aware of. Yes, that’ll be fun… not that lynx handles predominantly nōn-Latin text well anyway. But the OP used lynx -dump, so… I included the perlre(1) as a better hack. bye, //mirabilos -- 18:47⎜<mirabilos:#!/bin/mksh> well channels… you see, I see everything in the same window anyway 18:48⎜<xpt:#!/bin/mksh> i know, you have some kind of telnet with automatic pong 18:48⎜<mirabilos:#!/bin/mksh> haha, yes :D 18:49⎜<mirabilos:#!/bin/mksh> though that's more tinyirc – sirc is more comfy
