Closed Bug 279226 Opened 20 years ago Closed 20 years ago

message threads and german prefixes like "Aw:" instead of "Re:"

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 29179

People

(Reporter: zupi, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Hi, i'm a great fan of Thunderbird but i don't get happy with the threaded message view in the main window. You know, the feature that all messages with same subject are displayed threaded like in some discussion boards (don't know how to explain it in English). Thunderbird recognizes that "Re: My Subject" or "Fwd: My Subject" belong to "My Subject" ... but in Germany, we have some email clients (screw them!) that add prefixes like "Aw:" or even "Antwort:" (german word for "answer") which Thunderbird does not recognize to belong to the same topic. If you don't want to build this in for all localizations, maybe a preference would be nice where everyone can define prefixes for "belonging together" messages. Maybe there even is such a preference I don't know about? Greets from Germany! Reproducible: Always Steps to Reproduce:
similiar (treat AW: as Re:): read the following thread (in German): http://www.heise.de/newsticker/foren/go.shtml?read=1&msg_id=7206106&forum_id=71999 and see bug 213004 But this is not really what you want (to use Aw:).
Thats not what i've meant. But a reference therein points to bug 108163, which seems to be quite the same as mine. Sorry for this DUP, I did't have luck with my search terms.
This is a dupe of bug 29179 - its a problem in our core MailNews code, rather than Thunderbird in particular. *** This bug has been marked as a duplicate of 29179 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.