Neil Jerram <neiljer...@googlemail.com> writes:
> 2009/1/22 Simon Josefsson <si...@josefsson.org>:
>> Here it is. The module name and source filenames are rather long, but I
>> couldn't think of anything better. Untested, beware!
>
>> +void
>> +emit_bug_reporting_address (void)
>> +{
>> + /* TRANSLATORS: The placeholder indicates the bug-reporting address
>> + for this package. Please add _another line_ saying
>> + "Report translation bugs to <...>\n" with the address for translation
>> + bugs (typically your translation team's web or email address). */
>> + printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
>> + printf (_("%s home page: http://www.gnu.org/software/%s/\n";),
>> + PACKAGE_NAME, PACKAGE);
>> + printf (_("General help using GNU software:
>> http://www.gnu.org/gethelp/\n";));
>> +}
>
> If this is incorporated into a project as a Gnulib module, how should
> maintainers or translators do what the code instructs? (My impression
> thus far is that Gnulib module source should not be modified at the
> project level, because such modifications would be lost at the next
> import.)
I don't follow? The comment is aimed at translators, and translators
will add the 'Report translation bugs ...' line in the particular
gettext translation file. Thus, source code is not modified.
However, as far as I know there isn't a gnulib translation domain that
is automatically used for messages in gnulib code when you import it to
a project. So the strings above will end up in every project's *.po
files, to be re-translated again and again for every project.
/Simon
