Katsuhiko Momoi wrote: > Neil wrote: > >> Katsuhiko Momoi wrote: >> >>> There is a bug requesting that Mozilla use the charset specified in >>> the body when MIME charset info is not found in headers. >>> >>> http://bugzilla.mozilla.org/show_bug.cgi?id=77903 >> >> >> >> Thanks for the quick response! >> >>> This would work for POP mail but not really for IMAP mail since the >>> headers are downloaded first without peeking into the message body >>> or downloading it. >> >> >> >> Surely Content-Type is a header? Although this might not work for >> multipart messages. > > > I don't know exactly how this part works but it is my impression that > currently Mozilla downloads a "minimum" header set to create the > thread pane view for IMAP. But for the bug above, we might request > Content-type header in addition. Does anyone know what headers are > fetched in IMAP protocol by default or can a user agent specify what > headers to download? > > As for the multi-part messages, I think it would be reasonable to take > the first part as the basis for guessing the header charset. This > should catch a majority of cases.
Reasonable in concept but I guess this won't work because multi-part charset info is in the bodies. I don't think there is an easy way to correct the thread pane display afer the bodies are downloaded, either. > > >> >> >> BTW I noticed that when I forwarded the message the attachments pane >> displayed in Cyrillic but when I read the message in the newsgroup >> the attachment displays some Windows-1252 gibberish :-( > > > There might be a bug for this problem already. Let me CC a couple of > Mail testing people. If you have a specific example/test case, you > might want to file a bug to see if there is a duplicate bug. > > - Kat > -- Katsuhiko Momoi <[EMAIL PROTECTED]> Web Standards/Embedding Netscape Technology Evangelism/Developer Support
