Closed Bug 128634 Opened 22 years ago Closed 21 years ago

"Find in History" doesn't work with non-ascii characters

Categories

(Core Graveyard :: History: Global, defect, P4)

Product:
Core Graveyard
Component:
History: Global
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 206775
Milestone:
Future

People

(Reporter: kazhik, Assigned: bugzilla)

References

Details

(Keywords: intl) 

"Find in History" in History window doesn't work with
Japanese characters. Search result window is empty.
Target Milestone: --- → Future
Blocks: 157673
Keywords: intl
I can reproduce with 11/14 windows and linux trunk build.
Keywords: nsbeta1
assigned p4 priority - don't think many people know about this feature in the
first place.
Priority: -- → P4
Nav triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
*** Bug 142169 has been marked as a duplicate of this bug. ***
i18n triage team: nsbeta1-
Does not work on Win2K (2003021408) as well when trying to search with cyrillic
characters.

OS->All ?
Japanese -> to some more general description ?
Yes, this happens on all non-ascii characters - change summary.
OS: Linux → All
Hardware: PC → All
Summary: "Find in History" doesn't work with Japanese characters → "Find in History" doesn't work with non-ascii characters
*** Bug 200770 has been marked as a duplicate of this bug. ***
This bug affects Phoenix as well (with Hebrew). Very annoying.
From comment #2:
>assigned p4 priority - don't think many people know about 
>this feature in the first place

This feature is hightly visible in Phoenix's History sidebar (which is the only
way to access history in Phoenix). Should we bump this up a little?


I can search Japanese keyword by "Find in History" 
on recent Linux build.
Does anyone still reproduce?

*** This bug has been marked as a duplicate of 206775 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Verified dupe.  This was fixed on June 10.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.