Closed Bug 1104532 Opened 10 years ago Closed 10 years ago

[zh-CN] Update list of searchplugins for Firefox desktop

Categories

(Mozilla Localizations :: zh-CN / Chinese (Simplified), defect)

Product:
Mozilla Localizations
Component:
zh-CN / Chinese (Simplified)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: flod, Assigned: flod)

Details

(Keywords: productization)

Attachments

(1 file)

bug1104532.patch
10.60 KB, patch
Pike
: review+
Details | Diff | Splinter Review
Let's restart the discussion from bug 1096820. Now Baidu is set as default search engine and shouldn't need any more updates. The proposal was to ship: -Baidu (baidu.xml) -Bing (bing.xml) -Google (google.xml) -Amazon (amazondotcn.xml) -Wikipedia (wikipedia-zh-CN.xml) We'll need to take a look at Amazon and update the images since we're doing an update, Wikipedia was already fixed in a mass-change bug. The proposal means dropping from the current list - baiduzhidao - creativecommons - eachnet - paipai No doubts about creativecommons, since the plugin is already broken and we need to get rid of it. @mconnor Do we have any commitments regarding the other 3? Assigning the bug to myself for now for easier tracking.
Should we enable https for Bing?
Bing comes from en-US, when it's enabled it will be for all locales.
cn.bing.com also supports https. And in China, when you visit https://www.bing.com , the content is the same as the localized Bing.
The main issue has been scale and suggestions. We're continually pushing on it, hoping to have good news soon. bug 958873 is tracking this issue. We've migrated mobile, but desktop is a bigger scale and some of this infrastructure (mostly the suggestions service) is a factor.
(In reply to Francesco Lodolo [:flod] from comment #0) > > The proposal means dropping from the current list > - baiduzhidao > - creativecommons > - eachnet > - paipai > > No doubts about creativecommons, since the plugin is already broken and we > need to get rid of it. > > @mconnor > Do we have any commitments regarding the other 3? Hi Mike, What's the status on baiduzhidao, eachnet & paipai, can we proceed to remove them?
Flags: needinfo?(mconnor)
(In reply to Hector Zhao [:hectorz] from comment #5) > (In reply to Francesco Lodolo [:flod] from comment #0) > > > > The proposal means dropping from the current list > > - baiduzhidao > > - creativecommons > > - eachnet > > - paipai > > > > No doubts about creativecommons, since the plugin is already broken and we > > need to get rid of it. > > > > @mconnor > > Do we have any commitments regarding the other 3? > > Hi Mike, > > What's the status on baiduzhidao, eachnet & paipai, can we proceed to remove > them? And how about removing DuckDuckGo, too, which is banned in China? The name of "bing" also need to be translated to "必应". It has been translated by default on their site.
(In reply to hc5023295 from comment #6) > > And how about removing DuckDuckGo, too, which is banned in China? > The name of "bing" also need to be translated to "必应". It has been > translated by default on their site. Hi hc5023295, I hope you agree with us on the removal of the search engines mentioned above. Since your suggestions may require extra input from other community members, how about filing a new bug instead of extending the scope of this one? Thanks.
Let's see if Joanne can fill for Mike. Do we have any commitment to keep baiduzhidao, eachnet & paipai in Firefox Desktop for zh-CN?
Flags: needinfo?(jnagel)
Hi, Still waiting to get access to the contracts signed by Mozilla Online. Until I have those, I do not know the terms of the agreements. I'll follow-up once I have an update. Thanks, Joanne
Flags: needinfo?(jnagel)
Hi Francesco and Joanne, We do not have any commitment (or contracts) to keep baiduzhidao, eachnet & Paipai in Firefox Desktop for zh-CN. Thanks, Jack
Thanks, I think we're good to go then with this information.
Flags: needinfo?(mconnor)
Attached patch bug1104532.patch — — Splinter Review
* Remove baiduzhidao, creativecommons, eachnet, paipai and related XML files if present. * Reorder list.txt alphabetically * Fix permissions on wikipedia-zh-CN.xml (755->644) Images for Amazon and Wikipedia were already updated in bug 1069123 and bug 939834).
Attachment #8639701 - Flags: review?(l10n)
Attachment #8639701 - Flags: review?(l10n) → review+
http://hg.mozilla.org/releases/l10n/mozilla-aurora/zh-CN/rev/7ae630f34dbe http://hg.mozilla.org/l10n-central/zh-CN/rev/516b79b44737 Please make sure to request a new sign-off on Aurora if you want this to move to Beta. It would also be nice to verify this bug on tomorrow's build, and mark it as VERIFIED.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
There are Chinese users reporting amazon.cn been redirected to other sites if https is not enabled. As en-US has made amazon search use https, we can do the same thing with zh-CN. I've made a opensearch addon to do it: https://addons.mozilla.org/zh-CN/firefox/addon/%E4%BA%9A%E9%A9%AC%E9%80%8A/
Amazon is going to be updated very soon to SSL (bug 1179332).
(In reply to Francesco Lodolo [:flod] from comment #13) > > It would also be nice to verify this bug on tomorrow's build, and mark it as > VERIFIED. Verified: baiduzhidao, creativecommons, eachnet & paipai searchplugins are no longer present in DevEdition zh-CN build (20150729004002).
Status: RESOLVED → VERIFIED
(In reply to Francesco Lodolo [:flod] from comment #13) > Please make sure to request a new sign-off on Aurora if you want this to > move to Beta. > I can only find SeaMonkey's approval‑comm‑beta flag for this patch, should I use that to request the uplift?
(In reply to Hector Zhao [:hectorz] from comment #17) > I can only find SeaMonkey's approval‑comm‑beta flag for this patch, should I > use that to request the uplift? It's not something that you do in Bugzilla. You need to request a sign-off for Firefox Aurora in your team page (it's already been done). https://l10n.mozilla.org/shipping/signoffs/zh-CN/fx41 Thanks for verifying the bug.
Given how late we are in the beta cycle, I'd prefer to not uplift this to beta. Also, this bug has been around long enough so that I don't think another cycle hits us badly.
(In reply to Axel Hecht [:Pike] from comment #19) > Given how late we are in the beta cycle, I'd prefer to not uplift this to > beta. Also, this bug has been around long enough so that I don't think > another cycle hits us badly. We're talking about moving from Aurora to Beta at the end of the cycle (or at least I was).
(In reply to Francesco Lodolo [:flod] from comment #18) > > It's not something that you do in Bugzilla. You need to request a sign-off > for Firefox Aurora in your team page (it's already been done). > https://l10n.mozilla.org/shipping/signoffs/zh-CN/fx41 Thanks to Shaohua for taking care of it! (In reply to Francesco Lodolo [:flod] from comment #20) > (In reply to Axel Hecht [:Pike] from comment #19) > > Given how late we are in the beta cycle, I'd prefer to not uplift this to > > beta. Also, this bug has been around long enough so that I don't think > > another cycle hits us badly. > > We're talking about moving from Aurora to Beta at the end of the cycle (or > at least I was). I was indeed thinking about uplifting to Fx 40, but I can also understand :Pike's concerns, surely this can wait another six weeks. Thanks!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: