Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iText PDF Library turns 25

itextpdf.com

Post reply on HN
Print view View original

1–10 of 29 posts

Re: iText PDF Library turns 25

#4

Post by Tomte »

> When using iText Core/Community under AGPL, you must prominently mention iText and include the iText copyright and AGPL license in output file metadata, and also retain the producer line in every PDF that is created or manipulated using iText.

https://itextpdf.com/how-buy/AGPLv3-license

Not really AGPL, they just advertise AGPL and mean something else. Avoid.

Re: iText PDF Library turns 25

#5

Post by bklyn11201 »

_JamesA_ wrote: post #3

I stopped using iText back when it changed licensing because the developer wanted his government to pay to use it (or something like that). What ever happened with that fiasco?

The classname "lowagie" will live forever in the memory of Java developers, but we've all abandoned itext for the fork:

  https://github.com/LibrePDF/OpenPDF

Re: iText PDF Library turns 25

#6

Post by DannyB2 »

_JamesA_ wrote: post #3

I stopped using iText back when it changed licensing because the developer wanted his government to pay to use it (or something like that). What ever happened with that fiasco?

JasperReports library used that library, and forked it at it's last LGPL version.

Re: iText PDF Library turns 25

#7

Post by swsieber »

Tomte wrote: post #4

> When using iText Core/Community under AGPL, you must prominently mention iText and include the iText copyright and AGPL license in output file metadata, and also retain the producer line in every PDF that is created or manipulated using iText. https://itextpdf.com/how-buy/AGPLv3-license Not really AGPL, they just advertise AGPL and mean something else. Avoid.

Hmmm... they link to the AGPL and state it's under that. In a conflict between the two, the website extras, and the AGPL requirements, which would win?

I personally think the AGPL would win, but it's not something I'd be willing to enter a legal battle over.

Re: iText PDF Library turns 25

#9

Post by Tomte »

swsieber wrote: post #7
Tomte wrote: post #4

> When using iText Core/Community under AGPL, you must prominently mention iText and include the iText copyright and AGPL license in output file metadata, and also retain the producer line in every PDF that is created or manipulated using iText. https://itextpdf.com/how-buy/AGPLv3-license Not really AGPL, they just advertise AGPL and mean something else. Avoid.

Hmmm... they link to the AGPL and state it's under that. In a conflict between the two, the website extras, and the AGPL requirements, which would win? I personally think the AGPL would win, but it's not something I'd be willing to enter a legal battle over.

Exactly. That’s why I said avoid. Even if you think the AGPL prevails.

You already know that the licensor has his own, idiosyncratic interpretation. He either misunderstands the AGPL (probably clause 7 par 3 b), or he’s trying to deceive you. Both cases can easily lead to hostilities.

Re: iText PDF Library turns 25

#10

Post by whizzx »

bklyn11201 wrote: post #5
_JamesA_ wrote: post #3

I stopped using iText back when it changed licensing because the developer wanted his government to pay to use it (or something like that). What ever happened with that fiasco?

The classname "lowagie" will live forever in the memory of Java developers, but we've all abandoned itext for the fork: https://github.com/LibrePDF/OpenPDF

Does it support tagged documents and PDF2.0 as well?
Post reply on HN