ETDA Conference - Short overview of iText
•Download as PPTX, PDF•
0 likes•730 views
Presentation given by iText Software at the ETDA conference in Bangkok at July 27, 2017. Giving a short overview of iText.
Recommended
More Related Content
More from iText Group nv
More from iText Group nv (17)
Recently uploaded
Recently uploaded (20)
ETDA Conference - Short overview of iText
- 1. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA EDTA & iText Conference Bangkok, July 27, 2017
- 2. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Short overview of iText2 How did this happen?
- 3. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Short overview of iText3 How it all started for PDF 1991: “The Camelot Paper” by John Warnock, Adobe Explains why PDF is needed From Carousel Product Specification to PDF 1.0 Adobe’s bold move: make the Reader free of charge
- 4. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Short overview of iText4 How it all started for iText 1998: first open source PDF library; 2000: first iText release Bring PDF from the Desktop to the Server World-wide distribution as open source library iText’s bold move: Automate PDF creation
- 5. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA Document workflow
- 6. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Short overview of iText6
- 7. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Short overview of iText7
- 8. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA Open source
- 9. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Copyright versus Copyleft Copyright law allows an author to prohibit others from reproducing, adapting, or distributing copies of the author's work. Copyleft gives every person who receives a copy of a work permission to reproduce, adapt or distribute the work as long as any resulting copies or adaptations are also bound by the same copyleft licensing scheme. Short overview of iText9 © ©
- 10. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Open Source License overview Short overview of iText10
- 11. © 2015, iText Group NV, iText Software Corp., iText Software BVBA How the (A)GPL works A: you own the software You grant rights: copy, modify, distribute You distribute a copy of the source code Disclaimer: “as-is”; no warranties Additional rights: e.g. specific legal notices, use of trade names B: you distribute verbatim copies Everything listed under A still applies You may remove additional permissions The software remains GPL C: you distribute works “based on” Everything listed under A+B still applies Add notice + date for each modification ** Your work is automatically (A)GPL (viral effect!) Short overview of iText11 * * USE only: you don’t have to accept the GPL ** Modification: very broad interpretation
- 12. © 2015, iText Group NV, iText Software Corp., iText Software BVBA Licensing options Viral effect of the open source license: The product is available for free for those who accept and comply with the F/OSS license, The product is improved thanks to bug fixes and code contributions, As soon as the product is also distributed under another license, a commercial license is needed. Commercial license for commercial use: The product is available under a custom license for those who pay for the product: Support, Warranty, Indemnification, Release from the requirements of the F/OSS license, Perpetual (per server) + maintenance, Capacity Rental, OEM. Partnerships for co-creation and co-promotion of products! Short overview of iText12
- 13. © 2015, iText Group NV, iText Software Corp., iText Software BVBA iText DITO iText 7 platform 13 iText 7 Core pdfSweep pdfInvoice pdf- Calligraph pdf2Data pdfHTML ... pdfXFA pdfDebug iText 7 engine DITO SDK pdfHTML Designer Short overview of iText
- 14. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA Why iText?
- 15. © 2015, iText Group NV, iText Software Corp., iText Software BVBA What people tell us: We use iText because of the quality of the PDFs: E.g. many other products don’t support tagging, specific features we need,… We use iText because there is a big iText community: Many people write about iText; questions on Stack Overflow get answered quickly. We use iText because we see that it is actively developed: We see that iText Group constantly invests in new development, It’s as if iText has been around forever! The iText development team offers great support: The support team has helped us solve our problems; Feature requests from our company made it into the official road map. Short overview of iText15
- 16. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA Thank you!
Editor's Notes
- In 1991, Adobe’s John Warnock wrote “The Camelot Paper” in which he explained this specific problem: Most programs print to a wide range of printers, but there is no universal way to communicate and view this printed information electronically ... What industries badly need is a universal way to communicate documents across a wide variety of machine configurations, operating systems, and communication networks. I have personal experience with this problem long after this paper was written. When I started working at Ghent University in 1998, I was confronted with software that only worked on DOS and that could only print to an HP printer that couldn’t even be a network printer: it had to be attached to the local computer. I solved this problem by introducing PDF: PDF had the advantage that it can be viewed on every platform and that it can be printed in a reliable way, which were the requirements of my University project. The 1991 Camelot paper led to the Carousel Product Specification, which in turn resulted in the first PDF specification and software in 1993: Acrobat Distiller and Acrobat Reader. Although PDF had what it took to make the paperless world happen, it turned out that many people considered PDF as “a format for printing documents.” I also noticed this in my university project: people didn’t use the digital documents digitally, the first years the project was in production, the users of my application printed every PDF I produced. I wanted to solve this paradox and I succeeded: over the years people stopped printing PDFs and started to consume them digitally. How did I achieve this change of hearts with respect to paper?
- In the first decade of its existence, PDF was something that lived on the desktop. A PDF document was created manually by a human being, using a Word processor or desktop publishing software. The final purpose of many of those document was to be printed. People still loved paper more that digital. In 1998, I was one of the first people who created an open source library that allowed developers to create PDFs on the server automatically, without any human intervention. The major flaw of this first library was the fact that a developer needed to read and understand the PDF specification in order to use it. I soon discovered that I had to make it easier for developers to create documents if I wanted to make PDF a success. That’s why I created iText: a library that allows developers to create PDF documents programmatically without having to be a PDF specialist. The library was an instant hit: everyone in need of PDF functionality started to use iText. And here’s the second paradox: I created a library that multiplied the world-wide amount of PDF documents dramatically, hoping that this would make the dream of the paperless world happen. The secret to achieve this dream is “added value”: People will prefer digital over paper, once the digital document has added value when compared to the paper document. So I began focusing on the added value that PDF technology made available and I thought of ways to make PDF even more popular. iText made it possible to publish data from a database extremely fast, resulting in documents of hundred thousands of pages. Printing such a document would be madness, but the PDF format was a great way to archive a snapshot of a specific moment in time. Among the first iText users, there were a lot of banks who used iText to create PDFs for that specific purpose. But there’s more.