If multiple scripts have the same TEXTDOMAIN, for example:
then just one myapp.pot file and hence myapp.mo file will be created for all of those scripts.
Some people prefer this, as it is more efficient than having one .pot file for each script.
Note that these multiple scripts with same TEXTDOMAIN can be located anywhere. They do not have to be in the same directory.
A pre-existing .pot, for example /usr/share/doc/nls/myapp/myapp.pot, will automatically be used, instead of generating it from the script(s).
I could not see any reason why this should not be automatic.
Check out the changes in /usr/sbin/momanager, Woof commit:
A note about entering the TEXTDOMAIN into scripts:
...do not put quotes, do not append any comment, do not indent! Any of those might break MoManager.
Comments:Posted on 31 Jul 2012, 23:16 by BarryK
...um, no, appending comments should be ok.
Posted on 32 Jul 2012, 5:24 by rodin.s
New MoManager is great
Thank you. Than is just great. I have been testing it on my PETs here: http://www.murga-linux.com/puppy/viewtopic.php?p=643807#643807 (Some of those scripts could be added to Woof: SFS-converter, mtsnapshot) Now MoManager is more flexible.
Posted on 32 Jul 2012, 5:36 by L18L
MoManager enhanced is great
Thank you Barry
My 1st working example, pfilesearch-1.31: