Although I agree that using Python would make things easier for internationalisation, in the meantime I'm attaching a patch to complete the current package's i18n support.
A few notes:
* The current sources already had gettext calls in debian/local/Failsafe/failsafeXinit. Apart from modifying some of those calls, basically what remained to be done was to extract the strings from that source file and put them in a POT template. This POT template is now generated during the package build, so that it can be imported into Launchpad.
* I do not know of any standard approach to gettextizing shell files (intltool does not support them, so I had to use xgettext directly), so I've used a POTFILES.in file in a similar way to intltool-based packages. There might be more elegant approaches, but this should give you an idea of what is needed.
* My Debian packaging skills are limited, so if the modifications in debian/rules are not appropriate, let me know and I'll fix it.
Although I agree that using Python would make things easier for internationalis ation, in the meantime I'm attaching a patch to complete the current package's i18n support.
A few notes:
* The current sources already had gettext calls in debian/ local/Failsafe/ failsafeXinit. Apart from modifying some of those calls, basically what remained to be done was to extract the strings from that source file and put them in a POT template. This POT template is now generated during the package build, so that it can be imported into Launchpad.
* I do not know of any standard approach to gettextizing shell files (intltool does not support them, so I had to use xgettext directly), so I've used a POTFILES.in file in a similar way to intltool-based packages. There might be more elegant approaches, but this should give you an idea of what is needed.
* My Debian packaging skills are limited, so if the modifications in debian/rules are not appropriate, let me know and I'll fix it.
* This patch needs testing.