InDesign Package for Export

Can I make changes to the InDesign file after it's been Packaged for Export (correcting typing errors) or do I have to go back to the original file to make the changes and then re-export.  Thanks!

Try this in the Adobe InDesign forum, you are now in the Bridge forum and not very likely to get an answer

Similar Messages

  • BPC10 - Data manager package for dimension  data export and import

    Dear BPC Expers,
    Need your help.
    I am trying to set up a data manager package for first time to export dimension - master data from one application and import in another application ( both have same properties) .
    I created a test data manager package from Organize > add package > with  process chain /CPMB/EXPORT_MD_TO_FILE  and Add
    In the advance tab of each task there are some script logic already populated. please find attached the details of the script logic written under each of the tasks like MD_Source, concvert and target .
    I have not done any chnages in the script inside the task .
    But when i run the package , I have selected a dimension 'Entity' but in second prompt ,it ask for a transformation file , and syatem autometically add the file ... \ROOT\WEBFOLDERS\COLPAL\FINANCE\DATAMANAGER\TRANSFORMATIONFILES\Import.xls
    I have not changed anything there
    in the next prmpt , it ask for a output file ..and it won't allow me enter the file name .....i
    Not sure how to proceed further.
    I shall be greatfull if someone guide me from your experiance  how to set up a simple the data manager package for master data export from dimension . Should I update the transformation file in the script for import file and  output file in the advance tab. how and what  transformation file to be created and link to the data manager package for export / import .
    What are the steps to be executed to run the package for exporting master data from dimension and import it another application .
    Thanks in advance for your guidance.
    Thanks and Regards,
    Ramanuj
    =====================================================================================================
    Detals of the task
    Task : APPL_MD-SOURCE
    (DIMENSIONMEMBER, %DIMENSIONMEMBERS%, "Please select dimension", "Please select members", %DIMS%)
    (TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)
    (OUTFILE,,"Please enter an output file",Data files (*.txt)|*.txt|All files(*.*)|*.*)
    (RADIOBUTTON,%ADDITIONINFO%,"Add other information(Environment,Model,User,Time)?",1,{"Yes","No"},{"1","0"})
    (%TEMPNO1%,%INCREASENO%)
    (%TEMPNO2%,%INCREASENO%)
    (/CPMB/APPL_MD_SOURCE,SELECTION,%DIMENSIONMEMBERS%)
    (/CPMB/APPL_MD_SOURCE,OUTPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,INPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,TRANSFORMATIONFILEPATH,%TRANSFORMATION%)
    (/CPMB/EXPORT_MD_CONVERT,SUSER,%USER%)
    (/CPMB/EXPORT_MD_CONVERT,SAPPSET,%APPSET%)
    (/CPMB/EXPORT_MD_CONVERT,SAPP,%APP%)
    (/CPMB/EXPORT_MD_CONVERT,OUTPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,INPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,FULLFILENAME,%FILE%))
    (/CPMB/FILE_TARGET,ADDITIONALINFO,%ADDITIONINFO%))
    Task : EXPORT_MD_CONVERT
    (DIMENSIONMEMBER, %DIMENSIONMEMBERS%, "Please select dimension", "Please select members", %DIMS%)
    (TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)
    (OUTFILE,,"Please enter an output file",Data files (*.txt)|*.txt|All files(*.*)|*.*)
    (RADIOBUTTON,%ADDITIONINFO%,"Add other information(Environment,Model,User,Time)?",1,{"Yes","No"},{"1","0"})
    (%TEMPNO1%,%INCREASENO%)
    (%TEMPNO2%,%INCREASENO%)
    (/CPMB/APPL_MD_SOURCE,SELECTION,%DIMENSIONMEMBERS%)
    (/CPMB/APPL_MD_SOURCE,OUTPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,INPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,TRANSFORMATIONFILEPATH,%TRANSFORMATION%)
    (/CPMB/EXPORT_MD_CONVERT,SUSER,%USER%)
    (/CPMB/EXPORT_MD_CONVERT,SAPPSET,%APPSET%)
    (/CPMB/EXPORT_MD_CONVERT,SAPP,%APP%)
    (/CPMB/EXPORT_MD_CONVERT,OUTPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,INPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,FULLFILENAME,%FILE%))
    (/CPMB/FILE_TARGET,ADDITIONALINFO,%ADDITIONINFO%))
    Task : FILE_TARGET
    (DIMENSIONMEMBER, %DIMENSIONMEMBERS%, "Please select dimension", "Please select members", %DIMS%)
    (TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)
    (OUTFILE,,"Please enter an output file",Data files (*.txt)|*.txt|All files(*.*)|*.*)
    (RADIOBUTTON,%ADDITIONINFO%,"Add other information(Environment,Model,User,Time)?",1,{"Yes","No"},{"1","0"})
    (%TEMPNO1%,%INCREASENO%)
    (%TEMPNO2%,%INCREASENO%)
    (/CPMB/APPL_MD_SOURCE,SELECTION,%DIMENSIONMEMBERS%)
    (/CPMB/APPL_MD_SOURCE,OUTPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,INPUTNO,%TEMPNO1%)
    (/CPMB/EXPORT_MD_CONVERT,TRANSFORMATIONFILEPATH,%TRANSFORMATION%)
    (/CPMB/EXPORT_MD_CONVERT,SUSER,%USER%)
    (/CPMB/EXPORT_MD_CONVERT,SAPPSET,%APPSET%)
    (/CPMB/EXPORT_MD_CONVERT,SAPP,%APP%)
    (/CPMB/EXPORT_MD_CONVERT,OUTPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,INPUTNO,%TEMPNO2%)
    (/CPMB/FILE_TARGET,FULLFILENAME,%FILE%))
    (/CPMB/FILE_TARGET,ADDITIONALINFO,%ADDITIONINFO%))
    ================================================================================

    1. Perhaps you want to consider a system copy to a "virtual system" for UAT?
    2. Changes in QAS (as with PROD as well) will give you the delta. They should ideally be clean... You need to check the source system.
    Another option is to generate the profiles in the target system. But for that your config has to be sqeaky clean and in sync, including very well maintained and sync'ed Su24 data.
    Cheers,
    Julius

  • Placing SWF Movie into IDCS4 for export to PDF

    I'm trying to place a swf into an Indesign document for export to PDF.
    I made a simple swf using Flash CS4 (AS2 if it matters) and placed it using the File->Place menu.
    I checked the Movie Options and selected, Embed in PDF, and play options.
    Then I export to PDF and am sure that Interactive Elements is checked.
    I found someplace that suggested toggling "create tagged PDF" to the opposite setting of whatever it is, but that didn't make any difference.
    When I open the PDF with Acrobat and move to that page it just shows the default movie preview and shows a "buffering" window for ever, but the file is tiny so it should load immediately.
    So how do I do this? Is it possible? I've tried some searches, but most everything I'm finding is about exporting ID docs to swf. And that isn't what I want.
    At least I don't think this is what I want. I need to make a PDF that will have an animation of how to navigate a web app. So if anybody has a better way to do this, then please let me know!

    I wrote up a very long explanation of this for indesignsecrets.com.
    http://indesignsecrets.com/putting-swfs-into-indesign-documents.php
    The bottom line is:
    It's a bug on the Mac
    Windows users can play those SWFs but the Mac hangs
    Adobe is aware of the problem
    But if you want an SWF to play on both Mac and Windows, open the PDF in Acrobat Professional and add the SWF there.
    You will actually have more control than if you had placed it in InDesign and it played correctly.

  • Applescript and InDesign: Packaging/exporting -- can you help?

    I found and tweaked a droplet script that isn't quite working right. I tried and failed to learn to do this myself. Any help is greatly appreciated! This is for InDesign CS6 -- you don't really need to know InDesign in order to help (at least I don't think so).
    For the moment, I simply drag multiple InDesign files (for this example, "filename1.indd" and "filename2.indd") onto the droplet. InDesign packages them separately and outputs PDFs into each output folder. The problem is that it's creating too many folders and not putting things where I want.
    Another thing: when InDesign packages a file, it creates a "Instructions.txt" file for each package that I need deleted. I'd really like this added to the script as well. Is it possible?
    Current output (messy!)
    Desired output (perfect!)
    "exports" folder
         "filename1" folder
              filename1.pdf
              "filename1" folder
                   filename1.indd
                   Instructions.txt
         "filename2" folder
              filename2.pdf
              "filename2" folder
                   filename2.indd
                   Instructions.txt
    baseFolder <--- directory of original files
         "filename1" folder
              filename1.indd
              "PDF" folder
                   filename1.pdf
         "filename2" folder
              filename2.indd
              "PDF" folder
                   filename2.pdf
    Here's the script I have so far:
    property baseFolder : (path to desktop as text) & "exports:"
    on open mgItems
         repeat with mgThisItem in mgItems
              tell application id "com.adobe.InDesign"
                   try
              open mgThisItem
                   set mgDocName to name of active document
                   set text item delimiters of AppleScript to ".indd"
                   set mgShortName to text item 1 of mgDocName
                   set targetFolderPath to my createFolder(mgShortName)
                   set text item delimiters of AppleScript to ""
                   set mgPackageFilePath to targetFolderPath & mgShortName as string
                   set mgProofFilePath to mgPackageFilePath & ".pdf" as string
                   set properties of PDF export preferences to properties of PDF export preset "[Smallest File Size]"
                   tell the active document to export format PDF type to mgProofFilePath without showing options
                   tell the active document to package to mgPackageFilePath with copying fonts, ignore preflight errors, copying profiles, updating graphics, including hidden layers,copying linked graphics and creating report
      close active document saving no
                   on error e
                        display dialog e
                   end try
              end tell
         end repeat
         display dialog "PDFs created and InDesign file packaged"
    end open
    on createFolder(nameString)
         set macFolderPath to baseFolder & nameString
         do shell script "mkdir -p " & quoted form of POSIX path of macFolderPath
         return macFolderPath & ":"
    end createFolder
    Thanks very much!

    Easy enough. Note that I've moved things around a little to make a nicer flow:
    on open mgItems
      --make a date slug
              set shortDateString to short date string of (current date)
              set {oldTID, my text item delimiters} to {my text item delimiters, "/"}
              set dateBits to (text items of shortDateString)
              set my text item delimiters to ""
              set datePrefixString to (text item 3 of dateBits & text items 1 thru 2 of dateBits & "_Release") as text
              set my text item delimiters to oldTID
              repeat with mgThisItem in mgItems
                        tell application "System Events"
      --get path of the container of the passed in object
                                  set targetFolderPath to path of container of disk item (mgThisItem as text)
                        end tell
                        tell application id "com.adobe.InDesign"
                                  try
                                            open mgThisItem
                                            set mgDocName to name of active document
                                            set text item delimiters of AppleScript to ".indd"
                                            set mgShortName to text item 1 of mgDocName
      -- set up folder and file references
                                            set mgPackageFilePath to targetFolderPath & datePrefixString & ":" & mgShortName & ":"
                                            set mgProofFilePath to mgPackageFilePath & "PDF:" & mgShortName & ".pdf" as string
                                            set text item delimiters of AppleScript to ""
      -- create dat folder, main folder and internal PDF folder; passing in POSIX path, though most everything ele uses HFS paths
                                            my createFolders(POSIX path of file (mgPackageFilePath & "PDF:"))
                                            set properties of PDF export preferences to properties of PDF export preset "[Smallest File Size]"
                                            tell the active document to export format PDF type to mgProofFilePath without showing options
                                            tell the active document to package to mgPackageFilePath with copying fonts, ignore preflight errors, copying profiles, updating graphics, including hidden layers, copying linked graphics and creating report
                                            close active document saving no
                                  on error e
                                            display dialog e
                                  end try
                        end tell
      -- delete the instructions file
                        tell application "System Events"
                                  delete file (mgPackageFilePath & "instructions.txt")
                        end tell
              end repeat
              display dialog "PDFs created and InDesign file packaged"
    end open
    on createFolders(pathString)
              do shell script "mkdir -p " & quoted form of pathString
    end createFolders

  • Structure inDesign document and export as XML for use in the web

    Hello everyone,
    I just recently started using inDesign and I am fascinated by its possibilities! I use it for a project where a finished inDesign layout that is used for a printed publication is now supposed to be transformed for implementing it on a web site. My job is to export the inDesign document as an XML file. After massive reading the last weeks I'm quite familiar with the structuring and tagging in inDesign. Though there's some issues I do not understand. Your precious advice would be of highest meaning to me
    The programmer who will later use my XML output for the web-transformation needs the document structured in different levels like "Root > Chapter > Subchapter > Text passage / table". I already structured the document with tags like title, text passage, table, infobox,... but the structure is just linear, putting one item following to another.
    How can I structure the document with reoccuring tags that enable me to identify the exact position of an item in the document's structure? So that I can say for example "text passage X" is located in chapter 4, subchapter 1. This has to be done because the document is supposed to be updated later on. So maybe a chapter gets modified and has to be replaced, but this replacement is supposed to be displayed.
    I hope my problem becomes clear! That's my biggest issue for now. So for any help I'd be very thankful!

    Our print publications are created in InDesign CS5 for Mac then the text is exported to RTF files then sent to an outside company to be converted to our XML specifications for use by our website developers.  I would like to create a workflow in which our XML tags are included in the InDesign layouts and then export the XML from the layouts.
    Some more detail about what kind of formatting is necessary might be helpful.
    I know that IDML files contain the entire layout in XML format.  Is it a good idea to extract what we need from IDML, using the already-assigned tags?
    Well, if you want to export the whole document, it's the only reasonable approach.
    We use a workflow system such that each story is a seperate InCopy document, stored in ICML format (Basically a subset of IDML). Our web automation uses XSLT to convert each story into HTML for use on our web site; it also matches it up with external metadata so it knows what is a headline and what is not, etc.. It is not exactly hassle free, and every once in a while someone uses a new InDesign feature that breaks things (e.g., our XSLT has no support for paragraph numbering, so numbered paragraphs show up without their numbers).
    You could do the same thing with with IDML, you'd just have to pick out each story, but that's small potatoes compared to all the XSL work you're going to have to do.
    On the other hand, there may be better approaches if you're not going to export the whole document. For instance,  you could use scripting to export each story as an RTF file, and then you could convert the RTF files into HTML using other tools.

  • Is there a way to export data from Framemaker 7.0 to InDesign CS3 for the MAC

    I am asking this question for our Advertising department so I am not too close to the situation. Another company that is part of oujr platform designed their catalogs in Framermaker 7.0. We have Framemaker 6.0. The only reason we have it is to work with this other version of Framemaker 7.0. Our advertising people use InDesign CS3 for the Mac. Right now Advertising gives the person with Framermaker 7.0 changes to be made to their catalog. He exports the file as an IMF file and she pulls it into Framermaker 6.0.
    We tried to upgrade from Framemaker 6.0 to 9.0, but that wasn't possible.
    Ideally we would like to take a 600 page catalog created with Framemaker and convert it to InDesign.
    We would also like to take the files created with Framemaker 7.0 and import them into InDesign.
    Is there a way to do this?
    Thanks in advance.
    dh 

    You can convert FrameMaker MIF (interchange) files to InDesign with the dtptools.com MIF Filter plug-in for InDesign. The plug-in is free, because you have to pay for the pages you convert. The bigger bundle of pages you buy, the lower cost per page.
    dtptools.com also has a really free plug-in for FrameMaker that converts .fm files to .mif, whole directories at a time.
    The converted InDesign files usually look very close to the original FM files, but it's possible to create things in FM that fools the converter, so you'll need to look the conversions over carefully.
    I reviewed MIF Filter in some detail in InDesign Magazine in a late 2007 issue.
    You should be aware that InDesign CS3 is no longer sold, so you can't buy more copies for all your users to be working in the same release. While it's possible to exchange files between ID CS3 and CS4 there are some things that don't convert perfectly, so you'll still have to inspect closely. I believe the most-common issue is text reflow.
    It's not clear if you intend never to go back to using FrameMaker for any of the catalog work, except perhaps for creating original text.
    Without seeing an example of the catalog pages, it's impossible to recommend any useful strategies. You can post a screen shot to this forum by clicking the camera icon in the button bar above the reply entry area. Inserting with the camera puts the picture on the forum very quickly, vs. attaching the picture as a file (it takes hours or days.)
    There may be other strategies for creating your catalog.
    HTH
    Regards,
    Peter Gold
    KnowHow ProServices

  • Indesign Crashes when exporting PDF

    Hi,
    We are experiencing an issue when exporting an .indd file as .pdf. The process gets as far as a certain page (8 out of 13) and then crashes when reading a pdf image from that page. It does one of two things - it crashes or displays an 'out of memory' message. We had task manager running alongside the program to check memory usage and there are no major spikes during the export process (it doesn't even hit 80%)
    - We can export every other page in the document except this one
    - The export works without marks & bleeds enabled (not really sure of the terminology so I do apologise)
    The document is going off to print so the pdf image has to be of high resolution. Does anyone have any ideas as to how we can get around this issue?
    The INdesign package is CS4 (32bit) and the pc has 4GB of RAM
    Any assistance would be much appreciated

    Friends I'm reading all the posts, but I have the same problem. My Indesign crashes exporting a document of 60 pages into pdf.
    Can anybody help me please? The next week I have to deliver the project. Thank you!
    This is the error message:
    Process:               Adobe InDesign CS6 [2996]
    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:        ??? [1]
    Responsible:           Adobe InDesign CS6 [2996]
    User ID:               502
    Date/Time:             2014-11-20 12:07:06.086 +0100
    OS Version:            Mac OS X 10.10.1 (14B25)
    Report Version:        11
    Anonymous UUID:        1B173797-49B9-7B44-7C5E-AEF6059371E1
    Sleep/Wake UUID:       D5A59AA4-AE79-4927-BEF0-BDE56A168D31
    Time Awake Since Boot: 89000 seconds
    Time Since Wake:       14000 seconds
    Crashed Thread:        11
    Exception Type:        EXC_CRASH (SIGABRT)
    Exception Codes:       0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    [2996] stack overflow
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x955cba2e mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x955caad0 mach_msg + 68
    2   com.apple.CoreFoundation       0x927e2ae6 __CFRunLoopServiceMachPort + 214
    3   com.apple.CoreFoundation       0x927e1ef9 __CFRunLoopRun + 1529
    4   com.apple.CoreFoundation       0x927e1696 CFRunLoopRunSpecific + 390
    5   com.apple.CoreFoundation       0x927e14fb CFRunLoopRunInMode + 123
    6   com.apple.HIToolbox           0x99328178 RunCurrentEventLoopInMode + 262
    7   com.apple.HIToolbox           0x99327eb1 ReceiveNextEventCommon + 494
    8   com.apple.HIToolbox           0x994cd798 ReceiveNextEvent + 90
    9   com.adobe.InDesign.AppFramework 0x1006eaf8 0x10060000 + 60152
    10  com.adobe.InDesign.AppFramework 0x1008d327 GetPlugIn + 12007
    11  com.adobe.InDesign             0x00001ec5 main + 341
    12  com.adobe.InDesign             0x00001d55 start + 53
    Thread 1:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b7a _pthread_cond_wait + 842
    2   libsystem_pthread.dylib       0x988c7d9d pthread_cond_timedwait_relative_np + 47
    3   com.apple.CoreServices.CarbonCore 0x91f22316 TSWaitOnConditionTimedRelative + 167
    4   com.apple.CoreServices.CarbonCore 0x91eeddff MPWaitOnQueue + 199
    5   PMRuntime.dylib               0x005b9581 SetVSizeBaseline(unsigned long) + 1473
    6   com.apple.CoreServices.CarbonCore 0x91eee45a PrivateMPEntryPoint + 68
    7   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    8   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    9   libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 2:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib         0x955d28d2 kevent64 + 10
    1   libdispatch.dylib             0x9ae4f73f _dispatch_mgr_invoke + 245
    2   libdispatch.dylib             0x9ae4f3a2 _dispatch_mgr_thread + 52
    Thread 3:
    0   libsystem_kernel.dylib         0x955cba2e mach_msg_trap + 10
    1   libsystem_kernel.dylib         0x955caad0 mach_msg + 68
    2   com.apple.CoreServices.CarbonCore 0x91f1efc4 TS_exception_listener_thread + 138
    3   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    4   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    5   libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 4:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore 0x91f220fa TSWaitOnCondition + 133
    4   com.apple.CoreServices.CarbonCore 0x91f22332 TSWaitOnConditionTimedRelative + 195
    5   com.apple.CoreServices.CarbonCore 0x91eeddff MPWaitOnQueue + 199
    6   com.adobe.ACE                 0x00607a69 0x5c8000 + 260713
    7   com.adobe.ACE                 0x00606d99 0x5c8000 + 257433
    8   com.apple.CoreServices.CarbonCore 0x91eee45a PrivateMPEntryPoint + 68
    9   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    10  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    11  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 5:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.InDesign.AppFramework 0x10160556 GetPlugIn + 876822
    4   com.adobe.InDesign.AppFramework 0x1015c8ff GetPlugIn + 861375
    5   com.adobe.InDesign.AppFramework 0x1015d3c5 GetPlugIn + 864133
    6   com.adobe.InDesign.AppFramework 0x1015e98e GetPlugIn + 869710
    7   com.adobe.InDesign.AppFramework 0x1015e9fa GetPlugIn + 869818
    8   com.adobe.InDesign.AppFramework 0x1015ea66 GetPlugIn + 869926
    9   com.adobe.boost_threads.framework 0x01c6a40d thread_proxy + 141
    10  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    11  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    12  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 6:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.InDesign.AppFramework 0x10160556 GetPlugIn + 876822
    4   com.adobe.InDesign.AppFramework 0x1015c8ff GetPlugIn + 861375
    5   com.adobe.InDesign.AppFramework 0x1015d3c5 GetPlugIn + 864133
    6   com.adobe.InDesign.AppFramework 0x1015e98e GetPlugIn + 869710
    7   com.adobe.InDesign.AppFramework 0x1015e9fa GetPlugIn + 869818
    8   com.adobe.InDesign.AppFramework 0x1015ea66 GetPlugIn + 869926
    9   com.adobe.boost_threads.framework 0x01c6a40d thread_proxy + 141
    10  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    11  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    12  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 7:
    0   libsystem_kernel.dylib         0x955d18fa __semwait_signal + 10
    1   libsystem_c.dylib             0x9c001c16 nanosleep$UNIX2003 + 218
    2   com.adobe.InDesign.Support for JavaScript 0x1637eacb GetPlugIn + 317883
    3   com.adobe.InDesign.Support for JavaScript 0x16363f79 GetPlugIn + 208489
    4   com.adobe.InDesign.Support for JavaScript 0x1637ee38 GetPlugIn + 318760
    5   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    6   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    7   libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 8:
    0   libsystem_kernel.dylib         0x955d1772 __recvfrom + 10
    1   libsystem_c.dylib             0x9c001d32 recv$UNIX2003 + 55
    2   ServiceManager-Launcher.dylib 0x22f15733 Invoke + 47867
    3   ServiceManager-Launcher.dylib 0x22f14846 Invoke + 44046
    4   ServiceManager-Launcher.dylib 0x22f13988 Invoke + 40272
    5   ServiceManager-Launcher.dylib 0x22f13a0f Invoke + 40407
    6   ServiceManager-Launcher.dylib 0x22f0ebaf Invoke + 20343
    7   ServiceManager-Launcher.dylib 0x22f0eea7 Invoke + 21103
    8   ServiceManager-Launcher.dylib 0x22f0f685 Invoke + 23117
    9   ServiceManager-Launcher.dylib 0x22f0f8f9 Invoke + 23745
    10  ServiceManager-Launcher.dylib 0x22f122a0 Invoke + 34408
    11  ServiceManager-Launcher.dylib 0x22f123fd Invoke + 34757
    12  ServiceManager-Launcher.dylib 0x22f12c91 Invoke + 36953
    13  ServiceManager-Launcher.dylib 0x22f12db2 Invoke + 37242
    14  ServiceManager-Launcher.dylib 0x22f05656 Login + 461
    15  ServiceManager-Launcher.dylib 0x22f0909a Login + 15377
    16  ServiceManager-Launcher.dylib 0x22f13165 Invoke + 38189
    17  ServiceManager-Launcher.dylib 0x22f152eb Invoke + 46771
    18  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    19  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    20  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 9:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.InDesign.AppFramework 0x10160556 GetPlugIn + 876822
    4   com.adobe.InDesign.AppFramework 0x1015c8ff GetPlugIn + 861375
    5   com.adobe.InDesign.AppFramework 0x1015d3c5 GetPlugIn + 864133
    6   com.adobe.InDesign.AppFramework 0x1015e98e GetPlugIn + 869710
    7   com.adobe.InDesign.AppFramework 0x1015e9fa GetPlugIn + 869818
    8   com.adobe.InDesign.AppFramework 0x1015ea66 GetPlugIn + 869926
    9   com.adobe.boost_threads.framework 0x01c6a40d thread_proxy + 141
    10  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    11  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    12  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 10:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.InDesign.AppFramework 0x10160556 GetPlugIn + 876822
    4   com.adobe.InDesign.AppFramework 0x1015c8ff GetPlugIn + 861375
    5   com.adobe.InDesign.AppFramework 0x1015d3c5 GetPlugIn + 864133
    6   com.adobe.InDesign.AppFramework 0x1015e98e GetPlugIn + 869710
    7   com.adobe.InDesign.AppFramework 0x1015e9fa GetPlugIn + 869818
    8   com.adobe.InDesign.AppFramework 0x1015ea66 GetPlugIn + 869926
    9   com.adobe.boost_threads.framework 0x01c6a40d thread_proxy + 141
    10  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    11  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    12  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 11 Crashed:
    0   libsystem_kernel.dylib         0x955d169e __pthread_kill + 10
    1   libsystem_pthread.dylib       0x988c8fd5 pthread_kill + 101
    2   libsystem_c.dylib             0x9bfe1fca __abort + 187
    3   libsystem_c.dylib             0x9bfe284a __stack_chk_fail + 239
    4   com.adobe.CoolType             0x010137c9 CTInit + 1626733
    5   com.adobe.CoolType             0x01014053 CTInit + 1628919
    6   com.adobe.CoolType             0x010111ba CTInit + 1616990
    7   com.adobe.CoolType             0x0100f77e CTInit + 1610274
    8   com.adobe.CoolType             0x00f6478e CTInit + 909874
    9   com.adobe.CoolType             0x00ef40a2 CTInit + 449350
    10  com.adobe.CoolType             0x00e726ba 0xe1e000 + 345786
    11  com.adobe.PDFL                 0x2e5722e2 PDFontPSFlushIncrGlyphList + 85285
    12  com.adobe.PDFL                 0x2e987898 PDEFontGetWidthsNow + 8752
    13  com.adobe.PDFL                 0x2e987bb9 PDEFontGetWidthsNow + 9553
    14  com.adobe.PDFL                 0x2e988b13 PDEFontGetWidthsNow + 13483
    15  com.adobe.PDFL                 0x2e9899a1 PDEFontGetWidthsNow + 17209
    16  com.adobe.PDFPort             0x17267ffe PDFPortInitialize + 560298
    17  com.adobe.PDFPort             0x17268375 PDFPortInitialize + 561185
    18  com.adobe.PDFPort             0x172508f0 PDFPortInitialize + 464284
    19  com.adobe.InDesign.PDF         0x16f84f09 0x16f4f000 + 220937
    20  com.adobe.InDesign.PDF         0x16fa864d GetPlugIn + 66509
    21  com.adobe.InDesign.PDF         0x16fab0b8 GetPlugIn + 77368
    22  com.adobe.InDesign.PDF         0x16f92bb5 0x16f4f000 + 277429
    23  PublicLib.dylib               0x01701d7c Command::DoImmediate(short) + 62
    24  com.adobe.InDesign.Utilities   0x0fac5691 0xfac1000 + 18065
    25  com.adobe.InDesign.Utilities   0x0fac58a0 0xfac1000 + 18592
    26  com.adobe.InDesign.AppFramework 0x1007cbba 0x10060000 + 117690
    27  PublicLib.dylib               0x01702724 CmdUtils::ProcessCommand(ICommand*) + 48
    28  com.adobe.InDesign.PDF         0x170d2bb6 GetPlugIn + 1288502
    29  com.adobe.InDesign.PDF         0x170d6f47 GetPlugIn + 1305799
    30  com.adobe.InDesign.AppFramework 0x1015a749 GetPlugIn + 852745
    31  com.adobe.InDesign.AppFramework 0x1015bca6 GetPlugIn + 858214
    32  com.adobe.InDesign.AppFramework 0x1015c804 GetPlugIn + 861124
    33  com.adobe.InDesign.AppFramework 0x1015d3c5 GetPlugIn + 864133
    34  com.adobe.InDesign.AppFramework 0x1015e98e GetPlugIn + 869710
    35  com.adobe.InDesign.AppFramework 0x1015e9fa GetPlugIn + 869818
    36  com.adobe.InDesign.AppFramework 0x1015ea66 GetPlugIn + 869926
    37  com.adobe.boost_threads.framework 0x01c6a40d thread_proxy + 141
    38  libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    39  libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    40  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 12:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   MultiProcessor Support         0x0e451eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
    4   MultiProcessor Support         0x0e435513 ThreadFunctor::operator()() + 99
    5   MultiProcessor Support         0x0e43525a boost::detail::thread_data<ThreadFunctor>::run() + 22
    6   MultiProcessor Support         0x0e451547 thread_proxy + 167
    7   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    8   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    9   libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 13:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.ape.engine           0x379e704f APXGetHostAPI + 2633743
    4   com.adobe.ape.engine           0x3777862f APXGetHostAPI + 83439
    5   com.adobe.ape.engine           0x379e713e APXGetHostAPI + 2633982
    6   com.adobe.ape.engine           0x379e71a7 APXGetHostAPI + 2634087
    7   com.adobe.ape.engine           0x379e72c6 APXGetHostAPI + 2634374
    8   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    9   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    10  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 14:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b06 _pthread_cond_wait + 726
    2   libsystem_pthread.dylib       0x988cb1d1 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.ape.engine           0x379e704f APXGetHostAPI + 2633743
    4   com.adobe.ape.engine           0x3777862f APXGetHostAPI + 83439
    5   com.adobe.ape.engine           0x379e713e APXGetHostAPI + 2633982
    6   com.adobe.ape.engine           0x379e71a7 APXGetHostAPI + 2634087
    7   com.adobe.ape.engine           0x379e72c6 APXGetHostAPI + 2634374
    8   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    9   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    10  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 15:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b7a _pthread_cond_wait + 842
    2   libsystem_pthread.dylib       0x988c7d9d pthread_cond_timedwait_relative_np + 47
    3   com.adobe.ape.engine           0x379e7017 APXGetHostAPI + 2633687
    4   com.adobe.ape.engine           0x37a0020e APXGetHostAPI + 2736590
    5   com.adobe.ape.engine           0x379e713e APXGetHostAPI + 2633982
    6   com.adobe.ape.engine           0x379e71a7 APXGetHostAPI + 2634087
    7   com.adobe.ape.engine           0x379e72c6 APXGetHostAPI + 2634374
    8   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    9   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    10  libsystem_pthread.dylib       0x988c4f0e thread_start + 34
    Thread 16:
    0   libsystem_kernel.dylib         0x955d1516 __psynch_cvwait + 10
    1   libsystem_pthread.dylib       0x988c7b7a _pthread_cond_wait + 842
    2   libsystem_pthread.dylib       0x988c7d9d pthread_cond_timedwait_relative_np + 47
    3   com.adobe.ape.engine           0x379e7017 APXGetHostAPI + 2633687
    4   com.adobe.ape.engine           0x37b750c8 APXGetHostAPI + 4264072
    5   com.adobe.ape.engine           0x379e713e APXGetHostAPI + 2633982
    6   com.adobe.ape.engine           0x379e71a7 APXGetHostAPI + 2634087
    7   com.adobe.ape.engine           0x379e72c6 APXGetHostAPI + 2634374
    8   libsystem_pthread.dylib       0x988c6ecf _pthread_body + 138
    9   libsystem_pthread.dylib       0x988c6e45 _pthread_start + 162
    10  libsystem_pthread.dylib       0x988c4f0e thread_start + 34

  • Help! 'Package for Print' Script

    Hi all,
    I have a specific 'Package For Print' script, that needs a small modification, and and I was hoping someone could help me.
    Essentially, I need to OMIT 'Include PDF' option when packaging, since this makes things a bit wonky on my script (see below).
    Let me know if you need to see the script, and I'll post it.
    Thank you.

    Here you go, and thank you. I know notes are also included in it. Sorry about this.
    //Package the active document and setup the dockets folder structure.
    //The active document shouldn't have been saved (has no name), so provide a name
    //taken from the first and only link.  After creating the dockets folder structure,
    //close and delete the original file and open the file in the docket's originals
    //folder.
    #target InDesign
    //Constants
    const PROOF_PREFIX = 'Proof_';
    const OUTPUT_SUFFIX = ' Folder';
    const ORIGINALS_FOLDER = 'Originals';
    const PRINT_FOLDER = 'Print';
    const DIGITAL_PROOF_FOLDER = 'Digital Proof';
    const CLIENT_FOLDER = 'Client Provided Files';
    const DEFAULT_MAC_DOCKETS = '/Users/parham/Desktop';
    const PDF_PROFILE = 'Linx_Proof'
    function Err() {}
    //Use a more user-friendly version than throwing an error.
    Err.FatalError = function (msg) {
      alert(msg, 'Fatal Error', true);
      exit();
    function makeShowUI(runtime) {
      var doc = runtime.doc;
      var window = (function () {
      var windowDef = "Window {\
      type: 'dialog', \
      properties: { \
      resizeable: false, \
      closeButton: true, \
      maximizeButton: false, \
      minimizeButton: false \
      text: 'Dockets Package', \
      orientation: 'column', \
      var w = new Window(windowDef);
      //Folder name
      w.add("StaticText { text:'New Folder Name', alignment: 'left' }");
      var defaultName = doc.name;
      if (defaultName.slice(-5) == '.indd') {
      var origlength = defaultName.length;
      defaultName = defaultName.substr(0, origlength - 5);
      w.folderText = w.add("EditText { alignment: 'left', characters: 30, justify: 'left', " +
      "text:'" + defaultName + OUTPUT_SUFFIX + "'}");
      //Destination dir
      w.add("StaticText { text:'Save To', alignment: 'left' }");
      var dirGroup = w.add("Group { orientation: 'row', alignment: 'fill' }");
      w.dirText = dirGroup.add("EditText { characters: 30, justify: 'left', " +
      "text:'" + DEFAULT_MAC_DOCKETS + "'}");
      w.dirBrowseBtn = dirGroup.add("Button { text: 'Browse...' }");
      w.dirBrowseBtn.textBox = w.dirText;
      //Package Options
      w.options = w.add("Panel { orientation: 'column', alignment: 'fill', \
      text: 'Package Options', alignChildren: 'left'}");
      w.options.fonts = w.options.add("Checkbox { text: 'Copy Fonts' }");
      w.options.links = w.options.add("Checkbox { text: 'Copy Linked Graphics' }");
      w.options.profiles = w.options.add("Checkbox { text: 'Copy Color Profiles' }");
      w.options.update = w.options.add("Checkbox { text: 'Update Graphic Links In Package' }");
      w.options.hiddenContent = w.options.add("Checkbox { text: 'Include Fonts and Links From Hidden and Non-Printing Content' }");
      w.options.ignore = w.options.add("Checkbox { text: 'Ignore Preflight Errors' }");
      w.options.report = w.options.add("Checkbox { text: 'Create Report' }");
      w.options.fonts.value = true;
      w.options.links.value = true;
      w.options.profiles.value = true;
      w.options.update.value = true;
      w.options.hiddenContent.value = true;
      w.options.ignore.value = true; //Parham's request for true
      w.options.report.value = false; //Saeed's request for false (no instructions)
      //Digital Proof
      w.proof = w.add("Panel { orientation: 'column', alignment: 'fill', \
      text: 'Digital Proof', alignChildren: 'left'}");
      w.proof.make = w.proof.add("Checkbox { text: 'Make PDF Proof' }");
      w.proof.viewAfter = w.proof.add("Checkbox { text: 'View PDF' }");
      w.proof.make.value = false;
      w.proof.viewAfter.value = false;
      //OK / Cancel
      var buttonDef = "Group { orientation: 'row', alignment: 'right', alignChildren: 'right' }";
      w.bg = w.add(buttonDef);
      var okDef = "Button { text: 'OK', alignment: 'right' }";
      var cancelDef = "Button { text: 'Cancel', alignment: ['right', 'center'] }";
      w.okBtn = w.bg.add(okDef);
      w.cancelBtn = w.bg.add(cancelDef);
      return w;
      runtime.window = window;
      window.dirBrowseBtn.onClick = (function () {
      var result = Folder.selectDialog('Choose destination directory');
      if (null !== result) {
      //Replace string with selected path
      this.textBox.text = result.fullName;
      return window.show();
    function deleteFolder(folder) {
      if (!folder.exists) {
      return;
      var children = folder.getFiles();
      for (var i = 0, im = children.length; i < im; i++) {
      if (children[i] instanceof Folder) {
      deleteFolder(children[i]);
      } else {
      children[i].remove();
      folder.remove();
    //Main path
    try {
      var a = app.activeDocument;
    } catch (e) {
      Err.FatalError("No document open");
    var runtime = {};
    var doc = app.activeDocument;
    runtime.doc = doc;
    if (doc.saved) {
      //Document has already been saved (already has a name), so stop.
      Err.FatalError("Document has already been saved");
    //Ensure at least one link, since multipaged PDFs end up as more than 1 link.
    if (doc.links.length < 1) {
      Err.FatalError("Document has " + doc.links.length + " links.");
    //Save the existing file in a temporary place, same dir as first link.
    //Take the name from the first link
    var link = doc.links.firstItem();
    var defaultName = link.name;
    if (defaultName.slice(-4) == '.pdf') {
      var origlength = defaultName.length;
      defaultName = defaultName.substr(0, origlength - 4);
    } else {
      //Placed item is not a pdf, as per Parham's request, don't warn about it.
      //Just take the filename best guess and go with it.
    // if (confirm('Linked item is not a PDF.  Package anyways?',
    // true, 'Package non-PDF')) {
      //break on the last '.'
      var lastIndex = defaultName.lastIndexOf('.');
      if (lastIndex > -1) {
      defaultName = defaultName.substr(0, lastIndex);
      } else {
      defaultName = defaultName;
    // } else {
    // alert('Did not package.');
    // exit();
    //filePath should be a File, but is actually a string, so make a file.
    var linkFile = new File(link.filePath);
    var origFile = new File(linkFile.path + '/' + defaultName + '.indd');
    if (origFile.exists) {
      //Folder already exists, get user to confirm
      if (confirm("File " + defaultName + '.indd already exists.  Replace?',
      true, 'Replace File')) {
      //Erase the temp file
      origFile.remove();
      } else {
      alert('Did not overwrite existing files, did not package.');
      exit();
    doc.save(origFile);
    if (2 == makeShowUI(runtime)) {
      //User pressed cancel
      exit();
    //Main code, do the packaging and make the directories.
    //But first check for existing folder.
    var folderName = runtime.window.folderText.text;
    var destinationPath = runtime.window.dirText.text;
    if (destinationPath.slice(-1) == '/') {
      var newFolderPath = destinationPath + folderName;
    } else {
      var newFolderPath = destinationPath + '/' + folderName;
    var outputRoot = new Folder(newFolderPath);
    if (outputRoot instanceof Folder && outputRoot.exists) {
      //Folder already exists, get user to confirm
      if (confirm('Dockets folder ' + folderName + ' already exists.  Replace?',
      true, 'Replace Folder')) {
      //Erase the destination directory
      //Get all contained files + folders, then delete them.
      deleteFolder(outputRoot);
      } else {
      alert('Did not overwrite existing files.');
      exit();
    } else if (outputRoot instanceof File) {
      //Destination folder exists as a file, fail.
      Err.FatalError('File named ' + folderName + ' already exists, cannot make folder.');
    //Destination doesn't exist, create it.
    if (!outputRoot.create()) {
      Err.FatalError('Error creating folder ' + folderName);
    //We have an empty directory, now do the packaging and everything else.
    var printFolder = new Folder(newFolderPath);
    printFolder.changePath(PRINT_FOLDER);
    if (!printFolder.create()) {
      Err.FatalError('Error creating Print folder.');
    var digitalProofFolder = new Folder(newFolderPath);
    digitalProofFolder.changePath(DIGITAL_PROOF_FOLDER);
    if (!digitalProofFolder.create()) {
      Err.FatalError('Error creating Digital Proof folder.');
    var clientFolder = new Folder(newFolderPath);
    clientFolder.changePath(CLIENT_FOLDER);
    if (!clientFolder.create()) {
      Err.FatalError('Error creating Client folder.');
    var originalsFolder = new Folder(newFolderPath);
    originalsFolder.changePath(ORIGINALS_FOLDER);
    if (!originalsFolder.create()) {
      Err.FatalError('Error creating Originals folder.');
    //Do the package
    var f = runtime.window.options;
    if (doc.packageForPrint(originalsFolder, f.fonts.value, f.links.value, f.profiles.value, f.update.value, f.hiddenContent.value, f.ignore.value, f.report.value, false, true)) {
    } else {
      Err.FatalError('Failed to package.');
    //Do the PDF proof
    if (runtime.window.proof.make.value) {
      var proofname = PROOF_PREFIX + doc.name;
      if (proofname.slice(-5) == '.indd') {
      var origlength = proofname.length;
      proofname = proofname.substr(0, origlength - 5);
      proofname = proofname + '.pdf';
      var proofFile = new File(digitalProofFolder.fullName + '/' + proofname);
      if (proofFile.exists) {
      Err.FatalError('Digital proof already exists.');
      } else {
      var exportProfile = app.pdfExportPresets.itemByName(PDF_PROFILE);
      //We get an object even if the profile doesn't exist, have to check isValid
      if (!exportProfile.isValid) {
      Err.FatalError('PDF profile ' + PDF_PROFILE + " doesn't exist, digital proof not created.");
      //Explicitly set to export all pages.
      app.pdfExportPreferences.pageRange = PageRange.ALL_PAGES;
      //Set view preference
      app.pdfExportPreferences.viewPDF = runtime.window.proof.viewAfter.value;
      doc.exportFile(ExportFormat.PDF_TYPE, proofFile, false, exportProfile);
    //Open the Originals folder .indd, close the current file and delete it.
    var newFile = new File(originalsFolder.fullName + '/' + doc.name);
    if (!app.open(newFile)) {
      Err.FatalError("Failed to open packaged .indd");
    doc.close();
    origFile.remove();

  • Best Practices for setting up InDesign Effects for offset printing.

    I'm new to the forum so I hope I'm posting my question in the correct place.  I'm a prepress supervisor for a company that receives most of it's work as PDFs exported from InDesign.  I notice on more and more work (proabably 75%) our customers are setting up their effects in InDesign.  We receive files exported from CS3 and CS4, mac and pc.  Our prepress system is Prinergy 4.1.  We have job options that we recommend customers use for PDF export directly out of the applicaton and we are currently testing PDFX4.  The problem is we don't have consistent results with our ripped files, we often see artifacts around items that use certain effects (such as the bevel and emboss effect), many times the customer uses a drop shadow along with the bevel and emboss and we see "pixelation" or low-resolution "jagginess."   Files that use feathering often drop part of the feathered image and if black text is touching an effect it will process out to CMYK. If we have the InDesign file it sometimes works to change how the effect is applied (text, object, fill), sometimes we have to flatten on export or write a PDFX4.  If we are working with the customer's PDF we often have to flatten at the rip, save the PDF as a postscript file or request the native files to troubleshoot.  Are there guidelines to applying effects in Indesign?  We would like to try to document for our customers recommended processes for creating files.
    Thanks!

    Our strongest recommendation at Adobe for best PDF print publishing workflow results is to use the PDF/X-4 settings for exporting PDF from InDesign 6 and saving PDF from Adobe Illustrator 14. (The "draft PDF/X-4" support of InDesign 5 and Illustrator 13 was based on a draft version of the ISO PDF/X-4 specification that was significantly modified prior to final ISO standard ratification and publication!) PDF/X-4 provides for a reliable workflow in which live transparency and color management is carried in the PDF file itself; no "flattening" of transparency effects or color conversions occur until as late as possible in the print workflow, preferably at the RIP itself!
    PDF/X-4 is an excellent choice for PDF if you have a workflow which uses the Adobe PDF Print Engine technology in the RIP. In your case, Prinergy 4.1 does in fact provide Adobe PDF Print Engine technology. Make sure that (1) you enable the Adobe PDF Print Engine as opposed to CPSI and (2) you don't refine the pages as part of the Prinergy workflow (that process ruins your PDF by converting to PostScript and converting back to PDF - not something you want to do for a reliable PDF workflow with transparency and color management).
    Note that even if you do use PDF/X-4 and properly configure your PDF workflow system / RIP, it is still incumbent upon the designer to produce reasonable content. Just because "it looks good on the screen" (additive screen color) doesn't mean that it will reasonably translate to ink on substrate (subtractive printing color). Adobe does provide guidelines for use of transparency and color on its website for use by designers to guide them.
              - Dov

  • Problems previewing InDesign CS5.5 exported EPUBs in Apple iBooks, on an iOS device.

    I have EPUB Creation problems when I use my InDesign CS 5.5 document from my first EPUB book, as a template to create my other two EPUB books.
    My customer gave me a job that forced me to learn how to do EPUBs – and I'm still learning.  I created three books in Design CS 5.5, for fixed page PDF, with interactive table of contents and for exporting to a regular EPUB, with auto-reflow formatting and automated table of contents. These books were not created for print. 
    After I created the first one and successfully exported to an EPUB, that previewed fine in free Adobe Additions, I used the first InDesign CS 5.5 document as a template to create the other two publications.  These books were around a hundred pages, or less, with little or no placed jpeg images except on the three books' covers, so I did not create a Book.indb for each publication.  Each book is completed in single InDesign files with their own unique front cover art on their first page.
    When my customer previewed the three books on his iPad, in iBooks, all three books show the cover of the first book, when you see them on the iBooks library shelf.  Then when you open them, you see the correct cover for that specific book and the correct interior pages.
    When I open each InDesign file and open the File Information tabbed dialog, I have a different document title entered for each of the three different books.  When I export to EPUB, the EPUB Export Option dialog pops up and I have selected "Include Document Metadata."  I entered the Publisher name and a separate Unique Identifier for each book, when I export.
    After I emailed the three EPUBs to my iPod Touch, all three showed up in my iBooks library but when you see them on the library shelf they have the first book's cover on all three.  So I have a redundant cover preview on the library bookshelf icons, in the iBooks app, running in Apple iOS.
    I have two books by Elizabeth Castro about Creating EPUBs with InDesign.  I'm going to read them some more, especially the part about preparing your EPUB for Apple iBooks, on iOS.  But, I thought I would share my problem here to see if anyone has a solution for me.  Thanks.

    I often end up answering my own questions but I will do so again, this time, so that others can learn.  When you are exporting to EPUB in InDesign CS 5.5, an EPUB Export Options diolog appears.  Under "EPUB Cover," select "Use Existing Image file" and choose the actual file that was used on on the first page of the InDesign document, for the new book's cover.
    This feature can cause inbedded human error if you use a completed Indesign book as a template to create other books because even though you placed a new cover at the beginning of the book, the Export options still has the cover file selected for the previous book you worked on.
    I actually got the answer to my problem with the InDesign Help Menu, when InDesign CS 5.5 is launched.

  • Best practice for exporting a dps folio so a third party can work on it?

    Hi All,
    Keen for some thoughts on the best practice for exporting a dps folio, indd files, links and all, so a third party can carry on the work. Is their a better alternative to packaging each individual indd file and sharing the folio through adobe?
    I know there have been similar questions here in the past, but the last (that i've found) was updated mid 2011 and I was wondering if their have been any improvements to this seemingly backwards workflow since then.
    Thanks in advance!

    Nothing better than packaging them and using Dropbox to share. I caution you
    on one thing as far as packaging:
    http://indesignsecrets.com/file-packaging-feature-can-cause-problems-in-dps-
    workflows.php

  • Best audio format to embed for export to pdf?

    Hello, I was wondering what format for audio file would be best to embed for exporting to pdf. I want to embed the audio file in a button, for playback on mouseover in the exported pdf. Previously, when I had CS3, I actually had to convert my mp3s to avi files, as (believe it or not) that turned out to be the only format that would play back properly with a toolbar in the pdf, and only after I changed the media player (from quicktime to flash) for EACH audio file in the pdf. It was a headache trying to embed hundreds of audio files and I'm just wondering if CS5 has improved.

    Steve, that's (if I remember right) why I had to convert my mp3s to avi when I used CS3; because when I played them back in the exported pdf there was no controller-- but there was for avi. The problem I then had was with Acrobat/reader, which had quicktime set as the default player, so when I clicked the button to play the audio (avi) file, the pdf froze. This I solved by changing the default player FOR EACH audio file in the document (there were over 400) to adobe flash player; and because the audio was avi, as you say, a nice controller appeared, which disappeared once the audio finished. This was an OK workaround, if it wasn't for the fact that because I was using the flash player, the interactive pdf couldn't be used by mac users-- which many of the ebook's readers are. D'oh! So now I'm thinking to just stick with the mp3 format, now that Indesign can handle mp3s, and as you say, create buttons for stop and playback; this also solves the problem of having to post-export adjust the player settings for each file, which is not very fun, because when you edit the indesign document for future versions, it's kind of an annoyance to import pages to replace pages in the pdf without replacing the audio files. Anyway. Steve thank you for thinking out the finer details of my issue; I appreciate it and will have a go at making buttons, and let you know how that goes for such an interactive pdf. Thanks also Bob for the reply.

  • Multiple indesign files for product brochure one data merge file

    I have multiple indesign files for product brochure and there are price changes for various products.
    attached is a screen shot of the folder where all the indesign files are located as you can see each one has been laid out as a spread.
    Rather than opening each individual indesign file to amend prices can i quickly? or is there a way of compliling all documents into one file and quickly updating the price with the data merge file.
    thanks in advance.

    Absolutely not.
    (1)     PDF/VT-1 files must also be PDF/X-4 files. The “create PDF via distillation of PostScript” method precludes this since PostScript supports neither live transparency nor color management.
    (2)     The efficiencies of PDF/VT-1 require use of Forms XOjects and Image XObjects in the PDF file. That requires direct PDF creation that you get from PDF export. This is not available via any route that uses stink'in PostScript as an intermediary.
    (3)     Adobe most strongly endorses PDF creation from InDesign via the export function, not printing to PostScript and distilling. Such PostScript is optimized strictly for printing and not for PDF file creation.
              - Dov

  • Can I make an InDesign CS4 .swf export scale depending on the open size of a browser?

    Hi there.  I would like to make my inDesign CS4 .swf file able to scale in accordance with the open size of a browser.  When I have used Flash previously changing the size of the document to 100% achieved this effect.  However, I'm not having much luck with this approach with my inDesign CS4 .swf export.  I'm loathe to export it as an XML file for Flash as I want to keep my fancy page turns. Any help would be very much appreciated.  I'm not very fluent in Flash-speak so I'd also appreciate it if anyone offering a solution could t-a-l-k r-e-a-l s-l-o-w.
    Regards,
    Jackie

    This is quite old thread, I don´t have those source codes anymore... besides many people still uses monitors with width of 1024, 1219px wide magazine would clip in those monitors, so I don´t suggest to use it without shrinking....
    Anyway, if you want to improve positioning of your SWF, you have at least two way to do it
    1) Go to free http://www.bobbyvandersluis.com/swfobject/generator/index.html and create a new html-wrapper for your project
    2) If that´s not enough or you want some extra features like zoom, print or search, go to http://www.edocker.com and download a free trial of eDocker.
    ps. eDocker is in Adobe MAX Awards final, if you want to help it to win.... go to
    http://2010.max.adobe.com/awards/finalists/
    and vote for eDocker....

  • Building linkable navigation within an indesign document when exporting to pdf

    I'm working in InDesign CS3 and wondering if there is a way to create a linkable navigation in the program when exporting it to pdf. Also, how, if its possible, do I build an html file out of an InDesign document or exported from ID as a pdf?

    ID CS3 has an export to crossmedia xml for DreamWeaver option, but you need to edit the result in a html editor like DreamWeaver to clean it up and get a better result. You will never be able to get a page in html that looks exactly the same as in ID though unless you provide a pdf-page for download. You also do not have control of how a pdf on the web is shown for the user in his/her browser as that setting for that is done by the user, not by the page. Some show it on the page, others have pdfs for download (like me).

Maybe you are looking for