Closed Bug 442920 Opened 12 years ago Closed 12 years ago
[kn] Search engine setup for Firefox 3 for Kannada
We want to ship Firefox 3 a good list of search engines for Kannada. We're going to work towards this in three phases. First, the localization team and Mic (Michal Berman) will look at the market for the language and come up with a good set of search providers. Hari, Shankar, we already discussed most of this, the current guidelines are on http://wiki.mozilla.org/Firefox_web_services_guidelines. For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives: Google, Yahoo, Amazon, Answers, CC, eBay, Wikipedia In bug 410777, we got to google.com yahoo.in amazon.com kannadaStore.com kn.wikipedia.org Once we have a specification on what the searchengines for Kannada should look like, the localization team and Axel will work on an implementation on that. This should happen by the localization team creating and attaching patches for the desired changes, and requesting review from Axel. After a successful review, the localization team will land them. Please don't commit any modifications in l10n/kn/browser/searchplugins to the cvs repository without a patch reviewed by Axel or someone else appointed by Mic. The data here is sensitive to users and our search partners, thus the extra care here.
Component: Other → kn / Kannada
QA Contact: kannada.kn
please confirm the final list of search engine's would be: google.com yahoo.in amazon.com creativecommons kannadaStore.com kn.wikipedia.org note: i included creative commons as Mozilla supports them generally in all our builds
I agree with this list except that can we have http://www.google.com/intl/kn/ in place of google.com and http://in.kannada.yahoo.com/ in place of yahoo.com.
per comment #2. yes i believe these are geo-redirected by google and yahoo anyway. axel can confirm when he's next online in a couple days please add a patch with search engines and Axel can review. if you've not done that before then don't worry, we are experimenting with a new process where Axel may add the patch himself.
Mic, As I am not aware of patch submission process, I would be grateful if you or pike do the same. Thanks in advance..
Mic, Does the patch has been added? Can we resolve this bug?
This needs a few patches still. First thing I do is removing the en-US plugins from cvs. Please don't re-add them again, they shouldn't be in the l10n directories. If required, the build system picks them up from the en-US sources directly. in.kannada.yahoo.com doesn't have a search on its own, it's referring to in.yahoo.com for that, so we'll just gonna use the yahoo.in plugin we use for the rest of india. kn.wikipedia.org is a simple addition, too. I can do these two ad-hoc. For kannadaStore.com, I don't see us talking about permission to use that service yet, and no specs for search flags. I wouldn't block beta on this one, should we push that to a separate bug? The cvs removal part is done now, please update your working copies.
Moving yahoo and wikipedia over to the indian and kannada versions, resp. Shankar, could you review the change and set the 'r' flag to '+' if this is the right thing to do?
Attachment #332541 - Flags: review?(prasad.mvs)
comment #6, i have contacted Kannadastore.com, i am awaiting word back. Agree, let's not block ship on that, we can add them later. Ok by you Shankar?
Shankar, could you create a patch for region.properties to untranslate a bunch of the strings there? In particular, the browser.search.defaultenginename and the browser.search.order.1 and 2 should be just "Google" and "Yahoo", as they're referring to the ShortName elements in the en-US search plugins. I take it that the titles in the contentHandlers are just transcriptions of the en-US names? If so, those should be fine, assuming that those transcriptions are common for those product names in your locale.
Pike, I have reverted the region.properties to that of en-US
Pike, I am ok with patch mentioned in comment #7. (I tried to change the flag, but it said "You are not authorized to edit attachment"!)
Comment on attachment 332541 [details] [diff] [review] moving yahoo to yahoo.in and wikipedia to kn.wikipedia.org Denoting Shankar's review, and landed. Checking in list.txt; /l10n/l10n/kn/browser/searchplugins/list.txt,v <-- list.txt new revision: 1.3; previous revision: 1.2 done RCS file: /l10n/l10n/kn/browser/searchplugins/wikipedia-kn.xml,v done Checking in wikipedia-kn.xml; /l10n/l10n/kn/browser/searchplugins/wikipedia-kn.xml,v <-- wikipedia-kn.xml initial revision: 1.1 done RCS file: /l10n/l10n/kn/browser/searchplugins/yahoo-in.xml,v done Checking in yahoo-in.xml; /l10n/l10n/kn/browser/searchplugins/yahoo-in.xml,v <-- yahoo-in.xml initial revision: 1.1 done This should be beta ready now, should we move kannadaStore.com to a different bug?
Attachment #332541 - Flags: review?(prasad.mvs) → review+
Shankar, please cvs update kn/browser/searchplugins and if you get any cvs conflicts, please resolve them such that you end up with what we have in cvs now.
from comment #12, moving kannadastore.com to a new bug 450130 over to Axel and Shankar for final issues on patch, can close resolved fixed from my side :)
Resolved FIXED, then.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Ouch, ebay.com totally slipped my mind here. Mic, I don't see that really mentioned in bug 410777. Is kannadastore.com replacing ebay.com, and a better choice than ebay.in? I didn't remove answers either.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
yes it was my understanding ebay would be replaced - Shankar would you mind confirming that's the case and the rationale for this e.g., ebay is not relevant to kn users because they can't ship there, or no local users, etc.
This patch gets us on the safe side, if we figure that ebay.in is a good idea, we can still add it back in the beta period. I'll check this in right away, too.
Back to FIXED, hopefully for realz this time. Please file a new bug if ebay or answers are supposed to be added back in one way or the other.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.