Re: [tin 1.9.x] problem with Multipart/Mixed and text/plain iso-10646-ucs-2 base64 parts

On Fri, Aug 20, 2010 at 01:08:32AM +0200, Urs Janßen wrote:
> When reading a gated malinglist I noticed that tin didn't display a
> text/plain part in [...] iso-10646-ucs-2

root cause are possible NULL bytes in a multibyte char (in UTF-16, UTF.32,
...) but we are using string functions...
a trivial "workaround" would be to assemble a list of charsets which may
contain NULL bytes and tell tin to skip parts in that charset.
a partical fix would be to fix just the charset conversion, a real fix might
be much more complicated as tins code also relies on not seeing any 0 bytes
when reading an article from disk/net.