From: Pierre Habouzit <madcoder@debian•org>
To: Leo Razoumov <slonik.az@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: clean/smudge filters for pdf files
Date: Thu, 23 Oct 2008 23:32:03 +0200 [thread overview]
Message-ID: <20081023213203.GB26104@artemis.corp> (raw)
In-Reply-To: <ee2a733e0810231244u1510cdc8y7b27af9b8fdda1e0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Thu, Oct 23, 2008 at 07:44:39PM +0000, Leo Razoumov wrote:
> 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?
actually it uses some kind of zlib algorithm so that's pretty normal you
don't have the same result with a packer. Maybe one could write a tool
like pristine-tar for that purpose.
--
·O· Pierre Habouzit
··O madcoder@debian•org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-23 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 19:44 clean/smudge filters for pdf files Leo Razoumov
2008-10-23 21:32 ` Pierre Habouzit [this message]
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=20081023213203.GB26104@artemis.corp \
--to=madcoder@debian$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=slonik.az@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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