Open
Bug 44246
Opened 24 years ago
Updated 2 years ago
Underscore is removed from the subject field when being a part of non-ascii string
Categories
(MailNews Core :: Internationalization, defect, P3)
Tracking
(Not tracked)
NEW
Future
People
(Reporter: marina, Unassigned)
Details
(Whiteboard: intl)
**** observed with 2000-06-29 M17 build **** Steps to reproduce: -compose two messages :first with "le_sujet" in the Subject field and another one with "lé_süjet" iin the Subject field; - send both messages and note: //the one with ascii and underscore is OK, the other one where underscore is surrounded by non-ascii chars is stripped from underscore, it's gone (unable to look at the source because of bug# 44244
Comment 1•24 years ago
|
||
Actually the underscore is there in the source but is QP-encoded and apparently we are not able to show that in the headers only.
Comment 2•24 years ago
|
||
Looks like an inherited problem from 4.x. I can reproduce this by send/receive by using 4.x.
Status: NEW → ASSIGNED
Comment 3•24 years ago
|
||
I'm wondering if we are able to deal with any QP-encoded data bewlow 0x80 in the headers-- it is true we have the same problem in 4.x. 2 things to fix. 1. We should not encode these characters using QP. 2. We should be able to show them if they are there.
Updated•24 years ago
|
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
Mass change to bugs filed by marina --> QA contact to marina. thanks!
QA Contact: momoi → marina
Comment 5•23 years ago
|
||
worksforme on today's build (i'm on linux, but i don't think this is relevant here) - ciryllic subject "
Comment 7•23 years ago
|
||
Oops, please forget my prev comment, I misread some lines of code... :-(
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•15 years ago
|
QA Contact: marina → i18n
Updated•11 years ago
|
Assignee: nhottanscp → nobody
Status: ASSIGNED → NEW
Whiteboard: intl
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•