Hi,
Some of you may have noticed a few strings showing up as untranslated in
Pootle for Firefox 53 (Aurora).
That's not the result of string freeze being broken. A duplicated string
in netmonitor.properties caused a parsing error, and these strings were
not available for translation (other tools are not affected). That
explains also why some locales were complete in Pootle, but were still
showing 1 missing string on the l10n dashboard for Firefox.
The problem has been fixed over the week-end, thanks to the Pootle team
for the quick action.
If you work on Pootle (or did in the past), I have another ask, as
explained also in a previous message: check out for stray accesskeys,
especially when you accept a suggestion from translation memory.
1. Go to Transvision:
https://transvision.mozfr.org
2. Make sure that your locale is selected for Target Locale, and
Repository is Aurora
3. Search for &
4. Scroll down the page until you reach the second table, "Displaying X
results for the string & in YOUR_LOCALE:".
If the original string doesn't have a &, and yours does without a
good reason, you have an error. You can use the <edit in Pootle> link to
reach directly the string in Pootle.
Francesco