Closed Bug 464536 Opened 16 years ago Closed 16 years ago

[bn-IN] Backport about:rights to 3.0.5

Categories

(Mozilla Localizations :: bn-IN / Bengali (India), defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sethb, Unassigned)

References

()

Details

(Keywords: fixed1.9.0.5, Whiteboard: [stays en-US])

You're receiving this email because your about:rights has not yet been translated. Please let us know in this bug if you plan to keep the about:rights section untranslated. We will need to hear if you intend to translate these strings or if you want your locale to contain the en-US strings for about:rights. When/if you have finished your translation, please create a patch for about:rights and ask for approval to land it for FF 3.0.5. You can find the updated release schedule for Firefox 3.0.5 here: https://wiki.mozilla.org/Releases/Firefox_3.0.5#Schedule It obviously benefits us if you can get your changes in as soon as possible, but we know how busy you are, so please let us know if/how we can help.
We would like to keep the about:rights page unchanged for this release. Thanks.
Making that a note in the whiteboard, setting the URL to en-US so that the bug queries catch bn-IN as ready for migration (even if it's en-US). Thanks. We'll close this bug as soon as there are 3.0.5pre builds out with this.
Whiteboard: [stays en-US]
Checked in, marking FIXED and fixed1.9.0.5 RCS file: /l10n/l10n/bn-IN/browser/chrome/browser/aboutRights.dtd,v done Checking in bn-IN/browser/chrome/browser/aboutRights.dtd; /l10n/l10n/bn-IN/browser/chrome/browser/aboutRights.dtd,v <-- aboutRights.dtd initial revision: 1.1 done RCS file: /l10n/l10n/bn-IN/browser/chrome/browser/aboutRights.properties,v done Checking in bn-IN/browser/chrome/browser/aboutRights.properties; /l10n/l10n/bn-IN/browser/chrome/browser/aboutRights.properties,v <-- aboutRights.properties initial revision: 1.1 done
Status: NEW → RESOLVED
Closed: 16 years ago
Keywords: fixed1.9.0.5
Resolution: --- → FIXED
Marking fixed1.9.0.5, this bug should still get verified.
You need to log in before you can comment on or make changes to this bug.