Closed
Bug 667142
Opened 14 years ago
Closed 14 years ago
Update/Sign-Off Portuguese Locale for SeaMonkey 2.2
Categories
(Mozilla Localizations :: pt-PT / Portuguese, defect)
Tracking
(seamonkey2.2+)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| seamonkey2.2 | + | --- |
People
(Reporter: Callek, Assigned: lloco73)
Details
The Portuguese locale was shipped in SeaMonkey 2.1 and needs minimal changes to work in SeaMonkey 2.2
There will be no more SeaMonkey 2.1 releases.
We want to create an update offer for SeaMonkey 2.0 users on this locale to 2.2 once shipped.
Final spin is in ~1 week, and is off the l10n/mozilla-beta Mercurial branch.
Signoff https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=sea2.2
* "24 entries missing in existing files, 13 entries missing in new files"
** Details at https://l10n-stage-sj.mozilla.org/dashboard/compare?run=139035
** However the dashboard does not acknowledge chatzilla changes. (see below, from current aurora -- which is almost certainly the same changes needed for sea_beta). And chatzilla changes break the build.
Failing time to complete in time for SeaMonkey 2.2, our 2.3 release will be about 6 weeks later, coming off the "rapid release train" with Firefox 6/Thunderbird 6.
See current status of that tree at https://l10n-stage-sj.mozilla.org/dashboard/?tree=sea_aurora
Comparing pt-PT to en-US
Properties in ./chrome/chatzilla.properties don't match:
In ./en-US: (add these to your localization)
cmd.goto-startup.label
cmd.goto-startup.help
| Reporter | ||
Comment 1•14 years ago
|
||
You probably want to update http://hg.mozilla.org/releases/l10n/mozilla-beta/pt-PT/file/8292942e5672/extensions/irc/chrome/chatzilla.properties#l72 to 0.9.87 while you are here.
| Reporter | ||
Comment 3•14 years ago
|
||
Thank You! (Since I was looking to push now, I manually checked them, and signed off myself, and accepted)
| Assignee | ||
Comment 4•14 years ago
|
||
thanks
marked as resolved
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•