When merging ps files, some pages are missing

[Jayesh_Kumar@int]

Hi,

We are using PS merging option, the below steps we are following to create pdf from set of ps files

1. Merging all the .ps files into single .ps file

2. in Single ps file, path will be changed

3. Creating pdf from the merged single .ps file

but when we open that pdf, some pages are missing. Can anyone know that how to solve it. Is it the proper method. Please advice.

Regards

Jayesh

[Dov Isaacs]

Can we assume that by “PS” you mean PostScript?

For better or worse, you really cannot assume that concatenating PostScript files either to print or to distill into PDF will yield the same results as printing or distilling the PostScript files individually. The ability to do such concatenation really depends on how well the individual PostScript files encapsulate their graphics states and definitions.

         - Dov

[Jayesh_Kumar@int]

Yes, .ps means postscript. We are using the below method to distill the .ps to pdf

FOR EXAMPLE

%!
% PostScript program for distilling and combining multiple PostScript files.
% When embedding font subsets, it is highly recommended you use this technique
% to distill multiple PS files so only one font subset is used for each font.

/prun { /mysave save def       % Performs a save before running the PS file
        dup = flush            % Shows name of PS file being run
        RunFile                % Calls built in Distiller procedure
        clear cleardictstack   % Cleans up after PS file
        mysave restore         % Restores save level
} def

(d:/PS-Merge/3376815/9781107039322_pod.ps) prun
(d:/PS-Merge/PS-Merge/3376815/9781107039322c01.ps) prun
(d:/PS-Merge/PS-Merge/3376815/9781107039322c02.ps) prun
(d:/PS-Merge/3376815/9781107039322c03.ps) prun
(d:/PS-Merge/3376815/9781107039322c04.ps) prun
(d:/PS-Merge/3376815/9781107039322c05.ps) prun
(d:/PS-Merge/3376815/9781107039322c06.ps) prun

% INSTRUCTIONS
%
% 1. Locate all PostScript files to be distilled.
%
% 2. Make a copy of this file and give it the name you want to have as the prefix
%    for the resulting file. For example, you could name this file MyBook.ps.
%
% 3. Include a line for each PostScript file to be run using the pathname syntax
%    appropriate for the platform running Acrobat Distiller.
%
%       Macintosh pathname syntax:  (Macintosh HD:Folder:File.ps) prun
%       Windows pathname syntax:    (c:/mydir/file.ps) prun
%       UNIX pathname syntax:       (./mydir/File.ps) prun
%
%       Note: The syntax for Windows may look strange, but double escaping the
%             backslash character is required when using filenameforall.
%
% 4. Distill the file on the machine running Acrobat Distiller.

[Dov Isaacs]

Great. That is what I thought you were doing. Unfortunately the

/mysave save def      % Performs a save before running the PS file

        dup = flush   % Shows name of PS file being run

        RunFile       % Calls built in Distiller procedure

        clear cleardictstack

does not fully clean everything up between the PostScript fragments.

Assuming that each of your PostScript files define independent pages, you would be much safer by distilling each of the PostScript files individually into PDF files that you can combine together into a single PDF file via Actions or scripting in Acrobat.

         - Dov

[Jayesh_Kumar@int]

Ok Dov, Thanks for your reply...

[Jayesh_Kumar@int]

Is it PDF merging from Acrobat XI pro is the safest method? or do we receive any issue when merging pdf files using Acrobat XI pro?

[Test Screen Name]

‌Acrobat Pro XI is a good solution for merging on an interactive desktop. Not to be considered for a server or hands free system.

[Jayesh_Kumar@int]

Hi,

May I know that Why we should not use hands free system for pdf merging?

regards

Jayesh

[Test Screen Name]

Acrobat is not technically suitable for use in a non-interactive session. Some reasons for this are obvious (e.g. it will often pop up messages that need a reply), and others are less obvious and even unknown technical details.

Even more important for some applications, Acrobat is not licensed for server use. Adobe license other products for developers to use on servers. These cost much more - consider, this one server might replace a hundred sales of Acrobat on each desktop, and Adobe do not want to just lose this revenue... in general, and you may already know this, but it is worth mentioning for people who read this in future, for anything you plan to use on a server you must examine the license carefully. (I know of a case where some software was sold "per user", was used to store information on a web site, and the software company claimed a per user fee for each public user of the web site - hundreds of thousands of people).