Any opinions on how to deal with RFC2047 character sets? These are
an incredible pain.
I have written some other mail processing code that handles character sets.
This code works by converting everything into UTF-8 internally. It does
this by having mapping tables that map codes from various character sets
into UTF-8 codes. These tables live in a directory full of mapping files
as there are potentially a very large number of these. Is this an approach
that we should take with nmh?
Doing things this way means that character strings can be stored as such
instead of as arrays of character set, string pairs.
Separate from this, there is the issue of having to display these strings.
I don't know what's common out there, my terminal windows handle UTF-8.
There is no standard of which I'm aware for finding out the local character
set. What do we want to do here? I'm happy to just go UTF-8, but I don't
know whether or not this is a good idea for everybody.
Jon
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers