Closed Bug 560526 Opened 14 years ago Closed 14 years ago

[gd] Firefox 3.6 News reader setup for Scottish Gaelic

Categories

(Mozilla Localizations :: gd / Scottish Gaelic, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

()

Details

(Keywords: productization)

News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user to subscribe to it, either as a live bookmark or via one of the web services.

The current News Readers in en-US are Bloglines, My Yahoo, Google.

We want to ship a good set of defaults for Scottish Gaelic, and will work towards that in three stages.

First, the localization team and Stas (Stas Malolepszy) will look at the market for the language and come up with a good candidates. Michael, Kevin, we'll need your input on this, the guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decided on a particular news reader, Stas will contact the owner and ask for permission. Michael, Kevin, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for Scottish Gaelic should look like, the localization team and Stas will work on an implementation on that. This should happen by the localization team creating and attaching patches for the desired changes, and requesting review from Stas. After a successful review, the localization team will land them. If you're not feeling comfortable with creating those changes, ask Stas to help out.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by Stas, Axel or someone else appointed by Stas/SethB. The data here is sensitive to users and our search partners, thus the extra care here.
Nothing available in Gaelic except what Google might offer at some point through GoogleInYourLanguage but AFAIK it hasn't been added for Gaelic to date, so use whatever EN-GB has?
Component: Other → gd / Scottish Gaelic
QA Contact: gd
Probably not much chance for customization here.  So, copy the required lines for the news reader setup from region properties from here:

http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/en-GB/file/927644f513a9/browser/chrome/browser-region/region.properties

and attach a patch asking for a review.
Sorry for being so dense but
* are the "required lines" those in line 13 onwards?
* what do you mean with "attaching a patch"?
(In reply to comment #3)
> Sorry for being so dense but
> * are the "required lines" those in line 13 onwards?

For this bug, you would be interested in lines 13 - 20. But ultimately, we will need to create a region.properties file for gd with all the customizations for your local.  You should have a region.properties file in your local working gd directory where you can customize all the pieces we are working on in this bug and in other productization bugs.

> * what do you mean with "attaching a patch"?

In your gd working directory, anytime you change that code locally, you can create a "diff" that shows the differences between what you had and what you created.  You can then attach that diff as a "patch" for a review so we can see what you did.
Technically, do your local changes, and then do a 

hg diff

and if that looks like the changes you want to make, redirect them to a file

hg diff > some-file.patch

, attach it to this bug with the 'flag' checkbox on, and set the 'r' flag to '?', with requestee to sethb@moz
Just been looking at the file with Kevin - we think there's nothing actually that needs changing as there are no Gaelic specific newsreaders; the current file covers en-GB which is what we were aiming for anyway. Leave as it is?
Sounds good.  Let's leave it as is.  Your working copy for gd should contain the exact copy of lines 13-20:

http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/en-GB/file/927644f513a9/browser/chrome/browser-region/region.properties#l13
Marking this as fixed as per comment 6. Nothing needed to be changed :)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.