You've indicated an interest in participating in the localization of mobile Firefox (aka Fennec). We want to ship Fennec with a good list of search engines for Spanish. As the technical details of implementation are being worked on, we'd like to start the discussion about the choice of search engines. This bug is about agreeing on a set of search engines, and will not tackle the implementation (at least not yet). First, the localization team and Staś will look at the market for the locale and come up with a good set of search providers. The guidelines for making recommendations are on https://wiki.mozilla.org/L10n:Mobile/Productization. You're welcome to suggest engines already shipped in desktop Firefox for Spanish, if they fit well in the categories outlined on the wiki. For en-US, we currently use the following set, which may serve as an inspiration: Google, Wikipedia, Amazon, Yahoo, Twitter. Note that according to the guidelines, for some categories it may be better to leave them empty than to ship with en engine that's irrelevant or unavailable in your region. After we decided on a particular search engine, we will need to test it in Fennec. You can test on a mobile device and on the desktop (download the builds from <http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/>). Staś will help with testing on a device, too. If the service works fine, Staś will contact the owner and ask for permission, and for specifics like proper search flags. $name, we'll likely need your help to at least get the contact information if we don't have them already. We don't know the implementation details yet, so for now, please don't create patches nor land anything. We will keep you posted as we figure out the how's and when's. Thanks.
There you go, Guillermo! :-)
Hi Stas! Well, I think we should follow en-US searchplugins, except for Amazon that doesn't have an Spanish version (found http://www.amazon.com/Books/b?ie=UTF8&node=301731 which is a part of Amazon.com that is in Spanish with Spanish books), but I think it's very interesting for users in a mobile device (for example if they are in a library searching for a book and find it cheaper on Amazon). Twitter is still in English, but I've read that there will be a translated version for Spanish. Do you know when? Ricardo, what do you think about DRAE? It fits perfectly on a mobile phone (for Stas: http://buscon.rae.es/draeI/SrvltGUIBusUsual?TIPO_HTML=2&TIPO_BUS=3&LEMA=hola is a result for the "hola" word) Regads!
(In reply to comment #2) > Ricardo, what do you think about DRAE? It fits perfectly on a mobile phone (for > Stas: > http://buscon.rae.es/draeI/SrvltGUIBusUsual?TIPO_HTML=2&TIPO_BUS=3&LEMA=hola is > a result for the "hola" word) It may be nice for someone who doesn't have a local dictionary application. It would better if we managed to find a site that allows translations, too, but I guess that, if and when we find it, we should ask them for permission to include a link to their site in Fennec, and that may take too much time. OTOH, we have formal permission from RAE to include them in Firefox (there should be a bug somewhere in BZ database). :-) In short, I'd go with RAE for Fennec 1.0, and think about exploring further options in the future.
So, right now, we have this searchplugins in Fennec: http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/es-ES/file/tip/mobile/searchplugins/list.txt amazondotcom google twitter wikipedia yahoo Which are the same as en-US. Yes, I think that RAE should be included in this release, and find a nice (and mobile-compatible) webpage that has a dictionary and a translation service. Ricardo, and what about Amazon? Do you find it useful? Beside that, we should change from "wikipedia" to "wikipedia-es" as we do in Firefox as well as "yahoo" by "yahoo-es". Stas, how can we do that? Simply copying files from browser/searchplugins to mobile/searchplugins and change things in list.txt should work? (yes, and I'm asking for permission from l10n-drivers too ;-) )
(In reply to comment #4) > So, right now, we have this searchplugins in Fennec: > > http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/es-ES/file/tip/mobile/searchplugins/list.txt > > amazondotcom > google > twitter > wikipedia > yahoo > > Ricardo, and what about Amazon? Do you find it useful? Sorry for the delay. I'd say that mobile users are still a bit more techie than regular people and won't be shy about using the most popular online shop, so I'd keep it.
So this should be a 1.0. It changes yahoo by yahoo-es, wikipedia by wikipedia-es and adds DRAE seachplugin in list.txt (and adds these 3 searchplugins) Now, there are 6 searchplugins. Stas, do you think there are too much? Should we strip one of them? Regards!
Thanks, Guillermo and Ricardo, for your suggestions. I have a couple of comments: 1. Is the Spanish section of Amazon.com targeted at people living in Spain or in the US? If it's the latter, I would be in favor of leaving Amazon.com out completely. 2. RAE looks like a good idea, but it has a couple of layout issues when rendering on a small-screen device. The definitions are rendered with a huge font, and header layout breaks. See a screenshot: <http://l10n.mozilla.org/~stas/fennec-search/screenshot06.png>. 3. Do you have a good candidate for a local ("around-me") search for Spain? i don't think yahoo.es is the best choice. If wonder if we should leave this category empty if we don't find anything. In general, we should try our best to limit the number of default search enignes to 4, max. 5. The UI space is scarce in Fennec. Maybe the following list would be a good start: - google - es.wikipedia - twitter - RAE (+ reach out to them and ask to work on the layout issues). As you can see, there's no e-commerce nor local search. If we can add an engine to one of these categories, we should. Thoughts?
1- As I've checked on Amazon.com page and I think it's for English people that want to read something in Spanish. There are a lot of books for learn Spanish, but I don't know anyone that has purchased a book in Spanish in Amazon… Maybe for that kind of search we could use http://www.casadellibro.com/ , but for the time, I think we should remove Amazon.com from search plugins. 2- Yeah, I have tested the search page in the latest es-ES nightly for Fennec in a N810 and the result is worse: the definition seems that it's in another frame and it's at the right and quite unusable :( . If we finally decide to keep with DRAE search, we should ask RAE to change that page because it renders horrible. 3- About a local search, I'm going to send an email to our l10n list.
Here's a patch resetting the mobile/searchplugins/ directory to a minimal set of search engines that we would like to ship your locale with. Please read this comment carefully before you land this patch. *Important*: There has been a change to how we use the <Description/> elements present in the plug-ins (see bug 528655 and bug 529869). We want to emphasize that the search is integrated with the browser to better reflect what a search plugin is and what it does. You will need to edit the Wikipedia plug-in before you commit this patch. Please read <https://wiki.mozilla.org/L10n:Integrated_Search_Instructions> for detailed instructions. For Google and Twitter, we don't have to copy the XML files to your mobile/searchplugins/ directory. Plugins identical to en-US are pulled from source automatically. It's enough to put the engine's name in list.txt for this to work (which I did). I also updated the Wikipedia plug-in to use a bigger icon, see bug 517997 for details. Please edit the Wikipedia plug-in and commit this patch before you opt-in in the mozilla.dev.l10n newsgroup. Opt-ins without this patch will not be taken. This does not mean that we don't want to include other search engines. On the contrary, the work and the discussion will continue in this bug until we choose a good set of search engines for your locale. Then, you will be able to opt in again, so that in the final release we include more search engines than the mineral set from this patch. This patch is simply meant to reset your mobile/searchplugins directory so that we keep the repository clean and happy. Thanks for understanding!
(In reply to comment #9) > 1- As I've checked on Amazon.com page and I think it's for English people that > want to read something in Spanish. There are a lot of books for learn Spanish, > but I don't know anyone that has purchased a book in Spanish in Amazon… Maybe > for that kind of search we could use http://www.casadellibro.com/ , but for the > time, I think we should remove Amazon.com from search plugins. OK, let's remove Amazon and leave the spot open for now. casadellibro.com looks interesting -- do they offer a wide range of books? > 2- Yeah, I have tested the search page in the latest es-ES nightly for Fennec > in a N810 and the result is worse: the definition seems that it's in another > frame and it's at the right and quite unusable :( . If we finally decide to > keep with DRAE search, we should ask RAE to change that page because it renders > horrible. Would you mind writing to them and sending the screenshot that I took? Maybe they could fix the layout. Until that happens, I would prefer not to include their plugin. > 3- About a local search, I'm going to send an email to our l10n list. Cool, thanks.
Hi Stas, I have commited the changes: http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/es-ES/rev/3f0b43738ecb (and a followup because the "ú" seemed truncated: http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/es-ES/rev/c9e9baabe4e1 Should I do the same for l10n-central? (I prefer to do it, keeping in sync 1.9.2 and m-c)
(In reply to comment #11) I think Casa del Libro has a lot of books, every book that I have search on the webpage and on the physical shop it has been found. Anyway, sometimes they don't have the book, but they search for it in other shops or another depot. Anyway, Casa del Libro has layout issues (not as much as DRAE) as you can see here: http://willy.pijusmagnificus.com/mozilla/CasaDelLibroFennec.png Maybe if we decide to put Casa del Libro as a search engine, when we ask for permission we can ask for changing the layout too. And for translation, we are not sure about using Google Translate, as its layout is good for mobile devices as you can see here: http://willy.pijusmagnificus.com/mozilla/traduccionGoogle.png (tried the shout button to hear the word with *no Flash* gives me) http://willy.pijusmagnificus.com/mozilla/descargaTradGoogle.png Test a translation: http://www.google.com/dictionary?aq=f&langpair=es%7Cen&q=casa&hl=es
We have decided to include 11870 as a local search in Fennec. I have tested it in a N810 and there aren't any layout issues an the page is clean and easy to read and navigate. Should I create the patch and attach it here or create a new bug? Thanks Stas!
I sent an email to 11870.com, let's wait for their reply. I hope we'll get a larger icon that we can use in the plug-in.
We have some contacts in 11870 because we have talked by email these days about the mobile and classic version of their searchpage.
Oh, cool. Can you forward the email that I sent to them? (I copied you as well.) Thanks.
(pinged 11870 folks, waiting for an answer)
Status: NEW → ASSIGNED
Checked in the email sent to the folks at 11870 yesterday.
Attachment #425634 - Flags: review?(stas)
Stas, ping again
Comment on attachment 425634 [details] [diff] [review] 11870.com searchengine r=me, let's land this baby! (and so sorry for the wait) Please land this on 1.9.2 (and sign off again for 1.1) and on l10n-central. Thanks!
Attachment #425634 - Flags: review?(stas) → review+
http://hg.mozilla.org/l10n-central/es-ES/rev/874ef5547bfc http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/es-ES/rev/f8f71e83b570 Marked as Resolved-fixed. I'll try once there is a xpi from buildbot
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Thanks Guillermo. I updated the l10n-src-verification in http://hg.mozilla.org/l10n/l10n-src-verification/rev/f4b70184f3c0.
Whiteboard: [bootstrapped][twitter] → [bootstrapped][twitter][11870.com]
Verified with today nightly, enjoy!
Status: RESOLVED → VERIFIED
Taken for fennec 1.1 rc.
You need to log in before you can comment on or make changes to this bug.