Comment 4 for bug 1464159

Mistery solved:

<dpm> oSoMoN, so what I've done is to change the translation domain in the source package in LP from "oxide" to "oxide-qt". If I remember correctly, this will make the translations to be exported as "oxide-qt" in the next language pack export. I'd suggest to check with pitti next time the langpacks are built
<oSoMoN> dpm, thanks! How come this domain is hardcoded, instead of extracting the domain name from the filenames installed by the package?
<dpm> oSoMoN, the first time a source package that contains translations is uploaded, LP asks for the template name (how it will be shown in the translations URL) and for the domain (filename to export as in the langpacks). IIRC, LP does a guess and sets domain = source package name, which admins can manually override. Perhaps the first upload the source package was named "oxide"?
<oSoMoN> dpm, in fact the mo files used to be named oxide.mo, but were renamed oxide-qt.mo at some point, so the initial setup made sense
<dpm> so that was probably it. The setup made sense initially, but then the domain in LP wasn't updated according to the change

So this should be fixed with the next langpack update.