1413878 - Unlocalized strings in 9.3

Status: RESOLVED WONTFIX

(Firefox for iOS :: General, enhancement)

Description

[Stefan Plewako [:stef]]

Version 9.3 contains many untranslated strings (like in hamburger menu or in settings). This might be caused by broken l10n process that dosn't handle branching or sth elese.

Comment 1

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

This is very unfortunate. I think we've made the mistake to ship 9.3 while localization effort for 10.0 was already ongoing. That resulted in a renamed string table.

What we should have done is tag the repository before we announced / exported the strings for 10.0. So that we have a known version of the strings that we can use for the 9.x releases. This is something we need to start doing as a habit to prevent mistakes like this.

(Note that tagging would not work for .pl since you work off master and have your own timeline. Even if I go back in time now and pick the date before the export, I cannot guarantee that .pl is correct.)

I'll talk to the team and find out if we can still do a 9.4 release. It may be too late.

Comment 2

[Stefan Plewako [:stef]]

(In reply to Stefan Arentz [:st3fan] from comment #1)
> This is very unfortunate. I think we've made the mistake to ship 9.3 while
> localization effort for 10.0 was already ongoing. That resulted in a renamed
> string table.
> 
> What we should have done is tag the repository before we announced /
> exported the strings for 10.0. So that we have a known version of the
> strings that we can use for the 9.x releases. This is something we need to
> start doing as a habit to prevent mistakes like this.

I don't think that tagging or tagging around next version strings export time is the best option but having known and reliable process would improve things a lot.

> (Note that tagging would not work for .pl since you work off master and have
> your own timeline. Even if I go back in time now and pick the date before
> the export, I cannot guarantee that .pl is correct.)

I don't know where you get that but it is completely wrong. It would be great if you would stop spreading FUD about things that you don't have enough information. Between Spt. 14 (9.0 l10n deadline) and Oct. 12 (latest templates release) there was nothing in https://github.com/mozilla-l10n/firefoxios-l10n/commits/master/pl that would make strings appear untranslated in dot release. From my perspective whole responsibility falls on l10n drivers team and your comment is really inappropriate.

Accidentally, I just filled very similar bug for Focus, https://github.com/mozilla-mobile/focus-ios/issues/649

Comment 3

[Justin D'Arcangelo [:justindarc]]

Too late to fix this now.