Closed Bug 300781 Opened 19 years ago Closed 19 years ago

[website] In Camino Start Page, search cannot be done with non-english.

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sugar.waffle, Assigned: moz)

References

(
URL
)

Details

Reproducible: Always

Steps to Reproduce:
1. Open URL(Camino start page).
2. Non-english is input to the search text field in the page. 
   (eg. Input Japanese)
3. Push Enter key or search button.

Actual Results:
search cannot be done with non-english. 

Expected Results:  
search can be done with non-english. 

Mac OS X 10.3.9
2005071422 (v0.9a2)
the page is using the latin1 encoding, nothing to do with camino.
Assignee: pinkerton → bugzilla
Summary: In Camino Start Page, search cannot be done with non-english. → In Camino Start Page, search cannot be done with non-english.
Summary: In Camino Start Page, search cannot be done with non-english. → [website] In Camino Start Page, search cannot be done with non-english.
Ew, the page has an XML declaration that it's UTF-8 and an HTML charset of 8859-1:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Welcome to Camino!</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

The search field also explicitly specifies 8859-1:

<input type="hidden" name="ie" value="ISO-8859-1">
<input type="hidden" name="oe" value="ISO-8859-1">

Those should probably be UTF-8 like the toolbar search string.

All of that said, I *can* type some Arabic in that field and get results;
they're just incomprehensibly formatted because the results page is, I assume,
8859-1, too (it has no encoding).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Any encoding on the results page is Google's doing. We can fix the encoding on
the main page, but not on the results page(s).
You actually can, try those hidden inputs:
<input name="ie" value="utf-8">
<input name="oe" value="utf-8">

..and change the page encoding.
Assignee: bugzilla → mozilla
Taking.
Status: NEW → ASSIGNED
Fixed. I also removed the <?xml ?> declaration, as our doctype says HTML 4.01
(though it's a bad doctype).

The page really needs to be cleaned up a bit more, but that's out of the scope
of this bug.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
VERIFIED.
Thanks for quick work. ;-)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.