[or] Search engine setup for Firefox Mobile for Oriya

RESOLVED FIXED

Status

defect
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: gueroJeff, Assigned: flod)

Tracking

({productization})

Firefox Tracking Flags

(Not tracked)

Details

()

Attachments

(1 attachment, 1 obsolete attachment)

We want to ship Firefox Mobile with a good list of search engines for Oriya.

We're going to work towards this in three phases. First, the localization team and the l10n drivers will look at the market for the language and come up with a good set of search providers. Manoj, we'll need your input on this, the guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Mobile/Productization>.

For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:

> Google (mobile version), Yahoo, Bing, Amazon, Twitter, Wikipedia (slightly different to desktop, 32x32 icon)

We may also want to go with just a subset of the en-US engines, if that's more appropriate for the local market.

Once we decide to use a particular search engine (and we test it on a mobile device), l10n drivers will contact the owner and ask for permission, and for specifics like proper search flags. Manoj, we'll likely need your help to at least get the contact information.

For search engines that we already ship with on desktop and that you would like to include in mobile as well, the permission is not needed. Consider using a mobile version of the engine if one is available. Also, please make yourself familiar with instructions regarding the <Description/> element at <https://wiki.mozilla.org/L10n:Integrated_Search_Instructions>. For mobile, we'll want 64x64 size images, too.

Once we have a specification on what the search engines for Oriya should look like, flod (Francesco Lodolo) and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. Manoj, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by the l10n drivers. The data here is sensitive to users and our search partners, thus the extra care here.

The Oriya team and flod will be driving this bug to completion.
Hi Jeff,
For Odia (or), the search engines for mobile should be similar to firefox-desktop. 
Giving you my preferred list of search engines below:
 1 Amazon.in
 2 creativecommons
 3 eBay-in
 4 www.google.com/?hl=or
 5 yahoo-in
 6 wikipedia-or
 7 wiktionary-or 
Please do review and commit for Odia.

Thanks,
Manoj
(In reply to Manoj Kumar Giri from comment #1)
>  2 creativecommons

Hi Manoj, is there a specific reason to ship creativecommons? See also this discussion on dev-l10n
https://groups.google.com/forum/#!topic/mozilla.dev.l10n/cxpDTCESSzU

That searchplugin is currently broken and will be removed at some point.

About wiktionary: we're not currently shipping it for any locales. The current favicon includes a 32px version (https://bits.wikimedia.org/favicon/wiktionary/en.ico), and the website exposes a searchplugin that we can reuse for parameters, but I guess we need confirmation.

Ryan, are you the right person to loop in for this request? We'd like to ship Wiktionary searchplugin for a few Indic locales.
Flags: needinfo?(rlane)
(In reply to Francesco Lodolo [:flod] from comment #2)
> (In reply to Manoj Kumar Giri from comment #1)
> >  2 creativecommons
> 
> Hi Manoj, is there a specific reason to ship creativecommons? See also this
> discussion on dev-l10n
> https://groups.google.com/forum/#!topic/mozilla.dev.l10n/cxpDTCESSzU
> 
> That searchplugin is currently broken and will be removed at some point.
I was not aware of that issue. In this case better not to  include creativecommons.
> 
> About wiktionary: we're not currently shipping it for any locales. The
> current favicon includes a 32px version
> (https://bits.wikimedia.org/favicon/wiktionary/en.ico), and the website
> exposes a searchplugin that we can reuse for parameters, but I guess we need
> confirmation.
> 
> Ryan, are you the right person to loop in for this request? We'd like to
> ship Wiktionary searchplugin for a few Indic locales.

For Wikitionary, only I can hope for the best from the concern team to include it.
Ryan, do you have any info about Wiktionary that you can provide us with here?
Assignee: nobody → francesco.lodolo
(In reply to Jeff Beatty [:gueroJeff] from comment #4)
> Ryan, do you have any info about Wiktionary that you can provide us with
> here?

Not sure if we need to leave the needinfo open, in the meantime I found out we're actually shipping Wiktionary for a couple of locales (oc, te). Bug 987658 has a working version of Wiktionary for mobile, and bug 411100 a mail from Wiki Foundation saying that we don't need any specific permission.
Amazon.in
eBay-in
Google
yahoo-in
wikipedia-or
wiktionary-or 
Bing

We've received a request to include Bing in the searchplugins. Would this list be OK for you?
Flags: needinfo?(rlane)
Looks fine to me.

(In reply to Francesco Lodolo [:flod] from comment #6)
> Amazon.in
> eBay-in
> Google
> yahoo-in
> wikipedia-or
> wiktionary-or 
> Bing
> 
> We've received a request to include Bing in the searchplugins. Would this
> list be OK for you?
Posted patch bug987656.patch (obsolete) — Splinter Review
region.properties
Same values of en-US, handlerversion reset to 1

searchplugins
Usual Indic versions of eBay, Yahoo, Amazon, plus locale specific Wikipedia/Wiktionary

Searchplugins available for testing at
http://l10n.mozilla-community.org/~flod/testsp/
Attachment #8410210 - Flags: review?(l10n)
v2, remove unnecessary xml declaration at the beginning of Wiktionary
Attachment #8410210 - Attachment is obsolete: true
Attachment #8410210 - Flags: review?(l10n)
Attachment #8410220 - Flags: review?(l10n)
Status: NEW → ASSIGNED
Attachment #8410220 - Flags: review?(l10n) → review+
You need to log in before you can comment on or make changes to this bug.