Xerox/WH PDF – Part 15 iText v 2.1.7

Hermitian is concerned that the Courts are using an outdated version of iText

Of course the Mississippi Court is not the only Court using iText 2.1.7 to label its documents. As I have shown, so is a Florida District Court and logic indicates that probably many Courts are using iText in their workflow. Such as…

Producer:       EXP Systems LLC (www.exp-systems.com); modified using iText 2.1.7 by 1T3XT
Producer:       Adobe Acrobat 9.54 Paper Capture Plug-in; modified using iText 2.1.7 by 1T3XT

Another non-issue… Wow… Somehow I am sooo surprised…

As to iText 2.1.7 and beyond note the following. iText 5 skipped from the latest version of the old iText implementation which was 2.1.7. Since v5.0 is not backward compatible, the reason for staying with 2.1.7 seems rather straightforward. Fascinating what a little research can do…

iText 2.1.0 – 2.1.7 (March 27, 2008 – July, 2009)

The most visible change in 2.1 is the fact that the RTF package is separated from the main iText.jar. There’s also plenty of new RTF functionality involving the reuse existing RTF files.

Making iText a more professional library than it already is, is one of the goals of the 2.1.x releases as the library is backed by a company in Europe (1T3XT BVBA) and a company in the US (iText Software Corp) since 2008.

iText 5.0.0 – iText 5.0.6 (December 7, 2009 – February 4, 2011)

We’re jumping from iText 2.x.y to 5.0.0 for the following reasons:

  • We want to use the same version number for iText and iTextSharp.
  • From now on, the iText.jar is compiled using Java 5 (instead of with the JDK 1.4).
  • The F/OSS license has been upgraded from MPL/LGPL to AGPL.
  • The package names have changed from com.lowagie to com.itextpdf.
  • The toolbox and RTF support have been removed: they are now in a separate project at SourceForge.

Note that because of the change of the package names, you can’t upgrade to iText 5 without changing your code. Before upgrading to this new version, please read the new

3 thoughts on “Xerox/WH PDF – Part 15 iText v 2.1.7

  1. Why would someone use an outdated version of iT3XT? Perhaps iT3XT can shed some light on this:

    History

    iText 2.1.0 – 2.1.7 (March 27, 2008 – July, 2009)
    The most visible change in 2.1 is the fact that the RTF package is separated from the main iText.jar. There’s also plenty of new RTF functionality involving the reuse existing RTF files.

    Making iText a more professional library than it already is, is one of the goals of the 2.1.x releases as the library is backed by a company in Europe (1T3XT BVBA) and a company in the US (iText Software Corp) since 2008.

    Versions: iText 2.1.0, iText 2.1.1, iText 2.1.2 (and 2.1.2u), iText 2.1.3, iText 2.1.4, iText 2.1.5, iText 2.1.6, iText 2.1.7
    iText 5.0.0 – iText 5.0.6 (December 7, 2009 – February 4, 2011)
    We’re jumping from iText 2.x.y to 5.0.0 for the following reasons:

    We want to use the same version number for iText and iTextSharp.
    From now on, the iText.jar is compiled using Java 5 (instead of with the JDK 1.4).
    The F/OSS license has been upgraded from MPL/LGPL to AGPL.
    The package names have changed from com.lowagie to com.itextpdf.
    The toolbox and RTF support have been removed: they are now in a separate project at SourceForge.
    Note that because of the change of the package names, you can’t upgrade to iText 5 without changing your code. Before upgrading to this new version, please read the new Terms of Use.

    Versions: iText 5.0.0, iText 5.0.1, iText 5.0.2, iText 5.0.3, iText 5.0.4, iText 5.0.5, iText 5.0.6

    Changing the coding of the entire ECF/CM system wherever it uses iT3XT would be a massive endeavor! Note that 2.1.7 is the last of the old version.

  2. The big change I now noticed is the different license. I remember some slides by ECF/CM that discussed open source and licensing concerns.

    The F/OSS license has been upgraded from MPL/LGPL to AGPL.

    Check out the difference here

    v2.1.7 indeed is the latest MPL/LGPL version

    Read here

    I love this kind of detective work🙂

Comments are closed.