Open Bug 1606400 Opened 1 year ago Updated 1 month ago

Land strings for IRC client in SeaMonkey

Categories

(SeaMonkey :: General, task)

task
Not set
normal

Tracking

(seamonkey2.49esr unaffected, seamonkey2.53 unaffected, seamonkey2.57esr affected)

REOPENED
seamonkey 2.71
Tracking Status
seamonkey2.49esr --- unaffected
seamonkey2.53 --- unaffected
seamonkey2.57esr --- affected

People

(Reporter: iann_bugzilla, Assigned: iann_bugzilla)

Details

Attachments

(1 file)

SeaMonkey will need strings landing for the IRC client. These are currently a copy of the strings used for ChatZilla and will go into suite/locales/en-US/chrome/irc
For locales, to reduce work on re-translating, we would need to have copied the strings from extension/irc/chrome to suite/chrome/irc

Attached patch irc stringsSplinter Review
Attachment #9118127 - Flags: review?(frgrahl)
Attachment #9118127 - Flags: approval-comm-esr60?

This is the list of locales needing to have strings copied:
ca, cs, de, en-GB, es-ES, fi, fr, it, ja, ja-JP-mac, nb-NO, pl, pt-BR, pt-PT, ru, si, sk, sv-SE

Comment on attachment 9118127 [details] [diff] [review]
irc strings

lgtm
Attachment #9118127 - Flags: review?(frgrahl)
Attachment #9118127 - Flags: review+
Attachment #9118127 - Flags: approval-comm-esr60?
Attachment #9118127 - Flags: approval-comm-esr60+

Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/7ce4f25ecab9
Land strings for IRC client in SeaMonkey. r=frg

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey 2.71

You do realize that, without any coordination, all locales will have to retranslate everything from scratch? This should have NOT landed without setting up a plan first

This is actively blocking me from pushing strings for all other hg projects. Please back it out, or I'll ask sheriffs to back it out to unblock before end of weekend.

Open questions:

  • Comment 2 has a list of locales, who's going to copy the files and how?
  • You're landing this in esr-60?
Flags: needinfo?(iann_bugzilla)
Flags: needinfo?(frgrahl)
Attachment #9118127 - Flags: approval-comm-esr60+

Thanks.

On the who: that's going to be me, since it requires disabling sync for Pontoon before updating gecko-strings, and copying the files.

What I'd like to understand is

  1. Where the list in comment 2 comes from, given it doesn't match Pontoon's (even ignoring ja and ja-JP-mac)
    https://pontoon.mozilla.org/projects/seamonkey/
  2. What the actual request is (just hg cp extensions/irc/chrome/ suite/chrome/irc?)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Even looking at DXR for locales with the Chatzilla folder
https://dxr.mozilla.org/l10n-central/search?q=path%3Aextensions%2Firc%2Fchrome&redirect=false

be, ca, cs, de, en-CA, en-GB, es-ES, fi, fr, it, ja, ja-JP-mac, ku, nb-NO, pl, pt-BR, pt-PT, ro, ru, si, sk, sv-SE, tr

See comments in-line below.

(In reply to Francesco Lodolo [:flod] from comment #7)

Thanks.

On the who: that's going to be me, since it requires disabling sync for Pontoon before updating gecko-strings, and copying the files.

What I'd like to understand is

  1. Where the list in comment 2 comes from, given it doesn't match Pontoon's (even ignoring ja and ja-JP-mac)
    https://pontoon.mozilla.org/projects/seamonkey/

It was based on the list of all-locales from Chatzilla folder but perhaps your criteria from comment 8 is better.

  1. What the actual request is (just hg cp extensions/irc/chrome/ suite/chrome/irc?)

Yes, that is correct. (and from what I can work out that doesn't require any changes to l10n.toml)

Flags: needinfo?(iann_bugzilla)
Flags: needinfo?(frgrahl)

For those that are in https://pontoon.mozilla.org/projects/seamonkey/ but not in "be, ca, cs, de, en-CA, en-GB, es-ES, fi, fr, it, ja, ja-JP-mac, ku, nb-NO, pl, pt-BR, pt-PT, ro, ru, si, sk, sv-SE, tr", what is the best way of warning the localisers?
What are the next steps?

Flags: needinfo?(francesco.lodolo)

The new strings will simply show up for translation in Pontoon.

Having said that, I need to keep this on hold for a bit longer, because there's a larger conversation to have around localization. Hopefully, will be reaching out shortly.

Flags: needinfo?(francesco.lodolo)
You need to log in before you can comment on or make changes to this bug.