Attachment 26345 Details for Bug 22027 – suggested patch

[patch] suggested patch

poppler-0.10.7-readme.pat (text/plain), 1.51 KB, created by William Bader on 2009-06-01 14:54:35 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: William Bader

Created: 2009-06-01 14:54:35 UTC

Size: 1.51 KB

patch

obsolete

>--- poppler-0.10.7/README-	2009-05-02 14:14:56.000000000 +0200
>+++ poppler-0.10.7/README	2009-06-01 21:56:02.000000000 +0200
>@@ -3,19 +3,19 @@
> Poppler is a fork of the xpdf PDF viewer developed by Derek Noonburg
> of Glyph and Cog, LLC.  The purpose of forking xpdf is twofold.
> First, we want to provide PDF rendering functionality as a shared
>-library, to centralize the maintenence effort.  Today a number of
>+library, to centralize the maintenance effort.  Today a number of
> applications incorporate the xpdf code base, and whenever a security
> issue is discovered, all these applications exchange patches and put
> out new releases.  In turn, all distributions must package and release
> new version of these xpdf based viewers.  It's safe to say that
>-there's a lot of duplicated effort with the current situaion.  Even if
>+there's a lot of duplicated effort with the current situation.  Even if
> poppler in the short term introduces yet another xpdf derived code
> base to the world, we hope that over time these applications will
> adopt poppler.  After all, we only need one application to use poppler
> to break even.
> 
> Second, we would like to move libpoppler forward in a number of areas
>-that doesn't fit within the goals of xpdf.  By design, xpdf depends on
>+that don't fit within the goals of xpdf.  By design, xpdf depends on
> very few libraries and runs a wide range of X based platforms.  This
> is a strong feature and reasonable design goal.  However, with poppler
> we would like to replace parts of xpdf that are now available as

Actions: View | Splinter Review

Attachments on bug 22027: 26345

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.