From: Till Kamppeter <till.kamppeter@gmail.com>
To: Koji Otani <sho@bbr.jp>, Albert Astals Cid <aacid@kde.org>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] pdftopdf
Date: Mon, 05 Mar 2012 16:15:10 +0100 [thread overview]
Message-ID: <4F54D87E.6060801@gmail.com> (raw)
In-Reply-To: <1330949656.9812.8.camel@rubik>
On 03/05/2012 01:14 PM, Tim Waugh wrote:
> On Sat, 2012-03-03 at 11:33 +0900, Koji Otani wrote:
>> Sorry, I'm not good at English.
>
> Your English is fine. :-)
>
>> It seemes that poppler provides parsing and rendering PDF.
>> pdftopdf needs modifying PDF such as number-up, duplicating pages ,
>> inserting empty pages, scaling pages, embedding fonts and producing PDF.
>> When I began to develop poppler, I considered about various things
>> such as limited time, cost, etc. And I decided that I developed pdftopdf
>> outside of poppler. (Developing pdftopdf was funded by a Japanese governmental
>> organization)
>> It may be ok for poppler to include these features as you say.
>> I would appreciate it if you put these features into poppler.
>
> Thanks for explaining. If poppler doesn't currently expose enough to
> allow pdftopdf to do what it needs to then some work is needed to change
> that, in order to avoid duplication of bugs.
>
> Who knows the pdftopdf/poppler code well enough to do this?
>
> Do we know anyone on the poppler development team who could guide us as
> to what sort of changes they will accept?
>
Otani-san, can you provide a list of features which need to get exposed
in Poppler so that you can implement the pdftopdf and pdftoopvp filters
without code duplication? Please CC Albert Astals Cid (CCed in this
mail) when answering.
Albert, could you help us in making more secure and
distribution-friendly PDF print filters by adding some APIs to Poppler?
Till
next prev parent reply other threads:[~2012-03-05 15:15 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
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 [this message]
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=4F54D87E.6060801@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=aacid@kde.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=sho@bbr.jp \
/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.