Closed
Bug 335878
Opened 19 years ago
Closed 19 years ago
non-ascii search engine names are not correctly displayed
Categories
(Firefox :: Search, defect, P1)
Tracking
()
RESOLVED
FIXED
Firefox 2 alpha3
People
(Reporter: sugar.waffle, Assigned: Gavin)
References
()
Details
(Keywords: fixed1.8.1)
Attachments
(5 files, 1 obsolete file)
17.91 KB,
image/png
|
Details | |
23.99 KB,
image/png
|
Details | |
1.14 KB,
application/octet-stream
|
Details | |
24.30 KB,
patch
|
mconnor
:
review+
mconnor
:
approval-branch-1.8.1+
|
Details | Diff | Splinter Review |
14.98 KB,
image/png
|
Details |
A Japanese original report is http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=5136
Reproducible: Always
Steps to Reproduce:
1. Open URL.
2. Install search engin of "産経新聞 記事検索".
(The link is "javascript:addEngine. ('sankei','png','Search')")
3. See Search Engin pulldown menu and Search Engin Manager.
Windows NT, Mac OS X 10.3.9
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060428 Minefield/3.0a1
Assignee | ||
Comment 3•19 years ago
|
||
Which character encoding are the files in? This worked correctly using the old search service (Firefox 1.5)?
Assignee | ||
Updated•19 years ago
|
Summary: Search engin name of non-ascii is not correctly displayed. → non-ascii search engine names are not correctly displayed
Version: Trunk → 2.0 Branch
In Firefox1.5.0.2 release, there is no problem.
The character code of tried Search Engin is Shif-JIS.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; ja-JP-mac; rv:1.8.0.2) Gecko/20060328 Firefox/1.5.0.2
Assignee | ||
Comment 6•19 years ago
|
||
Do searches using non-ascii characters work correctly?
Comment 7•19 years ago
|
||
The character encoding for the .src file itself is supposed to come from sourceTextEncoding, an int in the set in MapScriptCodeToCharsetName(). And http://r09.org/sh/engine/sankei.src does indeed have sourceTextEncoding = "1", which says it's in Shift-JIS.
Assignee | ||
Comment 8•19 years ago
|
||
Bah, I shouldn't have missed that.
Assignee: nobody → gavin.sharp
Priority: -- → P1
Target Milestone: --- → Firefox 2 alpha2
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•19 years ago
|
||
I believe this fixes it. If anyone could test this patch out I would very much appreciate it. I'm going to be away for a little bit, I want to check this over again before asking for review.
Reporter | ||
Comment 10•19 years ago
|
||
(In reply to comment #9)
> Created an attachment (id=220276) [edit]
> patch
This patch was tried.
The installation of build and the search engine works normally.
I do not think that there is basically a problem.
Assignee | ||
Comment 11•19 years ago
|
||
Thank you for the testing.
This patch only affects loading of engines done through window.addSearchEngine(), I need to make it work for engines copied to the searchplugins folder manually as well.
Assignee | ||
Comment 12•19 years ago
|
||
Make the sherlock byte translating code common and make both code paths use it. More testing on this would be great. Copying files to the profile and app dir directly and loading files from the web both need to be tested, with as many character sets and sourceTextEncoding combinations as possible.
Attachment #220276 -
Attachment is obsolete: true
Attachment #220823 -
Flags: review?(mconnor)
Assignee | ||
Updated•19 years ago
|
Flags: blocking-firefox2?
Whiteboard: [patch-r?]
Target Milestone: Firefox 2 alpha2 → Firefox 2 alpha3
Assignee | ||
Updated•19 years ago
|
Attachment #220823 -
Flags: approval-branch-1.8.1?(mconnor)
Updated•19 years ago
|
Attachment #220823 -
Flags: review?(mconnor)
Attachment #220823 -
Flags: review+
Attachment #220823 -
Flags: approval-branch-1.8.1?(mconnor)
Attachment #220823 -
Flags: approval-branch-1.8.1+
Assignee | ||
Comment 13•19 years ago
|
||
Checked in on the trunk.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [patch-r?]
Assignee | ||
Updated•19 years ago
|
Whiteboard: [checkin needed (1.8 branch)]
Reporter | ||
Comment 14•19 years ago
|
||
I tried tinderbox-builds.
And commnet#0 doesn't have the problem.
But the problem still reproduced by following search plugin...
(These plug-ins do not have the problem before either. )
http://guide.search.goo.ne.jp/apply/firefox/install.php
javascript:add_goo('11goo_eiwa', 'gif', 'goo%E8%BE%9E%E6%9B%B8(%E8%8B%B1%E5%92%8C)','11goo_eiwa');
javascript:add_goo('12goo_waei', 'gif', 'goo%E8%BE%9E%E6%9B%B8(%E5%92%8C%E8%8B%B1)','12goo_waei');
javascript:add_goo('13goo_kokugo_shingo', 'gif', 'goo%E8%BE%9E%E6%9B%B8(%E5%9B%BD%E8%AA%9E)','13goo_kokugo_shingo');
Windows XP SP1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060516 Minefield/3.0a1
Reporter | ||
Comment 15•19 years ago
|
||
The plug-in of commnet#0 is correctly displayed.
But "goo search plugin" is not displayed still correctly.
Assignee | ||
Comment 16•19 years ago
|
||
(In reply to comment #15)
> The plug-in of commnet#0 is correctly displayed.
> But "goo search plugin" is not displayed still correctly.
Thanks a lot for testing this - I filed bug 338252 on this new issue, I will try to fix that as soon as possible.
Assignee | ||
Comment 17•19 years ago
|
||
Checked in on the branch for a3.
mozilla/browser/components/search/nsSearchService.js 1.1.2.20
Keywords: fixed1.8.1
Whiteboard: [checkin needed (1.8 branch)]
Assignee | ||
Updated•19 years ago
|
Flags: blocking-firefox2?
You need to log in
before you can comment on or make changes to this bug.
Description
•