JPN Mail header should be properly MIME-encoded on send

VERIFIED FIXED in M5

Status

MailNews Core
Internationalization
P3
normal
VERIFIED FIXED
18 years ago
9 years ago

People

(Reporter: Katsuhiko Momoi, Assigned: nhottanscp)

Tracking

Trunk
All
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
** Obserevd with 4/20/99 Win32 build **

Currently we are lacking iso-2022-jp converter to/from Unicode.
Because of this, we cannot verify if MIME-encoder is working properly
for Japanese. We verified that it is working for ISO-8859-1 in
Bug 3994.
This bug has been filed to make sure that JPN MIME-encoding is
working OK on mail header once the converter gets checked in.
(Assignee)

Comment 1

18 years ago
iso-2022-jp converter from Unicode is available so we can see Japanese subject
and the body.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M5
(Reporter)

Comment 2

18 years ago
It is true that we can display Japanese headers and body.

What I meant to say is that I'm not able to conrifm that
Japanese headers we send out by 5.0 is properly MIME-encoded.

There is an Editor bug probably which is preventing the input in
Japanese. Also copy/pase of Japanese strings does not work in the
Subject header area.

In any case, at this point I'm still not able to confirm
that 5.0 sends out properly encoded Japanese headers.
Sine I already verified ISO-8859-1 header encoding in Bug 3994,
this bug has been filed to keep track of the Japanese header
encoding on send.
(Assignee)

Comment 3

18 years ago
>iso-2022-jp converter from Unicode is available
incorrect, only to Unicode is available not from

Comment 4

18 years ago
Cata is working on the 2022-jp encoder now
http://bugzilla.mozilla.org/show_bug.cgi?id=5289
(Assignee)

Comment 5

18 years ago
5289 is marked as fixed, Endder bug (4388) should also be fixed in order to test
Japanse message body send.
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

18 years ago
My last comment was not correct, this bug is about header not body (4388).
I mark this as FIXED. I know there is an input bug 5061 so we cannot veriry.
I think this bug may be marked as dup of 5061.
(Reporter)

Comment 7

18 years ago
No. We should keep this bug separate from 5061. Even if
5061 is fixed, we still need to confirm that Japanese
headers are MIME-encoded correctly.
(Reporter)

Comment 8

18 years ago
Unverifiable until we get Ender widgets for the headers.
(Reporter)

Comment 9

18 years ago
Tried tne new GFX widget for the Subject header and but
the apprunner crashed. So, I guess this has to wait another cycle
for verification.

Comment 10

18 years ago
Last week we were able to type Japanese into form text fields and text areas.
Teruko, Is this still working?  Or is there a mail specific problem?
Kat, Were you able to type anything before crashing?
(Reporter)

Comment 11

18 years ago
GFX thing is not very stable. Sometimes I see input in Japanese and
then it crashes on Send. Sometimes, it simply crashes on Japanese
input into the Subject window and I don't even see Japanese input.
These are probably mail-specific problems -- I would file a bug
if it will be taken seriously at this point. I think Steve Clark
said that he would look at only functional bugs.
(Reporter)

Updated

18 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 12

18 years ago
** Checked with 9/16/99 Win32 M11 build **

JPN input into the subject header has been working
since the GFX widget got tunred as default (more or less).
We can finally see that we MIME-encode JPN subject correctly,i.e.
B64of iso-2022-jp.

Marking it verified as fixed.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.