Closed Bug 933323 Opened 6 years ago Closed 6 years ago
Ensure new about:home is properly localized before shipping Firefox 26
No description provided.
From email: Czech (ca), Irish (ga-IE), Magyar (hu), Korean (ko), Brazillian Portuguese (pt-BR), Portuguese (pt-PT), Romanian (ro), Ukranian (uk) are mostly affected here. From IRC: gueroJeff> mfinkle: I've been approving sign-offs that contain those localizations on Beta today. pt-PT, for example, was just approved and has those strings localized We'll use this bug to keep a relnote on 26 Beta regarding known issue with some locales not being complete but keep picking up new l10n changesets throughout Beta to increase the completion of this localization while on Beta.
(In reply to Erin Lancaster [:elancaster] from comment #2) > Should we refresh the notes for beta 1 to include this? This is in the Known Issues section of the notes, I'm not sure why Lucas removed the flag (please don't do that, we set them according to what's in our relnotes db).
We really ought to put very visible known issues directly written on Google Play and not hidden at the bottom of release-notes but that's another story
thank you! the removal of the flag was likely a triage snafu...
Is Beta 2 in a better state? If so, this can be resolved.
(oh we didn't set a target candidate, nm)
I expect beta 2 to be in a much better shape. AFAICT, only ga-IE, ro, and uk are open at this point.
Let's keep this open until all the listed locales are up to snuff. (In reply to Aaron Train [:aaronmt] from comment #4) > We really ought to put very visible known issues directly written on Google > Play and not hidden at the bottom of release-notes but that's another story that should be directed to Jesse Montano who is managing the Play Store copy - Jesse can you update the What's New for Firefox 26 Beta?
We're about to ship FF26 and this is, afaik, complete so resolving.
Firefox 26 Beta 8 Device Galaxy Nexus Strings were translated starting Beta 2. I will set this to verified fix.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.