Re: [bgware] Announcing ezmlm-browse version 0.13

--8Tx+BDMK09J610+l
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tuesday, September 23 at 01:08 PM, quoth Bruce Guenter:
>Version 0.13 of ezmlm-browse is now available at:
>	http://untroubled.org/ezmlm-browse/

Could the next version of ezmlm-browse be modified to handle non-UTF-8=20
messages, and to correctly convert things (e.g. via iconv)? Currently,=20
the charset handling is pretty awful. Take, for example, this:=20
http://www.memoryhole.net/cgi-bin/ezmlm-browse?list=3Dstate_of&cmd=3Dshowms=
g&msgnum=3D41

The original message was in the windows-1252 charset (relatively=20
common). The entire page is tagged as UTF-8, but the message contents=20
are transmitted unchanged from the original, which means they're=20
mis-tagged. Any browser that looks at that will choke, because all the=20
non-ascii characters must be considered (at best) malformed utf-8=20
characters. Since the message is already tagged as utf-8, all that=20
needs to happen is ezmlm-browse should actually convert the messages=20
=66rom their labeled character sets into valid utf-8.

~Kyle
--=20
I like to keep an open mind, but not so open my brains fall out.
                                -- Arthur Sulzberger, NY Times chairman

--8Tx+BDMK09J610+l
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkjZWLkACgkQBkIOoMqOI15kdACeK4d49xdjNVLTLhr+LuG3FmVl
sEoAn26r7dh/Ah8/EM0kHmuYFsdrsJ27
=xurT
-----END PGP SIGNATURE-----

--8Tx+BDMK09J610+l--