-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/18/12 10:43, Thomas Dickey wrote: > > However, your example isn't 7bit ASCII. It contains 8 non-ASCII bytes (all > from the 128-255 range). >
Sure. The problem is not that the 8bit chars are not shown, but that xterm refuses to output _anything_ after the "unwanted" 8bit chars, even if the rest is pure 7bit ASCII. > One of those bytes is 0x9f, which happens to be a C1 control character. > Obviously xterm changes an internal state when this control char has to be printed. Is the rest of the text "illegal" in this new state? > xterm has an option allowing you to suppress this behavior: > > -k8 This option sets the allowC1Printable resource. When > allowC1Printable is set, xterm overrides the mapping of C1 con‐ trol > characters (code 128-159) to treat them as printable. > > but the 0x9f would not produce output in this case unless your font happened > to be one of the less-used ones that provides a glyph in that position. > Of course I tried: Seems to work. It also works, if I set and immediately unset the "UTF-8 Encoding" mode in the Ctrl-RButton menu, before I run "zcat x.gz". This is still weird. Can you reproduce this? Regards Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlBcnnwACgkQUTlbRTxpHjeLTgCggSxJXHu/mk0O56MHawSFRY1/ VP8Ani3Y6zAY1Swr7Erx2DRa1iOkjw1V =jPCN -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
