For the maintainer, the general procedure differs from the C language case in two ways.
gettextizeprogram without the ‘--intl’ option, and that he invokes the
AM_GNU_GETTEXTautoconf macro via ‘AM_GNU_GETTEXT([external])’.
XGETTEXT_OPTIONSvariable in po/Makevars (see po/Makevars) should be adjusted to match the
xgettextoptions for that particular programming language. If the package uses more than one programming language with
gettextsupport, it becomes necessary to change the POT file construction rule in po/Makefile.in.in. It is recommended to make one
xgettextinvocation per programming language, each with the options appropriate for that language, and to combine the resulting files using