On Tue, Apr 26, 2016 at 09:32:02PM +0200, Daniel Pocock wrote: > > > It is well documented how developers should create po files for i18n > support in their debconf configuration questions during package install[1]. > > What about arbitrary scripts that are run from the command line and > don't use debconf to store the user responses? How should they interact > with whiptail and translated strings? Is there either a document > explaining how to do this or any existing script that provides a good > example, in a way that makes it easy for Debian translators to support > the package containing the script? the gettext documentation itself? https://www.gnu.org/software/gettext/manual/html_node/Preparing-Shell-Scripts.html All you need to do is make sure is that the installed package puts the compiled .mo files in the right location so gettext finds them. During development, you can probably export some environment variable to make gettext look for translations in your development tree.
Attachment:
signature.asc
Description: PGP signature