87 results found

1. Bug: exporting SVG's via exportFile(fileObjSingle, ExportType.SVG, svgOptions). has completely changed since 28.4

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program over many years that depends on special characters in the SVG ID's, and it is now completely broken.

   Does anyone know how to get back the previous SVG export format?

   Does anyone know if this is a bug that will be fixed?

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program… more

   6 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  ·  SDK and Scripting  ·  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

   Submit Rating

2. Incorrect word count via script

   At some point (I think v27) Illustrator has changed its word counting/division algorithm.

   So, where previously the results were sensible:
   "This.Was.Four.Words" — word count: 4
   "This.Is.3.Words" — word count: 4
   "I.WF05f.07.AB.000" — word count: 5
   "I.WF05f.AB.07.000" — word count: 5

   In version 27.4 the results are now confused:
   "This.Was.Four.Words" — word count: 1
   "This.Is.3.Words" — word count: 3
   "I.WF05f.07.AB.000" — word count: 4
   "I.WF05f.AB.07.000" — word count: 2

   For a discussion on the topic, and a testing script, see this thread.

   Note: maybe this bug was introduced while fixing this bug.

   6 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  ·  SDK and Scripting  ·  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

   Submit Rating

3. Scripting window keeps appearing and no way to remove it

   Uninstalling/Reinstalling does not remove prompt. Starting appearing after most recent update to with the new ipad features. Going back to older version, the window doesn't appear.

   •  

   •  

   •  

   •  

   6 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

   7 comments  ·  SDK and Scripting  ·  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

   Submit Rating
   Under Review  ·  AdminRama (Mgr, Software Development, Adobe Illustrator) responded

   This issue is happening due to a security feature added in Illustrator to inform the user if any external application tries to execute a script in Illustrator.

   Solution: Update your Logitech options app to the latest version – https://www.logitech.com/en-in/product/options

   https://helpx.adobe.com/illustrator/kb/fix-scripting-error.html

   We heard from some users that above solution is not working for them, we are investigating this issue. Meanwhile users can try the below workaround

   Create a JSX file with the following content:
   app.preferences.setBooleanPreference(“ShowExternalJSXWarning”, false);
   Save the above JSX file. Now, go to File > Scripts > Other Script, and choose the newly saved jsx file.

   This will suppress the warning dialog and run the script.

4. Add Bleed setting / reading value in Illustrator JavaScript

   I checked illustrator JavaScript Scripting Reference
   In 2017, only the document bleeding documentbleedoffsetrect can be set, but the bleeding size that has been set in the document cannot be obtained. Is it because the document is incomplete or this method is not provided? Now how can I get the bleeding size of the current document. thank you!

   Examples code:
   //set bleed
   docPreset.documentBleedOffset = [10, 10 10,10];

   But there is no way to get the value that has been set

   •  

   5 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  ·  SDK and Scripting  ·  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

   Submit Rating

5. Plugins Disappeared

   after updating to version 25.1
   the plugins in the "plugins folder"
   don't Load up
   when downgrade back to version 25.0.1
   Its work fine

   5 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  ·  SDK and Scripting  ·  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

   Submit Rating

6. Failure to create artboards when reading file with SDK in CC 2018

   Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

   In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems to be based on the documents the user has been working with.

   This means that if you have two users, one who uses small documents and one who uses large documents and they both open the same medium size file using your plugin, it works for the user who has been using large documents but not for the user who has been using small documents. As there is no AIDocument::SetDocumentMaxArtboardBounds function, there seems to be no way the plugin can overcome this issue.

   Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

   In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems… more

   5 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

   10 comments  ·  SDK and Scripting  ·  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

   Submit Rating

7. [ExtendScript] Rasterizing group creates two rasterItems

   1. MacOS 15.2.
   2. Adobe Illustrator 29.1
   3. Open demo document (attached) and run script (below).
   4. Should create one RasterItem, but instead creates two.

   Test Script (for use on attached test file):

   
   (function () {
   
       var doc = app.activeDocument;
       var item = doc.groupItems[0];
   
       // Raster Options
       var rasterOpts = new RasterizeOptions;
       rasterOpts.resolution = 192;
       rasterOpts.antiAliasingMethod = AntiAliasingMethod.None;
       rasterOpts.backgroundBlack = false;
       rasterOpts.clippingMask = false;
       rasterOpts.colorModel = RasterizationColorModel.DEFAULTCOLORMODEL;
       rasterOpts.convertTextToOutlines = false;
       rasterOpts.includeLayers = false;
       rasterOpts.padding = 0;
       rasterOpts.transparency = false;
       rasterOpts.convertSpotColors = true;
   
       doc.rasterize(item, item.geometricBounds, rasterOpts);
   
       var count = doc.rasterItems.length;
   
       if (count > 1)
           alert('The rasterization created two images but should have created only one.');
   
   })();
   
   
   

   See also this forum post.

   Edit: Note that the resolution (greater than 191) and the exact position of the group's path items makes a difference.

   1. MacOS 15.2.
   2. Adobe Illustrator 29.1
   3. Open demo document (attached) and run script (below).
   4. Should create one RasterItem, but instead creates two.

   Test Script (for use on attached test file):

   
   (function () {
   
       var doc = app.activeDocument;
       var item = doc.groupItems[0];
   
       // Raster Options
       var rasterOpts = new RasterizeOptions;
       rasterOpts.resolution = 192;
       rasterOpts.antiAliasingMethod = AntiAliasingMethod.None;
       rasterOpts.backgroundBlack = false;
       rasterOpts.clippingMask = false;
       rasterOpts.colorModel = RasterizationColorModel.DEFAULTCOLORMODEL;
       rasterOpts.convertTextToOutlines = false;
       rasterOpts.includeLayers = false;
       rasterOpts.padding = 0;
       rasterOpts.transparency = false;
       rasterOpts.convertSpotColors = true;
   
       doc.rasterize(item, item.geometricBounds, rasterOpts);
   
       var count = doc.rasterItems.length;
   
       if (count > 1)
           alert('The rasterization created two images but should have created only one.');

   … 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

   2 comments  ·  SDK and Scripting  ·  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

   Submit Rating

8. [ExtendScript] PageItem.resize doesn't scale Live Paint strokes

   While scaling Live Paint object correctly scales strokes if done via the UI, it fails to scale strokes if done via the PageItem.resize method in the scripting API.

   MacOS 15.0.1 Illustrator 29.0.

   Steps to reproduce:
   1. New document
   2. Create a Live Paint object including stroked areas.
   3. Select the Live Paint object.
   4. Run the following script:

   var item = app.activeDocument.selection[0];
   item.resize(200, 200, true, true, true, true);
   

   Expected result is that the Live Paint object's stroke widths would double. However they remain the same as before.

   See this user post.

   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  ·  SDK and Scripting  ·  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

   Submit Rating

9. [ExtendScript] Cannot change `underline` value of some text ranges.

   We cannot successfully set characterAttribute.underline to false in some textRanges.

   (MacOS 15.0 Adobe Illustrator 28.7.1)

   Steps to reproduce:
   1. New document
   2. Make a text frame with contents "ab"
   3. Set the "b" to a different fontStyle, eg. "italic"
   4. Run the below script, and check the console output.

   Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

   Actual result, test B on the "b" fails.

   Script:
   ```
   (function () {

   var doc = app.activeDocument,
       tf = doc.textFrames[0];
   
   var results = ['Results:'];
   
   tf.textRanges[0].characterAttributes.underline = true
   results.push('textRanges[0] test A: ' + (true === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[0].characterAttributes.underline = false;
   results.push('textRanges[0] test B: ' + (false === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[1].characterAttributes.underline = true;
   results.push('textRanges[1] test A: ' + (true === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[1].characterAttributes.underline = false;
   results.push('textRanges[1] test B: ' + (false === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   alert(results.join('\n'));
   

   })();
   ```

   See this community forum post.

   Update: User sttk3 discovered that the bug is actually that Illustrator ignores an attempt to set a characterAtrribute property if the value is the same as the applied character style's value for the same attribute.

   We cannot successfully set characterAttribute.underline to false in some textRanges.

   (MacOS 15.0 Adobe Illustrator 28.7.1)

   Steps to reproduce:
   1. New document
   2. Make a text frame with contents "ab"
   3. Set the "b" to a different fontStyle, eg. "italic"
   4. Run the below script, and check the console output.

   Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

   Actual result, test B on the "b" fails.

   Script:
   ```
   (function () {

   var doc = app.activeDocument,
       tf = doc.textFrames[0];
   
   var results = ['Results:'];
   
   tf.textRanges[0].characterAttributes.underline = true
   results.push('textRanges[0] test A: ' +

   … 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  ·  SDK and Scripting  ·  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

   Submit Rating

10. [ExtendScript] Line feed \u000A character assigned to text contents is converted to carriage return

    MacOS 13.3.1, Adobe Illustrator 27.4.1
    Also reported on Windows same version of Illustrator.

    Steps to reproduce.
    To see problem, run this script
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Break\u000Ame.';
    alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Break\u0003me.';
    alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
    

    })();
    ```
    I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
    The text on the right is a workaround, using an unexpected character (u+0003).

    There is a discussion here.

    This silent conversion is unexpected, and never wanted by the user (the scripter).

    MacOS 13.3.1, Adobe Illustrator 27.4.1
    Also reported on Windows same version of Illustrator.

    Steps to reproduce.
    To see problem, run this script
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Break\u000Ame.';
    alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Break\u0003me.';
    alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
    

    })();
    ```
    I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
    The text on the right is a workaround,… 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  ·  SDK and Scripting  ·  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

    Submit Rating

11. IUStringUnitsToAIReal doesn't recognize comma as decimal separator

    std::string input_ = "1,5"; // From Adobe header: The string to convert, which uses the localized international utilities (IU) decimal separator.
    AIReal n;
    sAIUser->IUStringUnitsToAIReal(ai::UnicodeString(input_), &n);

    This function interprets the text "1,5" as "15" even when the locale is set to a country where the system uses a comma decimal separator. Related functions IUStringToAIReal recognizes the comma, though.

    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  ·  SDK and Scripting  ·  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

    Submit Rating

12. AIPaintStyleSuite not found

    Trying to update a plugin to use the Illustrator 2020 SDK on Mac. Previously using the 2017 SDK. The SPBasicSuite AcquireSuite function fails to find the AIPaintStyleSuite when building with the 2020 SDK.

    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

    3 comments  ·  SDK and Scripting  ·  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

    Submit Rating

13. GetPresetSettings function doesn't work correctly in CC 2017 and later

    In Illustrator CC 2017 (22.x) and CC 2018 (23.x) the AIDocumentList::GetPresetSettings function is broken. It still returns an error if the preset doesn't exist, but if the preset does exist, it returns 0, but doesn't fill in the AINewDocumentPreset structure.

    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  ·  SDK and Scripting  ·  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

    Submit Rating

14. Javacript locking embeded image

    In Illustrator 29.1 this script worked just fine. I place an image, move it, name it, lock it and embed it. But in 29.3 this code gives an error message: It says that it cannot operate on a locked layer, BUT it still locks the placed item. If I move the lock to after the embed, the lock does not happen. So this code no longer works in 29.3.

    I think its weird in 29.1 that you were allowed to lock the placeditem before you embed it, but it doesn't work if you lock it afterwards.

    We are using macos 15.1.1 (and 15.3.1). I have verified that this code functions on 29.1 and fails on 29.3. We have verified this across multiple desktop computers.

    We found this issue in a much larger code base, but I was able to extract this down to this code chunk below.

    var doc = app.activeDocument;
    var scriptFile = new File($.fileName);
    var scriptFolder = scriptFile.path;
    var filePath = new File(scriptFolder + "/Golf Ball.png");

    // Place the image
    var placedItem = doc.placedItems.add();
    placedItem.file = filePath;

    // Center the image
    var docBounds = doc.artboards[0].artboardRect;
    var centerX = (docBounds[0] + docBounds[2]) / 2;
    var centerY = (docBounds[1] + docBounds[3]) / 2;

    placedItem.position = [centerX - placedItem.width / 2, centerY + placedItem.height / 2];

    // Embed the image

    placedItem.name = "Golf Ball Texture"; // Name the placed item

    placedItem.locked = true;
    placedItem.embed();

    In Illustrator 29.1 this script worked just fine. I place an image, move it, name it, lock it and embed it. But in 29.3 this code gives an error message: It says that it cannot operate on a locked layer, BUT it still locks the placed item. If I move the lock to after the embed, the lock does not happen. So this code no longer works in 29.3.

    I think its weird in 29.1 that you were allowed to lock the placeditem before you embed it, but it doesn't work if you lock it afterwards.

    We are using macos… 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

    4 comments  ·  SDK and Scripting  ·  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

    Submit Rating
    Done (Available in Prerelease)  ·  AdminEgor Chistyakov (Admin, Adobe Illustrator) responded

    The issue is reported to be fixed in the latest Pre-release build 29.4.130.

    The provided script should now work without any error dialog, as before.

    Please also see the recommended way to achieve locking of embedded art in modified script, in a comment within.

15. [ExtendScript] Cannot set Document.rulerUnits

    There is no way via scripting to set a document's rulerUnits (pts, mm, inch, etc) because the property Document.rulerUnits is—erroneously, surely—read only.

    If Document.rulerUnits was writable, we would simply do this:

      var doc = app.activeDocument;
      doc.rulerUnits = RulerUnits.MILLIMETERS;
    

    This is important because there is literally no way to set this via script, except to create a new document.

    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

    0 comments  ·  SDK and Scripting  ·  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

    Submit Rating

16. app.preferences.setIntegerPreference() does not work

    app.preferences.setIntegerPreference("rulerType", 0) changes the selection in the GUI but doesn't actually apply the change to the document.

    I still have to go into the GUI preferences, change the units to something else, then back to inches and close for the change to actually apply to the current document.

    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

    1 comment  ·  SDK and Scripting  ·  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

    Submit Rating

17. [ExtendScript] Incorrect paragraph count when linefeeds are used.

    MacOS 13.3.1, Adobe Illustrator 27.4.1

    To see the issue, run this script:
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Paragraph one\u000DParagraph two';
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Paragraph one\u0003still paragraph one';
    alert('Paragraph counts\n2 paragraphs: ' + tf1.paragraphs.length + '\n1 paragraphs with forced line break:\n ' + tf2.paragraphs.length);
    

    })();
    ```

    I expect the left text frame to have 2 paragraphs and the right text frame to have 1 paragraph, but the right text frame is incorrectly shown to have 2 paragraphs.

    This discussion revolves around this issue.

    Also, because the issue relates to conflating U+000A and U+000D, this bug may be implicated in this bug, this bug and this bug.

    MacOS 13.3.1, Adobe Illustrator 27.4.1

    To see the issue, run this script:
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Paragraph one\u000DParagraph two';
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Paragraph one\u0003still paragraph one';
    alert('Paragraph counts\n2 paragraphs: ' + tf1.paragraphs.length + '\n1 paragraphs with forced line break:\n ' + tf2.paragraphs.length);
    

    })();
    ```

    I expect the left text frame to have 2 paragraphs and the right text frame to have 1 paragraph, but the right text frame is incorrectly shown to have 2 paragraphs.

    This discussion revolves around… 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

    0 comments  ·  SDK and Scripting  ·  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

    Submit Rating

18. SVG Export for ExportOptionsSVG does "Save As" and not an "Export As"

    There is no true option for the File -> Export -> Export As for an SVG, doing app.activeDocument.exportFile( fileSpec, 'SVG', exportOptions ) is actually running the equivalent of File -> Save As SVG... Which produces an AI compatible type SVG but not a fully compatible SVG with other programs.

    It'd be nice to have a true "ExportOptionsCompatibleSVG"

    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

    0 comments  ·  SDK and Scripting  ·  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

    Submit Rating

19. Scripting: move selection to layer doesn't work if layer is not visible

    When moving selected elements to a layer, if that layer's visibility is set to false, it reports that it cannot move elements to a locked layer. However, it's not locked, it's just not visible. I do this all the time by physically dragging to a layer that is not currently visible. I was able to work around it by setting visibility to true, moving the elements, then making it false again, but it seems like a bug.

    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

    1 comment  ·  SDK and Scripting  ·  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

    Submit Rating

20. ExtendscriptToolkit is 32bit-only, OSX Catalina is 64bit-only

    I use a script I wrote for an important business function. For the last couple OSX upgrades, it has been warning me that ExtendscriptToolkit is not compatible with future versions of the OS. Specifically, OSX Catalina, which has been seeded to developers, will only support 64bit applications, and ExtendscriptToolkit is a 32bit application. Is that going to be addressed before the OS is released?

    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

    0 comments  ·  SDK and Scripting  ·  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

    Submit Rating