Closed Bug 1412651 Opened 4 years ago Closed 4 years ago

Update en-GB for Gecko 57

Categories

(Mozilla Localizations :: en-GB / English (United Kingdom), enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: iann_bugzilla, Assigned: iann_bugzilla)

Details

Attachments

(5 files)

Locale changes needed for Gecko 57 as a basis for Firefox 57, Thunderbird 57, Mobile 57 and SeaMonkey 2.54
Attachment #8924066 - Flags: review+
Attachment #8924065 - Attachment description: Toolkit 57 en-GB update → Toolkit 57 en-GB update [Checked in: Comment 6]
Attachment #8924066 - Attachment description: Firefox 57 en-GB update → Firefox 57 en-GB update [Checked in: Comment 6]
Attachment #8924067 - Attachment description: Mobile 57 en-GB update → Mobile 57 en-GB update [Checked in: Comment 6]
Attachment #8924068 - Attachment description: Thunderbird 57 en-GB update → Thunderbird 57 en-GB update [Checked in: Comment 6]
Attachment #8924069 - Attachment description: SeaMonkey 2.54 en-GB update → SeaMonkey 2.54 en-GB update [Checked in: Comment 6]
Beta is not the right repository to land these changes, and today is the last day to have anything shipping in 57 :-\
https://groups.google.com/d/msg/mozilla.dev.l10n/_K2j7Sg0Orw/5A4GzHAKAAAJ

Since you're landing in Beta, I'm afraid the content might also not be what we expect (see discussion linked above for references).

I'm going to merge this content down to l10n-central, to at least try to ship something in 57, but we really need to fix this process.
https://hg.mozilla.org/l10n-central/en-GB

At this point I don't know how you're managing updates to en-GB (is it generated via scripts from en-US?), but I would really suggest to use Pontoon and add more people with translator rights, so that we don't end up in this situation every cycle.
(In reply to Francesco Lodolo [:flod] from comment #7)
> Since you're landing in Beta, I'm afraid the content might also not be what
> we expect (see discussion linked above for references).

Beta seems good, but I confess I don't feel comfortable in shipping an update directly to release without a single beta build. I'll make an exception for 57, but next time I won't take a sign-off on the last day available.

Please let's figure out how to solve this going forward.
(In reply to Francesco Lodolo [:flod] from comment #8)
> (In reply to Francesco Lodolo [:flod] from comment #7)
> > Since you're landing in Beta, I'm afraid the content might also not be what
> > we expect (see discussion linked above for references).
> 
> Beta seems good, but I confess I don't feel comfortable in shipping an
> update directly to release without a single beta build. I'll make an
> exception for 57, but next time I won't take a sign-off on the last day
> available.
> 
> Please let's figure out how to solve this going forward.

I currently use compare-locale on the command line, along with vi for editing and diff to compare and contrast against en-US.
Last time one of the en-GB translators used Pontoon on the Firefox files, it stripped any blank lines from those files.
This is probably only for use when comparing en-US against another en-* locale, but being able to see just the entities that differ is good for catching changes where the entity has not been renamed.
It is also useful to see the bigger picture rather than just of entities, so seeing the context within the locale files.
I presume that the online help for SeaMonkey isn't available via Pontoon so would still have to be done in another way?
(In reply to Ian Neal from comment #9)
> Last time one of the en-GB translators used Pontoon on the Firefox files, it
> stripped any blank lines from those files.

That seems strange. Pontoon takes the en-US file, and only adds translations, so it should have exactly the same structure as en-US.

> I presume that the online help for SeaMonkey isn't available via Pontoon so
> would still have to be done in another way?

Yes, xhtml files are not available in Pontoon, the only way is to commit changes to Mercurial.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.