Closed Bug 348101 Opened 18 years ago Closed 18 years ago

ko Search Feature Tracking for Firefox 2

Categories

(Mozilla Localizations :: ko / Korean, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: chofmann, Assigned: channy)

References

Details

(Keywords: fixed1.8.1, Whiteboard: BD OK with Daum, Naver)

Attachments

(3 files, 1 obsolete file)

tracking bug to make sure we get things on the list below working correctly for
each locale:

Full Default Search partner list/order.
primary/secondary search selection behavior
Search codes.
Search Suggests enable/disable for locales where available or not
Summary: ko-KR → ko-KR Search Feature Tracking for Firefox 2
Blocks: 349850
No longer blocks: 349850
Depends on: 349850
Blocks: 349850
No longer depends on: 349850
No longer blocks: 349850
Depends on: 349850
Depends on: 349390
Depends on: 349389
Blocks: fx20-ko
just a note to make sure the yahoo code is correct
fr=moz1      %IDENTIFIER% when Yahoo is in the #1 search position
fr=moz2      %IDENTIFIER% when Yahoo is in the #2 search position
Hi Channy,  I notice that Amazon search generates this query  http://www.amazon.com/gp/search/103-9872877-2921428?search-alias=aps&keywords=test
and points at the us-en Amazon site.  I guess we have done that in the past, but I'm wondering if there would be better subsitutions for on-line shopping in the ko build.   We might not be able to make these changes for 2.0, but should be thinking about what makes the most sense.
Whiteboard: bizdev-future look at amazon.com?
Attached file v1 ko search box test
Channy/Mic, do you know if we have contact info, review, and approval on file for Daum and Naver?
I know Asa made a recent presention to them on a visit to Korea. He might have contact info too.
Flags: blocking-firefox2?
Whiteboard: bizdev-future look at amazon.com? → blocking on yahoo fr=moz1 code
Flags: blocking-firefox2? → blocking-firefox2+
Any news on the contact info for Daum and Naver?

Mic, if we don't get that info in time, we wouldn't block on that right? As the two already shipped in 1.5?
Severity: normal → critical
No longer depends on: 349389, 349390
OS: Windows XP → All
Hardware: PC → All
Summary: ko-KR Search Feature Tracking for Firefox 2 → ko Search Feature Tracking for Firefox 2
Depends on: 346863
(In reply to comment #1)
> just a note to make sure the yahoo code is correct
> fr=moz1      %IDENTIFIER% when Yahoo is in the #1 search position
> fr=moz2      %IDENTIFIER% when Yahoo is in the #2 search position
> 

Sorry for my delay. I have two things to fix in yahoo-kr.xml. One is suggestion url  , the other is to fix to fr=moz1. Right?
QA Contact: admin
(In reply to comment #5)
> Created an attachment (id=236185) [edit]
> update with daum and naver search query examples.
> 
> Channy/Mic, do you know if we have contact info, review, and approval on file
> for Daum and Naver?
> 

I have a contact point. 
Daum: Channy Yun, channy@daumcorp.com
Naver: Jaekwang Lee, leesop@nhncorp.com
Attachment #237679 - Attachment is obsolete: true
Depends on: 351817
hey all
BD has reviewed and we are good to go for FF2
Channy thanks for contacts at Daum and Naver, have you been in touch with them recently, can you confirm they are aware that we ship with their plug-ins
best
mic
Comment on attachment 237680 [details] [diff] [review]
yahoo-kr.xml patch to fix search suggestion url and parameter.

The parameter was fixed by benjamin in another bug, please make sure that you keep that.

r+ on the change of the suggest url.
Attachment #237680 - Flags: review?
Attachment #237680 - Flags: review+
Attachment #237680 - Flags: approval-l10n?
Attachment #237680 - Flags: approval-l10n+
(In reply to comment #13)
> (From update of attachment 237680 [details] [diff] [review] [edit])
> The parameter was fixed by benjamin in another bug, please make sure that you
> keep that.
> 
> r+ on the change of the suggest url.
> 

I did it only for suggestion url. Is there another issues?
(In reply to comment #2)
> Hi Channy,  I notice that Amazon search generates this query 
> http://www.amazon.com/gp/search/103-9872877-2921428?search-alias=aps&keywords=test
> and points at the us-en Amazon site.  I guess we have done that in the past,
> but I'm wondering if there would be better subsitutions for on-line shopping in
> the ko build.   We might not be able to make these changes for 2.0, but should
> be thinking about what makes the most sense.
> 

Chris, thanks for your comment. I contacted several korean shopping sites. But, I didn't get responses. (Also most of them are broken in Firefox because of non-standard web page.) So my community decided to contact web site to offer price comparision service such as http://danawa.co.kr. If they don't responce to me till RC1 lockdown, we will give up it.

Yahoo is fixed, list is ok.

Talking about Korea and shopping, is there any progress on the secure http front? Is it still mostly that special non-https protocol? If so, do you have any news on the implementation of that that we heard about a while ago?

Just asking because adding a non-secure shopping site would so not be Firefox.

Regardless, I'm closing this bug down now. If you get feedback from danawa in time, feel free to reopen.

Please test all plugins on a fresh profile in a nightly and VERIFY.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Whiteboard: blocking on yahoo fr=moz1 code → BD OK with Daum, Naver
Axel, should this be marked fixed1.8.1?
Note that:

http://lxr.mozilla.org/l10n-mozilla1.8/source/ko/browser/searchplugins/yahoo-kr.xml

Shows fr as set *twice* - once hardcoded and once using MozParam.  We should remove the hardcoded version...
(In reply to comment #14)
> (In reply to comment #13)
> > (From update of attachment 237680 [details] [diff] [review] [edit] [edit])
> > The parameter was fixed by benjamin in another bug, please make sure that you
> > keep that.
> > 
> > r+ on the change of the suggest url.
> > 
> 
> I did it only for suggestion url. Is there another issues?

Hrm. You did add the fr=moz1 hardocded parameter in this check-in. I reverted that in CVS now, please do a cvs diff -u before you commit changes and make sure that only those changes show up that are supposed to happen. That's a good practice in general, btw.

Reopening until I verified that my check-in does the right thing.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
FIXED, please check all plugins on a nightly build and a fresh profile to VERIFY that they work as expected.
Status: REOPENED → RESOLVED
Closed: 18 years ago18 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
(In reply to comment #20)
> FIXED, please check all plugins on a nightly build and a fresh profile to
> VERIFY that they work as expected.
> 

okay. i'll do that.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: