gettext: Bug Report Address

1 
1 4.8 Letting Users Report Translation Bugs
1 =========================================
1 
1    Code sometimes has bugs, but translations sometimes have bugs too.
1 The users need to be able to report them.  Reporting translation bugs to
1 the programmer or maintainer of a package is not very useful, since the
1 maintainer must never change a translation, except on behalf of the
1 translator.  Hence the translation bugs must be reported to the
1 translators.
1 
1    Here is a way to organize this so that the maintainer does not need
1 to forward translation bug reports, nor even keep a list of the
1 addresses of the translators or their translation teams.
1 
1    Every program has a place where is shows the bug report address.  For
1 GNU programs, it is the code which handles the “–help” option, typically
1 in a function called “usage”.  In this place, instruct the translator to
1 add her own bug reporting address.  For example, if that code has a
1 statement
1 
1      printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT);
1 
1    you can add some translator instructions like this:
1 
1      /* TRANSLATORS: The placeholder indicates the bug-reporting address
1         for this package.  Please add _another line_ saying
1         "Report translation bugs to <...>\n" with the address for translation
1         bugs (typically your translation team's web or email address).  */
1      printf (_("Report bugs to <%s>.\n"), PACKAGE_BUGREPORT);
1 
1    These will be extracted by ‘xgettext’, leading to a .pot file that
1 contains this:
1 
1      #. TRANSLATORS: The placeholder indicates the bug-reporting address
1      #. for this package.  Please add _another line_ saying
1      #. "Report translation bugs to <...>\n" with the address for translation
1      #. bugs (typically your translation team's web or email address).
1      #: src/hello.c:178
1      #, c-format
1      msgid "Report bugs to <%s>.\n"
1      msgstr ""
1