<Initial description transferred from bugsplat bug 333117. Assigning to phil
for now because jefft and bienvenu do not yet have a bugzilla account>
Messenger ignores MIME charset label
Messenger always ignores the value of the charset= parameter of the
Content-Type: header of the text part it is displaying.
------- Additional Comments From phil 11/14/98 22:42 -------
Bob and Naoki, any comments on our capability to support this?
Setting all current Open/Normal to M4.
qa contact to pmock for now
Reassigning to Rich Pizzarro
Should be able to deal with this in the new emitters.
Setting to M5 for now. Does anyone have an example of this that I could use.
Adding nhotta and bobj to cc: list.
Latin1 example can be easily created by 4.5.
1) In the subject field hold "Alt" key and type 0201 in the num key then release
the "Alt". You should be able to see É.
2) Make sure that MIME encoding is enabled in the pref.
3) Sent out header should contain
4) If the MIME decoder is properly hook up, É should be seen for the above line.
Rich, can this be done for M4? This was working for M3.
I think we just need to hook up the MIME decoder.
Also, if you change the "iso-8859-1" to "iso-8859-5" you should see something
other than latin capital letter E with acute.
Sorry, but my development system has imploded as of yesterday at noon and I
really dont have a stable build environment. I have some changes that I've
salvaged that I need to checkin today, but that is about all I will be able to
do. Sorry :-(
I think this has been fixed but the verification is blocked by XML UTF-8 bug.
Rich, is there way to verify this (e.g. by view source)?
If so, please change the status to 'FIXED'.
If the problem here is that the UTF-8 conversion is getting truncated, then the
view source will look truncated as well. I think this should remain fixed,
(which it is) and the verification will have to wait on the other bug.
Verification depends upon a fix for
The main blocker of this is the XML bug #4463.
The MIME decode is done but I am seeing ISO-2022-JP string appears in the view
instead of UTF-8.
After MIME decode, we need to convert from the charset returned by MIME decoder
Clear the resolution.
I think Rich has a fix, waiting for the tree to open.
Got these changes FINALLY checked in so this should be fixed. Thanks naoki :-)
Verified on the in the April 27 Win32 build (build id 1999042708). When I send
my a message to myself that contain an accented character the received message
header contains the string "=?iso-8859-1?Q?=C9?=".
On Linux build (build id 1999042708), I have not been able to verify on this
platform because, there doesn't appear to be an easy way to generated accented
I have asked a couple of unix engineers but they didn't know. It was
suggested to talk to Akkana so I emailed her.
Side note, the only information I found was on our international qa web page,
http://home.netscape.com/eng/intl/accentinput.html In previous projects, I got
around this problem by sending myself a message from windows that
contained the desired accented character then doing a copy and paste.
Unfortunately, copy and paste is not implmented.
Final verification is pending...
Peter, we need to test this for a variety of charsets to see
if this is working.Please re-assign this bug verification to me.
Received message to Akkana. You can copy and paste the accented character in.
I was able to test the bug successfully. It didn't work for me previously
because I was still using Alt+C and Alt+V. I didn't know the short cut keys
changed from Nova to Ctl+C and Ctl+V. It works on Linux.
Per Momoi request, I am reassigning this bug to him for final verification.
** Checked with 4/29/99 Win32 and Linux builds **
We are now able to display headers and body of messages in
many different languages without switching the encoding menu.
(In fact, at this stage, the encoding menu for Mail lists
only Latin1 and Japanese.) As long as we have the right fonts --
I use the new Bitstream Cyberbit 2.0 font for this purpose --
we can display the following languages headers and body without
doing anything on the part of the user, which is what this bug
The list of converters to/from Unicode enabled up to M5 can be
found at the above URL. I've confirmed that the following charset
msgs can be displayed on Windows:
ISO-8859-1 (French, German)
ISO-8859-4 (Estonian: Baltic)
Traditional Chinese (Big5)
Simplified Chinese (Gb2312)
On Unix/Linux, display seems correct only for Japanese and Latin 1,
but this is currently a known limitation on Unix where GFX nulti-
font rendering needs to be implemented properly.
All the above shows that charset label honoring is now in
place. Marking the fix verified on Win32 and Linux.