v3.17 Question regarding the GPL license of html2pdf - Page 1

I noticed that "html2pdf" is released as GPL software. I was wondering, this does mean every user has to to release their entire PHP application as GPL to use it? Or hasn't this been the intention of the author?

Thanks in advice

"html2pdf" is released as GPL software beceause it is based on "fpdf" who is under GPL.

vdboor (./1) :
I noticed that "html2pdf" is released as GPL software. I was wondering, this does mean every user has to to release their entire PHP application as GPL to use it?

Only if the application itself is released, not if it's just run on a server. Only the Affero GPL requires source code to be provided (under the terms of the Affero GPL) even in that situation (i.e. for web apps which are offered on a central server), the regular GPL (which is what's being used here) doesn't (nor does the LGPL).

That said, if you do release your PHP application as such, my understanding is that you do have to do so under the terms of the GPL, as is it linked to the GPLed FPDF and HTML2PDF code.

(Disclaimer: I am not a lawyer. This is not legal advice.)

Thanks for your answers! This clears things up for me a bit.

Spipu (./2) :
"html2pdf" is released as GPL software beceause it is based on "fpdf" who is under GPL.

That seams to make sense

I also checked the pdf site and the _fpdf/FAQ.html file from your source (online version) I it seams they've changed their license to something BSD style.

FPDF is released under a permissive license: there is no usage restriction. You may embed it freely in your application (commercial or not), with or without modifications.

Kevin Kofler (./3) :
Only if the application itself is released, not if it's just run on a server. (...) That said, if you do release your PHP application as such, my understanding is that you do have to do so under the terms of the GPL, as is it linked to the GPLed FPDF and HTML2PDF code.
(Disclaimer: I am not a lawyer. This is not legal advice.)

In my case there isn't an application which is released, just an internal module which is called from the site. I'm not using PHP so application will be called by invoking /usr/bin/php as separate tool.

So am I correct there isn't a licensing problem in my situation?

Right, as I understand it, in that situation the GPL does not impose any requirements on you, as you are not distributing the GPLed code. And additionally, invoking the PHP code as a separate process is normally not considered linking to the code.

vdboor (./4) :
So am I correct there isn't a licensing problem in my situation?

Right

Thanks I'm glad to hear this is possible.