Re: 8-bit characters mapped to 0xFF

JBeck> ... used to ... cut-and-paste 8-bit characters, ... exmh would do
JBeck> the Right Thing.  But 2.7.2 seems to mangle all such characters to
JBeck> 255 (0xFF).  Note that if I attach a file and specify base64 or
JBeck> quoted-printable as the encoding, then all is fine, but if I specify
JBeck> none as the encoding, or just insert a file, or just cut-and-paste
JBeck> directly into a plain text message, then the mangling occurs.

Klaus> I had the same problem. ... when changing from 2.7 to 2.7.2
Klaus> I changed nothing within my X11 configuration. (Solaris 9,
Klaus> /usr/sfw/bin/wishx8.3). The old version 2.7 even works.

For me it is Solaris 10, with the same 8.3 version of Tcl/Tk in /usr/sfw,
and going back to exmh 2.7.0 also "fixed" the problem.

Klaus> ... compiled myself a new tcl-tk (8.4) version.  This works with
Klaus> 2.7.2.  So problem seems to be incombability to tcl-tk 7.3?

Good suggestion; I just grabbed Tcl/Tk 8.4 from an (internal, probably old)
Blastwave mirror and changed my /usr/local/bin/wish sym-link from the 8.3
version in /usr/sfw to the 8.4 version in /opt/csw, restarted exmh (2.7.2),
tested again, and the problem is fixed.

So I wonder whether this is a bug in exmh 2.7.2 depending on something
which Tcl/Tk 8.3 cannot provide?

-- John