298485 - Mail contents is mangled - Doesn't match source view

Status: RESOLVED DUPLICATE of bug 141983

(Thunderbird :: General, defect)

Description

[Christian 'CeeJay' Jensen]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

When I post ascii-art to newsgroups using Thunderbird , it looks just fine 
when I post it. 
When I view it later in the group it still looks fine .. however other people 
see it differently .. like it's been garbled .. and it looks this way in the 
messagesource too .. and also when I try viewing it with Google Groups. 


Reproducible: Always

Steps to Reproduce:
1. Post ascii-art (or any thing with a very specific layout)
2. View the post in the newsgroup
3. View the post with source view or with another newsreader

Actual Results:  
The output contains extra blank spaces that were not in the message written

Expected Results:  
I expected the posting to look exactly as I typed (and/or copy/pasted) it.
The displayed output , the displayed input and the message source should all 
be indentical (except for the headers in the source)

The bug is not limited to newsposting only .. the exact same thing happens 
with mail.

Since this garbles my postings ( some of which I didn't save elsewhere ) , I 
count this as loosing data and I'm marking this bug as critical
It borders on major though , so I understand if it's marked down as such.

Comment 1

[Christian 'CeeJay' Jensen]

If you're not familiar with the structure of a figlet font (.flf file) here is 
how the posting was supposed to look: 
http://ceejay.dk/ascii/swan.flf

Comment 2

[Mike Cowperthwaite]

Broken ASCII art does not qualify as dataloss.  This is not a critical problem.
Your comment in the dupe that this is related is correct -- which is why I'm 
duping it.  Since you've presumably already read the discussion there, you're 
aware of the workaround.

*** This bug has been marked as a duplicate of 114954 ***

Comment 3

[Mike Cowperthwaite]

Duped to the wrong bug, my mistake.

Don't bother commenting in the dupe, or in the bug this was just unduped from, 
again -- neither is going to be "fixed," because the behavior is as designed.
See attachment 134270 [details].

*** This bug has been marked as a duplicate of 141983 ***