A bug has been opened in the Gettext bug tracker about this issue:
https://savannah.gnu.org/bugs/?49654
In my opinion (as former Gettext maintainer) the fix ought to go into
msgfmt, not xgettext.
The gettext.diff.txt patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792687
is
Hello,
Daniel Shahaf wrote:
> Putting the fix into msgfmt is an option when the .mo file needs to be
> reproducible
Yes, .mo files are binary files, installed on the end users' systems. Therefore
we've made .mo files reproducible [1].
> but I'm facing an issue where I'd like the .pot file
>
Daniel Shahaf wrote:
> > it's plain text, and it's a small diff.
>
> This doesn't scale. (For example, in my use-case, I'm dealing with a
> 5000-line unified diff full of one-line changes in date strings and C
> comments and any number of other things. My goal is to get the number of
> lines
Santiago Vila wrote:
> But so far, the non-reproducible Debian packages using gettext I've
> seen fail to be reproducible because maintainers insist on
> regenerating a .pot file at build time and performing msgmerge on all
> the .po files with the newly generated .pot file "just in case", or
>
