Closed
Bug 149546
Opened 23 years ago
Closed 16 years ago
wrong comment for charset parameter in nsIMsgHeaderParser.idl
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: KaiE, Unassigned)
Details
dmose believes the comment in nsIMsgHeaderParser.idl, saying that default
charset is us-ascii when no charset is specified, is wrong. He believes the
default is UTF8.
If that is true, the comment should get changed.
The implementation seems to ignore the charset parameter at all, but seems to
walk over the string by detecting UTF8 chars.
Updated•23 years ago
|
QA Contact: gayatri → stephend
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Assignee: mscott → nobody
QA Contact: stephend → backend
Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
Comment 1•16 years ago
|
||
Charset arguments in nsIMsgHeaderParser.idl are a thing of the past now.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•