> 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! > 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 much UTF-8 does), or, alternatively, on the other layers involved to not check that the supposedly-Latin-1 text is entirely within the Latin-1 text range. 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. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
