448139 - A line break is inserted in the middle of a Hangul word followed by a long HTML tag

Status: RESOLVED DUPLICATE of bug 653342

(Thunderbird :: Message Compose Window, defect)

Description

[Seungbeom Kim]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: version 2.0.0.16 (20080708)

When you're composing an HTML message and a Hangul word appears as the text of a link whose target address is long, Thunderbird breaks the Hangul word as an effort to avoid the HTML source line getting too long. However, Hangul words (and I believe it's the same with Chinese or Hiragana/Katakana words) should not be broken just because it's at the end of an HTML source line, though they can be broken when *displayed* at the end of a line.

For example:

<a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird&format=guided">안녕하세요</a>

Here, the word "안녕하세요" should not be broken. However, Thunderbird inserts a line break after the first character "안", so the word appears as "안 녕하세요" when displayed. This is a very serious problem in composing Korean messages in HTML.

The problem is worse because you don't notice this happening in your composition window, until you save it as a draft or send it to someone and choose the saved/sent message to retrieve it.

Reproducible: Always

Steps to Reproduce:
1. Open a HTML message composition window (If your default is plain text, hold Shift while clicking Write), and set the character encoding to Korean (EUC-KR) or Unicode (UTF-8).
2. Press Ctrl+L, enter a single Korean word such as "안녕하세요" (without quotes) for the text, and a long address such as https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird&format=guided for the location.
3. Save the message as a draft.
4. Go to the Drafts folder and retrieve the message you just saved.
Actual Results:  
The text appears as "안 녕하세요".

Expected Results:  
The text should appear as "안녕하세요" without any white space in the middle of the word.

Comment 1

[Magnus Melin [:mkmelin]]

Tried with a 3.0 alpha build?

Comment 2

[Wayne Mery (:wsmwk)]

do you see this in version 3?

Comment 3

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.

Comment 4

[Seungbeom Kim]

Sorry, somehow I didn't get the notifications... :(

I tried the same thing with Thunderbird 10.0.2, and the problem persists.

Since the lack of response was why this was marked RESOLVED INCOMPLETE, with this more info it can be marked UNCONFIRMED again, I guess.

By the way, are the steps to reproduce this bug vague or hard to follow for others? Let me know if they can be improved.

Comment 5

[Wayne Mery (:wsmwk)]

wada, are you able to comment on this or suggest someone who can?

Comment 6

[WADA:World Anti-bad-Duping Agency]

Perhaps a phenomenon of bug 653342(see bug 653342 comment #14).

Comment 7

[Seungbeom Kim]

Bug 653342 looks like the same problem, indeed.