Closed
Bug 603941
(fx40-p12n-as)
Opened 14 years ago
Closed 13 years ago
[as] Firefox productization review for Assamese
Categories
(Mozilla Localizations :: as / Assamese, defect)
Mozilla Localizations
as / Assamese
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stas, Unassigned)
References
Details
(Keywords: productization)
As you might have seen in the newsgroups or on the Mozilla blog, there's a couple of changes to search engines planned for the 4.0 release for en-US: <http://groups.google.com/group/mozilla.dev.l10n/msg/81073d8d67e1c4c3>. We would like to use this opportunity to review the current productization setup for Assamese and make any changes that you think will be good for our users.
What is a productization review?
================================
Here's what we're interested in:
* search engines,
* protocol handlers,
* feed readers,
* live bookmark.
You can see what your locale currently ships with at <http://hg.mozilla.org/l10n/l10n-src-verification/file/default/reference/browser/2.0/as>
Please take a moment and review the choice of services available by default in your locale. If there have been any new services that have recently gained popularity and that offer good value for the users, please suggest adding them to your locale. On the other hand, if there are services that lost credibility (e.g. display too many adds) or have poor user experience, consider suggesting that we remove them. If in doubt, feel free to make a suggestion and we'll look at it together. You might find the guidelines at <https://wiki.mozilla.org/L10n:Productization> and <https://wiki.mozilla.org/L10n:Firefox/Productization> helpful, too.
Required changes
================
There's two things I would like to draw your attention to (if applicable):
1) if you have a google.xml file in your `searchplugins` directory, please remove it,
2) Bloglines is closing down on November 1st and we need to remove it from the feed reader options for all locales (see bug 595485). We suspect that it will make sense to move Google Reader up to the first position (if your locale has it). We will be offering technical help with this change, either in form of ready-made patches or a mass-landing by one of the l10n-drivers. If you don't think that moving Google Reader up is a good idea for your locale, please let us know!
Changes in en-US and en-GB
==========================
Here's the changes that we will be making in en-US and en-GB:
* add Bing as the 3rd general search engine (see bug 603298),
* remove Answers,
* remove Creative Commons.
We're making these changes in en-US and en-GB because we feel that they follow the recent market trends and user preferences in the US and the UK. We would like to go through the same thought process for your locale and see if any of these changes would make sense in Assamese builds as well. If you decide that implementing these changes would be in your users' best interest then please go ahead and include them in the patch you'll attach to this bug.
Implementation
==============
Please make suggestions for changes and attach patches that Seth, Axel or I will review. Please note that since Bing provides a global plugin which does the locale detection itself, you will only need to add "bing" to your list.txt if you decide to include it. The XML file will be automatically pulled from en-US.
Once a review is granted, you can land the patch on l10n-central if your locale actively maintains it. Otherwise, please wait for further instructions which will be put in the comments of this bug and announced in mozilla.dev.l10n (we're still unsure when the branching will happen). Please do not land any changes except for the required ones (google.xml, Bloglines) on 1.9.2.
If you do not wish to make any changes, let us know, and we'll only work on removing Bloglines.
Thanks!
Comment 1•14 years ago
|
||
Hi, Bloglines still remains in your 1.9.2 repository. Please prepare a patch to remove it.
Also, if you have any productization changes to make for Firefox 4, like the Bing suggestion listed in comment 0, please provide a patch to make that change on l10n-central.
Thank you.
Comment 2•14 years ago
|
||
Amit, if you are intending to work on FF4, you can work on this bug. Please take a look.
Comment 3•14 years ago
|
||
Hi,
I will start the localisation work again now. Sorry that I was unable to respond to this bug earlier. If working on this bug is still a requirement, I will proceed accordingly, else please close this bug for now.
Comment 4•13 years ago
|
||
I see that we're still using creativecommons in Assamese. Might be a good idea to remove that. We also have two search engines in en-US that you could pick up, if they're useful, bing and twitter.
browser/chrome/browser-region/region.properties needs a tad of love, in particular, it changed without review in http://hg.mozilla.org/releases/l10n/mozilla-beta/as/diff/2969e14f183b/browser/chrome/browser-region/region.properties.
Nilamdyuti, if you want to do changes to region.properties, please file a bug on them upfront, and request review on the diff.
As for the changes themselves, the removal of bloglines is OK. I'm not sure if translating yahoo mail is OK, that really only makes sense if yahoo themselves use that translation on their site. We only want to set an order for bing, if we're shipping it ourselves, so depending on your choice there, we should remove that again or not.
As the right productization choices block final release, setting this bug to block fx-l10n-as.
Blocks: fx-l10n-as
Summary: [as] Firefox 4.0 productization review for Assamese → [as] Firefox productization review for Assamese
Comment 5•13 years ago
|
||
Most of comment 4 was handled in bug 714726.
Remaining: keep creative-commons or remove? Also, want to add bing and/or twitter?
Depends on: 714726
Comment 6•13 years ago
|
||
creative-commons: keep
Add bing and/or twitter: No
Comment 7•13 years ago
|
||
Cool, than we can close this bug out, thanks.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
Thanks! :)
You need to log in
before you can comment on or make changes to this bug.
Description
•