问题描述
现在iText已经了，我假设有人要去采取旧的（2.1.7或）代码并分叉它以保持LGPL版本。有没有人知道这样的叉子已经开始了？
Now that iText has gone AGPL, I'm assuming someone is going to take the old (2.1.7 or 4.2.0) code and fork it to keep an LGPL version going. Does anyone know of such a fork already started?
推荐答案
我在博客中讨论了iText AGPL许可证的一些实际问题（与我的SO资料相关联）。为什么不直接购买IText？它当然是许多商业PDF库中的一个选项，尽管它们确实需要在竞争中标准化它们的价格。
I discussed some practical issues with the iText AGPL license in my blog (which is linked from my SO profile). Why not just buy IText? It is certainly an option among many commercial PDF libraries out there, although they really need to standardize their pricing against the competition.
事实是我从来没有真正使用iText过去。它总是要么缺少某些功能，要么API比其他（非自由）替代方案要困难得多，特别是对于最小的PDF操作（例如，而不是生成报告所需的PDF操作级别） 。
The truth is I never really used iText much in the past. It always either lacked certain features, or the API was much more difficult than other (non-free) alternatives to wrap your head around, especially for minimal PDF manipulation (rather than the level of PDF manipulation required to generate a report, for example).
此时我所知道的唯一获得同样许可的PDF库是ICEPdf，它位于，但其商业模式是拥有更多限制版本并收取更多高级功能（例如更多字体支持）。
At this point the only similarly licenced PDF library I know of is ICEPdf, which is under the MPL 1.1 license, but its business model is to have a more limited version and charge for more advanced features (such as more font support).
这篇关于有谁知道iText的分叉？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！