Code review comment for lp://qastaging/~seb128/ubuntu-docs/updated-translations
Revision history for this message
| David Planella (dpm) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
The way imports work in Launchpad is that at build time translations (the .pot file and all .po files) are extracted from the package, put together in a tarball and then fed to Launchpad Translations.
This is the point where translations enter the translations imports queue (e.g. [1]). This is what happens after for a package like ubuntu-docs:
1. The .pot file is examined, including format correctness checks
2. If it's correct and it can be matched to an existing template in Ubuntu [2], it is imported, and Launchpad is then updated with the latest translatable messages
3. Once the template is imported, then all its associated .po files are imported too
Where we've got issues sometimes is when a package does not create a .pot file during the build. In that case, the tarball fed to Launchpad only contains the .po file and Launchpad does not know what to do with it. I.e. it knows the source package they belong to, but not the template.
Looking at the imports queue, I don't see any .pot file waiting to be imported, so my hunch is that the .po files from the 04.07. upload were missing a .pot file, so they ended up in the queue and they will never got imported (unless someone manually goes through them one and approves them one by one).
I don't think it's critical that they are not imported, as translations for ubuntu-docs happen exclusively in Launchpad and they are already on the database. The critical part for ubuntu-docs is to make sure the .pot file is kept up to date.
[1] https:/
[2] https:/