Configuration option: store translations in single .pot file
The way I understand gettext support in sphinx tip right now is that one .pot file per section is created and that for every language .po/.mo files for each section are necessary.
I set up a very primitive example where I after calling "make gettext" get a .pot file for every .rst file in _build/locale.
The standard gettext layout is to either have one .pot file (po/project.pot) or numerous templates (template1/template1.pot, template2/template2.pot...). The translations itself are stored alongside the .pot file, named after their ISO 639 code (po/project.pot, po/ca.po, po/de.po...). An example of this can be found at http://git.gnome.org/browse/gedit/tree/po
As a side-note: .mo files are for the user later on installed into /usr/share/locale (ie: /usr/share/locale-langpack/de/LC_MESSAGES/gedit.mo).
For our work-flow it would be great if this was possible. Launchpad, our online translations tool, follows the standard gettext format. In it, .pot files are imported and translators would need to choose all available message catalogues one after another and translations would be split up in various files later on.
In the single .pot file case (https://translations.launchpad.net/ubuntu/maverick/+source/gedit/+pots/gedit/de/+translate) for example Launchpad paginates the strings (and looks in other projects for suggestions to translate).
It would be great if there was a translation_in_single_catalog option to allow above mentioned work-flow.