[I think that this topic fits better in the Ubuntu Unity Development category to be seen by the right people, but I’m not allowed to post a new topic there. Can some administrator please move it into that category.]
We got this message from a translator who asked how to correct translations of indicator-datetime.
The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs.
Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe, and that’s the reason for the current somewhat unclear situation. It’s important that the Unity7 team makes a decision about how to deal with translations going forward.
As @seb128 pointed out in a reply, it’s possible to re-enable the LP translation interface and the language packs for the Unity packages. The translations of those packages are generally in good shape, and this would probably be the smoothest solution.
For that to happen, someone needs to go through all the packages, add the line
to the debian/control file in each package source (where it’s not there already), and upload.
One idea is to file a bug report and there state each affected package.
Since this is about simply adding a line, I don’t think that merge requests would be helpful. I rather think that it’s just as easy for someone with upload rights to just do it based on the list of packages in the bug report.
That’s a step in the right direction, @khurshid-alam, but please note that this is not just about the indicator-* packages, but also about for instance:
In other words, I think that the whole Unity stack needs to be considered. Possibly some packages include that line already, but all packages which don’t - and if they include translatable strings - must be changed.
I’m not a ‘Unity 7 dev’ per se but I don’t know anyone who actually is? We’re all just trying to help as (near-)complete novices to keep Unity in universe?
@dale-f-beaudoin or someone else…do you have a manifest of the ubuntu-unity.iso? That might be helpful…but I guess this needs sorting ASAP and Dale might not be around in time
This Package Search Result (packages with ‘unity’ in their names in universe in bionic) might be useful but presumably some of those dependencies need fixing as well? Also do the doc ones need fixing or not?
As regards affected packages, I run a command which resulted in this list. Possibly something to work with…
Now, after some observations stated in the bug report, it seems like the state of Unity package translations is worse than I thought. Many packages includes a setting which tells the package builder to strip the translations from source, and at the same time no translations will be included in the langpacks without action.
So yes, as @ads20000 said, this is indeed urgent. If it’s not sorted very soon, we may end up with a Unity desktop in 18.04 with a lot of translations absent.
I have asked @seb128 for advice on certain things, and we won’t proceed with package uploads before he has responded.
U-c-c and u-s-d both use X-Ubuntu-Use-Langpack: yes. Although lack of template could be a problem. Why they got deleted? As for u-s-d most translation is done at gnome-settings-daemon (usd doesn’t really have a data folder). We can skip lenses and scopes for now. I am going to drop those lenses which doesn’t work anymore.