Hello,
If using the snapshot build, you could try the utf-8-encode.mrc
file to see if it will solve your problem.
I did, but it didn't work. I had to use Shift_JIS for everything. I
mean, the body of the messages is converted to Unicode correctly, but
not the attachments. The problem here is that the message bodies are
encoded using ISO-2022-JP, while filenames are encoded in Shift_JIS.
MHonArc converted the ISO-2022-JP body to Unicode, and the Shift_JIS
filenames to HTML entities, so if I chose to use Unicode in my browser I
could read the message, but not the filename, and if I chose Shift_JIS I
could read the file names, but not the messages.
I 'solved' it using a bit of preprocessing using sed and nkf, but it's
neither elegant nor robust. It will break if someone sends (for example)
an attachment with an EUC-encoded filename.
If not, could you provide me (via private mail) an example
message that illustrates the problem. Hmmm, thinking about, could
you provide me an example message even if utf-8-encode works for
you. It may help me determine if I have to make any changes in
how extracted header information is handled.
Hmmm, we have the archive running already and I prefer not to touch it.
I'll install MHonArc later in my own server at home
(http://www.ag0ny.com) and I'll do some testing with my mailinglist
archives.
Regards,
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-USERS
