Closed Bug 655587 Opened 10 years ago Closed 10 years ago

[br] Breton translation for Thunderbird 3.3

Categories

(Mozilla Localizations :: br / Breton, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mnedeleg, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

Attached file Breton translation for Thunderbird 3.1 (obsolete) —
Hello,

Our team has recently made an official release for Firefox 4 and we would like to do the same with Thunderbid 3.3.

We have just started working on Thunderbird 3.3 but you can find the translation for Thunderbird 3.1 in the attached file.

Is there anything I should do, apart from updating the translation ?
Attachment #530919 - Flags: review?(l10n)
An here is the localization for Thunderbird 3.3 (comm-miramar)
Attachment #530919 - Attachment is obsolete: true
Attachment #530919 - Flags: review?(l10n)
Attachment #531909 - Flags: review?(l10n)
Comment on attachment 531909 [details]
Breton translation for Thunderbird 3.3 (comm-miramar)

Hi Michel, thank you for taking on Thunderbird.

I can take a look at this. The compare locales output looks good, but there's a few more in-depth things that I need to check. I'll try and get time soon to look at this.
Attachment #531909 - Flags: review?(l10n) → review?(mbanner)
Comment on attachment 531909 [details]
Breton translation for Thunderbird 3.3 (comm-miramar)

This looks fine, I'll set up the l10n builders for you (which will also mean it'll being showing up on the l10n dashboard).
Attachment #531909 - Flags: review?(mbanner) → review+
Great!
Michel, if you need help to go through, don't hesitate to ping me.
The builders are all set up - you'll get nightly builds from tomorrow. br is also now listed on the l10n dashboard for 3.3x:

https://l10n-stage-sj.mozilla.org/dashboard/?tree=tb33x

Please mark this bug as fixed when you land the changes.
Thanks, the changes are landed !
Signs-offs are still closed but I suppose I will be able to do that later.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.