l10n.ini and l10n-central.ini are out of sync

RESOLVED FIXED

Status

Fennec Graveyard
General
--
critical
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: Pike, Assigned: Pike)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

7 years ago
Created attachment 500044 [details] [diff] [review]
update l10n-central.ini to the contents of l10n.ini

The l10n.ini in locales is out of sync with l10n-central.ini, which it shouldn't be.

de-facto, this is hiding the strings for sync and embedding from the dashboard, which is looking at l10n-central.ini.

Best to get them to have the same content. Pseuo-patch attached for review.
Attachment #500044 - Flags: review?(mark.finkle)
(Assignee)

Updated

7 years ago
tracking-fennec: --- → ?
Comment on attachment 500044 [details] [diff] [review]
update l10n-central.ini to the contents of l10n.ini

This looks OK to me. Do we need to update l10n-mozilla-2.0.ini too? And can we remove l10n-mozilla-1.9.2.ini ?
Attachment #500044 - Flags: review?(mark.finkle) → review+
(Assignee)

Comment 2

7 years ago
the 1.9.2 one is used for the 1.1 builds still, which we'd use for security updates.

the mozilla-2.0 is not yet used, I'll update that as well, as I'm on it.
(Assignee)

Comment 3

7 years ago
http://hg.mozilla.org/mobile-browser/rev/3f16ddfc7fc3, thanks, marking FIXED.

dashboard is getting up to date with the android strings showing up now, too.
(Assignee)

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(In reply to comment #2)
> the 1.9.2 one is used for the 1.1 builds still, which we'd use for security
> updates.

Wouldn't we use the file in the 1.1 repo?
(Assignee)

Comment 5

7 years ago
Good call. We should remove the l10n-central.ini in the 1.1 repo, too, then.

New bug, or rs= ?
(In reply to comment #5)
> Good call. We should remove the l10n-central.ini in the 1.1 repo, too, then.
> 
> New bug, or rs= ?

rs=me

Comment 7

7 years ago
Can somebody verify this, please?
tracking-fennec: ? → ---
You need to log in before you can comment on or make changes to this bug.