Kenneth Nielsen wrote: > Isn't manually uploading to compensate for lack of automatic > integration of upstream translations, a bit like peeing in your pants > to stay warm? As far as I know, as soon as you upload manually it > counts as a LP translation, which means that all the usual fun and > horror with override priorities start kecking in. Personally I would > leave it, the only effect the users will see are bad translation for > the first month or so, but I really don't think it is worth > introducing permanent work for us to fix that.
I can't say I've tried that method of staying warm, but manual uploads can make sense: the Ubuntu package builds pump hundreds of thousands of files into the translations import queue, and some proportion of them will fail. And it's not usually clear who should be notified about those failures. If somebody then steps up and re-uploads the files that failed to import, the system will notify them of any errors and they can be handled on a case-by-case basis. For instance, we just discovered that a bunch of KDE files used a bit of syntax that our parser couldn't handle: "#~|" to mark old msgids of messages that are both fuzzy and obsolete. So we stripped out the offending lines and re-uploaded just the affected files. There were only about 1400 of these, so the automated "blind" upload took care of most of the work and made it possible to do something about the missing ones. Something else I'd like to do about this (when there is time! :-/ ) is to make the failure messages accessible from the import queue UI. See the blueprint here: https://blueprints.launchpad.net/rosetta/+spec/import-queue-failed-error-display Jeroen -- ubuntu-translators mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
