Closed Bug 1303742 Opened 9 years ago Closed 8 years ago

Context menu New Tab strings not localized in Polish Firefox for iOS 5.2 (1)

Categories

(Firefox for iOS :: Localization, defect)

Product:
Firefox for iOS
Component:
Localization
Platform:
Other
iOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: stef, Unassigned)

References

Details

This is probably direct result of https://github.com/mozilla-l10n/firefoxios-l10n/commit/03edbe512273abbfdfd5cd6ae7912459b3241a56 but am I missing something or such strings (still used in released version) removal (from en-US) is against the rules?
Summary: Context menu New Tab strings not localized in Polish TestFlight 5.2 (1) → Context menu New Tab strings not localized in Polish Firefox for iOS 5.2 (1)
I have to admit that I don't know if there are rules concerning removal of strings still used in release version... Also, better not to translate on master as this wouldn't happen.
(In reply to Delphine Lebédel [:delphine - use need info] from comment #1) > I have to admit that I don't know if there are rules concerning removal of > strings still used in release version... Also, better not to translate on > master as this wouldn't happen. Yes, in this case not translating master would hide that problem but in general it doesn't change much.
Flags: needinfo?(francesco.lodolo)
Delphine owns mobile, including iOS, so not sure why the needinfo for me. The rule is indeed to not remove strings from en-US if they're still shipping, in fact they haven't been removed from the l10n repository yet, they will be removed when localization for 6.0 starts. The problem is that you're localizing against master, and we've warned you in several occasions that this could happen.
Flags: needinfo?(francesco.lodolo)
Do I understanding correctly that these strings somehow won't be removed for 6.0 localization?
If they're already removed from master, they should not be in 6.0, as far as I can understand their development cycle.
Then this problem seems general and will affect all locales in case of 5.x release after l10n drivers will "allow" 6.0 translations.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Would it be too much to ask for justification?
You need to log in before you can comment on or make changes to this bug.