Land strings for IRC client in SeaMonkey
Categories
(SeaMonkey :: General, task)
Tracking
(seamonkey2.49esr unaffected, seamonkey2.53 unaffected, seamonkey2.57esr affected)
Tracking | Status | |
---|---|---|
seamonkey2.49esr | --- | unaffected |
seamonkey2.53 | --- | unaffected |
seamonkey2.57esr | --- | affected |
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
References
Details
Attachments
(1 file)
121.50 KB,
patch
|
frg
:
review+
|
Details | Diff | Splinter Review |
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
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 3•2 years ago
|
||
Comment on attachment 9118127 [details] [diff] [review] irc strings lgtm
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/7ce4f25ecab9
Land strings for IRC client in SeaMonkey. r=frg
![]() |
||
Updated•2 years ago
|
Comment 5•2 years ago
|
||
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?
Comment 7•2 years ago
|
||
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
- Where the list in comment 2 comes from, given it doesn't match Pontoon's (even ignoring
ja
andja-JP-mac
)
https://pontoon.mozilla.org/projects/seamonkey/ - What the actual request is (just
hg cp extensions/irc/chrome/ suite/chrome/irc
?)
Comment 8•2 years ago
|
||
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
- Where the list in comment 2 comes from, given it doesn't match Pontoon's (even ignoring
ja
andja-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.
- 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)
Assignee | ||
Comment 10•2 years ago
|
||
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?
Comment 11•2 years ago
|
||
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.
Assignee | ||
Comment 12•11 months ago
|
||
Landed over in Bug 1707459
Description
•