Holger,
I have a guess as to what happened. (And I don't think it is a Mozilla bug.)
1. You are probably using non-MIME headers. That is, you have the
following line in your prefs.js.
user_pref("mail.strictly_mime_headers", false);
2. You send a msg in ISO-8859-15, which seems to be your favorite encoding.
3. Your NNTP-posting host does not like non UTF-8 8-bit headers and so
it changes 8-bit characters to UTF-8 bytes -- some people are promoting
UTF-8 headers and so this news posting host you use might have that
conversion set for offending headers.
4. When your NNTP posting host does this conversion, it also converts
your Content-Type charset to [object Window]. But the body remains in
ISO-8859-15.
I looked at 500 most recent msgs in the newsgroup you cited in your
message and your msg was one of 3 msgs or so that used raw 8-bit
characters in the Subject header. Other posters are using MIME subject
headers for 8-bit characters. I also confirmed that your subject header
contains UTF-8 bytes. (BTW, Mozilla to its credit automatically detects
UTF-8 in headers.)
My suggestion would be:
A. Send MIME encoded headers by deleting the following line from your
profile:
user_pref("mail.strictly_mime_headers", false);
B. This will make your headers 7-bit and will not be touched by your
NNTP posting host.
I used ISO-8859-15 encoding with raw 8-bit header bytes in a test
message with the latest build and it seems to be sending out the bytes
correctly in ISO-8859-15 if I use a character like umlaut "�". So, I
don't think it is a Mozilla side bug unless something changed in the
last 10 hours or so.
So my guess is that your NNTP posting host might be doing the
conversion. Try posting a news article from another news host if
possible and see if there is any difference -- that is, if you don't
want to send MIME headers. I do recommend strongly that you use MIME
headers in news and mail instead.
- Kat
Holger Metzger wrote:
> Using the latest nightly.
>
> I posted a message in de.comm.software.newsreader where the subject line
> contained an umlaut ("�") (I know I should have avoided that, but I
> trusted Mozilla).
>
> Mozilla used the following weird-looking content-type:
>
> Content-Type: text/plain; charset=[object Window]
>
> Never heard of that charset. :-) What's going on. And yet again an
> embarrassment for Mozilla in a professional newsreader group. :-/
>
> Should I report a bug?
>
> -Holger
>
>
--
Katsuhiko Momoi <[EMAIL PROTECTED]>
Web Standards/Embedding
Netscape Technology Evangelism/Developer Support
