Actually, unity-firefox-extension is only set up for translations in the
upstream project [1]

It needs to also be set up for translations in the source package [2] as
any other Ubuntu translatable package. Not being there means there is no
visibility from translators. Ubuntu Translators do their work on
https://launchpad.net/ubuntu/quantal rather than on every separate
project (*)

Right now, due to this reduced visibility it is only fully translated
into one language and partially into 2 other. I didn't even know it
existed.

So please, ensure that the package creates a .pot file during the build
(e.g. with dh-translations), so that translations can be imported and
exposed into Launchpad. In terms of shipping the translations, I haven't
looked at the code, but I'm guessing that it being a Mozilla extension,
we'll need to manually merge them in the package. Otherwise, we can just
export them in the language packs.

Let me know if I can help in anything.

[1] 
https://translations.launchpad.net/unity-firefox-extension/trunk/+pots/unity-firefox-extension
[2] https://launchpad.net/ubuntu/quantal/+source/unity-firefox-extension

(*) Admittedly some teams do translate projects upstream, but it is
pretty difficult to keep track of individual upstreams unless they are
part of a big project (e.g. GNOME)

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

Title:
  Typos in strings to translate in template "Unity-Firefox-extension"

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-firefox-extension/+bug/1055803/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to