Translations for installed apps not displayed

Indeed, what's the story for translating apps? Is Path= from the .desktop file added to gettext's locale path or something? We should employ the same approach for desktop parsing.

Another area is click scope, that takes most of its data online - does it support requests for other languages? And does the scope take the locale into account?

Translations for the app themselves are handled separately. The path to load translations from is set in the app with i18n.textdomain, which generally developers won't even need to set, as the SDK takes care of it (*).

See comment #2 from Sergio on bug 1233071 about Unity finding the translations from the desktop files.

As per the translations of the click scope desktop files (and descriptions) I believe these will need to be handled differently, as they live on the store. I'm subscribing Martin Albisetti for this one, as he can provide more details, but I think we'll need a separate bug for loading translations from the click scope.

(*) Or will do it, once the fix for bug 1233071 lands

Right, so any translation of the metadata about the app needs to be added in the store.
There's currently no programatic way of adding it, you will need to enter the translations in the store's web ui.

The translations for the apps that we install by default are already available in the click packages, and in terms of maintenance it'd be much easier to load them from there - they're placed there automatically vs. manually uploading them to the store's web UI.

Could Unity 8 (or whichever part of the stack that shows the apps' desktop files in the Launcher and in the Applications scope) not just load those, in the same way translations for the app itself are loaded?

Also, if translations from the .desktop files are not loaded from the already available local .mo files and from the store instead, they'd appear in English until there is a network connection.

That's different for installed apps, though: those should load the translations from the .mo files available locally.

From the IRC conversation:

<Saviq> dpm, the scope needs to load them
<Saviq> dpm, so for installed apps it needs to come from the .mo files, but for remote ones - all translations need to be in the store
<Saviq> dpm, also, ideally the store would just extract them from .mo files, too
<dpm> Saviq, I fully agree on that one, but I think that might a bit more complex and perhaps be step 2

I've split this into two bugs; this one for the translation of installed apps, and bug #1314781 for the translation of available apps, as we get the data for each from different places, so the fixes will be different and independent.

This bug was fixed in the package unity-scope-click - 0.1+14.10.20140508.1-0ubuntu1

---------------
unity-scope-click (0.1+14.10.20140508.1-0ubuntu1) utopic; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Rodney Dawes ]
  * Support for translations of installed apps. (LP: #1237992) Fix
    translations not being installed. (LP: #1316802) Fix merge of
    translations to clickscope.ini. (LP: #1316778) Strip full path from
    translations and template. (LP: #1316777) Enable submission of
    reviews from the installed preview. (LP: #1237992, #1316777,
    #1316802, #1316778)
 -- Ubuntu daily release <email address hidden> Thu, 08 May 2014 18:24:59 +0000