Open
Bug 62409
Opened 24 years ago
Updated 17 years ago
Local Charsets are not supported in SearchPlugins
Categories
(SeaMonkey :: Search, enhancement)
Tracking
(Not tracked)
NEW
People
(Reporter: indeyets, Unassigned)
References
Details
(Keywords: helpwanted)
Attachments
(1 file)
726 bytes,
application/octet-stream
|
Details |
Whenever some search-engine returns not-ISO characters (Cyrillic windows-1251 in
my case), "Search-Results" tab in "My Sidebar" converts them into ISO-8859-1.
So, there is not much of use of search-plugins on non-english search-engines.
Possible solution - using the charset defined in browser, or, at least, some way
to specify charset for the search-engine manually.
Comment 1•24 years ago
|
||
You can do this with the attributes:
queryCharset="ISO-8859-1"
charset="ISO-8859-1"
queryCharset is the charset you are sending the query in, and charset is the
charset (i.e. character (en)coding) of the result page (which the page really
should say using HTTP headers).
But this bug isn't fixed, since Mozilla doesn't interpret the charset names
case-insensitively. I have created a search engine plugin, which uses the
following charsets:
queryCharset="iso-8859-1"
charset="iso-8859-1"
When I do the search (Mozilla 0.6), the query is performed in UTF-8, and not in
iso-8859-1. If I change the charsets to uppercase, everything works OK.
Comment 2•24 years ago
|
||
Marking NEW so someone will look at it. I am also seeing this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Local Charsets are not supported in SearchPlugins → [RFE] Local Charsets are not supported in SearchPlugins
Comment 3•23 years ago
|
||
-->future
Assignee: matt → sgehani
Severity: normal → enhancement
Keywords: helpwanted
Target Milestone: --- → Future
For Google search plugin, I have customized one which enables searching in
languages supported in UTF8(must be supported by Google).
am not sure its code is ought to be or not though.
Google search plugin will be updated to support Unicode.
( bug 145375 )
Comment 7•22 years ago
|
||
*** Bug 170382 has been marked as a duplicate of this bug. ***
Comment 8•22 years ago
|
||
*** Bug 157225 has been marked as a duplicate of this bug. ***
Comment 9•22 years ago
|
||
*** Bug 154773 has been marked as a duplicate of this bug. ***
Updated•22 years ago
|
Summary: [RFE] Local Charsets are not supported in SearchPlugins → Local Charsets are not supported in SearchPlugins
Comment 10•22 years ago
|
||
See also bug 174027 and comments therein. Search tab should use the charset
returned/used by the search engine.
Comment 11•19 years ago
|
||
(In reply to comment #1)
>
> But this bug isn't fixed, since Mozilla doesn't interpret the charset names
> case-insensitively. I have created a search engine plugin, which uses the
> following charsets:
>
> queryCharset="iso-8859-1"
> charset="iso-8859-1"
This must have been fixed a long time ago. Do you still see this problem?
Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
Updated•17 years ago
|
Assignee: samir_bugzilla → nobody
Priority: P3 → --
QA Contact: claudius → search
Target Milestone: Future → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•