"Stefan Monnier" <monn...@iro.umontreal.ca> writes:
>>>> + printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
> [...]
>> 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.
>
> In the above line's case it's a feature rather than a problem.
> Otherwise, there would be no way for the translation team to give
> a different email address for translation bugs of different packages.
Oh. Good point.
Sergey Poznyakoff <g...@gnu.org.ua> writes:
>> There actually is, although I admit I don't know how the messages get
>> integrated into the gnulib-using packages:
>> http://translationproject.org/domain/gnulib.html
>
> It is a "compendium" domain, and is used by translators when preparing
> their .po files. The translator gets the gnulib.po file from the
> corresponding language team and incorporates it into his $project.po by
> using msgcat+msgmerge.
Ah, interesting, I wasn't aware of this feature. Do I as maintainer of
projects using gnulib have to do anything special to make this usable
for translators?
Thanks,
/Simon
