Add a function to nsIMimeConverter which strip out "Re:" from subject header

NEW
Unassigned

Status

MailNews Core
MIME
16 years ago
9 years ago

People

(Reporter: nhottanscp, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Separated from bug 131983.

http://bugzilla.mozilla.org/show_bug.cgi?id=131983#c30

> It is possible to skip "RE:" without encoding the string again. It needs to
> decode MIME encode but without charset conversion then we can search for "RE:",
> remember the positions and copy the rest of the string over. This way, the
> result is always shorter than the original and no modification to the subject
> except for removing "RE:". Probably, we want that functionality in the MIME
> decoder/encoder interface. I think this would be not a small change, so not for
> moz1.0.


http://bugzilla.mozilla.org/show_bug.cgi?id=131983#c32

> NS_MsgStripRE() must return "Hello, world." for the all of following input (it's
> in raw ISO-2022-JP for viewing purpose):
> 
>     Re: Hello, world.
>     \x1b(BRe: Hello, world.
>     \x1b(JRe: Hello, world.
> 
> Although I don't know actual implementation works this way, they are all
> comformance to RFC 1468.
(Reporter)

Comment 1

16 years ago
Reassign to nhott.
Assignee: ducarroz → nhotta
(Reporter)

Updated

16 years ago
Summary: Add a function to nsIMimeConverter.h which strip out "Re:" from subject header → Add a function to nsIMimeConverter which strip out "Re:" from subject header
(Reporter)

Updated

16 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.2alpha

Updated

16 years ago
QA Contact: gayatri → carosendahl

Updated

16 years ago
QA Contact: carosendahl → gayatri
(Reporter)

Updated

16 years ago
Target Milestone: mozilla1.2alpha → Future
QA Contact: gayatri → stephend
Product: MailNews → Core

Updated

10 years ago
Assignee: nhottanscp → nobody
Status: ASSIGNED → NEW
QA Contact: stephend → mime
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core
Target Milestone: Future → ---
You need to log in before you can comment on or make changes to this bug.