From: "Leo Razoumov" <slonik.az@gmail.com>
To: git@vger.kernel.org
Subject: clean/smudge filters for pdf files
Date: Thu, 23 Oct 2008 15:44:39 -0400 [thread overview]
Message-ID: <ee2a733e0810231244u1510cdc8y7b27af9b8fdda1e0@mail.gmail.com> (raw)
I am trying to improve storage efficiency for PDF files in a git repo.
Following earlier discussions in this list I am trying to set up
proper clean/smudge filters. What follows is my current setup
# in ~/.gitconfig
[filter "pdf"]
clean = "pdftk - output - uncompress"
smudge = "pdftk - output - compress"
# in .gitattributes
*.pdf filter=pdf
Unfortunately, it seems as though that pdftk uncompress followed by
pdftk compress do not leave the file invariant. I tried several
uncompress+compress iterations and the file still keep changing (the
size though stays the same).
Is there any other alternative way to store PDF files in git repo more
efficiently?
Any alternative to pdftk on Linux?
--Leo--
next reply other threads:[~2008-10-23 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 19:44 Leo Razoumov [this message]
2008-10-23 21:32 ` clean/smudge filters for pdf files Pierre Habouzit
2008-10-24 1:40 ` Leo Razoumov
2008-10-24 8:10 ` Michael J Gruber
2008-10-24 8:44 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee2a733e0810231244u1510cdc8y7b27af9b8fdda1e0@mail.gmail.com \
--to=slonik.az@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).