I created a custom shell script that tries to figure out the right values. Then you can use localize.py script in a modified way (see below) to automatically create translation files. (Line break, somewhere very important). If there are more objects to translate, the shell script can be modified accordingly.
#!/bin/bash
rm -f $2
sed -n 'N;/<key>Title<\/key>/{N;/<string>.*<\/string>/{s/.*<string>\(.*\)<\/string>.*/\/* \1 *\/\
"\1" = "\1";\
/p;};}' $1 >> $2
sed -n 'N;/<key>FooterText<\/key>/{N;/<string>.*<\/string>/{s/.*<string>\(.*\)<\/string>.*/\/* \1 *\/\
\"\1" = "\1";\
/p;}
;}' $1 >> $2
sed -n 'N;/<key>Titles<\/key>/{N;/<array>/{:a
N;/<\/array>/!{
/<string>.*<\/string>/{s/.*<string>\(.*\)<\/string>.*/\/* \1 *\/\
\"\1" = "\1";\
/p;}
ba
;};};}' $1 >> $2
localize.py script requires some modification. Therefore, I created a small package containing a localizer for the source code and for the plist files. The new script supports Duplikates (which means it will hit them)
gamma source
share