Closed
Bug 226387
Opened 22 years ago
Closed 15 years ago
automatically created anchor name for a header in Chinese doesn't work
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: speedogoo, Unassigned)
Details
(Keywords: helpwanted)
Attachments
(4 files)
The anchor name value as typed in Chinese in Big5 in Composer
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.5) Gecko/20031007
Mozilla composer has a really fantastic feature that when you want to create a
link, the dialog box can show a list of existing headers (those h1,h2 things).
if you choose one, Composer will automatically create an anchor at that header
and make the link to this anchor. THE PROBLEM IS: if the header is Chinese, then
the anchor name will be created in Chinese also, BUT, the href of the link is
url-encoded like '%DD%EE%CC' things. so, clicking the link will not go to the
anchor.
Reproducible: Always
Steps to Reproduce:
1. Start Composer
2. Write a Header in Chinese
3. Write some other words
4. select the "other words" and click link tool button
5. open the drop list and choose the header name, Press OK
Actual Results:
1. View source now
2. you see an anchor with a Chinese name is placed before the header with a
Chinese name same as the header words
3. you can also see the "other words" is surround by a link whose href is some
magical words
Expected Results:
the anchor name and the link href should match, no matter what language
(although it's better to be formal url-encoded string)
i must say this is a blocker, because it make this great great great feature
completely useless. i simply use all English header now, but if the document is
written for other people, i can only cry and do all these things manually.
|
||
Updated•22 years ago
|
Severity: blocker → normal
|
||
Comment 1•22 years ago
|
||
> BUT, the href of the link is url-encoded like '%DD%EE%CC' things. so, clicking
> the link will not go to the anchor.
We should be unescaping the href of the link before doing the name lookup (and
in fact, we do, when I look at the docshell code).
Further, your steps work for me IF I change the encoding of the composer
document from ISO-8859-1 to an encoding that can actually handle the language
I'm using (I tested Russian, not Chinese). Are you putting Chinese text into an
ISO-8859-1 document and expecting things to be happy?
|
||
Comment 3•21 years ago
|
||
|
|
||
Comment 4•21 years ago
|
||
|
|
||
Comment 5•21 years ago
|
||
|
|
||
Comment 6•21 years ago
|
||
Load this page and File/Edit Page...Ctrl+E ; in Composer try to set the href
value of the link to the name of the anchor; verify that this is the case in
Composer's <HTML> Source editing mode; then click the Browse button
(File/Browse Page) and try the link.
Expected results: href value should be anchor's name value and the page should
reach the anchor.
|
|
||
Comment 7•21 years ago
|
||
Mozilla 1.8a5 build 2004100504 under XP Pro SP2 here.
CONFIRMING
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
|
||
Comment 8•21 years ago
|
||
I must add that sometimes clicking the link "goes to" the anchor: somehow, it
depends on the anchor's [chinese] name. So, this bug may not be reproducible all
the time. <argh>
Having someone fluent in Chinese would help here as I could create a genuine,
realistic testcase: e.g. an anchor saying #Top (in Chinese) or #SectionA (in
Chinese) or some other typical real webpage example.
I'm seeking/surfing Chinese Big5 pages for this.
I've asked (via email) help to this site:
Tools to write Chinese web pages
http://www.ust.hk/itsc/webguide/reference/chinese-web.html
Keywords: helpwanted
|
||
Updated•21 years ago
|
Product: Browser → Seamonkey
|
||
Updated•17 years ago
|
Assignee: composer → nobody
QA Contact: composer
|
|
||
Comment 9•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
|
|
||
Comment 10•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•