Is any possible way to convert a SCS spool entry into an AFPDS spool file with all the refernece fonts being embedded into .RSC file?
And if is really the case, can we identify the fonts which is being used by SCS spool entry and export those fonts being used in other ways (e.g. exported as an .fnt file)?
Software/Hardware used:
ASKED:
June 24, 2010 9:06 AM
UPDATED:
June 24, 2010 10:00 PM
…convert a SCS spool entry…
I’m not clear on what you mean. A “spool entry” is an already generated file that is formatted for a printer. The printer type and data stream type have already been applied. This involves attributes in the file headers as well as possible embedded printer control commands in the data.
Once generated, the only way that I’m aware of to “convert” it is to retrieve all of the attributes and then read all of the data in the spooled file. Then create a new spooled file with your chosen new attributes, inserting the data where you need it.
That could involve “reprinting” through another printer file or writing the control commands directly, perhaps by using the Spooled File APIs to build a spooled file user space.
I can also imagine possibilities for the Writer Transform Exit Program or the Print Driver Exit Program, too. But I’d expect plenty of obstacles with either of those.
The List Spooled File AFPDS Resources (QGSLRSC) API would be useful if the spooled file was already ASPDS. For a SCS spooled file, there are no resources to return, so the lists are empty.
What exactly are you trying to accomplish? And why? Maybe there are suggestions if the business objective can be described.
Tom