If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[ku] Firefox Sync feature inconsistently localized



Mozilla Localizations
ku / Kurdish
7 years ago
7 years ago


(Reporter: Pike, Unassigned)


Firefox Tracking Flags

(Not tracked)





7 years ago
In http://hg.mozilla.org/l10n-central/ku/file/ffd2a5d90c44/browser/chrome/browser/syncBrand.dtd, Sync is either Sync or Senkronîzekirina, that's confusing. In other locales, Ragavan (Sync lead) favored to keep the name to just Sync and "Firefox Sync".

Anyway, it should really be consistent.

I'll not block b4 on this, but we should really get this fixed for final.

Comment 1

7 years ago
CCing Erdal, doesn't seem to be watching the Kurdish bug component. Should we set up an alias so that that's independent of following amed?

Comment 2

7 years ago
Yep, that would be good. We should both follow the Kurdish bug component.

Comment 3

7 years ago
For the bug, I understand "Sync" in "Sync tabs" as a verb, while it is a noun in "Firefox Sync". That is a reason for different translations. But I'll check the contexts again on the nightlies.

Comment 4

7 years ago
Nope, it's both referring to the feature name, once with and once without "Firefox" as context, that is, both are nouns.

Also, this is just within syncBrand.dtd, where just "Sync" is "Sync", and "Firefox Sync" is translated with "Senkronîzekirina Firefoxê"

Comment 5

7 years ago
I don't claim it's consistent, you are right, it is inconsistently translated. 

But if I am asked in the menu like this:

Minefield will:

[ ] Sync Bookmarks
[ ] Sync Passwords

then sync is a verb (Lesezeichen synchronisieren etc.). So it here it has to be translated differently.

Comment 6

7 years ago
Fixed in Narro, changed translation of "Firefox Sync" to "Firefox Sync". Will be pushed in a while.
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 7

7 years ago
Filed bug 590881 on the bug component changes, fwiw.
You need to log in before you can comment on or make changes to this bug.