Re: MIDRANGE-L Digest, Vol 13, Issue 1934

Note that iText went through some significant licensing changes and you
more or less now need to buy a commercial version.

Aaron Bartell

On Tue, Dec 9, 2014 at 1:23 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Yeah PDF becomes almost trivial with iText.

No object refrences, pointers or offsets to think about.

Just good old SMASH !!

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com

------------------------------

message: 3
date: Tue, 9 Dec 2014 13:07:38 -0600
from: Bradley Stone <bvstone@xxxxxxxxx>
subject: Re: Merging PDFs

Jon

I think the answer is going to be "bite the bullet" then. I understand
your concerns coming from an ISV standpoint. But remember you're also
asking for functional code to implement in yours for basically nothing.

Merging PDFs isn't "that simple". I stand by that. :) Although I am
waiting for the C code that was promised to see if there's something about
the PDF spec I'm missing. It's not just slapping two files together.
Object references, etc... they can get messy.

As a side, our PDF "concater" requires min V5R2 and Java 1.4 (it uses an
old version of iText). Those are both VERY old and if someone is on older
OS versions than that, well, there are other issues. But I do understand
the issue with if they already have a package installed (for example, if
they had our SPLTOOL and put your software one there would be 2 copies of
the .jars and commands). And working with class paths stinks.

Good luck in your venture, though. I've been there too a few times with
many projects.. I think I spent a couple months or so a few years back just
going over the PDF spec when I was doing all my PDF stuff for our
software. And that was a very rudimentary version of PDF files (basically
just plain text).

Brad
www.bvstools.com


_______________


Confidentiality Notice: This e-mail, including attachments, may include
confidential and/or proprietary information, and may be used only by the
person or entity to which it is addressed. If the reader of this e-mail is
not the intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of this
e-mail is prohibited. If you have received this e-mail in error, please
notify the sender by replying to this message and delete this e-mail
immediately.

________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.