ubuntu-translations-coordinators team mailing list archive

[Gabor Kelemen <kelemeng@xxxxxxxx>]

Since we no longer use LP Translations for FF, I think this is obsolete
now.

** Changed in: ubuntu-translations
       Status: Triaged => Invalid

** Changed in: firefox (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/705392

Title:
  The generated en-US.xpi translation template lacks branding

Status in Ubuntu Translations:
  Invalid
Status in “firefox” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  During a package build we create a en-US.xpi file, which is
  essentially a language pack with all the translatable strings in
  Firefox, in English. This file is then imported upon upload and is
  used as a template to be translated into all other languages.

  I've noticed that this generated en-US.xpi file, unlike the one
  available upstream [1], is missing the /chrome/en-US/locale/branding/
  folder in its contents.

  This causes the translatable strings in there not to be exposed in
  Launchpad, and thus not be translatable. This in turn prevents some
  teams to translate (transliterate would be more correct in some cases)
  the brand names in their languages or scripts.

  An example: in Arabic, Firefox should be فَيَرفُكس, but it cannot be
  translated this way because of this bug.

  Would it be possible to generate the en-US.xpi file with the branding
  folder? Otherwise, how are the files at [1] generated?

  [1]
  http://releases.mozilla.org/pub/mozilla.org/firefox/releases/4.0b9/linux-i686/xpi
  /en-US.xpi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/705392/+subscriptions