New Forum | Previous | Next | (P-PDF) Developers
Topic: PDFMaker Ver. 5.0 vs. 4.0 -- File Save
Conf: (P-PDF) Developers, Msg: 55616
Date: 5/29/2002 05:13 PM
This message was posted a few days ago in P-PDF General, but got no takers there. I'll re-bait my hook and cast it in the Developers' pond....
Everybody knows by now that Acrobat broke (IMHO) the automatic filenaming process in PDFMaker when it released Acrobat 5. In Acrobat 4 when you created a PDF from MS Word using the PDFMaker macro, by default the new PDF would have the same name (but with a PDF extension instead of a DOC exten.) and be saved to the same path/location as the Doc it was based on. This was very convenient. Several messages in this forum seem to share my sentiment.
Unfortunately, when I asked Adobe about this, I was told that this was a "feature." There appears to be no intention by Adobe to fix (change) this, or at least make it an option.
Q: can we get there some other way?
Can you pass a filespec for naming to the PDF_Distiller or PDF_Writer printer drivers? If you could then it would be easy enough to write a Word macro (or even a Visual Basic one) which took the existing Doc file name (and path) and (after parsing off the .doc extension), passed that to either the PDF_Distiller or PDF_Writer printer drivers.
Q: is there a way to pass parameters to the driver for file naming?
I've looked at the SDK reference material for Distiller and Writer. It does seem that one could write a Visual Basic macro could make the requisite writes/reads to the registry. I'm less sure of whether a Word macro alone could do so. On the other hand, that's is essentially what the PDFMaker macro is doing anyway, so clearly it's possible.
If only the PDFMaker macros were not locked not just from editing, but also from viewing. I could take the code, make a few minor changes, and get what I want. Surely I'm not the only person who is irritated and inconvenienced by this new change in PDFMaker.