First of all, thanks for the explanations and the links.
While playing around with the changes that you proposed in your patch, I discovered the following (I used the package currently available in the repository of lucid): I only have to delete the following line from the setup command in setup.py in order to have the strings from the ui file merged into the POT template.
('share/onboard/data', glob.glob('data/*.ui*')),
So it seems that the ui file is automatically merged in the POT template only if it is also automatically picked up; it must not be explicitely added to the package with a line in the setup command.
And now, there is not any difference anymore between creating the POT template by using the "./setup.py build_i18n" command and the "dpkg-buildpackage -b" commands. (In fact, the langpack.mk rule fixed the problem only for "dpkg-buildpackage -b" and not for "./setup.py build_i18n"; I thought that this difference should be solved through the usage of a POTFILES.in file, but it turned out that the POTFILES.in file is not necessary either in both cases. )
Tomorrow, I will try to understand why the setup.cfg file is not necessary anymore, as your patch is suggesting.
Hi David,
First of all, thanks for the explanations and the links.
While playing around with the changes that you proposed in your patch, I discovered the following (I used the package currently available in the repository of lucid): I only have to delete the following line from the setup command in setup.py in order to have the strings from the ui file merged into the POT template. onboard/ data', glob.glob( 'data/* .ui*')) ,
('share/
So it seems that the ui file is automatically merged in the POT template only if it is also automatically picked up; it must not be explicitely added to the package with a line in the setup command.
And now, there is not any difference anymore between creating the POT template by using the "./setup.py build_i18n" command and the "dpkg-buildpackage -b" commands. (In fact, the langpack.mk rule fixed the problem only for "dpkg-buildpackage -b" and not for "./setup.py build_i18n"; I thought that this difference should be solved through the usage of a POTFILES.in file, but it turned out that the POTFILES.in file is not necessary either in both cases. )
Tomorrow, I will try to understand why the setup.cfg file is not necessary anymore, as your patch is suggesting.
Thanks again for all your help.