I agree that having the .pot file in the source tree is not ideal, but
it's the easiest way to get translations automatically imported in
Launchpad. The other option is to manually upload the .pot template
every time it is updated.
Launchpad used to have support for automatically generating .pot f
Fix committed into lp:address-book-app at revision 117, scheduled for
release in address-book-app, milestone ubuntu-13.07
** Changed in: address-book-app
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinator
We should not have the .pot committed to the tree. It will very easily
result in situations with conflicts between trunk and proposed branches.
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching
** Changed in: unity-scope-click (Ubuntu)
Assignee: (unassigned) => Alejandro J. Cura (alecu)
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
h
Public bug reported:
The click scope needs to be set up for translations.
In summary, to make translations happen, we need to:
- Have a top-level po folder to contain translations
- Have the build system generate a .pot template that is committed to the
source tree
- Have the .deb package creat
5 matches
Mail list logo
