Open
Bug 305745
Opened 19 years ago
Updated 12 years ago
composer makes non-ascii link is garbage
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: baffclan, Unassigned)
Details
(Keywords: intl)
Attachments
(1 file)
|
1003 bytes,
text/html; charset=iso-2022-jp
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050822 SeaMonkey/1.0a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050822 SeaMonkey/1.0a composer makes non-ascii link is garbage Reproducible: Always Steps to Reproduce: 1. make a New composer page, charset is iso-2022-jp 2. make a link with japanese kanji Actual Results: japanese kanji encoding by iso-2022-jp. Expected Results: japanese kanji encoding by utf-8.
composer make a "2. kanji encoding by iso-2022-jp." 2. kanji encoding by iso-2022-jp in a element. <a href="mailto:example@example.jp?Subject=%1B%24B4A%3Bz%24N7oL%3E">mail</a> click a mail link, open Thunderbird, Subject is garbage. If encoding by utf-8, does not become garbage. 3. kanji encoding by utf-8 in a element. <a href="mailto:example@example.jp?Subject=%E6%BC%A2%E5%AD%97%E3%81%AE%E4%BB%B6%E5%90%8D">mail</a>
|
||
Comment 2•19 years ago
|
||
This is likely to be a dupe. For now, I'm taking it.
Assignee: composer → jshin1987
|
||
Comment 3•19 years ago
|
||
Should we hook at JS code? If so, I think that we need to change here. http://lxr.mozilla.org/mozilla/source/editor/ui/dialogs/content/EdLinkProps.js#317 317 function onAccept() But I think that we may have same issue somewhere. Are there some better idea? And I think that if we support URL encoding for editing, we should support URL decoding at loading this dialog.
|
|
||
Comment 4•19 years ago
|
||
Maybe, this is important and difficult problem. Should we always escape the non-ASCII characters to UTF-8 on CGI params? (i.e., after '?'.)
|
|
||
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attachment #193684 -
Attachment mime type: text/html → text/html; charset=iso-2022-jp
|
||
Comment 5•16 years ago
|
||
Can you reproduce with current SeaMonkey v2.0a1pre ?
Assignee: jshin1987 → nobody
QA Contact: composer
Version: unspecified → Trunk
(In reply to comment #5) > Can you reproduce with current SeaMonkey v2.0a1pre ? yes, reproduce with latest-trunk. Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9pre) Gecko/2008061102 SeaMonkey/2.0a1pre
Still reproducible User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 Build identifier: 20120712003002
You need to log in
before you can comment on or make changes to this bug.
Description
•