Advice on creating PDF

I'm working in Adobe Illustrator on some 11x17 page size illustrator files that are of aerial photo maps (with a legend).
I realize this is the Acrobat forum, but please hear me out. When I save the illustrator files as PDFs (Illustrator files are 515kb) they come out to a size of 5.15mb. Is there a tool in Acrobat Pro 9 (I dont have X) that can reduce the file size and keep the photo quality high? There is a tool in Tools>Print Production>Flattener that reduces the file some but I dont know what this tool does and I dont know if there is a better tool to use.
Thanks

What is the intended end result for these documents?
An aerial view map has me thinking plenty of detail as to terrain, color, imagery. If these are going to be printed at any decent resolution, 5mb is the lowest you're going to achieve, and possibly to low.
The Illy file is 515kb; that encomapsses the data for Illy to create the document, but likely only a pointer to the graphics/links.
If your links are embedded, I expect the file size would be significantly larger.
The pdf has any links/images embedded, as part of the end product.
What is the intended ouptut?
Are there links? images?
Embedded in Illy or linked?
What is the file size of any links/images, what are the pixel dimensions & resolution?

Similar Messages

Advice on software for creating pdf's

What is the best option for software to create pdf's?I downloaded Primo PDF and the quality was lousy. Suggestions greatly appreciated!

Tried Acrobat?
http://www.adobe.com/products/acrobatpro/tryout.html

FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

Problems in creating PDFs from Indesign under Snow Leopard

The Acrobat PDF Printer does not work under Snow Leopard anymore.
Adobe gives this alternative:
http://kb2.adobe.com/cps/509/cpsid_50981.html
After an update to Acrobat 9.1.3 PDFs should now be generated through a new "Save as Adobe PDF" option under the "PDF" button in the system print dialog.
This does not at all work in Adobe Indesign with it's proprietary print dialog. The PDF-Button is only available in the system print dialog (I know it is accessible from within the Indesign print dialog panel, yet clicking on the PDF button and selecting "Save as Adobe PDF" is ignored).
To make things worse: If you follow the advice to delete the Acrobat Printer from the "Print & Fax" panel this deletes the ADPDF9.PPD from the Library/PPD folder! You even cannot produce .ps files and distill them manually. Fortunately I was able to restore the ADPDF9.PPD from a backup.
This is really annoying: How can Adobe state everything works fine under Snow Leopard if you are not able to create PDFs any more? Or did I miss something?

Hi.
make this.
1. Go to the Apple> System Preferences...
2. Open the "Print & Fax" preference panel.
3. Select the Printing tab, to get to the printers list.
4. Select the printer "Adobe PDF 9.0".
5. Click the options and supplies button.
6. Choose the Drive.
Now I have reinstalled Leopard. but first like a Drive I have listed only a "Generic Printer".
I tried to reassign it ADPDF9.PPD but is not recognized and automatically resets to a generic printer.
So after some tests that I have found here
http://kb2.adobe.com/cps/509/cpsid_50981.html
I have reinstall leopard
This has been my problem.
mario

Cannot create PDF w/ custom page size in FM 9

I just upgraded to the new Technical Communication Suite and cannot create a PDF from FrameMaker with a custom page size anymore. I need to create a PDF with a page size of 8.125" by 10.875", and have tried both Save As PDF and Print to the PDF driver. I followed all of the instructions on how to do so via the PDF printer driver's "Printing Preferences", Adobe PDF page size, etc. When that didn't work, I also tried Save As PDF with a custom page size ... still won't print to the custom size no matter how many places I specify it.
My only way to get my custom page size at this point is to create the PDF and then go in and modify Document > Crop Pages > Change Page Size to Custom, and specify my size. This is clearly less than desirable.
I am using FM version 9.0p 196. Any help/advice/suggestions welcome!

Cindy,
You should get the FM updates. There have been 3 patches released since the 9.0p196 version. Install them in order.
Before creating PDFs, make certain that your default printer is set to the AdobePDF printer instance. The SetPrint utility from Sundorne helps ensure that this is always the case for FM, see http://www.sundorne.com/FrameMaker/Freeware/setPrint.htm
In the Save As PDF dialogue, set the "Page Size" for the output on the Settings tab, as shown here:
Set your PDF joboptions for the appropriate press requirements.
Set your registration if required.
Make sure the "Convert CMYK Colors to RGB" is set (the PDF CMYK generation is still buggy).
Hit the "Set" button and you should get the correctly sized output.
When you were creating the ouptut via the printer route, if you had set the "Generate Acrobat Data" option, then FM sets the document so that it is always cropped to the FM page size, rather than the printer specified output sheet size, in the final PDF. Omit setting this option and it should work via this route as well.

Acrobat 8 Pro and Create PDF from a Website

Hi,
I'm out of sorts. I can't seem to be able to turn a website thread into PDF file using my Acrobat 8 Pro (Mac user)....
The thread I'm trying to save has multiple pages and all Acrobat 8 does is save only the first page and not any of the subsequent pages.... unless I manually go page by page but then I end up with multiple PDF files that I would have to combine and that is just too time consuming --and would have to learn to do that as well.
Here's the link to the website thread I'm trying to convert into PDF:http://tinyurl.com/6guqpf
Could someone please advice what I may be doing wrong?
Thanks,
R

Thanks Paul, I've tried to Save as PDF in the OSX print dialogue box- but it only saves the first page of the thread I'm trying to save (when most threads have more than 1 page, sometimes up to 30 pages each)
This is what my friend wrote and how she found a way to solve her problem.... however I don't have Adobe 5 as she does and I would like to not have to get Adobe 5 but use only Adobe 8....
<<I start Adobe 8.
Select Create PDF from Web Page and paste in:
http://learningcenter.atkins.com/sessions/discussions/index.jsp?courseSessionId=7233&webPa geId=1000007&courseId=3856
When it's made the first page (see attached) [<<=== can't attach here since you need a password to view it.]
I save it and exit.
Then I open Adobe 5 and then I can click on each topic to start capturing the information (meaning all pages to each thread without a problem).
If I click on a topic in Adobe 8 ... it makes a page in a new browser window ... and I'm lost.>>
Do you or anyone else know why this is so? Why Adobe 8 would open a page in a new browser window and Adobe 5 doesn't?
Thanks again,
R

Win Freehand can't create PDFs correctly

Any help with the problem below would be much appreciated.
We recently upgraded to Freehand MX (11.0.2) running on 3
Windows (XP) machines but we can't create a pdf file where the
fonts are included correctly using the print to pdf option.
Freehand will also not produce a PS file for printing correctly as
the fonts are also not being included. We have checked all of the
include font options but still they do not appear to be included in
the file. Also, copy and pasting from the created pdf file creates
gibberish.
Within the pdf's document preferences the fonts show up as:
Gen.Frutiger-45-Light (Embedded Subset)
Type: Type 1
Encoding: Custom
Within the actual document page the font appears to have been
substituted with an equivalent. Outputting to an EPS also has the
same problem. And, the problem also occurs with all fonts. Freehand
9 still works OK.
So far all Adobe have said is that Freehand just doesn't
work: 'Unfortunately there is nothing we can do about this as
Freehand is a discontinued product and the compatability between
Freehand and Acrobat will not be updated'.
Has anyone else had this problem? Any help would be much
appreciated as at the moment Freehand MX is just unusable and
Adobe's opinion seems to be so what.
Thanks in anticipation

I have had the same problem in the past. In the end I got a
pro to sort it out. It would be great get some advice if the
problem occurs again.

SharePoint Online - Generate or create PDF documents with content

Hi,
We are in the process of evaluating SharePoint Online for a project that requires to create PDF documents. These documents are kind of reports that can be generated in the system. In case of on-premise we would have created a custom farm solution probably
using some PDF creation DLL to create the document.
However, wanted to know what are the options in SPOnline? The word automation service might not help because in that case we will need to generate a word document first and then convert it to PDF. Also, creation of this word document would again be a question
to answer.
Any suggestion/thoughts?

There is no create a PDF option in SharePoint. (not in on-prem and not in online)
You can print to PDF in most of the Operating systems and/or browsers by default.
And you can of course create a document and save that to PDF (or export to PDF or Print to PDF)
The Word Automation service..... is for Word... as you mention you dont't want to use word.... so that is not an option.
In general ... WHY?
If it is for Locking down the posibilities for a end user who sees the document you can also implement IRM (based on AADRM or just in Word itself)
If it is for publishing... you also need a "source document" and that can be Word.
So without the whole story it is difficult to advice.... In general if you want to create PDF document and edit it right from PDF and also don't want to use the Office suite, maybe a solution of Adobe like: https://www.adobe.com/creativecloud.html
Michiel Hamers www.SharePointman.nl Don't hesitate to contact me for a SharePoint/O365 question.

Problems with black color creating PDF from Excel 2013

Hi
I want to create PDF from Excel 2013 using Adobe Acrobat distiller. When I do so I have problem with black which is 300 percent black instead of 100K. Problem is only with drawed lines from Excel's symbol menu (text is fine).
I use Acrobat 9 Pro and few days ago switched from Office 2000 to 2013.....and problems started.
Office 2000 and Acrobat 9 Pro worked ok and everything including drawed symbols like lines or squares were 100K black in PDF. Now in the case of Excel 2013 it is not so but when I use export function included in Excel and export file to PDF output is 100K. I am not sure if this kind of export is good for me. I use PDF's as inputs to InDesign. So I would like to have more control when create PDF from excel. But in Excel setup I can choose standard and minimum size and that is all.
I imported Adobe PDF Settings from computer where these settings worked with Excel 2010 but they do not do same job for me in combination with Excel 2013 (I have 300 black).
To explain my workflow:
I am a publisher of crossword magazine and I use Excel to write crosswords. Then I create PDF's and import them into InDesign.
Should I use internal export included in Excel 2013? Are these PDF's ok for working in InDesign and finally for print purposes?
Or If you have any suggestion how to create PDF via Adobe Acrobat distiller setup (which I prefer) please give me advice.
Thank you in advance
Juraj

These are tough issues I suspect and the answer you need is probably trivial (it is finding it). I will make some suggestions, but I have no idea if any will work.
- In the printer under the Properties>Layout>Advanced>print quality, I use 300 dpi (default is 1200).
- Under the printer preferences>settings>edit the settings file, I use again 300 dpi (default is 1200 dpi).
These may not fix your issue, but migth be worth a try. You could also try using the preflight script to change to gray-scale. It may not make any changes, but again may be worth a try.
All I am trying to suggest are the things I would be looking at. Maybe they will lead you someplace. Others may be by with better suggestions in time.

Creat PDF funtion in Word 2010 Not Working Correctly

Hello.
We recently installed Adobe Acrobat XI Standard within our orginization. We are having issues with our company letter head and the Create PDF function within Word 2010. When we attempt to use the Create PDF function, it creates a PDF that has the letterhead elements, but no text on the page. When we select to print to PDF, that option works without issue. Can someone lend some advice here?
Thank you!

Hi LotteNZ,
Just for clarification, I'm using PowerPoint 2010 and Adobe Pro XI. I have an ongoing project for which I have to produce a PDF based on a PowerPoint file that has a lot of links. I eventually found an actual Adobe person who answered my question so I could stop looking for features that don't exist.
Here's the bottom line:
- Links that go to Next, Previous, First, or Last slide will work correctly in the PDF
- Links that go to other specific slides within the file will not be transferred to the PDF
- The links that don't get "inherited" in the PFD have to be re-created in the PFD (which isn't difficult -- just tedious when there are a lot of them)
Adobe is aware of this but the person who wrote me did not know of any specific plans to fix it in future releases (which doesn't necessarily mean that they won't).
I think Adobe supports "its own" first, which makes sense. I believe that If the source file was created in InDesign, all of the links would be supported. But for a variety of reasons, in my case, my source file has to be PowerPoint.
It's annoying having to recreate links every time I make changes in my source file and so one trick I've learned is to only replace pages that have changes. It's an imperfect system, but it does speed things up.
Hope that helps!
Fifi
www.FifiKlein.com

Creating PDFs using Pages and Mail

Hi,
I'm a contractor and I use Pages and Mail to to create PDFs of invoices that I email to clients in the form of attachments. I have Mail set up to to send only Windows friendly attachments, and to put them at the end of emails. I have one client, the facilities director of a large community college, who consistently cannot open the attachments; he can read the text of the emails, but he cannot open the attachments. He has to send them to his IT department, where they use a mac computer of some kind to open the attachments, which they send them back to him. I've discussed this with their IT department, and they've told me that they have to use a mac to open my attachments. If anyone can offer some advice on this issue, I'd appreciate it.
Caoim

I know from my own experience that although there should be no problems with Mail's attachments, just once in a while recipients have the problems you describe.
The solution that worked for me 100% reliably was to install the paid for plug-in Attachment Tamer from: lokiware.info
You can use it for free to test it before committing to purchase, but I'm pretty sure all your recipients will be able to cope with all your attachments.
To elaborate, I used to have to send numerous attachments every day to mostly PC users. Randomly some would complain that I'd either forgotten to include the attachment (I hadn't) or they couldn't read it/open it/save it, etc. It's quite likely the fault was in the way their email client was configured. All I know is that as soon as I installed Attachment Tamer (it was Mail Attachments Iconizer back then) I never had any more complaints. For the knowledge that I wasn't going to be pestered into trying different ways of sending the files I was happy to pay for the plugin.
(Usual caveat: I have no connection with Lokiware, but very happy to recommend their product).

Creating PDFs - Page size

We are scanning Docs as Jpegs at 150dpi resolution. When I try to create a PDF through AA 8.01 Prof effectively an A4 image is recognised as being A3. In Windows the file property shows the image to be at 96dpi. Has anybody come across this before? If I convert the image to 150dpi through paint shop pro Adobe then picks up the correct page size!!! Is this a Microsoft issue or what?
Any advice would be very much appreciated

Aandi,
The number of pixels remain the same - Hence reducing the DPI increases the physical size when its converted to a PDF. The process is that scanned images are rotated etc... in software. We then run a create PDF program (Arts Import). Because we didn't realise that there were rogue images the resultant PDF showed pages that were bigger. This is no fault of AA its a fact of life that if the number of pixels remains the same, then differing DPIs will result in differing page sizes - Something I have learned today!!
Thanks for your help but AA is not at fault - Its the step from scanned images to making them fit for purpose before creating PDFs

Problems Creating PDFs

A lot of problems creating PDFs come from using the wrong printer to create the PDF or underlying printfile.
You should use Adobe's Distiller printer instance to create a PDF. This comprises the latest Adobe Postscript printer for your operating system plus the Distiller PPD.
Don't use an HP printer to create your PDF. PostScript, or otherwise.
Don't use a Xerox printer to create your PDF. PostScript or otherwise.
See #1.
Note: If you are outputting to a service bureau, you might want to use something other than the Distiller printer instance. However, if you encounter problems with your particular PDFs, try using the official method with the Distiller printer to see whether any problems are limited just to your setup. If problems persist, you might have to create your PostScript output using one printer driver and the PDF using Adobe's Distiller printer instance.
Common problems include:
Black and white, or greyscale, PDFs created from color FrameMaker books and documents.
Distiller terminating the PDF creation process early, thus no PDF is created.
Troubleshooting:
For lack-of-color problems, first check you don't have Spot as Black set in the Frame Print dialog.
Update the printer you are using to the latest Adobe PostScript printer driver version.
Uninstall the printer you are using to create PDFs and to reinstall the latest version from scratch.

FAQ: Creating PDF Files from FrameMaker Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!
Dov Isaacs - 07:02pm Dec 6, 2001 Pacific
An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

Save as does not Create PDF Compatible File even when the creare pdf compatible files is on, Illustrator CC 2014

save as does not Create PDF Compatible File even when the creare pdf compatible files is on, Illustrator CC 2014

When I open is adobe acrobat I get this message.
"This is an Adobe® Illustrator® File that was
saved without PDF Content.
To Place or open this le in other
applications, it should be re-saved from
Adobe Illustrator with the "Create PDF
Compatible File" option turned on. This
option is in the Illustrator Native Format
Options dialog box, which appears when
saving an Adobe Illustrator le using the
Save As command."

How to create pdf and html usin oracle policy automation with steps.

Hi,
I tried to create pdf report.But they have some problem for while creating xslt.
Pls provide more steps or simple example creating xslt and which xml use for that also.

Below is a working (OPA 10.1) example, which I found earlier in this forum. You can call it from a document control on the summary screen. The xml is provided by the server containing all attributes with a public name.
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:fn="http://www.w3.org/2005/xpath-functions">
<xsl:output method="xml" indent="yes" encoding="utf-8"/>
<xsl:template match="/">
<fo:root>
<fo:layout-master-set>
    <fo:simple-page-master master-name="my-page">
      <fo:region-body margin="1in"/>
    </fo:simple-page-master>
</fo:layout-master-set>
<fo:page-sequence master-reference="my-page">
    <fo:flow flow-name="xsl-region-body">
      <fo:block margin-top=".5cm" margin-left=".1cm" border-start-style="solid">
        <xsl:apply-templates mode="dump" select="/session"/>
      </fo:block>
    </fo:flow>
</fo:page-sequence>
</fo:root>
</xsl:template>
<xsl:template match="*" mode="dump" priority="100">
            <fo:block margin-top=".5cm" margin-left=".1cm" border-start-style="solid">
                Node:
                <xsl:value-of select="name()"/>
                <xsl:if test="count(@*) > 0">
                    <fo:block margin-left="1cm">
                        Attributes:
                        <xsl:for-each select="@*">
                            <fo:block><xsl:value-of select="name()"/>=<xsl:value-of select="."/></fo:block>
                        </xsl:for-each>
                    </fo:block>
                </xsl:if>
                <xsl:if test="string-length(normalize-space(text())) > 0">
                    <fo:block>Text Value: "<xsl:value-of select="text()"/>"</fo:block>
                </xsl:if>
                <xsl:apply-templates mode="dump" select="*"/>
            </fo:block>
    </xsl:template>
</xsl:stylesheet>

Advice on creating PDF

Similar Messages

Maybe you are looking for