265579 - when searching for a word with a german umlaut with the toolbar search field, the umlaut is replaced with '?'

Status: RESOLVED INVALID

(Firefox :: Search, defect)

Description

[matthias]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

If you search for a word with a german umlaut like 'Völker' the 'ö' is replaced
with a question mark '?' and the search engine, for example google, searches for
'V?lker'.

Reproducible: Always
Steps to Reproduce:
1. enter a word with german umlauts in the toolbar search field and choose
google to handle the search.
2. press enter to execute search query
3. google website is shown in the browser window and in its search field every
umlaut in the search term is replaced by a question mark.

Comment 1

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041029
Firefox/1.0RC1

WFM

tried "hören"  -> search result hören and hoeren
tried "tränen" -> search result tränen
tried "haüser" -> search result haüser
tried "übel"   -> search result uebel and übel

Comment 2

[matthias]

It occurs only with the search engine "Google Switzerland". With the default
Google search engine (google.com) everything is fine. maybe its a bug of the
search engine.

Comment 3

[OstGote!]

*** Bug 268986 has been marked as a duplicate of this bug. ***

Comment 4

[OstGote!]

Related is Bug 251331. Google.de seems also to be affected. It works with my
en-US FF build, which uses http://www.google.com/search?lr=&ie=UTF-8&oe=UTF-8&q=
as search url. Please look with about:config for the value of the pref
browser.search.defaulturl if it is set to Google. Perhaps localized builds like
de-DE have a wrong search URL.

Comment 5

[Nickolay_Ponomarev]

confirming per dupes.

Comment 6

[matthias]

there is a bug entry for this in the buglist of mozdev.org/mycroft #7114
(http://mozdev.org/bugs/show_bug.cgi?id=7114). there is also a solution to fix
this bug.

Comment 7

[Siegfried Wessler]

(In reply to comment #2)
> It occurs only with the search engine "Google Switzerland". 

It also happens using Wikipedia.de.

Comment 8

[OstGote!]

*** Bug 272819 has been marked as a duplicate of this bug. ***

Comment 9

[Phil Ringnalda (:philor)]

This is not the result of a bug in Firefox or Seamonkey, but a bug in the search
plugins: to work with anything but ASCII, the search plugin needs to have a
queryCharset attribute on the search element that says what charset the search
engine uses, and for things like Google or Yahoo that can take input in more
than one encoding, also needs to have an input element that specifies the same
charset. For example, the googleCH.src that started this bug should have

<SEARCH
   version = "7.1" 
   name="Google - Switzerland"
   description="Google Search for sites in Switzerland"
   method="GET"
   action="http://www.google.ch/search"    
   queryCharset="utf-8"     
>
<input name="ie" value="utf-8">
<input name="oe" value="utf-8">

For search plugins other than the ones that ship with Firefox, or with a Mozilla
localized build, you need to file a bug in http://mycroft.mozdev.org/bugs.html
(if there isn't one already for your plugin: they are way behind) - since those
are maintained as a separate project, not part of mozilla.org, there's nothing
we can do about them here. For a search plugin that's distributed as a part of a
localized build or language pack, you need to file a bug on that particular
localization in the Mozilla Localizations product.

So, resolutions: this bug, on the Google Switzerland plugin (and also the
mentioned Wikipedia-DE) is invalid, since it's the Mycroft folks that need to
fix them. Dup'd bug 272819 would be a valid bug on the de-AT localization,
except it was on the 1.7.3 build, and the current builds appear to have fixed
search plugins (at least, the langpack does, while the 1.7.3 langpack had a
working plugin for google.at and broken ones for google.ch and google.de). bug
268986 I'm not sure about: the plugin that's in CVS for the de-DE Firefox 1.0
build ought to work, while the one on mozdev ought not to, so I assume it wasn't
the included one that was the problem.

Comment 10

[:Gavin Sharp [email: [e-mail]]]

*** Bug 301038 has been marked as a duplicate of this bug. ***