Closed Bug 979857 Opened 11 years ago Closed 8 years ago

Adding characters like right-arrow or right-single-quotation-mark to plaint-text email when default charset=ISO-8859-1 causes all leading spaces to be removed

Categories

(Thunderbird :: Message Compose Window, defect)

24 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: rudametkin, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36 Steps to reproduce: Send a plain-text email with default charset=ISO-8859-1 format=flowed, leading spaces and a single 'weird' character. EXAMPLE: 10 leading spaces then a ’ character (right-single-quotation-mark) Actual results: Email is converted to charset=WINDOWS=1252 (or UTF-8 if → arrow is used). All leading spaces are removed throughout the email. RESULT: 10 leading spaces then a ’ character (right-single-quotation-mark) Expected results: Leading spaces should be preserved when converting email to WINDOWS=1252 or UTF-8. EXPECTED: 10 leading spaces then a ’ character (right-single-quotation-mark)
A workaround for this issue is to set email to UTF-8 (Edit→Preferences→Display→Advanced), thus avoiding any conversions that cause leading whitespace to be lost. I wrote a longer version of this issue here: http://rudametw.github.io/blog/posts/2014.03.05/Thunderbird-leading-spaces-bug.html Walter Rudametkin
Can you reproduce this in version 45?
Component: Untriaged → Message Compose Window
Flags: needinfo?(rudametkin)
Hi, It took me a bit to find a non UTF-8 email, seems all of my contacts are now using UTF-8. So I tested autoconverting a couple of emails in us-ascii and ISO-8859-1 to Windows-1252 and UTF-8 and it works fine now. I still use flowed text, which has a couple of other issues, but in this case leading spaces are properly kept. IMHO you can close this bug. Regards, Walter
Thanks for the update
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(rudametkin)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.