Hi, I haven't tested this, but just wanted to add that this note about gettext domains/catalogues.
With linux packaging it makes sense to split the tools that use wx from the tools that don't e.g. on fedora the 'hugin-base' package can be installed independently of the 'hugin' package. So it would make sense that if all the tools are to be translatable then there should be two domains (i.e. two .pot files).
i.e. these are all the tools that use wx and that would be in the 'hugin' domain:
Hi, I haven't tested this, but just wanted to add that this note about gettext domains/catalogues.
With linux packaging it makes sense to split the tools that use wx from the tools that don't e.g. on fedora the 'hugin-base' package can be installed independently of the 'hugin' package. So it would make sense that if all the tools are to be translatable then there should be two domains (i.e. two .pot files).
i.e. these are all the tools that use wx and that would be in the 'hugin' domain:
/usr/bin/PTBatcher PTBatcherGUI hugin_stitch_ project
/usr/bin/
/usr/bin/hugin
/usr/bin/
/usr/bin/icpfind
/usr/bin/nona_gui
...these are the tools that don't use wx and which should be in a separate 'hugin-base' domain:
/usr/bin/ align_image_ stack autooptimiser calibrate_ lens celeste_ standalone deghosting_ mask hugin_hdrmerge matchpoint pano_modify pano_trafo tca_correct vig_optimize
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/checkpto
/usr/bin/cpclean
/usr/bin/cpfind
/usr/bin/
/usr/bin/fulla
/usr/bin/
/usr/bin/keypoints
/usr/bin/
/usr/bin/nona
/usr/bin/
/usr/bin/
/usr/bin/pto2mk
/usr/bin/pto_merge
/usr/bin/
/usr/bin/
This has an advantage in that translators can choose to just work on the GUI tools, or they can choose to work on both catalogues.