MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: Create an Overlay from a PDF



fixed

Thanks Dan.

No special settings in Infoprint Server. A fact is very clear: the same
type of spool converted in PDF using the same virtual device if created
with Overlays has a "normal" size, using AFPRSC (*PDFSPO) is ten times
bigger. Looks like Overlays resources are encapsulated into the PDF
document, AFPRSC are encapsulated into each page.





--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


2013/12/3 Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx>

I don't have a 7.1 machine nor the time to play with it at the moment, but
there's obviously some things going on that perhaps you can remedy.

With AFPRSC the numbers you are reporting make it obvious that the tool,
as you have it set up, is rendering the PDF as a series of compressed
bitmap images, probably jpeg with full color depth as your numbers are so
large. In other words, all the letter characters, lines, boxes, and so
forth that comprise a page with overlay are being rendered inside the tool
into an image bitmap, the bitmap is compressed, and then added to the PDF
file as a single-component page.

That's not the only way to build a PDF page, of course. PDF is a page
composition language like AFP. PDF can contain text, bitmap graphics (CCITT
or JPEG or ??), vector graphics, and other types of elements. The tools
that you are using to render the page with overlays (instead of AFPRSC to a
PDF) are translating those SCS or AFP text or vector graphics directly into
the same types of objects in the destination PDF. These things are much
smaller, of course, as they rely on the printer to do the final rendition
into bitmaps that result in ink dots on the page.

Are you using a text-content PDF as the AFPRSC? Only if it is text (and/or
vector graphics) can the tool produce text-based PDF components. If you
start with a resource PDF in bitmap graphics, the tool will almost be
forced to render into full page bitmap.

Next, look at the settings you are using for the WSCST that is directing
the transformation in HPT. Do you have settings there that are doing
something to prefer a full image rendering?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Marco Facchinetti
Sent: Tuesday, December 03, 2013 5:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: Create an Overlay from a PDF

Thanks Eric, it's my italian English... I try to explaine better.

We generate spools with Overlay the schema is:

Page1: OverlayA, some text, boxes, lines and so on
Page2/3/4: OverlayB, some text, boxes, lines and so on
Page5: OverlayA, some text, boxes, lines and so on
Page6/7/8/9: OverlayB, some text, boxes, lines and so on

When the spool is complete we convert it in PDF using a virtual printer
(Inforpint Server). The size is usually the sum of OverlayA, OverlayB and
few KB of text. So if OverlayA is 1,2Mb, OverlayB 670Kb the resulting PDF
will be less than 2Mb.

The problem using AFPRSC (with a single page PDF) instead of Overlays is
that the PDF's size will be 7,2 Mb (=1200*2+670*7). When the spool is
small, few pages, it's not a problem but our customers average spools
are >
70k pages so the resulting PDF instead of 300/400 Mb became 12/15 Gb.

IBM lab's told me that is working as designed and if I don't like it the
only way is submitting a Design Change Request. And, maybe, in the next 3
or 4 years will be fixed, of course if IBM grants the budget to do it.

Actually overlays generation is complicated:

1 - If already present delete the old one
2 - Print the PDF using IBM Afp printer driver to generate the
intermediate
object
3 - Import the intermediate object using System i Navigator

Our customers refuse this type of procedure, beside that the users should
have access to production libraries, have the AFP driver and Iseries i
Navigator installed on their Pc.

This is the reason why I'm looking for a tool to convert (automatically
under the covers) a single page PDF into an Overlay.

TIA


--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


2013/12/2 DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx>

I am notably NOT a printer output expert, but I am totally stumped why
you
would need to convert a PDF into an overlay. This seems like a
complete
waste of time and effort... A PDF is a composite document, which would
already imbed any page segments and overlays referenced during its
creation.

You mention about document size, I suppose in relation to the imbedded
graphical overlays, but with PDF, there's no such concept as caching of
page segments and overlay resources. IPDS handles that on behalf of
the
HPT engine, but a similar caching concept for PDFs is foreign to the
PDF
document specification. PDF is intended to be completely self
contained,
an so all resources used in the production of output is encapsulated
into
the PDF document.

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Marco Facchinetti
Sent: Saturday, November 30, 2013 12:59 PM
To: Midrange Systems Technical Discussion
Subject: Create an Overlay from a PDF

Hi all,

we have implemented the use of AFPRSC in DDS defined printer files
using
single page PDF (object type *PDFSPO) and it's working, the PDF is
nicely
rendered in the print out. The problem is that Afprsc behaves
differently
from overlay when the spool is transofrmed in PDF using Infoprint
Server.
Overlay is included by reference, AFPRSC by value. The effect is in
PDF's
size: it's increased from 300 Mb to 12/15 Gb.

As usual IBM labs told "works as designed".

Since the procedure of converting PC docs using AFP driver and System I
Navigator is not user friendly (the main reason we implemented AFPRSC
was
to avoid it) now I'm looking for something to automate the conversion
from
PDF to Overlay.

TIA
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco
--
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.


--
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.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact