CH-S, CH-T, KO: Search results contain corrupted characters

RESOLVED MOVED

Status

P1
normal
RESOLVED MOVED
18 years ago
7 years ago

People

(Reporter: lbaliman, Assigned: chau)

Tracking

({intl})

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(6 attachments)

(Reporter)

Description

18 years ago
Using Netscape 6.01 US and with
Prefs set for the proper language (Appearance/Font)
Using Windows CH-T (1a,b) or CH-T (2a,b) or KO(3a,b)
Search results contain corrupted characters


1a.  Steps to reproduce (CH-T, search string and Enter Key)
*  Launch Netscape.com home page for China, 
http://home.netscape.com/zh/cn/escapes/search/netsearch_0.html
*  Copy first 2 characters from first ODP directory entry
*  Paste these 2 characters into the location bar
*  Press Enter
Netscape Search returns four search results in the browser window.  The search 
results browser window contains upside-down question marks, rather than proper 
Chinese characters.  Sidebar search tab also contains 4 search results


1b.  Steps to reproduce (CH-S, search string and Search Button)
*  Launch Netscape.com home page for China, 
http://home.netscape.com/zh/cn/escapes/search/netsearch_0.html
*  Copy first 2 characters from first ODP directory entry
*  Paste these 2 characters into the location bar
*  Press Search Button
Netscape Search returns NO search results in the brwoser window.  Sidebar search 
tab also contains NO search results

-------------------------------------------------------------------------------
2a.  Steps to reproduce (CH-T, search string and Enter Key)
*  Launch Netscape.com home page for Taiwan, 
http://home.netscape.com/zh/tw/index.html
*  Copy first 2 characters from first ODP directory entry
*  Paste these 2 characters into the location bar
*  Press Enter
Netscape Search returns one search result in the browser window.  The search 
results browser window contains upside-down question marks, rather than proper 
Chinese characters.  Sidebar search tab also contains 1 search result


2b.  Steps to reproduce (CH-T, search string and Search Button)
*  Launch Netscape.com home page for Taiwan, 
http://home.netscape.com/zh/tw/index.html
*  Copy first 2 characters from first ODP directory entry
*  Paste these 2 characters into the location bar
*  Press Search Button
Netscape Search returns NO search results in the browser window.  Sidebar search 
tab also contains NO search results

--------------------------------------------------------------------------
3a.  Steps to reproduce (KO, search string and Enter Key)
*  Launch Netscape.com home page for Korea, 
http://home.netscape.com/ko/index.html
*  Copy first all characters from second ODP directory entry
*  Paste these characters into the location bar
*  Press Enter
Netscape Search returns search results in the browser window.  The search 
results browser window contains upside-down question marks, rather than proper 
Korean characters.  Sidebar search tab also contains search results with 
upside-down question marks.


3b.  Steps to reproduce (KO, search string and Search Button)
*  Launch Netscape.com home page for Korea, 
http://home.netscape.com/ko/index.html
*  Copy all characters from second ODP directory entry
*  Paste these characters into the location bar
*  Press Search Button
Netscape Search returns search results in the browser window, with upside-down 
question marks, rather than proper Korean characters.  Sidebar search tab also 
contains search results with upside-down question marks.
(Reporter)

Comment 1

18 years ago
Created attachment 25971 [details]
CH-S, search string, Enter Key
(Reporter)

Comment 2

18 years ago
Created attachment 25972 [details]
Ch-S, search string, Search Button
(Reporter)

Comment 3

18 years ago
Created attachment 25973 [details]
CH-T, search string, Enter Key
(Reporter)

Comment 4

18 years ago
Created attachment 25974 [details]
CH-T, search string, Search Button
(Reporter)

Comment 5

18 years ago
Created attachment 25975 [details]
KO, search string, Enter Key
(Reporter)

Comment 6

18 years ago
Created attachment 25976 [details]
KO, search string, Search Button
(Reporter)

Comment 7

18 years ago
Set priority = P1, added keywords intl and nsbeta1

Assigned (temporarily) to Nancy Wang.  Nancy, please re-assign

Lynn Webb QA contact
Assignee: matt → nwang
Keywords: intl, nsbeta1
Priority: -- → P1
QA Contact: claudius → lynnw

Comment 8

18 years ago
reporter: do  you have chinese fonts installed?

on windows2000, i added all languages using the regional options control panel, 
and then things usually work for me.  however i don't play w/ IMEs so i don't 
know how to follow your steeps to reproduce
(Reporter)

Comment 9

18 years ago
Yes, Chinese fonts were installed.

Comment 10

18 years ago
This bug is "invalid" because the search URL is not pointing to the localized 
templates. 

1. In order for the keyword server to detect chinese or korean, you need to 
change the language preferences to the chinese or korean languages. Then when 
you enter a word in the URL bar and use the Enter key, you will be taken to the 
appropriate template. 

2. There is no chinese or korean build at the moment, so the URL built into the 
browser for the URL bar search using the search button is still using the US 
template. Google on the US side may not support these languages.

3. No sherlock file has been built for these languages, so sidebar searching 
would not work at this time.

4. If the intention of this bug is to get the US search to work for all 
languages, then the bug is still valid, in which case we need to reassign to the 
appropriate US producer.

Comment 11

18 years ago
By the way, since there is no sherlock file, if you happen to see any sidebar 
results when you use the keyword server, they will be corrupted. I don't think 
you will see any results due to the fact that there is no sherlock file for 
these languages.
(Reporter)

Comment 12

18 years ago
Using Netscape 6.0 US, US Windows, with font and language prefs properly set--
If I place a search string with French or German or Japanese characters in the 
location bar and hit Enter, I get valid search results--no corrupted characters. 
  That is why I expected to get valid search results for the Asian fonts--why 
would the Asian fonts behave differently?
(Assignee)

Comment 13

18 years ago
I am re-assigning to myself for now.

It seems like this problem is like the JA Google template.

I have sent an email to the Dulles team, requesting them to fix the double-bytes 
google templates, like the JA Google team. Once they have assigned an engineer 
to the project, I will re-assign this bug to him.

BTW- Linda when you press Enter, please set the Language preference to the 
countries you are interested in.  Go to Preferences.  Under Navigator, select 
language and select the countries you are interested in.  The keyword use the 
language preference to know what search template they will redirect the search 
query to go to.

Reproduce the first case (1a)
-Change my language preference to zh-cn.  Move it up to the top of the list.
-Copy first 2 characters from first ODP directory entry
-Paste these 2 characters into the location bar
-Press Enter
-I go to the Chinese (zh-cn) google template.  No gibberish

I have worked with the Dulles engineering team to make the keyword search to go 
directly to the google template for zh-cn and zh-tw.  The reason for this is  
because most of the time, the search will fall-through to Google template 
anymore, due to the fact that the ODP websites for double-bytes are not 
impressive.

Please test 1a and 2a again and see the search results.

Thanks!


(Assignee)

Comment 14

18 years ago
Linda, 

You are using the US browser, thus the Search button will always point to the US 
Search page.  There are FONT FACE tags in the US Search page that will display 
the double-bytes characters in gibberish.

Thus, you are seeing the corrupted characters.

-C
(Reporter)

Comment 15

18 years ago
Using US Nscp 6.0 build, Windows NT for CH-T or CH-S

1aa.  Chinese Traditional, Big Five, Enter Key
Results:  Many OK search results in browser window;  Sidebar stays closed
1aaa. Chinese Traditional, EUC-TW, Enter Key
Results:  Many OK search results in browser window;  Sidebar stays closed

1bb.  Chinese Traditional, Big Five, Search Button (Font Tag problem)
Results:  Garbled "no results" in browser window;  Sidebar open but empty 
1bbb.  Chinese Traditional, Big Five, Search Button (Font Tag problem)
Results:  Garbled "No results" in browser window;  Sidebar open but empty

2aa.  Chinese Simplified, GB2312, Enter Key
Results:  Little bit garbled search results in browser window;  Sidebar closed
2aaa.  Chinese Simplified, GBK, Enter Key
Results:  Little bit garbled search results in browser window;  Sidebar closed

2bb.  Chinese Simplified, GB 2312, Search Button (Font Tag problem)
Results:  Garbled results in browser window;  Sidebar open with results
2bbb.  Chinese Simplified, GBK, Search Button (Font Tag problem)
Results:  Garbled results in browser window and 1 of 2 chars is lost in search 
string;  Sidebar open with results

Summary, Chinese Characters
*  Searching with Enter Key, we get good results in browser window, but Sidebar 
stays closed.  Once we have a true Chinese build, this problem should go away.
*  Searching with Search Button, we get garbled results in browser window, and 
Sidebar opens (but might be empty.  This is the Font Tag problem that Chau has 
asked Dulles to work on.
Assignee: nwang → chau

Comment 16

18 years ago
changing to nsbeta1-. this one does not meet beta stopper guidelines.

Chau - Pls accept this one for M0.9.2
Keywords: nsbeta1 → nsbeta1-

Comment 17

18 years ago
If this is a Netscape.com server side issue, pls move to bugscape. Thxs

Comment 18

18 years ago
Marking as nsCatFood. 

Linda - Pls get with Chau on this one.
Keywords: nsCatFood

Comment 19

18 years ago
This bug should be moved to Bugscape. This is a server-side and sherlock file 
issue only. It is definitely not a beta issue. Only valid for any future Chinese 
build. Please have the bug moved to Bugscape.

Updated

18 years ago
Keywords: nsbeta1-
CC Asa : 
Can you please move this bug to bugscpae as requested in comment #19 ?
Thanks

Comment 21

16 years ago
Asa, can we mark this bug as fixed now?

Comment 22

15 years ago
Bug moved to http://bugscape.netscape.com/.

If the move succeeded, asa@mozilla.org will receive a mail
containing the number of the new bug in the other database.
If all went well,  please mark this bug verified, and paste
in a link to the new bug. Otherwise, reopen this bug.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → MOVED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.