Bug 3663 - Packaging: po/pl.po translation file is present in git tag 3.13.2, but not added to release tar.xz
Summary: Packaging: po/pl.po translation file is present in git tag 3.13.2, but not ad...
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.13.2
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-08-03 00:43 UTC by Michal Rus
Modified: 2016-08-03 22:58 UTC (History)
1 user (show)

See Also:


Attachments

Description Michal Rus 2016-08-03 00:43:38 UTC
Well, really, not much more can be said. Proof:

Release:

% wget -O claws-mail-3.13.2.tar.xz 'http://www.claws-mail.org/download.php?file=releases/claws-mail-3.13.2.tar.xz'
% md5sum claws-mail-3.13.2.tar.xz
05e36d2ba3a91ef2aa646cde79e0ae3c  claws-mail-3.13.2.tar.xz
% tar -tf claws-mail-3.13.2.tar.xz | grep pl.po
%

Source:

% git clone http://git.claws-mail.org/readonly/claws.git
% cd claws
% git checkout 3.13.2
% find | grep pl.po
./po/pl.po
%

Packaging error?

Best,
Michal.
Comment 1 Ricardo Mones 2016-08-03 01:45:09 UTC
No, that's not a packaging error. It was simply dropped from release tarball because it was unmaintained, see:

http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=76f1303d

Submit an updated one and will be added again ;-)
Comment 2 Michal Rus 2016-08-03 01:52:01 UTC
Ahhhhhhh! Sorry for not digging deeper, then. =)

Is there a way for me to generate the initial diff automatically? And then only fill the missing/changed parts.

I did some translations earlier, but it was never software. If the work needed is not overwhelming (like, say, you changed 90%+ messages), I might help!

Thank you for quick response,
Michal.
Comment 3 Andrej Kacian 2016-08-03 07:10:50 UTC
Yes, gettext has several utilities that work with message catalogs or templates. Look up "msgmerge".
Comment 4 Michal Rus 2016-08-03 12:05:08 UTC
Will do, thank you!
Comment 6 Michal Rus 2016-08-03 22:58:46 UTC
Paul, even better! Thank you.

Note You need to log in before you can comment on or make changes to this bug.