DCS 2.0 EPS PROBLEM ON PDF

Hi,
When I place DCS 2.0 formatted EPS jobs TO Distiller for PDF, the resolution is too low, but same job is ok when Tiff. My pdf settings are PDF/X-3:2002.
Can anybody help this trouble?
Many Thanks...

DCS2 is NOT EPS, and cannot be distilled directly. This is by design.
Or do you mean you are placing the DCS and distilling a colour file?
Don't, DCS2 is for making separations. DCS2 is designed to produce a
low resolution preview if you ignore this and print colour (assumed to
be a proof).
Apparently the very latest InDesign can rejig DCS2 files and combine
separations to make it work as people seem to expect...
Aandi Inston

Similar Messages

  • Converting Multi page .eps files to .pdf Preview is broken

    I have in the past used Preview to convert multi page .eps files into
    .pdf files. Since I have upgraded to Tiger 10.4.3 Preview will no longer work.
    Does anyone know how to uninstall Tiger 3.03 version and go back to 2.xx version? Are there any utilities to do this for me? On my older mac (9.x) I have Adobe distiller.
    Thanks
    Max

    I have just copies the older version of Preview onto this machine and am running 2.10 of Preview to solve this problem.
    Max

  • Include EPS image in PDF

    Hi.
    I Want to include EPS image in PDF document but i don't know how to!
    Please help me, i don't found in the PDF referece how to!
    Thanks bye!

    > The PDF reference don't talk about that.
    It doesn't talk about it, because you cannot do it directly. The same
    with any other vector format, like WMF.
    Think of the problem as two stage:
    1. Convert your vector format to PDF.
    2. Merge the PDF content into your PDF.
    The simplest way to merge content is to take a page from your new PDF,
    turn the page into a form XObject, and add the form XObject to the old
    page. Then add q/cm/Do/Q to the page stream of the main page.
    For step 1, convert PostScript to PDF, you may want to make use of
    existing tools. Otherwise, this is a fascinating project but not less
    than 4 solid years of work.
    Aandi Inston

  • 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

  • Preview not saving when converting multiple .eps files to .pdf

    Hi,
    I have a macbook pro with snow leopard. I open a group of .eps image files using preview into the same window. I then shut the window with "cmd w". It says do you want to save all. I click save all. But then no saves are made.
    If i open the group of .eps files using preview into separate windows and click "cmd w", then click save, it tries to save as untitled.pdf as opposed to "filename".pdf.
    I previously used preview on a powerbook to convert .eps images to .pdf. In that version of preview the files would open in their own window. When i hit "cmd w" and save it would use save file as "filename".pdf.
    Why does the newer version of preview not at least do this? Preferably the new version of preview would save all the .eps files as a batch as stated in my first sentence.
    Does anyone have any ideas what i can do?

    Possibly similar problem:
    When I open a JPEG in Preview, adjust the quality, and try to Save As, it simply saves as the original, not the new reduced-quality file. This is true even if I save it in a new location.
    - open a 200kb JPEG
    - try to Save As with quality reduced to only 50kb
    - it saves as the original 200kb file

  • How can I output eps data from PDF?

    With CS6, why can't I output eps data from PDF, as I could did in use with CS zero version?

    What specifically? AI stil lcan save EPS, so what's the problem?
    Mylenium

  • I am having a problem opening pdf document.  I get error message: "Adobe Reader has stopped working"

    I am having a problem opening pdf document.  I get error message: "Adobe Reader has stopped working" then I get Windows is looking on line for a solution, but then my document closes. I tried uninstalling and reinstalling Adobe Reader XI, rebooted my computer but this did not help.  I get the same message. What to do?

    Can you open Reader by itself?  If so, check if disabling Protected Mode improves the situation [Edit | Preferences | Security (Enhanced)].

  • Printing problem when PDF is sent to the printer with certain fonts - missing text

    I'm running into a printing problem when PDFs containing certain characters of the Calibri font are used.  The text in large sections of the PDF is missing on the paper version, but the text is there on the screen.  It's also happened when the PDFs we created were e-mailed out to a client and printed on their printer.  The problem is not present when printing directly from the programs (Microsoft Word, Excel, Visio, etc.).  I've been trying to get tech support from Adobe on this, but every time I call they apologize and say they will call back in 4-6 hours with an answer.  Same result each time, no call back.  If anyone from Adobe is listening, it's case number 184891587.  The font appears as an embedded subset when I look at the document properties.  Sometimes deleting one or two Characters allows for larger text blocks to be printed - i.e. removing a long dash in bold from the heading of a paragraph makes the paragraph reappear when printed to paper from PDF.  In all cases the PDF appears correct on the screen.  Printing as an image allows the text to appear, but the image quality isn't acceptable for small text, even at the 600 dpi setting on the printer.  If the PDF is sent out by e-mail, we do not have control over the end-user's printer setup anyway, so we need this to work in all cases.  
    The setup/process I'm using is as follows:
    Windows 7 Professional SP1 64-Bit
    Microsoft Office 2013 - problem is present when printing documents from Word, Excel or Visio.  Even other variations on documents. 
    I've tried Acrobat versions 11.0.0 to 11.0.5 as well as Acrobat Pro 11.0.0 and 11.0.1.  Same Result
    Printing to Adobe PDF as the printer, from the third party application
    Printing to a Xerox printer from PDF using Acrobat - Text missing
    Client prints to Konica printer - Text missing
    I print to the wide-format Ricoh (which also does 11x17) and the text is present. 
    Is there something I'm missing?  Is the entire font not getting embedded into the PDF file?  I noticed that rolling back to a much older version of the Calibri font (1.02 compared to 5.72) makes the problem mostly go away, but it's not completely gone.  Is it possible the font is too large to be completely embedded?  Where can I go from here? 

    Success!  At least for now.  It looks like my problem was fixed with Adobe's most recent update, 11.0.06.  From the release notes:
    PDF creation
    Added support for Lotus Notes 9.
    Added support for WebCapture in IE 11.
    Added support for conversions from AutoCAD 2013.
    3652540 A blank pdf is created for files having hidden visual style.
    3601108 Flow Chart converts as a multicolored square.
    3654345 Word documents missing parts of images in conversion to PDF.
    3654572 Temporary file size increases when creating pdf by combining multiple files into one PDF.
    3670155 PDF file created with Distiller XI prints incorrectly to some printers. (Emphasis mine)
    3599407 Checkbox check marks do not appear in these files.
    3663233 IE Web Capture in localized OS: Icons and drop-down menu items are missing and conversion dialog is not localized.
    3651931 Chrome Only: Few web pages when converted to pdf from Chrome plugin doesn’t show up the Save As dialog.
    3597910 EPM Mode On: Web capture is not working on Windows 8-32 bit when cache folder is missing.
    3610644 Firefox 23.0: With Firefox version 23.0 (latest), the WebCapture icon shows up very dim as if it is disabled.
    3650244 ODA falis to convert DWG files to PDF for large files.
    I don't know if that's definately what solved the problem, but it sure sounds similar and this is the update that made the printing problem go away.  We can't get the PDFs to fail at this point with our printers, even with Calibri 5.72.  I'll come back to thread if we have printing problems at the end-user locations. 

  • Problem with PDF extract in a report

    Hi guys,
    We are facing a peculiar problem with PDF extract in a report. When we run a report and export PDF , all the records in the result set are populated in the PDF. however, if I navigate away from the report and return back to the same report, and click on export pdf (with the result set already populated) i get a blank PDF document without any records. If i run the report again and then export the PDF it works fine.
    Export excel works fine for all cases.
    I am assuming it has got something to do with the way the system handles the cache for PDF export.
    I also found that this occurs only when we have a value list filter with "none" set as default,and in this case, initially on opening  the report for the first time the query does not get executed automatically.
    Any help on this would be highly appreciated.
    Thanks and Regards,
    immanuel

    Hi Immanuel,
    Have you tried clearing the cache? My guess is, it is probably a defect.
    Regards,
    Vikram

  • Problems opening PDFs from SharePoint 2010 with Acrobat X Pro

    Is anyone else having problems integrating pdf document support into Sharepoint 2010?
    I now have the icon showing for any pdf documents saved in a Document Lirary, However I don't get the options of Checking out - editing an checking in. There is also no revision control. I think that when I open a pdf document, the servers own copy of Adobe Reader opens, and not my local copy of Reader or Acrobat X pro.
    I've done what it says in the Administrators guide for Sharepoint integration and I'm still unable to get this functionality to work. As we use interactivve pdfs for a lot of our internal documentation the pdf integration features are very important.
    Any help from users who have already been through the pain of sharepoint integration would be really appreciated.
    Regards.

    Hi Bill,
    Looking at your initial problem of not being able to open the SharePoint hosted PDF document from the web browser.
    Could you please verify that as per the "Enterprise Administration Guide", the DocIcon.xml file of your server contains the following line:
    <Mapping Key="pdf" Value="AdobePDF.png" OpenControl="AdobeAcrobat.OpenDocuments"/>
    Please verify that the OpenControl attribute is also mentioned correctly. Without this the Acrobat Active X component would not be invoked.
    thanks,
    Shivani

  • Adobe Acrobat 9.4 Pro / Win7 Enterprise (64bit) - problem opening pdf

    Hello,
    i got problems opening pdf files.
    when i try to open the pdf file i get the message 'access denied'. That happens when i try to open it with a standard user.
    opening that file 'as administrator' works fine.
    I tried the Win7 compatibility check and Win7 tells me that Acrobat isn't compatibel. I tried to run acrobat.exe in different compatibilty modes (XP SP2/SP3, Win NT) -> no cure . Only thing working is to run Acrobat as administrator )

    You can try to enable Admin rights on your computer.
    In start menu use the search field, type in cmd once you see that  in your search result right click on cmd and Select "Run as Administrator".
    Once the Command Prompt open's type in.
    net user administrator /active:yes hit enter after typing it.
    You should the message "The command completed successfully."
    After you try this launch the software.

  • Adobe Acrobat Pro XI problems printing PDFs created from AutoCAD.

    Just installed Adobe Acrobat Pro XI and am having problems printing PDFs created from AutoCAD.  Printing other PDF created by MS Word works well.  Had a similar problem in an earlier version of Pro.  The fix I figure out then was to print the PDF file as another PDF.  Using the second PDF to print to a plotter typically worked.  It does not work for Adoabe Acrobat Pro XI.

    Hi presottom
    Please refer ; http://helpx.adobe.com/acrobat/kb/troubleshoot-pdf-printing-acrobat-reader.html
    or
    Let us know more details about it to help you better ?
    What is the OS ?
    is there any error message , etc .. ?

  • Having problems converting pdf to word. I'm not able to convert the file, what do I need to do?

    having problems converting pdf to word. I'm not able to convert the file, what do I need to do?

    Hi prates77,
    I'm sorry to hear that you're having trouble converting files. Are you receiving the conversion error regardless of the file that you try to convert? Does the error occur whether you use the web interface, or convert via Reader? And an odd question: how many files do you have stored in your Acrobat.com account? We have seen reports of this error when there are a large number of files stored in the root folder of your Acrobat.com account.
    I look forward to hearing back from you.
    Best,
    Sara

  • Since I downloaded Adobe Reader 11.0.07 I have been totally unable to print any PDF files using my Dell 1720 laser printer - I just get a blinking "error" light on the printer, no other error messages . I never had a problem printing PDF files before down

    Since I downloaded Adobe Reader 11.0.07 I have been totally unable to print any PDF files using my Dell 1720 laser printer - I just get a blinking "error" light on the printer, no other error messages . I never had a problem printing PDF files before downloading the new Reader version. Suggestions? Thank you.

    Hi,
    Which version of Adobe Reader were you using earlier when printing using Dell printed was working fine?
    Thanks,
    Shakti K

  • Consolas hyphen problem in PDFs

    Here's the setup: FrameMaker 7.2, Windows XP, Acrobat Pro 8.1.3, although I think all versions are actually irrelevant to the issue.
    I recently switched to Consolas font for my code listings.  But when Acrobat/Distiller converts the FrameMaker file to PDF, the hyphens end up with the wrong encoding.
    It's definitely an Acrobat issue.  When I copy-paste from my FrameMaker source file to a text file, the consolas hyphen correctly shows as unicode 2D (decimal 45, the "hyphen minus" character).  But copy-pasting from the PDF ends up with the unicode 2010 character (the "hyphen" instead of the "hyphen minus" char).  And while they "look" the same, engineering readers need to be able to copy-paste from the PDF.
    So, is there a patch or a way to tell Distiller to map this character as needed?
    TIA,
    -Monique

    Please delete me from your mailing list.  Tks.
    Date: Wed, 10 Feb 2010 10:54:49 -0700
    From: [email protected]
    To: [email protected]
    Subject: Re: Consolas hyphen problem in PDFs
    Exactly how are you converting to PDF. You say Acrobat/Distiller, but what are the steps you are taking. There are too many options not to isolate your process first. Are you printing to the Adobe PDF printer, exporting, or something else?
    >

Maybe you are looking for