Converting PDFs from non-ADSC to ADSC

[Norman_Teck@adobeforums.com]

Is Adobe Acrobat Professional or Adobe Distiller capable of opening an ADSC non-compliant PDF and saving it as an ADSC (Adobe Document Structuring Convention… page independent)-compliant PDF? Since it appears that Mac OS X drivers can no longer generate page-independent PostScript or PDF output this puts a serious limitation on Mac as a useful tool in the digital printing industry.

The only workaround I've found so far is to open the non-compliant PDF in Preview, print to file as a PostScript file, mount an ADSC-compliant setting in Adobe Distiller and then Distill the PostScript file.

[Aandi_Inston@adobeforums.com]

Adobe Document Structuring Convention is a PostScript standard. It has
no connection to PDF. All PDF files are page independent, by
definition.

Aandi Inston

[Norman_Teck@adobeforums.com]

I guess I need a little more clarification here. I knew that PDFs were device independent, but I've used Distiller to create PDFs from PostScript code and when printing large documents, graphic-rich with more than 100 pages, I've found that although the PDF was viewable on my monitor, the printer ran out of resources before the interpreter could RIP the job that was created from page interdependent PostScript, but had no difficulty making its way through ADSC-compliant PS-based PDFs.

I'm a little confused by the presence of the DSC controls on the advanced settings tab of Adobe Acrobat. If PDFs are page independent, wouldn't that be redundant?

If I'm working off of misinformation, I'd appreciate your pointing me toward the documentation that shows PDF are inherently page independent.

[Aandi_Inston@adobeforums.com]

> but had no difficulty making its way through ADSC-compliant PS-based PDFs.

That suggests the difference is the volume of resources that get used.
PDF pages are indepenent, always. Whether the PostScript that is
produced is page independent is another matter. Recent version of
Acrobat also include control over the way fonts are sent (fonts are
the main culprit in running out of printer memory, not graphics).

>
>I'm a little confused by the presence of the DSC controls on the advanced settings tab of Adobe Acrobat.

Acrobat can use the DSC comments in a PostScript file to extract
information about the job. Or not. It doesn't affect the way a PDF is
made.

>I'd appreciate your pointing me toward the documentation that shows PDF are inherently page independent.

PDF Reference. But there's 1000 pages of it.

Aandi Inston

[Norman_Teck@adobeforums.com]

If the PDF is Distilled from a PostScript file that was generated by drivers Optimized for Speed, does the Distilling process restructure repair the page interdependencies and create an ADSC-compliant PDF?

Is the reasoning behind the processes shown on hte <http://www.ddap.org> website for creating PDFs flawed? Their explanation for using page-independent PostScript as a basis for generating PDFs made sense to me. Obviously, including the font metrics within the document assures that the print output doesn't reflow and look different from the screen output.

I deeply appreciate your pursuing this dialog with me.

[Aandi_Inston@adobeforums.com]

>If the PDF is Distilled from a PostScript file that was generated by drivers Optimized for Speed, does the Distilling process restructure repair the page interdependencies and create an ADSC-compliant PDF?

Still not really a meaningful question. There's nothing to repair.
PDFs just are page independent. You won't get me to agree to the term
"ADSC compliant PDF".

>
>Is the reasoning behind the processes shown on hte <http://www.ddap.org> website for creating PDFs flawed?

Can you give a more exact URL?

Aandi Inston

[Norman_Teck@adobeforums.com]

I'm not trying to trick you into accepting any flawed premises under which I've been operating. I'm trying to build a bridge from my current level of understanding toward the new information you've been providing me. My syntax is the product of where I am. It will change as I gain an understanding of new information.

I'll attempt to restate my question so that I may make that transition. If someone creates a large document with a Windows application, prints to file with PostScript drivers that are optimized for speed, pipes the resulting PostScript code through Adobe Distiller, the result will be (at the risk of being redundant) a page independent PDF?

I'll try to find the DDAP reference later.

[Aandi_Inston@adobeforums.com]

The result will be, as it always is, a page independent PDF...

Aandi Inston