Open Bug 173447 Opened 19 years ago Updated 8 years ago

Literal MIME word entered into header fields not encoded

Categories

(MailNews Core :: Internationalization, defect)

defect
Not set
minor

Tracking

(Not tracked)

People

(Reporter: 3.14, Unassigned)

Details

(Whiteboard: intl)

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/2002100214

This bug is kind of obscure. I was wondering, why Mozilla did not decode the
following in the subject of a posting:
=?iso-8859-1?Q?Ist=20Website=20testen=20mit=20Mozilla=201=20und=20Netscape=207=20n=F6tig??=

I came to the conclusion that the ?? in the end was not correct (the first
should have been encoded). Fine, so I wrote an answer and was surprised that it
remained there literally (I added something in front, but nevermind). So I tried
to paste the above string into a subject of a fresh message, but removed the
bogus ?. So it became a correct MIME word. But now something interesting
happened. Mozilla again let the subject as is. When receiving this new message
it was hence decoded. But this is certainly different from what I wrote into the
subject field (namely a MIME word).

pi
Product: MailNews → Core
Severity: normal → minor
OS: Linux → All
Hardware: PC → All
Summary: MIME words in header fields not encoded → Literal MIME word entered into header fields not encoded
Product: Core → MailNews Core
QA Contact: marina → i18n
Assignee: nhottanscp → nobody
Whiteboard: intl
You need to log in before you can comment on or make changes to this bug.