It seems like the target languages for bq are covered there too.
Depending on whether the translations are shipped in a click package or as a .deb package, the developer will need to do some work to integrate and ship the translations.
Looking at https://translations.launchpad.net/ubuntu/wily/+source/unity-scopes-shell it seems it's shipped as a .deb package, in which case, I'd recommend using the same setup as other scopes shipped by default. In summary, it's about ensuring that the .deb package generates a .pot file on build, which boils down to:
1. Add X-Ubuntu-Use-Langpack: yes to debian/control's source record
2. Use dh_translations to generate a POT file during the build process.
A call was sent to translators on the 16th of June [1], and the upstream project is translated into 23 languages already:
https:/ /translations. launchpad. net/unity- scopes- shell/trunk
It seems like the target languages for bq are covered there too.
Depending on whether the translations are shipped in a click package or as a .deb package, the developer will need to do some work to integrate and ship the translations.
Looking at https:/ /translations. launchpad. net/ubuntu/ wily/+source/ unity-scopes- shell it seems it's shipped as a .deb package, in which case, I'd recommend using the same setup as other scopes shipped by default. In summary, it's about ensuring that the .deb package generates a .pot file on build, which boils down to:
1. Add X-Ubuntu- Use-Langpack: yes to debian/control's source record
2. Use dh_translations to generate a POT file during the build process.
[1] https:/ /lists. ubuntu. com/archives/ ubuntu- translators/ 2015-July/ 006949. html