Right, when projects use Launchpad to do upstream translations the .pot needs to live in bzr trunk to get imported. But most Ubuntu packages only build the POT during package build and thus get imported into Launchpad as *ubuntu package* (not upstream project) translations.
The langpacks that we build are always built from Ubuntu package translations. They usually sync with upstream's (called "message sharing"). The slight advantage of also translating strings in the upstream project is that LP can (and usually is) be configured to directly commit them to trunk, and thus the turnaround between doing translations and getting langpack updates from them is just minutes. With Ubuntu translations you need to release/upload the project first and wait for a new LP export of Ubuntu translations. (langpack-o-matic has the script "merge-touch- upstream-translations" for that, which is a hack intended to speed up translations and the move to langpacks, but isn't intended to be a long- term thing). So in summary, it's fine to do like the indicators and translate in Ubuntu only as long as there is an up to date POT being built during package build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348825 Title: Transfer indicator needs internationalization To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1348825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
