Closed Bug 33692 Opened 24 years ago Closed 24 years ago

Netcenter search pages are supposedly UTF-8 encoded, but are sending back bad data

Categories

(SeaMonkey :: Search, defect, P2)

Product:
SeaMonkey
Component:
Search
Type:
defect

Tracking

(Not tracked)

Status:
CLOSED FIXED

People

(Reporter: mozilla, Assigned: jlinley)

References

(
URL
)

Details

(Whiteboard: [nsbeta2+]) 

In Mozilla, if you search Netcenter (see exact full URL above) for "Jennifer 
Lopez", you'll notice that the list of results in the sidebar is incorrect. (We 
only display five results.)

Look carefully at the third "Web Site Category" item. Its "Lopez, Jennifer - 
found in: World>Espanol>...". Notice how the "ñ" in "Español" is an n-umlaut.

If you look at the HTML source, you'll find:

<LI><a 
href="http://directory.netscape.com/World/Español/Artes/Cine/Actrices_y_Actores/
L/Lopez,_Jennifer">

but the n-umlaut isn't UTF-8 encoded.

We either need all Netcenter search data to be properly UTF-8 encoded, or if 
they are using some other encoding, the associated encoding numbers needs to be 
described in all of our Netcenter Sherlock files.

Without this being fixed, Netcenter search results with improperly encoding data 
will cause problems with Mozilla's search sidebar panel.

John, can you work on this with Netcenter folks?  Thanks.
Quick typo fix:

Look carefully at the third "Web Site Category" item. Its "Lopez, Jennifer - 
found in: World>Español>...". Notice how the "ñ" in "Español" is an n-umlaut.
As another example of something being bad with Netcenter search results on 
"Jennifer Lopez" when using Mozilla, do the search using the URL given for this 
bug, then select the menu:
    "View->Character Encoding->Multibyte->Unicode (UTF-8)"

You'll notice how the page contents stop on the third "Web Site Category" 
item... i.e. the line with the n-umlaut that is improperly encoded.
Same exact encoding problem when searching for "Netcenter".


John, any luck with the Netcenter folks at fixing this encoding problem?
Jared, can you fix this encoding problem?
Assignee: johng → jlinley
Priority: P3 → P2
Target Milestone: --- → M15
How come this is still M15? M15 is already out!
Any new status on this bug?
Target Milestone: M15 → M16
We are in the process of UTF-8 encoding our data and templates. I'll update this 
bug with an ETR asap.
Status: NEW → ASSIGNED
Our new ETR for this bug is 6/1, however we have a dependency on the 
installation of NES 4.1. Barring problems with NES we should have UTF-8 encoding 
across Netscape Search by 6/1.

*** This bug has been marked as a duplicate of 26260 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
My mistake, this is not a duplicate #35630 and #26260 are duplicates
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
nominating nsbeta2
Keywords: nsbeta2
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
Adding netcenter keyword.
Keywords: netcenter
The URL only works if Español is entered as Espa%c3%b1ol. This bug exists in 
older browsers as well, so it is not an issue with NS6.
This bug is fixed with the UTF-8 encoded data and NPE plugin.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Closing.
Status: RESOLVED → CLOSED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.