Closed
Bug 603956
(fx40-p12n-eo)
Opened 14 years ago
Closed 14 years ago
[eo] Firefox 4.0 productization review for Esperanto
Categories
(Mozilla Localizations :: eo / Esperanto, defect)
Mozilla Localizations
eo / Esperanto
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stas, Unassigned)
References
Details
(Keywords: productization, Whiteboard: [l10n-src-verification updated])
Attachments
(3 files, 2 obsolete files)
(deleted),
patch
|
sethb
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
sethb
:
review-
|
Details | Diff | Splinter Review |
(deleted),
patch
|
sethb
:
review+
|
Details | Diff | Splinter Review |
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 Esperanto 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/eo>
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 Esperanto 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 3•14 years ago
|
||
I checked the link you provided:
"You can see what your locale currently ships with at
<http://hg.mozilla.org/l10n/l10n-src-verification/file/default/reference/browser/2.0/eo>"
But I can't find the google.xml we are supposed to be shipping right now:
http://hg.mozilla.org/l10n-central/eo/file/01f1c98d1a84/browser/searchplugins
http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/eo/file/4ba5f317f045/browser/searchplugins
Where can I find it?
Comment 4•14 years ago
|
||
Hi Eduardo,
Your XML files are fine as they are here:
http://hg.mozilla.org/l10n-central/eo/file/default/browser/searchplugins
http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/eo/file/default/browser/searchplugins
However, I noticed that your files here:
http://hg.mozilla.org/l10n-central/eo/file/default/browser/chrome/browser-region/region.properties
and
http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/eo/file/default/browser/chrome/browser-region/region.properties
still contain Bloglines. Can you prepare a patch that removes Bloglines from those two? Thanks!
Comment 5•14 years ago
|
||
But I already did, they're attached to this bug waiting for review.
Comment 6•14 years ago
|
||
Comment on attachment 487202 [details]
diff for 1.9.2
We don't need to add Bing to 1.9.2. Only for 2.0.
Attachment #487202 -
Flags: review? → review-
Comment 7•14 years ago
|
||
Comment on attachment 487200 [details]
diff for l10n-central
You will need to add bing to your list.txt file, too. Please do that and reattach the next patch. Thanks, Eduardo.
Attachment #487200 -
Flags: review? → review-
Comment 8•14 years ago
|
||
Removed Bloglines.
Attachment #487202 -
Attachment is obsolete: true
Attachment #487311 -
Flags: review?
Comment 9•14 years ago
|
||
Comment on attachment 487311 [details] [diff] [review]
diff for 1.9.2
Please land this on the 1.9.2 branch, adding a comment to your check-in that references bug 603956 and this change.
Attachment #487311 -
Flags: review? → review+
Updated•14 years ago
|
Whiteboard: [update l10n-src-verification]
Comment 10•14 years ago
|
||
Added Bing. Removed Bloglines. Removed obsolete entity "keyword.URL" [1].
[1] http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/a1004883745e5ef3?fwc=1
Attachment #487313 -
Flags: review?
Comment 11•14 years ago
|
||
In case the removing of "keyword.URL" doesn't belong to this bug this is the patch that only adds Bing and removes Bloglines.
Attachment #487200 -
Attachment is obsolete: true
Attachment #487314 -
Flags: review?
Comment 12•14 years ago
|
||
> Please land this on the 1.9.2 branch, adding a comment to your check-in that
> references bug 603956 and this change.
http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/eo/rev/84b0d73a6e30
Comment 13•14 years ago
|
||
Comment on attachment 487314 [details] [diff] [review]
diff for l10n (without removing the obsolete entity)
Please land this on l10n-central, adding a comment that references bug 603956 and this change.
Also, are you now shipping with 8 search plugins? Do you want to remove Creative Commons?
Attachment #487314 -
Flags: review? → review+
Comment 14•14 years ago
|
||
Comment on attachment 487313 [details] [diff] [review]
diff for l10n-central
Let's take care of keyword.URL in Bug 601120.
Attachment #487313 -
Flags: review? → review-
Comment 15•14 years ago
|
||
> Please land this on l10n-central, adding a comment that references bug 603956
> and this change.
http://hg.mozilla.org/l10n-central/eo/rev/2b745b7d277d
> Also, are you now shipping with 8 search plugins? Do you want to remove
> Creative Commons?
Hmm, I'll check with the rest of the team and I'll get back to you with another patch.
Comment 16•14 years ago
|
||
Resolving this as fixed for now. If you want to make other changes after consulting the team, just reopen this bug and add your new comment.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 17•14 years ago
|
||
Whiteboard: [update l10n-src-verification] → [l10n-src-verification updated]
You need to log in
before you can comment on or make changes to this bug.
Description
•