L10n:Mobile/Bugogram: Difference between revisions

Jump to navigation Jump to search
→‎search: compat with desktop on process now
No edit summary
(→‎search: compat with desktop on process now)
Line 26: Line 26:
For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:
For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:


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


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. %(name)s, we'll likely need your help to at least get the contact information.
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. %(name)s, we'll likely need your help to at least get the contact information.
Line 32: Line 32:
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 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>.


Finally, once we have a specification on what the search engines for %(language)s should look like, the localization team and the l10n drivers will work on the implementation. This should happen by the localization team creating and attaching patches for the desired changes, and requesting review from milos@moz. After a successful review, the localization team will land them.
Once we have a specification on what the search engines for %(language)s should look like, Milos and the localization team will work on an implementation on that. Milos will create and attach patches for the desired changes and get them reviewed. After a successful review, Milos will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask Milos for review on those before landing.  


Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by Milos, 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.
Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by Milos, 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 %(language)s team will be driving this bug to completion.
The %(language)s team and Milos will be driving this bug to completion.


== done ==
== done ==
That's all folks.
That's all folks.
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits

Navigation menu