Closed Bug 590149 Opened 14 years ago Closed 14 years ago

Create l10n bugzilla component for Songhay (son)

Categories

(bugzilla.mozilla.org :: Administration, task)

task
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: Pike, Assigned: marcia)

References

Details

We need a bugzilla component for the son Localization.  We'll start off with the current scheme and then migrate the existing bugs once we change over to the new scheme.


Product: Mozilla Localizations
Component: son / Songhay
Description: Songhay Localization (...)

Assignee: nobody
QA Contact: son@localization.bugs

Mohomodou, could you provide a utf-8 encoded translation of 'Songhay Localization' to include in the component description? In preparation of the new scheme, fill out the descriptions for Firefox on https://localize.mozilla.org/son/bugzilla_components/, too? You'll be able to log in with your ldap credentials once you have them (along with your hg access), or create an account there. Either way, I'll need to grant you permissions on the server, so poke me with your account details for that.
Following up on this bug to see if we can get the translation so I can create the component. Thanks.
(In reply to comment #1)
> Following up on this bug to see if we can get the translation so I can create
> the component. Thanks.

Thank you. 
Probably in another bug, here again:

Songhay = "Soŋay"
Songhay Localization = "Soŋay šenni berandiyan"

Hope this helps.
Resolving fixed as this has been added.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Thanks.

Mohomodou, mind starting to watch son@localization.bugs? You do that by adding that email on https://bugzilla.mozilla.org/userprefs.cgi?tab=email#new_watched_by_you.

That way, you'll automatically get mail on new bugs filed on Songhay and updates on those bugs.
Status: RESOLVED → VERIFIED
Thank you Axel – I've added son@localization.bugs to the watch list.
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.