Messy tab_queue_notification_settings

[Michal Stanke]

Hi.

We are facing a problem with one fennec string, partially because how it
was escaped by Pontoon and partially how the string is. I am talking
about tab_queue_notification_settings in
mobile/android/base/android_strings.dtd. Dashboard is complaining
<https://l10n.mozilla.org/dashboard/compare?run=569064> about unescaped
/&quot;/ (which is copied from English) and I am complaining about
/\&apos;/ placed to our translation, where /\'/ in original is. ;)

Just compare English
<https://hg.mozilla.org/releases/mozilla-aurora/file/a64f10073370/mobile/android/base/locales/en-US/android_strings.dtd#l272>
and Czech
<https://hg.mozilla.org/releases/l10n/mozilla-aurora/cs/file/7b339432800f/mobile/android/base/android_strings.dtd#l272>.
--
Michal Stanke

[Matjaz Horvat]

If you use the source string as translation, you get the same error:
http://hg.mozilla.org/releases/l10n/mozilla-aurora/sl/rev/5c7fb10f723e
https://l10n.mozilla.org/dashboard/compare?run=569226

So it's a bug in the source sting:
https://bugzilla.mozilla.org/show_bug.cgi?id=1205216#c32

Thanks for reporting, Michal. And to Sebastian for testing. We should
expect the string to be changed soon.

Context: Fennec DTD files located in the mobile/android/base folder
require special escaping of quotes and apostrophes:
http://developer.android.com/guide/topics/resources/string-resource.html#FormattingAndStyling

So when exporting translations, Pontoon replaces quotes (") with
\&quot; and apostrophes (') with \&apos;. The original string however
contains &quot; without the backslash, which is not allowed. And if
you re-use it in the translation, it breaks.

To fix the error, you can replace &quot; with " in your translation.
But you might need to do it again after the original string changes.

-Matjaž

> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n

[Michal Stanke]

Thank you for the info. If the string is going to change, but keep the
entity name, I will rather remove it from our translation now and wait
until it's fixed, so we won't forget.

Michal Stanke

Dne 29.1.2016 v 20:32 Matjaz Horvat napsal(a):