[Affected versions]: - latest Dev Edition 50.0a2 - latest Nightly 51.0a1 [Affected platforms]: - Windows 10 64-bit - Ubuntu 16.04 64-bit - Mac OS X 10.11 [Steps to reproduce]: 1. Launch Firefox. 2. Open Inspector: Ctrl + Shift + C (for Windows & Ubuntu) or Cmd + Opt + C (for Mac OS X). 3. Focus on the tab names from CSS pane. [Expected result]: - Strings are translated. [Actual result]: - Strings are not translated. [Regression range]: - Last good Nightly: 2016-07-16 - First bad Nightly: 2016-07-17 - Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4c05938a64a7fde3ac2d7f4493aee1c5f2ad8a0a&tochange=711963e8daa312ae06409f8ab5c06612cb0b8f7b - based on bug 1287391 comment 13 this looks like a regression of bug 1259819 [Additional notes]: - Screenshot: https://imgur.com/jrahnnK - Not reproducible with fr build - the strings are still translated; reproducible with ar and he build

:flod, strings were moved from a .dtd to a .properties file. Is there some messaging to do to make sure the strings get moved over for locales as well ?

(In reply to Tim Nguyen :ntim (use needinfo?) from comment #1) > :flod, strings were moved from a .dtd to a .properties file. Is there some > messaging to do to make sure the strings get moved over for locales as well ? It's great to see someone checking l10n, but this bug is invalid for a few reasons: * There are 5/6 locales working on Nightly, none of them is RTL. French and Italian are usually up to date, that's why French is OK. If you want to check localization issues in Nightly, Italian is your best pick. * Almost all locales work on aurora, which means the cycle started 3 days ago or so. Some of them catch up at the very end of the cycle. * Expecting Dev Tools to be localized in all languages is not realistic. Given the size (2.3k strings) and target, we actually want to reach a point where smaller locales can decide to not translate them at all, and fallback to a different language. Communication was already done through the localization channels, but given that most locales don't work on files but in tools, it's not just a matter of copying a string from a file to another, they will have to "retranslate" them, hopefully relying on translation memory from the tool of their choice. https://blog.mozilla.org/l10n/2016/08/01/firefox-l10n-report-aurora-50/