[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Joseph Campo <campoj@xxxxxxxxxxxxxxxx>, FrameUsers List <Framers@xxxxxxxxxxxxxx>, Frame List <Framers@xxxxxxxxx>
Subject: Re: thanks for suggestions on pdf file display problems
From: Jay Smith <jay@xxxxxxxxxxxx>
Date: Fri, 12 Feb 1999 11:52:20 -0500
Cc: Frank Elmore <elmsoft@xxxxxxxxxxxxxx>
Organization: Jay Smith & Associates
References: <199902121642.LAA20121@defoe.teradyne.com>
Sender: owner-framers@xxxxxxxxx
Joseph, One clarification... My suggestion was NOT to SAVE to .ps files, but to *PRINT* to .ps files. (I think that is what you meant, but I want to be sure.) As for having to do that step, I agree that it is a pain. HOWEVER.... I believe that one could use the FrameScript scripting language to open all files in a directory(s) and print them (to .ps). Furthermore, Distiller can be configured with Watched Folders so that as soon as the frame files are printed to .ps files, Distiller will (automatically in the background) Distill them to PDF. While setting up the FrameScript script might be a little work, one could really let FrameScript and Distiller blast through this stuff overnight. (Joseph, I have copied this message to Frank Elmore, of FrameScript fame, you may wish to carry this conversation on with him.) Note that using this type of automation, the Frame files can be edited as needed, and then the script(s) run overnight to generate all new PDF files -- replacing the previous versions. You might then need a batch file/script to move the various PDFs to the directories where they are needed on your server(s), however, one could theoretically process thousands of files this way, without intervention. -- Jay Smith e-mail: jay@jaysmith.com The Press for History(tm), The Press for Education(tm), The Press for [Your Industry](tm), The Press for....(tm) On-demand printing and binding of hardbound books. Minimum run one copy. P.O. Box 650 Snow Camp, NC 27349 USA Phone: Int+US+336-376-9991 Toll-Free Phone in US & Canada: 1-800-447-8267 Fax: Int+US+336-376-6750 Joseph Campo wrote: > > Dear Jim, Max, and Jay > > Thanks for your suggestions shown below re the pdf problem posted on frameusers. > I am not working on it, just posting the problem. I have been told that > 1. The ftp was set to binary automatically, so that should not be the problem Jim. > 2. My colleagues believe the ftp transfers should not have caused the problem, as other people in other departments have done this without similar problems Max. > 3. My colleague said she hopes that she does not have to save each individual file to ps as per Jay's suggestion. That would take quite a long time. Our doc set is very large. > > They are going to try doing the whole thing on a PC (we are in the process of changing our SUN stations/UNIX for the PC windows nt environment) to see if that works. > > Thanks again for your help. > > Joseph Campo > Tech writer > Teradyne > Boston, MA USA > > Two ideas: > 1. Be sure you are using binary in FTP (enter the bin command at an FTP > prompt). > 2. Be sure you are using lowercase file names throughout, including all > Catalog files and directories (if the index files have any uppercase letters, > change them to lower case). > Jim Welch > ---------------------------------- > ---------------------------------- > The "This file is damaged but is being repaired" message actually means > that something got slightly messed up with the files. The two FTP transfers > look to me as the culprit for that, but it could also be that the files got > saved on the PC, and that certain font names could have gone strange, or > that some encoding changed. When you open the documents again on the > Solaris machine, Reader/Exchange repairs the file on the fly. It seems that > Reader/Exchange runs out of resources after those 500 pages. You can try to > individually open these files and save them again. As far as I can see, the > index (created with Catalog) should still be OK. > > Another possibility would be to set up a mini-network with the PC used to > run Catalog accessing the files via PC-NFS or so. This would eliminate the > FTP transfer problems. > > Hope, this can help. > > Max Wyss > PRODOK Engineering > ---------------------------------- > ---------------------------------- > Generally speaking, you should PRINT (using the Distiller print driver) the > Frame files to PS files and then DISTILL the PS files to PDF files. > > Otherwise you will have a mess. > > You may be having memory problems on the PC anyway, as somebody mentioned, > however, if you do not PRINT to PS and then DISTILL to PDF, you WILL have > problems. > > -- > Jay Smith ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **