This affects Release through Nightly. es-ES also has this problem (bug 1211860), while es-AR and es-CL use “refrescar”. http://mxr.mozilla.org/l10n-mozilla-release/source/es-MX/browser/chrome/browser/safeMode.dtd http://mxr.mozilla.org/l10n-mozilla-beta/source/es-MX/browser/chrome/browser/safeMode.dtd http://mxr.mozilla.org/l10n-mozilla-aurora/source/es-MX/browser/chrome/browser/safeMode.dtd http://mxr.mozilla.org/l10n-central/source/es-MX/browser/chrome/browser/safeMode.dtd
Thanks for filing this bug. We have different Spanish locales is to allow such variance, however, so I wouldn't necessarily classify this as a bug. Roberto, can you verify whethe this is a bug or a translation preference?
As you can see, es-ES was fixed in the meantime; they went for “restablecer” rather than “refrescar” like es-AR and es-CL. The point of this report isn't to have everyone use the exact same verbatim translation. The Refresh Firefox button replaces the current profile with a fresh copy, tossing out add-ons and preferences. To restart Firefox means to close Firefox and start it back up again, leaving your data intact. This is a translation bug.
I think we should go with "restablecer" this time, for the same reasons that Gingerbread Man exposes.
It is fixed it. We will see the change very soon.
Nightly and FDE are fixed inconsistently: refreshProfile.label uses “restablecer” but refreshProfileInstead.label uses “refrescar”. Beta is still affected.
We should not be using "refrescar". Also, it is possible that the changes are not properly reflected on nightly, since we use (only) the aurora channel on es-MX. I'll give it a look, and I'm sure Roberto will do, too. :)