All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Koji Otani <sho@bbr.jp>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] pdftopdf
Date: Thu, 01 Mar 2012 13:36:52 +0100	[thread overview]
Message-ID: <4F4F6D64.7030100@gmail.com> (raw)
In-Reply-To: <1330600735.18587.3.camel@rubik>

Tim, I did not know that. At least it links against libpoppler.

Otani-san, is there still code-duplication of XPDF or Poppler in the 
pdftopdf filter? Can this be avoided?

Tim, which version of pdftopdf are you looking at?

    Till

On 03/01/2012 12:18 PM, Tim Waugh wrote:
> Hi,
>
> Looking at the source code to pdftopdf, it seems like it is *another*
> fork of xpdf.
>
> Is there a reason it can't use the poppler library to do what it needs
> to do?
>
> Has it been security audited, or at least have the recent xpdf
> vulnerabilities from the last few years been verified not to be present
> in pdftopdf?
>
> Thanks,
> Tim.
> */
>


  reply	other threads:[~2012-03-01 12:36 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 [this message]
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
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=4F4F6D64.7030100@gmail.com \
    --to=till.kamppeter@gmail.com \
    --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.