Indesign Loses Text Gradient After Export To PDF SWF

I have some Indesign files from a client and everytime I export from indesign to pdf and then convert to a swf, it removes the text gradient and adds black instead. Images attached for reference.
<---PDF
<---SWF
I've tried numerous export options. Is there something in particular that I'm supposed to be flattening?
Any help would be much appreciated!
Thanks!

Hi DesPro_7, Thank you! Your answer was very helpful, and it seems to solve one of my problems, which is the same as what Franklinsdictionary describes.
I have a design using gradients in text, including a gradient effect on a rule below, used as a banner behind my text. I'm losing the gradient when the PDF is converted to SWF, and while we're working on a way to export to SWF directly from InDesign, our current workflow is cropping and optimizing a printer PDF to convert to SWF.
Before InDesign CS5, we had little trouble with transparencies, but this became an issue on our projects using CS5 or above.
Part of the optimizing process includes flattening transparencies, but text with gradients doesn't seem to flatten, nor do my banners created using rule below behind the text.
Any idea why this seems to be an issue with text? Any insight might help!

Similar Messages

  • Indesign CS4 button flashes after exported to PDF and viewed in Acrobat Reader/Professional X

    Hey everyone,
    Greetings!
    I've encountered this odd problem when preparing my portfolio.
    I've created some 40 buttons in InDesign CS4 (all according to the official tutorial) to Show/Hide Fields (specificly images), and navigate through the pages.
    The buttons all have their own Normal and Rollover states, but no Click states.
    After exporting the file to PDF, I tested the buttons in Acrobat Reader 9 and Acrobat Pro 9, and both the actions and the states worked fine.
    BUT that's not the case with Acrobat Reader X or Acrobat Pro X.
    The actions are still there, showing the images and navigating, but the states are not!
    The buttons' rollover states just flashes when the mouse hover above them, and even in Normal state, they kept *blinking* randomly.
    Frustrated for a week.
    PS. I suspected and used a Indesign file with only one simple button to rule out the following:
    1. Overlapping buttons
    2. Slow processing due to large image size
    3. Mishandling of transparency
    At this moment I'm pretty sure it's an Acrobat thing...Help!

    Thanks Dave! I was in the middle of writing this when your post came in:
    Not sure if this will help anyone, but I changed the button fill color to white and it seemed to fix the flicker. I exported each state from indesign as a PDF and recreated the button from scratch. This still had the flicker. I'm guessing something strange is happening with the transparancy of the states.
    Glad to hear it's fixed!

  • Indesign to PDF. Logo appears blurred after exporting to PDF.

    I have a png and jpeg logo that appears fine in my indesign doc but when I export to PDF the image is blurred and has a white line around the logo edge as if the image is bleeding into the page.
    The png and jpeg logo file (I have tried both versions) is 4x4 inches and 300 dpi. I am a loss at to what the problem is. I have tried smooth line art in the Adobe preferences.. but nothing works there.
    Is there a standard setting for Indesign and Adobe (in terms of output) that would help resolve this issue.. ? Any ideas greatly appreciated...

    Hi. Thanks for stepping in with some advice. I'm actually exporting at print quality so avoiding the low resolution pdf issue but the logo has a transparent background and is a png file. Would it help if I resaved it as a vector file? Any further advice would be welcome. It looks 100% fine in Indesign but just my exporting to PDF makes the logo look terrible. Thanks again..

  • Text quality when exporting to PDF -- CS4

    Hi,
    Whenever I export my InDesign document to a "high quality print" (PDF) or any PDF preset, for that matter, the text becomes "chunky." The picture below illustrates the problem. The text on the left is how the text appears in InDesign, while the text on the right is how the text appears after exported to a PDF. I have used system fonts and the problem still persists. When I first installed InDesign, I never had this problem, but after having to reinstall it, my exported PDFs look terrible. How can I get the text to appear as it does in InDesign when exporting to a PDF?
    http://img35.imageshack.us/img35/549/fontsf.jpg
    Thanks!

    Acrobat, and Reader, have user preferences, just like other Adobe programs, and you can turn smoothing on or off for text and lineart (this also affects "stitching" on PDFs made with flattened transparency).
    InDesign automatically tries to embed all but the most complex (read CJK) fonts when exporting, and should throw a warning, if you haven't turned it off, when it cannot embed due to font licensing restrictions (in which case I would change the font). Printing to PDF requires that font embedding be enabled in the joboptions that are used by distiller, and those options are quite flexible as far as all, none, or some (i.e. you can designate fonts to always embed or never embed).

  • CS 3 InDesign Crashes when trying to Export To PDF

    Our File Problem
    Dell Microsoft XP service pack 2
    Mac Intel Duo, Tiger
    CS3 Fully Updated as of 3/17/08
    CS2 Fully Updated as of 3/20/08
    The problem first arose back when we upgraded to CS3, we found that files inside our document were crashing InDesign CS3 when we went to print or export the document as a pdf, the file originally made an interchange file which we could work with in CS2 so we went back and avoided CS3 until the catalog was finished.
    The problem arose again after we started using CS3 again, but not right away. Many documents have been built and exported and printed with no problem. I was able to find and fix the problem through a piece by piece removal process of elimination. I isolated the problem link, opened it in photoshop, made a new psd file and saved the new file with a different name. Problem solved.
    The problem became more complicated recently when I created a document, filled it with links, exported the file, changed nothing but copy in the document went to export and the document crashed InDesign. I then started the process of elimination and found that the problem link was different every time, and when placed into another fresh document would export just fine. All of the links were re-created in photoshop and used to create another document. The document was re created on other machines, everything went well until drop shadows were added into the document, then it crashed InDesign and could not be exported to PDF. We then took the same document, with the drop shadows, exported it in Interchange to CS2 and the document exported just fine to PDF.
    As a test on the drop shadow issue, we took a number of different files and tested these in CS2 and CS3 with and without drop shadows. Every file we tried in CS2 worked fine with and without a drop shadow. However ,we experienced a number of crashed of InDesign with the drop shadows on these files in CS3. It seems to be just a portion of images, of a certain type of product we carry, but other than that there is no consistency to what is causing the crash. We also tested other effects and had the same results with InDesign CS3 crashing.
    The other issue we see with this is that before the 1st of the year, we were able to export the same images in InDesign with the drop shadows and other effects. It seems that since the first of the year, the same images are not longer able to export from CS3 to a PDF. A couple of the possible thoughts we had were that there was an issue with recent updates in CS3, to test this we are going to uninstall CS3 and reinstall without running updates. We also are going to try to recreate the files that crashed InDesign and see if they can crash again on export.
    Has anybody else experienced any similar issues? Does anybody know of a way to identify the problem in CS3 or with our files other than through trial and error? This is a major issue and problem for us since we are primarily a catalog based business and cannot have out catalog crash unexpectedly when we spend months working on it.
    This problem is also not operating system specific, it is happening on both machines listed above

    Dean,
    We found that the issue is a bug in the program, and this was the response i Got from an Adobe guy:
    Initial Response:
    Thank you very much. Weve been able to reproduce the crash. It appears the underlying bug is triggered by having tall narrow PSD images and transparency effects (i.e. drop shadow). Well be working to further understand the root cause, and then working on a fix for a future release/update.
    In the interim the best workaround I can come up with is to rotate the canvas in Photoshop 90 degrees so the image is short and wide, and then rotate it -90 degrees in InDesign after placing so you get the vertical orientation you want. The bug is triggered when processing the data as saved by Photoshop, so avoiding the tall and narrow psd should avoid the bug.
    Im sorry to not have an easier workaround or immediate fix. Please let me know if you encounter any new crashes. Ill let you know if our further investigation changes our understanding of the root cause of the bug.
    Second response:
    Well, I have a bit more info. Switching from a tall narrow image size to a short and wide one should avoid the crash for any specific image that crashed when tall and narrow, but unfortunately the root cause of the bug is in code that could potentially be triggered by any image. It appears to be exceptionally rare for other image proportions, but it is still theoretically possible. It just turns out its much more likely for a tall narrow CMYK+Alpha image.
    So, as it stands I dont have a 100% guaranteed way to avoid this crash, but it should be much less common for short and wide images. If you do encounter the crash, switching the orientation should avoid the crash. Hopefully the orientation workaround will allow you to be productive with InDesign until a future release contains the fix.
    Hope that helps

  • Hyperlinks from other placed indd documents or pdfs getting lost after export to PDF

    after upgrade vom CS 5.5 to CS 6: hyperlinks from other placed indd documents or pdfs getting lost after export to PDF
    I tried all options for the as well known and working export options

    after upgrade vom CS 5.5 to CS 6: hyperlinks from other placed indd documents or pdfs getting lost after export to PDF
    I tried all options for the as well known and working export options

  • Pages 5.0 (2013 Mavericks) Table of Contents loses page links when exported to PDF

    I'm using the new Pages 5.0 in Mavericks.  I have a TOC with page numbers that link to the sections in my document.  The links work fine in Pages.  When I export the document to PDF, the page numbers are no longer links.
    I tried the same in Pages '09 (which I still have on my computer) and the links work fine after exporting to PDF.
    Am I missing something, or is this a bug?

    Apple has removed over 90 features from Pages 5 and introduced a swag of bugs.
    http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
    Pages '09 should still be in your Applications/iWork folder.
    Archive/trash Pages 5 and rate/review it in the App Store, then get back to work.
    Peter

  • Failed to display CR after export to PDF in Browser

    Post Author: asnila
    CA Forum: Exporting
    Hi,
    I had a problem to display CR after export to PDF in browser. No message error displayed except the browser is blank.
    Below is the code that i had been used.
    Dim RptFilePath As StringDim RptExportOpt As CrystalDecisions.Shared.ExportOptionsDim ExportLocation As New CrystalDecisions.Shared.DiskFileDestinationOptionsDim ExportPath As StringRptFilePath = "C:\Project\reportPro.rpt"myReport.Refresh()myReport.SetDatabaseLogon("root", "", "localhost", "dbpro")ExportPath = "C:\Project\reportPro.pdf"ExportLocation.DiskFileName = ExportPathRptExportOpt = myReport.ExportOptionsWith RptExportOpt.DestinationOptions = ExportLocation.ExportDestinationType = ExportDestinationType.DiskFile.ExportFormatType = ExportFormatType.PortableDocFormatEnd WithmyReport.Export()Response.ClearContent()Response.ClearHeaders()Response.ContentType = "application/pdf"Response.WriteFile(ExportPath)Response.Flush()Response.Close()MyConnection.Close()
    Fyi, i'm using Crystal Report 10 embedded with VS 2005. Please help me.

    It looks like the 2 DLLs you mentioned, are getting corrupted or modified due to some operation that might have been performed on them. Can you please try the below mentioned instructions and see if that gets your application to install without any errors:
    1. Try installing your business app.
    2. When you see the error message as stated, try running the below mentioned commands: (Start | Run | Type cmd and hit Enter)
        regsvr32 LTKRN11n.dll /i /s
        regsvr32 LTKRN11n.dll /s
        regsvr32 LTDIS11n.dll /i /s
        regsvr32 LTDIS11n.dll /s
    3. The above commands should fix the issues in the mentioned DLLs and allow normal installation of your business app.
    Hope this gets your app to work and install properly.

  • Running headers wrong after export to PDF

    I am trying to use a Running Header (Paragraph Style) variable to display in the header of several sections in an InDesign file. It all works fine when viewed in InDesign. But when I export to PDF, the header in every section displays the title of the first section, not the current section. How can I fix this?

    Both. I have a single file divided into three sections, call it content.indd. That file is combined with another file in a book (.indb) The problem arises when I export the book to PDF. The second and third sections derived from the content.indd file are the ones with the incorrect headers.
    To be specific, in the PDF rendition, the first section header is correctly "Section 1: Overview." The second and third sections are titled differently, but still show "Section 1: Overview" in the header.
    Any ideas?

  • How to fix InDesign CS6 cloud crashes while exporting to pdf?

    Hi My InDesign CS6 cloud crashes when exporting to pdf.
    It's a Mac Book Pro, OS X 10.7.4. It shows a blank warning, and then there is a long report, here is part of it. Even all my old files can't be exported to pdf. Can any one help?
    Process:         Adobe InDesign CS6 [325]
    Path:            /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
    Identifier:      com.adobe.InDesign
    Version:         8.0.0.370 (8000)
    Code Type:       X86 (Native)
    Parent Process:  launchd [119]
    Date/Time:       2013-04-23 18:08:27.430 +1000
    OS Version:      Mac OS X 10.7.4 (11E2620)
    Report Version:  9
    Interval Since Last Report:          572434 sec
    Crashes Since Last Report:           18
    Per-App Interval Since Last Report:  621470 sec
    Per-App Crashes Since Last Report:   13
    Anonymous UUID:                      33716403-25A9-4DBD-B3F9-99FAE5855C5D
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

    Indeed. To be more specific, typically program execution begins in a main() function, which calls some other function (say, to handle menu selections), which calls some other function (whatever menu function the user chose), which calls some other function, etc., etc., perhaps 30 or 40 functions deep.
    Because of the way C++ calling conventions work, the history of which function called which other function is preserved in a data structure known as the stack. (The stack also does other things). Under normal circumstances, this "stack trace" is reconstructed to form the crash report.
    There is one stack trace for each thread (parallel execution components of the program), but the thread that crashed is usually the only one of interest.
    In this case, thread 0 crashed. Its stack trace is meaningless. It contains two stack frames (e.g. functions). At the top, the most recent function is called _XHNDL_trapback_instruction, which is a pseudo address that basically tells us nothing, other than there was some sort of fault.
    But typically we will see what function called that top function; and the function that called that; etc., etc.
    In your case we do not. Allegedly the crashing code was called from the address 4294967295, or in hexadecimal 0xffffffff. And that is the largest number that a 32-bit word can hold. It is, sadly, garbage.
    So your stack trace tell us zilch

  • Can you retain text highlighting when exporting to PDF from InDesign?

    Hi,
    I have several publications that are now going to be reviewed by another individual and I was planning to export them to PDF.
    However, I've already highlighted bibliographic references, table call outs, figure call outs in the InDesign file using different colors and I was wondering if there is a way to retain that highlighting when exporting to PDF? Just thought it might make their life a little easier since I already have all that done in the file.
    Thanks!

    Ah ha! Got it! All I needed was your prompt! I looked to make sure that it was set up as conditional text and noticed the Show/Hide option at the bottom of the pop-up. (I knew I saw something before that would allow this, but couldn't remember where!)
    Thanks for jogging my memory!

  • Text wrapping when exporting to .pdf

    I'm running Pages 5.2 on OSX 10.9.2. When exporting my document to .pdf, it does not retain it's text wrapping. When viewing the document in Pages, everything is where I put it. When viewing the document as a .pdf after exporting, some of the text will no longer be wrapped around some of the pictures. Which text no longer wraps around which picture changes every time I export, even without altering the document in any way. I have tried grouping the objects and the text together, which only seemed to cause more text to fail to wrap.

    I'm using Acrobat X. I've attached a cap of the InDesign poster, and what I get when exporting to PDF -- I lose the title, and "Directed by..." (which is the same type size/color as the playwright). Also, I have overprint preview checked for automatic (and tried all the other settings, too).

  • Can I ask InDesign to resample as it exports to PDF?

    When I export an InDesign CS document to PDF I'd like to know what InDesign does to the images that it exports. InDesign Help, in this case, was no help.
    I'll give a preamble so you know what I'm on about. Originally when I first started this project 2 years ago, I thought I would layout the images within InDesign, and just before printing I would go through every one of the 800 or so images in the book (it's a big book), and crop and resample them to 300 dpi at exactly the final printed size. Big job.
    After a few months of using InDesign I thought: no, I won't do that. When I export to PDF I'll assume InDesign will give me options to 'crop to frame size' and set the ppi to 300 dpi as well as converting images to grayscale if I so choose. It'll be automatic.
    I'll make it clear with an example. Let's assume an original image was scanned to give an image that is 4000 pixels wide and 2000 high, and that the final image is 20" x 10". It is to be printed on a Xerox iGen which requires 300 dpi for no loss of quality. So how does InDesign get that particular image into the PDF?
    Q1: Does it resample and export at 300 dpi? i.e. in the example above, will it export an image of 6000 x 3000 pixels to the PDF?
    Q2. Or does it export the original image and does nothing to the image except cropping if I ask it to? If it needs resampling that will be done at print stage by the iGen.
    Q3: I didn't see any options for converting to grayscale. Can you export a PDF as grayscale?
    Why I am concerned about this is because if the original image is exported, that may cause me file-size problems. I scanned most of my images at 20MB-60MB, yet a lot of them when printed will be of the order of 20 square inches and only require about 6 MB for adequate printing. I may end up with a PDF file that is 5 to 10 times larger than necessary.
    The real problem I have is: I trust PS and InDesign to resample my images, but I don't have that kind of faith in the iGen. If I can't ask InDesign to resample images when it exports, I may have a problem.
    When I did my original series of test prints in July 2006 on the iGen, I cropped and resampled the images ready for printing before I imported them into InDesign. So I haven't tested the iGen's resampling capabilities. I be blunt I don't trust it. The iGen ( a machine costing in the millions) failed a simple test of converting colour documents to grayscale. Here are my notes written at the time:
    b Converting to Grayscale using the iGen
    Do not use the iGen RIP to convert colour images to grayscale because it converts all gray densities above 90% to 100%. ie dark shadows end up as 100% solid black shadows with the accompanying sheen. I measured this figure from the K-only gradient at the bottom of the page. It appeared solid black for the first 9mm of a 96 mm black-to-white gradient. All densities between 100% and 91% ended up as 100%. The effect is very obvious in Mums hair which became a solid mass.
    My full notes on the iGen are here: http://jucreek.googlepages.com/temporary if anyone wants to have a look.
    Anyway, that's why I have concerns about images. Maybe I should just knuckle down for a week and go through 800 images, cropping and resampling every one in Photoshop. Talk me out of it, please.
    And that brings me to my final question:
    Q4: Can I ask InDesign to do that job for me: to crop, to resample at a certain dpi, and to overwrite the original image so that it all matches up?

    Guy,
    Let me try to recap all your statments with my comments:
    > Let's assume an original image was scanned to give an image that is 4000 pixels wide and 2000 high, and that the final image is 20" x 10". It is to be printed on a Xerox iGen which requires 300 dpi for no loss of quality.
    From the very start you're in trouble.
    The image size you describe, set at 300 dpi, will only be 13 1/3" by 6 2/3". If the image is scaled up to be 20" by 10", it will only be 200
    >dpi.
    So, we're starting with insufficient data according to your requirements.
    Nothing that InDesign or Acrobat does can make that image the correct resolution.
    > Q1: Does it resample and export at 300 dpi? i.e. in the example above, will it export an image of 6000 x 3000 pixels to the PDF?
    No, InDesign and Acrobat's print device will only resample
    b down.
    Neither will resample up.
    > Q2. Or does it export the original image and does nothing to the image except cropping if I ask it to?
    The image created in the PDF will be cropped. It doesn't touch the original file.
    > If it needs resampling that will be done at print stage by the iGen.
    I believe the iGen will only resample
    b down
    the same as InDesign and Acrobat's creation of the PDF.
    > Q3: I didn't see any options for converting to grayscale. Can you export a PDF as grayscale?
    As mentioned, that won't happen in the PDF Export but will happen with the PDF Print driver. However, that will also convert colors in the ID file, not just images, to grayscale.
    > Why I am concerned about this is because if the original image is exported, that may cause me file-size problems. I scanned most of my images at 20MB-60MB, yet a lot of them when printed will be of the order of 20 square inches and only require about 6 MB for adequate printing. I may end up with a PDF file that is 5 to 10 times larger than necessary.
    Perhaps I did my math incorrectly, but in your original example, 4000 x 2000 pixels cannot be set at 20 inches by 10 inches at 300 dpi.
    It requires 6000 by 3000 inches to be 300 dpi at 20 inches by 10 inches.
    > The real problem I have is: I trust PS and InDesign to resample my images, but I don't have that kind of faith in the iGen.
    I don't think you need to worry about the iGen if you set your images correctly. But as I said above, you haven't sampled them enough. So the iGen isn't going to do anything.
    > If I can't ask InDesign to resample images when it exports, I may have a problem.
    You set ID and Acrobat to
    b downsample
    not
    b upsample.
    > When I did my original series of test prints in July 2006 on the iGen, I cropped and resampled the images ready for printing before I imported them into InDesign.
    Cropping and resampling in Photoshop is always preferred as you have the options for how the resampling occurs that neither ID nor Acrobat have.
    > So I haven't tested the iGen's resampling capabilities. I be blunt I don't trust it. The iGen ( a machine costing in the millions) failed a simple test of converting colour documents to grayscale.
    No, I wouldn't have expected the iGen to convert to grayscale at all! Converting to grayscale can be done in the Acrobat print driver, but I would prefer to do it in Photoshop if I demanded very refined conversions.
    > My full notes on the iGen are here: http://jucreek.googlepages.com/temporary if anyone wants to have a look.
    See my comments above.
    > Anyway, that's why I have concerns about images. Maybe I should just knuckle down for a week and go through 800 images, cropping and resampling every one in Photoshop. Talk me out of it, please.
    You can resample using Photoshop's batch processing, but depending on the type of cropping that might need to be done manually in Photoshop. But if the cropping is always of a certain size and position that could be done in batch processing.
    > Q4: Can I ask InDesign to do that job for me: to crop, to resample at a certain dpi, and to overwrite the original image so that it all matches up?
    No, InDesign doesn't overwrite your original image, but it will change the image in the final PDF.

  • Text dropping when exporting to PDF

    I'm working on an very large poster for a theatre company. The poster has an image, and uses the font Gotham for the text. When I export to PDF from InDesign 5.5, some of the text disappears. I used effects on the title, which disappears, but also some text at the same size/color as other text that does show up. It can't be a corrupt font issue because it's showing up correctly in most areas. Does anyone have any ideas what could be causing this?

    I'm using Acrobat X. I've attached a cap of the InDesign poster, and what I get when exporting to PDF -- I lose the title, and "Directed by..." (which is the same type size/color as the playwright). Also, I have overprint preview checked for automatic (and tried all the other settings, too).

  • Pages crashes after exporting to PDF or .doc

    This is a problem now that it happens everytime i use pages.
    I'm working on a document and then I go to save a PDF by either Export in the File menu
    or by choosing "save as PDF" in the printer dialogue
    after it saves the PDF as soon as I go back to the pages doc the app crashes.
    and asks me if i want to reopen cancel or send a report - which i have done.
    this also happens if i save as .doc
    maybe i have to reset the app?
    this is making pages unusable unfortunately

    There used to be a reproducible crash in the past with a footnote, if you deleted the text referencing the footnote without deleting the footnote and then printed/exported to PDF. However, that problem is gone in the latest versions, as far as I can tell.
    Apart from that, I do not know of any definite crash scenarios.

Maybe you are looking for