fangjf Reporter
	Description • 19 years ago

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)
Build Identifier: 

when searching for bugs,type chinese keywords and search...->no bugs found

in fact even in there are also problems in bugzilla of Bugzilla

when use https://bugzilla.mozilla.org/query.cgi?format=specific and type "中文" 
in "words" and found nothing.  While when
use https://bugzilla.mozilla.org/query.cgi?format=advanced and type "中文" 
in "summary" and search----->bug 220066 found

as for myself ,when search in chinese, both search found nothing.
so strange!(btw, i can see the chinese from IE correctly)


Reproducible: Always

Steps to Reproduce:
1.see the detail above
2.
3.

	fangjf Reporter
	Comment 1 • 19 years ago

the strange words in the Description :"ÖÐÎÄ" should  be a valid chinese 
character

	Marc Schumann [:Wurblzap]
	Comment 2 • 19 years ago

I think this is either a duplicate of bug 126266, or it should be moved to the
Bugzilla component in the mozilla.org product...

	Marc Schumann [:Wurblzap]
	Comment 3 • 19 years ago

See also bug 311356.

The reason is that the character set encodings of the bug entry form, the query
forms and what's in the database may all differ between each other. An older bug
creation may have put "中文" into the database, gb2312-encoded (for example --
for a long time, it was the browser's choice). When you type "中文" while
creating a newer bug, the character set encoding will be UTF-8. So the same text
*typed* is represented differently in the database!
It gets worse when adding new comments to an older bug, or new comments to a
newer bug. Again, character set encodings may be different.

Now, when searching for "中文", Bugzilla will try to find it in the encoding as
used on the search form. This may or may not be the same encoding as used when
creating the bug or adding a comment to it. So you may or may not find the bug
you're looking for :(

So this might go away with bug 304149 and/or bug 280633, I think... At any rate,
the current database contents need to be converted to UTF-8 for searches to work
correctly.

Duping to bug 280633 because it is most likely to be the bug which will help you.

*** This bug has been marked as a duplicate of 280633 ***