124 results found

1. Ability to identify if a Story is TOC_STORY, which TOC_STYLE is in use

   Using InDesign Server (or scripts in InDesign Desktop) via JavaScript, it would be very helpful if there was an API/mechanism for discovering details for table of contents usage.

   Current Issue:
   It doesn't look like there is a way to see if a TOCStyle is actually used anywhere. A document can contain multiple TOCStyles, but it's possible only one is placed in the document. Likewise, it doesn't appear there is a way to resolve the TOCStyle being used for a Story that is of type StoryTypes.TOC_STORY.

   Proposed solution(s):
   - Add a Stories property to the TOCStyle object that contains references to the Story objects that have that TOCStyle applied.
   - Expose the Story 'AppliedTOCStyle' property via ExtendScipt. This property already exists on the Story IDML object but doesn't appear to be exposed through ExtendScript.

   Thanks for your time!

   Using InDesign Server (or scripts in InDesign Desktop) via JavaScript, it would be very helpful if there was an API/mechanism for discovering details for table of contents usage.

   Current Issue:
   It doesn't look like there is a way to see if a TOCStyle is actually used anywhere. A document can contain multiple TOCStyles, but it's possible only one is placed in the document. Likewise, it doesn't appear there is a way to resolve the TOCStyle being used for a Story that is of type StoryTypes.TOC_STORY.

   Proposed solution(s):
   - Add a Stories property to the TOCStyle object that contains references to… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  InDesign Server  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Determine Link of a placed document and update it when document gets modified externally
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. HyperlinkTextDestination elements missing from anchored objects in exported icml

   When exporting icml from InDesign, anchored objects with hyperlink text destinations inside of them are missing those destinations.

   Steps to reproduce:

   1. Make a new document with text.
   2. Insert an anchored text frame with text into the story.
   3. Insert a hyperlink text destination into the anchored text frame.
   4. Create a hyperlink from outside of the text frame to inside of it.
   5. Export icml of the story.

   In the exported icml, the hyperlink destination will be missing and the link will be broken.

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  InDesign Server  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Indesign has stopped working / turns off when turned on / while document is open / after restoration turns off again

   Hello, I am writing to you asking for help. Since yesterday, adobe indesign has stopped working properly. After creating a new document / or opening a file that I was working on, the program crashes. It gives you a file rollback and shuts down again. Once we managed to turn on the program for a moment, but it was enough to stick to paragraph styles and move the frame, the program turns off immediately. I would ask for info on this matter. Tried installing previous versions, still the same problem; I tried uninstalling and reinstalling the program and the situation repeats itself. I am asking for help in this matter.

   Thanks for your reply in advance

   Hello, I am writing to you asking for help. Since yesterday, adobe indesign has stopped working properly. After creating a new document / or opening a file that I was working on, the program crashes. It gives you a file rollback and shuts down again. Once we managed to turn on the program for a moment, but it was enough to stick to paragraph styles and move the frame, the program turns off immediately. I would ask for info on this matter. Tried installing previous versions, still the same problem; I tried uninstalling and reinstalling the program and the situation… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Apple Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Handle SpecialCharacters with unicode equivalents as normal text

   SpecialCharacters are certainly necessary in places where there is no unicode equivalent (such as AUTOPAGENUMBER) but for many characters with unicode equivalents (BULLETCHARACTER, COPYRIGHTSYMBOL), it complicates string manipulation with no benefit (that I can see).

   Example:
   mySelectionContents = app.selection[0].contents;
   alert("The current selection is when added to a string is " + mySelectionContents);
   alert("The current selection is when coerced to a string is " + String(mySelectionContents));

   If you select a single bullet character, and force the specialCharacter to a string by adding it to the alert string you get "1396862068" or "BULLET_CHARACTER" if you explicitly convert to a string. You get an error in some places if you try to use mySelectionContents as text without this explicit conversion (my specific issues is objectExportOptions.customAltText).
   If you select two bullet characters with nothing else, you get •• with no need to coerce anything.

   Requested change:
   Ideally any character that has a unicode equivalent should be removed from the "special characters" set and handled like a normal character.

   If thats not possible, when getting the contents of a text object, the behavior should be the same regardless of the number of selected character, and should return the proper unicode value and not the special character value.

   Allow specialCharacters to be a valid value for objectExportOptions.customAltText (would fix the specific issue I'm having today, but there are a few other places where I have already worked around this issue)

   If none of these is possible, as a last resort, please provide access to the function used when multiple special characters in a row are selected, so we can use the same conversion.

   SpecialCharacters are certainly necessary in places where there is no unicode equivalent (such as AUTOPAGENUMBER) but for many characters with unicode equivalents (BULLETCHARACTER, COPYRIGHTSYMBOL), it complicates string manipulation with no benefit (that I can see).

   Example:
   mySelectionContents = app.selection[0].contents;
   alert("The current selection is when added to a string is " + mySelectionContents);
   alert("The current selection is when coerced to a string is " + String(mySelectionContents));

   If you select a single bullet character, and force the specialCharacter to a string by adding it to the alert string you get "1396862068" or "BULLET_CHARACTER" if you explicitly convert to… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Some plug-ins compiled for InDesign 2021 16.0 crash InDesign 2021 16.1 - the 16.0 and 16.1 SDK are incompatible

   When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.

   The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72

   Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point __ZN5boost16re_detail_10650018get_default_syntaxEh (unmangled: boost::re_detail_106500) when handling regular expressions.

   The problem is that this entrypoint's name is dependent on the Boost version (1.65).

   This entry point is provided by the (on Mac) embedded framework

   /Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regex

   When a plug-in compiled against SDK 16.0 is used with InDesign 2021 16.1, this entry point does not exist any more.

   Instead, the equivalent entry point is now boost::re_detail_107200 and boost::re_detail_106500 does not exist in InDesign 2021 16.1

   That causes the plug-in to crash InDesign.

   As a result, plug-ins that use boost_regex that are compiled for 2021 16.0 are incompatible with 2021 16.1 and vice-versa.

   When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.

   The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72

   Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point __ZN5boost16re_detail_10650018get_default_syntaxEh (unmangled: boost::re_detail_106500) when handling regular expressions.

   The problem is that this entrypoint's name is dependent on the Boost version (1.65).

   This entry point is provided by the (on Mac) embedded framework

   /Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regex

   When a plug-in compiled against SDK 16.0 is… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Bug when creating a form check box

   Creating a check box anchored in a text frame systematically ends with a crash in ID v16.2.1.

   javascript:
   app.select( app.selection[0].paragraphs[0].insertionPoints[-2] );
   app.selection[0].checkBoxes.add();

   applescript:
   set thePoint to insertion point -2 of paragraph 1 of selection
   tell thePoint to make check box

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Apple Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Can't retrieve XMP-metadata from Cloud-stored files

   Hello Adobe and hello Community,

   I'm having a problem with a Javascript I wrote to retrieve XMP metadata from linked files, that are stored in a Creative Cloud Library (Bought from Adobe Stock -> stored in a Library, because i was unable to download the files).

   Ultimately, the script retrieves the Creditline of all the linked graphics in an InDesign-file / InDesign-files in a folder by bulk processing.

   I have to accesse the XMP to retrieve the correct copyrightinfo.
   @Adobe: On Adobe Stock you guys put the information to give credit to the creator in the XMP field "Creditline" (creator - stock.adobe.com). In InDesign you cannot retrieve that field by out-of-the-box extendscript methods like: Link.linkXmp.copyrightNotice
   Please add the method to retrieve the correct field in extendscript!

   The Script I'm running works perfectly fine for links, that are located on my local drive or server but it doesn't work for Assets that are linked in the document from Adobe Creative Cloud.

   My Script looks something like this:

      if ( !ExternalObject.AdobeXMPScript ){
       try{ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');}
       catch (e){alert('Unable to load the AdobeXMPScript library!');}
   }
   
   
   var myFile = File(app.selection[0].graphics[0].itemLink.filePath);
   alert(myFile.fsName);
   xmpFile = new XMPFile(myFile.fsName, XMPConst.UNKNOWN, XMPConst.OPEN_FOR_READ);
   var myXmp = xmpFile.getXMP();
   xmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY);
   
   
   var myPsCredit = myXmp.getProperty(XMPConst.NS_PHOTOSHOP,"Credit");
   var myDcCredit = myXmp.getProperty(XMPConst.NS_DC,'rights[1]');
   if (myPsCredit) {
       var output = myPsCredit;
   } else{
       var output = myDcCredit;
   }
   
      alert(output);
   
   
      if( ExternalObject.AdobeXMPScript ){
       try{ExternalObject.AdobeXMPScript.unload(); ExternalObject.AdobeXMPScript = undefined;}
       catch (e){alert('Unable to unload the AdobeXMPScript library!');}
   }
   

   In this line I'm getting an error:

   errornumber: 1000

   errorstring: XMP Exception: OpenFile returned false

      xmpFile = new XMPFile(myFile.fsName, XMPConst.UNKNOWN, XMPConst.OPEN_FOR_READ);
   

   I'm reading from this, that the XMP of that file which is located in the Creative Cloud, cannot be opened.

   Is there a way for still retrieving the XMP-data from those files?

   Unless there is a way to bulk-download all the Assets from the cloud and automatically re-link them in all the files i want to check (which Adobe also does not support. You can only download one file at a time from the Creative Cloud App. Great job, well done, users are sooooo happy about that), I have to access the XMP in the Cloud-stored files.

   If there is no other way to access the needed XMP-data, please implement a fix to do so.

   Also posted here, but so far I didn't receive an answer: https://community.adobe.com/t5/indesign/retrieving-xmp-data-from-cloud-asset-throws-error/m-p/11522046?page=1

   Hello Adobe and hello Community,

   I'm having a problem with a Javascript I wrote to retrieve XMP metadata from linked files, that are stored in a Creative Cloud Library (Bought from Adobe Stock -> stored in a Library, because i was unable to download the files).

   Ultimately, the script retrieves the Creditline of all the linked graphics in an InDesign-file / InDesign-files in a folder by bulk processing.

   I have to accesse the XMP to retrieve the correct copyrightinfo.
   @Adobe: On Adobe Stock you guys put the information to give credit to the creator in the XMP field "Creditline" (creator… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. InDesign Scripting bug? Master Pageitems of specific Layer as Collection

   I want to see all 'master' page items of all master spreads on a specific layer using code like this:

   app.activeDocument.layers.itemByName('existLayerName').pageItems.everyItem().getElements();

   Even such a layer contains 'master' page items, this code always returns an empty array!

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. issue with find/replace in Text block, the option of article direction is missing in REPLACE panel

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Events: 'afterSelectionAttributeChanged' (LayoutWindow)

    The event 'afterSelectionAttributeChanged' (LayoutWindow) has the "Event" class, but logically its class should be "MutationEvent", since it is not clear which attribute of the object has been changed...

    The mutation event in most classes that have an addEventListener method does not work.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. InDesign Server + Catalina = heavy permission problems

    --- Update: PROBLEM SOLVED. See comment below ---

    We have run into to serious problems with running InDesign Server (IDS) on Mac OS 10.5.x Catalina: The problems are somehow related to file permissions and will only show when the IDS instances are started by launch agents (or launch deamons).

    This problem manifests itself in several ways we have encountered – using IDS CC 2020 as well as IDS 2019:

    1. Documents can only be opened from a limited number of locations – actually only one location as far as we know, the /private/tmp/ directory on the local machine. When one of our scripts (applescripts) tells IDS to open a file stored in any other location that we have tried – like the desktop or on a network volume connected to with smb or afp – IDS always trow back error number 29445, stating that the file is opened by another user or in another program (which its not).

    Copying or moving the document file manually to the /tmp folder makes the document openable without any error message. This might suggest a possible workaround – but no: the files cannot be copied or moved either by the scripts themselves:

    1. Any command to do something with files, other than files in the /tmp-folder, results in error ”Operation not permitted” when run from a script executed from IDS started with launch agents. Finder commands or shell script commands like cp, mv and touch all fails. So it’s not even possible to copy a document to the /tmp directory from the script before opening it.

    2. Trying to place an EPS-file in a document from a script in the ”forbidden” locations results in the same error message as mentioned first above: 29445. This does not happen with pdf:s, jpg:s or png:s. This is a smaller problem than the other two above, since it can be worked around by converting the eps-files to pdf.s in another process.

    But problem 1+2 is a showstopper.

    All these problems (probably having a common cause) are totally non-existent under other circumstances:
    • IDS is started with launch agents in systems older than 0.5.x Catalina – no problem.
    • IDS is started from Terminal with Catalina – no problem.
    • Indesign CC (client version) is used, under any Mac OS.
    There is no difference with IDS CC 2020 compared to IDS CC 2019 in this respect.

    The problems could be related to the new security measures introduced with Catalina, where access to network volumes and some local directories (like the desktop) are more heavily controlled than in previous systems, demanding the user to actively allow access to such locations. But with IDS, when started by agents or deamons, those dialogs never show up – only the error messages. And it’s not possible (as far as we know by all the ways we have tried) to allow such access for IDS.

    Another security measure, introduced with Mac OS 10.14 – the limitation for scripts to automate other applications without user consentis – is possible to handle under Catalina: A startup script (telling osascript to tell applications to do something) can force the desired dialogs in wich the user can allow InDesign Server to send Apple Events to those applications – once and for all. That’s fine.

    But using a startup script to force the corresponding dialogs for directory access will not work with IDS when started from launch agents. Whatever method we have tried, there is always the same the error message: Operation not permitted.

    Dragging launchd to the Full Disk Access panel doesn’t help either

    However, when IDS is started from Terminal, the same startup script gives us the desired result: The user is asked to give application Terminal access to the network filesystem – which we then can give it, once and for all.

    Starting IDS from Terminal is not a plausible solution in real production though, at least for stability reasons.

    So the question is: Why can IDS not be given access to file directories when started by launch agents? Why won’t the necessary questions show up?

    I guess the cause of the problems relies somewhere inbetween Apple and Adobe. The combination of launch agents and InDesign Server does not work in combination with the new Catalina security measures. Adobe certainly has responsibility, at least partly, since there is no announcement that running IDS by launch agents under MacOS Catalina will not work.

    We hav invested in machines that canon ot run systems older than Mac OS Catalina, so our scripts must work in that environment.

    Anyway, the most important question for us right now is: What can we do in the current situation? Is there a workaround?

    --- Update: PROBLEM SOLVED. See comment below ---

    We have run into to serious problems with running InDesign Server (IDS) on Mac OS 10.5.x Catalina: The problems are somehow related to file permissions and will only show when the IDS instances are started by launch agents (or launch deamons).

    This problem manifests itself in several ways we have encountered – using IDS CC 2020 as well as IDS 2019:

    1. Documents can only be opened from a limited number of locations – actually only one location as far as we know, the /private/tmp/ directory on the local machine. When one of… more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  InDesign Server  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Update Indesign script to support ES6

    Update Indesign to support modern ES6.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Separate the indesign scripting forum from the indesign community support forum

    With the relaunch of Adobe's community support forums, the indesign scripting forum was merged with the general indesign forum. Please separate the two so users can find the most relevant content.

    45 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    19 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Partial Fix  ·  amaarora responded

    Hi,
    1. The majority of InDesign Scripting threads were merged and archived at first.
    2. After a month or so, InDesign Scripting re-appeared as its own topic in the new forums.
    3. David K. started un-archiving older threads last week, a few at a time, very slowly and by hand, because of odd server-side limitations.
    4. There is no “Direct Link” to the Scripting Topic at this time, but this ought to be fixed with the current sprint from the forums team. The internal bug number is: ALFD-1530

    While we wait for ALFD-1530, there is a backdoor way to find direct links to topics. You can follow a topic then look at your follows… or just use these links:

    • InDesign Scripting: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/scripting
    • InDesign SDK: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/sdk
    • InDesign Server Developers: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/server%20developers

    Thanks

15. fos az egesz

    szar

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. BUG - Scripting: multiple paragraph styles for multiple paragraphs in one text box not working correctly

    Paragraph styles are not being applied correctly when setting more than two paragraph styles for more than one paragraph in a text box.

    For three or more paragraphs, paragraph n is set to paragraph style n, and paragraphs 1 through n-1 are set to paragraph style n-1. The expected behaviour would be that paragraph 1 is set to paragraph style 1, paragraph 2 is set to paragraph style 2, paragraph 3 is set to paragraph style 3, ..., paragraph n is set to paragraph style n.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. PreflightScope not working

    PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

    var currDoc = app.documents[0];
    if (app.preflightProfiles.itemByName("export").isValid){
            app.preflightProfiles.itemByName("export").remove();
    }
    var pfProfile = app.preflightProfiles.add({name: "export"});
    var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
    pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
    currDoc.preflightOptions.preflightScope = '1-2';
    var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
    pfProcess.waitForProcess();
    pfResults = pfProcess.aggregatedResults[2];
    $.writeln(pfResults);
    

    ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’ and ‘1,2’)

    We would very much like to speed our preflight process and get rid of the tedious parsing of preflight results only to discard pages not set in the scope.

    One additional note on its behavior that could be fixed, too: if you define a scope that includes page numbers not in the document, either as
    - a range e.g. "1-5" when document has pages numbers 1,4,5,6,... or
    - e.g. "14" when the document has only 12 pages
    ––> InDesign throws an error "Error 30477: Invalid value for set property 'preflightScope'. Expected PreflightScopeOptions enumerator or String, but received "1-5".", which is quite misleading.

    PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

    var currDoc = app.documents[0];
    if (app.preflightProfiles.itemByName("export").isValid){
            app.preflightProfiles.itemByName("export").remove();
    }
    var pfProfile = app.preflightProfiles.add({name: "export"});
    var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
    pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
    currDoc.preflightOptions.preflightScope = '1-2';
    var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
    pfProcess.waitForProcess();
    pfResults = pfProcess.aggregatedResults[2];
    $.writeln(pfResults);
    

    ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’… more

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  CEP  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Under Review  ·  amaarora responded

    Thanks for reporting
    We are reviewing the issue

    -InDesign Team

18. Catalina AppleScript seems to be broken

    Tried a few samples that came with ID -- they all stop with errors

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Apple Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. A new TextFrame InsertionPoints.count changes from 1 to zero when linked to a previous frame and the program effectively crashes

    Replaces a previous post - this is written and tested in VB Script:

    Set myInDesign = CreateObject("InDesign.Application.2020")
    Set myDocument = myInDesign.Documents.Add
    Set myPage = myDocument.Pages.Item(1)
    Set myTextFrameA = myPage.TextFrames.Add
    myTextFrameA.geometricBounds = Array(72, 72, 144, 144)
    Rem Add a page.
    Set myNewPage = myDocument.Pages.Add
    Rem Create another text frame on the new page.
    Set myTextFrameB = myNewPage.TextFrames.Add
    myTextFrameB.geometricBounds = Array(72, 72, 144, 144)
    mycount = myTextFrameB.InsertionPoints.Count
    msgbox(mycount)
    myTextFrameA.NextTextFrame = myTextFrameB
    mycount = myTextFrameB.InsertionPoints.Count
    msgbox(mycount)
    myTextFrameB.InsertionPoints.FirstItem.Contents = "This is Bob"
    Rem "Program Crashes"

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  VB Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Make the (Black) Color Swatch a TRUE BLACK

    In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

    The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

    Please, Please, Please, make the (Black) color swatch a true rich black color (since users cannot adjust this color).

    Since the standard (Black) color swatch isn't true black, it will take me quite a bit of time to apply a new color to all my previously designed files that use your standard (Black) color swatch.

    In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

    The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

    Please, Please, Please, make the (Black) color swatch a… more

    •  

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  InDesign Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close