The generated en-US.xpi translation template lacks branding

[David Planella]

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

[Chris Coulson (chrisccoulson)]

This is deliberate, to handle abrowser (which works by providing alternate strings for the branding message ID's). If we translate these in Launchpad, then the abrowser branding will stop working (it will always show the Firefox branding strings from the language packs)

[David Planella (dpm)]

El dj 20 de 01 de 2011 a les 13:21 +0000, en/na Chris Coulson va
escriure:
> This is deliberate, to handle abrowser (which works by providing
> alternate strings for the branding message ID's). If we translate these
> in Launchpad, then the abrowser branding will stop working (it will
> always show the Firefox branding strings from the language packs)
>

Ah, didn't know about that.

Still, I'm not sure I can quite follow it. Chris, could you explain in
more detail how the abrowser branding works? I can't quite figure out
how translators can provide localized branding through that.

Thanks!

[Gabor Kelemen (kelemeng)]

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