On Fri, 6 Jul 2001, Joey Smith wrote:
There are 2 parts that are required to make PDF's using pdflib. There is
the pdflib code, and the PHP code that makes calls to the pdflib
code. We can ship our own code, but not pdflib's.
And that is what I'm talking about here. Changing only the PHP
That's the whole point. The code that generates the watermarks, or times
out, or whatever, is based in pdflib's code (IE, pdflib.dll). It has
nothing to do with our code.
There is the question of whether or not we can ship pdflib.dll with PHP
at all. I've asked the members of the PHP Group for
On Mon, 2 Jul 2001, Joey Smith wrote:
Surely you are kidding.
I cannot see in any of our packages where we bundle the PDF library with
our release. If we are, we should probably remove it.
In either case, there is no way we can compile an unencumbered version
of PDFLib. That would be
There are 2 parts that are required to make PDF's using pdflib. There is
the pdflib code, and the PHP code that makes calls to the pdflib
code. We can ship our own code, but not pdflib's.
On Fri, 6 Jul 2001, Joao Prado Maia wrote the following to Joey Smith :
Ok, I must be missing something
Surely you are kidding.
I cannot see in any of our packages where we bundle the PDF library with
our release. If we are, we should probably remove it.
In either case, there is no way we can compile an unencumbered version
of PDFLib. That would be illegal. PDFLib is not free, in the
gratis
That is not true at all, if you bundle the PDF library with PHP releases
on the Windows binary it starts being your problem too. I just went to
pdflib.com and it seems to me that binary packages of pdflib for Windows
have a demo / time limit. May I suggest to whoever packaged the Windows
binary
