1412651 - Update en-GB for Gecko 57

Status: RESOLVED FIXED

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

Description

[Ian Neal]

Locale changes needed for Gecko 57 as a basis for Firefox 57, Thunderbird 57, Mobile 57 and SeaMonkey 2.54

Comment 1

[Ian Neal]

Attachment: Toolkit 57 en-GB update [Checked in: Comment 6]

Comment 2

[Ian Neal]

Attachment: Firefox 57 en-GB update [Checked in: Comment 6]

Comment 3

[Ian Neal]

Attachment: Mobile 57 en-GB update [Checked in: Comment 6]

Comment 4

[Ian Neal]

Attachment: Thunderbird 57 en-GB update [Checked in: Comment 6]

Comment 5

[Ian Neal]

Attachment: SeaMonkey 2.54 en-GB update [Checked in: Comment 6]

Comment 6

[Ian Neal]

https://hg.mozilla.org/releases/l10n/mozilla-beta/en-GB/rev/c256cb77525cdc98f7bf58c5edf31faee8efe829
https://hg.mozilla.org/releases/l10n/mozilla-beta/en-GB/rev/18e839c988496073bd68d7f18b943ce277e0d98c
https://hg.mozilla.org/releases/l10n/mozilla-beta/en-GB/rev/21a6d2110c1c131c806631a81889d5e497df5195
https://hg.mozilla.org/releases/l10n/mozilla-beta/en-GB/rev/d468844d7c0a28b44c897ab3195474014df5012c
https://hg.mozilla.org/releases/l10n/mozilla-beta/en-GB/rev/ebed7a0da3727c7063c6927dc23f8941687469d4

Comment 7

[Francesco Lodolo [:flod]]

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.

Comment 8

[Francesco Lodolo [:flod]]

(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.

Comment 9

[Ian Neal]

(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?

Comment 10

[Francesco Lodolo [:flod]]

(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.