From: Tim Waugh <twaugh@redhat.com>
To: Koji Otani <sho@bbr.jp>
Cc: printing-architecture@lists.linux-foundation.org,
till.kamppeter@gmail.com
Subject: Re: [Printing-architecture] pdftopdf
Date: Fri, 02 Mar 2012 12:13:38 +0000 [thread overview]
Message-ID: <1330690418.32498.29.camel@rubik> (raw)
In-Reply-To: <20120302.210815.55716582.sho@bbr.jp>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Fri, 2012-03-02 at 21:08 +0900, Koji Otani wrote:
> Changes I made are needless for poppler and poppler can't use them.
> I used only a frame of codes in some files.
I don't understand. Wasn't the whole idea of poppler to avoid having
bits of xpdf copied into every project that wants to do things to a PDF
file? And doesn't pdftopdf want to do things to a PDF file?
Can you explain why it is that poppler "can't use" the extra bits you've
changed? Can you describe what they are? It seems to me that poppler
ought to provide sufficient insight into the structure of a PDF file so
that pdftopdf can do its job. If it doesn't, that sounds like something
the poppler project would want to provide... no?
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2012-03-02 12:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:18 [Printing-architecture] pdftopdf Tim Waugh
2012-03-01 12:36 ` Till Kamppeter
2012-03-01 13:55 ` Tim Waugh
2012-03-02 4:03 ` Koji Otani
2012-03-02 9:39 ` Richard Hughes
2012-03-02 9:58 ` Koji Otani
2012-03-02 11:22 ` Tim Waugh
2012-03-02 12:08 ` Koji Otani
2012-03-02 12:13 ` Tim Waugh [this message]
2012-03-03 2:33 ` Koji Otani
2012-03-05 12:14 ` Tim Waugh
2012-03-05 15:02 ` Till Kamppeter
2012-05-29 16:06 ` Jiri Popelka
2012-05-29 16:50 ` Till Kamppeter
2012-03-05 15:15 ` Till Kamppeter
2012-03-06 6:01 ` Koji Otani
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=1330690418.32498.29.camel@rubik \
--to=twaugh@redhat.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=sho@bbr.jp \
--cc=till.kamppeter@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.