Closed Bug 40199 Opened 25 years ago Closed 25 years ago

Search files need to default to "ISO-8859-1", not "UTF-8"

Categories

(SeaMonkey :: Search, defect, P1)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

Details

(Whiteboard: [NEED INFO])

Attachments

(1 file)

Search files need to default to "ISO-8859-1", not "UTF-8". This is extremely important for when a search file doesn't specify its encoding.
Marking nsbeta2... looking for approval to check in.
Status: NEW → ASSIGNED
Keywords: nsbeta2
Priority: P3 → P1
Target Milestone: --- → M16
Target Milestone: M16 → M17
What is the use visible affect here?
Whiteboard: [NEED INFO]
The "visible effect" is that many Sherlock files (for non-Latin-1 web sites) from the net won't work correctly. This is a trivial fix... merely a string change.
Chris (Waterson), I've attached a proposed diff... care to give me a quick review?
Looks good. Use NS_ConvertASCIItoUCS2()... r=waterson
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
marking VERIFIED
Status: RESOLVED → VERIFIED
Since the default is changed to ISO-8859-1, NetCenter search file should specify charset as UTF-8, otherwise non Latin1 (e.g. Japanese) search will not work.
Netcenter is working on switching over internally to UTF-8... once they are done, the appropriate files can/will be changed over. :^)
Has this regressed? bug 35076 DE:PR1 "Ticket OnlineEvents" search extended char. problem claims it is still failing with a 6/9 build.
I believe this is fixed. Can we close?
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: