7119 results found

1. RTL Text Bugs Despite "Fixed" Notification

   InDesign 20.3.1.073

   Dear Adobe InDesign Development Team,
   We appreciate your efforts in addressing the RTL text issues introduced with the HarfBuzz engine in InDesign 19 (2024) and the improvements made through version 20.3.1.073.
   However, we must bring to your urgent attention that, contrary to your recent "Fixed" notification, several critical bugs remain unresolved, several critical bugs remain unresolved, impacting right-to-left (RTL) workflows (Hebrew & Arabic).

   Critical Bug:

   • #1: Disappearing Punctuation/Text in PDF Export with Drop Cap and Line Break When a drop cap is applied )in justified RTL text( followed by punctuation and a line break, the punctuation marks (and sometimes adjacent text) completely disappear in the exported PDF, leaving only white space. This issue is particularly dangerous because it appears ONLY in the exported PDF, not in InDesign's interface and can easily lead to published documents with missing content. o Report + screenshots: https://www.adobeprerelease.com/beta/C6DFA254-C40C-4EEB-8F6D-F4AEDA2E6171/feedback/item/ID-4262114

   Additional Unresolved Bugs:

   • 2: Reversed Cursor Navigation with Modifier Keys
     When navigating RTL text using arrow keys with Shift (to select text) or Command/Control (to skip words), the cursor moves in the opposite direction of the arrow pressed (e.g., right arrow selects text to the left). Regular arrow navigation (without modifiers) works correctly. This occurs in “Visual” cursor movement mode (Preferences > RTL > Cursor Movement) which is commonly used by RTL users.
     o Report + video: https://www.adobeprerelease.com/beta/C6DFA254-C40C-4EEB-8F6D-F4AEDA2E6171/feedback/item/ID-4260041

   • 3: No Visual Indication for 'Nikkud' (Diacritics) Selection
     Unlike the previous text engine, the HarfBuzz engine lacks visual feedback when selecting nikkud (Hebrew diacritics), making it difficult to edit accurately.
     o Report + screenshots: https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/48967916--id-4246352-nikkud-accents-diacritics-selection

   We urge the InDesign team to prioritize the critical PDF export bug (Issue #1) for immediate resolution, work toward a complete solution for all RTL bugs, and update the misleading “Fixed” notification for version 20.3.1.073.

   Please let us know how we can assist further (e.g., providing test files or additional details).

   Thank you for your attention to this matter.

   Sincerely,
   Adobe InDesign User Community
   RTL Languages

   InDesign 20.3.1.073

   Dear Adobe InDesign Development Team,
   We appreciate your efforts in addressing the RTL text issues introduced with the HarfBuzz engine in InDesign 19 (2024) and the improvements made through version 20.3.1.073.
   However, we must bring to your urgent attention that, contrary to your recent "Fixed" notification, several critical bugs remain unresolved, several critical bugs remain unresolved, impacting right-to-left (RTL) workflows (Hebrew & Arabic).

   Critical Bug:

   • #1: Disappearing Punctuation/Text in PDF Export with Drop Cap and Line Break When a drop cap is applied )in justified RTL text( followed by punctuation and a line break, the punctuation marks (and… more

   • 

   •  

   •  

   • 

   • 

   131 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

   58 comments  ·  Text/Story/Table  ·  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. [ID-4258070]Disappearing Punctuation Marks in Hebrew RTL Justified Text in Exported PDF

   Severity Level: Critical
   Impact: Severe disruption to Hebrew text layout workflow and document integrity

   Bug Description

   Punctuation marks are randomly disappearing in justified Hebrew text blocks (RTL direction), specifically at:
   - Paragraph endings
   - Forced line breaks
   - Last lines of justified paragraphs

   Technical Context

   • Text Direction: Right-to-Left (RTL)
   • Language: Hebrew
   • Text Alignment: Justified

   Affected Punctuation Marks

   • Periods (.)
   • Semicolons (;)
   • Commas (,)
   • Colons (:)

   Specific Behavior in RTL Context

   1. When Hebrew text is set to justified alignment, punctuation marks vanish:
      • At the end of paragraphs
      • Before forced line breaks
   2. Exception: Punctuation marks remain visible if the last line is explicitly right-aligned
   3. The issue appears to be specific to RTL text direction and does not occur in LTR text

   Known Workarounds and Their Limitations

   1. Legacy Composition Engine Option:

      • While switching to the legacy composition engine in preferences resolves this specific issue
      • We strongly advise against this solution due to:
        • Previously reported bugs and limitations in the legacy engine (see bug reports #ID-4245219)
        • Performance issues documented in our earlier reports
        • Compatibility concerns with newer features
      • We require a proper fix in the current composition engine rather than reverting to legacy solutions

   2. Temporary Layout Workaround:

      • Right-align the last line of affected paragraphs
      • This is not viable for production as it:
        • Affects layout consistency
        • Requires constant manual intervention
        • Disrupts automated workflows

   Technical Impact

   • Compromises Hebrew document accuracy
   • Requires constant manual checking and fixes
   • Disrupts automated workflows for Hebrew text processing
   • May lead to incorrect final output in published Hebrew materials

   Priority Level

   Immediate attention required as this bug:
   - Affects core Hebrew typography functionality
   - Creates significant quality control issues in RTL text layouts
   - Requires time-consuming manual verification
   - May result in incorrect published content

   Steps to Reproduce

   1. Set paragraph direction to RTL
   2. Create a Hebrew text block with justified alignment
   3. Type a paragraph ending with any punctuation mark
   4. Add forced line breaks within the paragraph
   5. Observe the disappearance of punctuation marks at:
      • Paragraph endings
      • Before forced line breaks

   Technical Investigation Request

   Please investigate:
   - RTL text rendering engine behavior
   - Interaction between justified alignment and RTL text direction
   - Potential conflicts between Hebrew text processing and punctuation handling
   - Implementation of punctuation handling in the current composition engine

   Request

   Immediate investigation and hotfix needed in the current composition engine. While we acknowledge the existence of a legacy engine workaround, we require a proper fix in the current engine to maintain workflow efficiency and compatibility with modern features.

   Severity Level: Critical
   Impact: Severe disruption to Hebrew text layout workflow and document integrity

   Bug Description

   Punctuation marks are randomly disappearing in justified Hebrew text blocks (RTL direction), specifically at:
   - Paragraph endings
   - Forced line breaks
   - Last lines of justified paragraphs

   Technical Context

   • Text Direction: Right-to-Left (RTL)
   • Language: Hebrew
   • Text Alignment: Justified

   Affected Punctuation Marks

   • Periods (.)
   • Semicolons (;)
   • Commas (,)
   • Colons (:)

   Specific Behavior in RTL Context

   1. When Hebrew text is set to justified alignment, punctuation marks vanish:
      • At the end of paragraphs
      • Before forced line breaks
   2. Exception: Punctuation marks remain visible if the last line is… more

   •  

   • 

   •  

   •  

   •  

   • 

   406 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

   171 comments  ·  Text/Story/Table  ·  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
   FIXED  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.3.1.073). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

3. Hebrew Text Bugs in InDesign 2025

   1. Incorrect cursor movement with arrow keys in Visual movement mode: When working with Hebrew text in Visual movement mode, the arrow keys do not move the cursor in the expected or desired direction. This issue disrupts editing and text arrangement in Hebrew.
      Tracked via https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/48967859-cursor-movement-wrong

   2. Disappearance of punctuation marks and letters in exported PDFs: In various situations when working with Hebrew text, certain punctuation marks (e.g., periods, commas, etc.) and individual letters disappear in the final exported PDF file.
      Tracked via https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/49051367--id-4245219-disappearing-punctuation-marks-in-hebr

   3. Second letter disappears after an opening letter: Under certain conditions, the second letter after the opening letter in a word vanishes. This issue affects the appearance and natural flow of the text.
      Tracked via https://indesign.uservoice.com/forums/601180/suggestions/49198283

   1. Incorrect cursor movement with arrow keys in Visual movement mode: When working with Hebrew text in Visual movement mode, the arrow keys do not move the cursor in the expected or desired direction. This issue disrupts editing and text arrangement in Hebrew.
      Tracked via https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/48967859-cursor-movement-wrong

   2. Disappearance of punctuation marks and letters in exported PDFs: In various situations when working with Hebrew text, certain punctuation marks (e.g., periods, commas, etc.) and individual letters disappear in the final exported PDF file.
      Tracked via https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/49051367--id-4245219-disappearing-punctuation-marks-in-hebr

   3. Second letter disappears after an opening letter: Under certain conditions, the second letter after the opening letter in… more

   350 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

   122 comments  ·  Text/Story/Table  ·  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
   CLOSED  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   This issue is amalgamation of multiple issues related to Hebrew Text. We are now tracking all the issues via different UserVoice thread as listed in the description.

   -

   Adobe InDesign Team

4. [ID-4257184]InDesign 2025(v20.0) Performance issues: Delay or beach balls on basic operations

   Problem: 

   InDesign Performance issues: Delay or beach balls observed on basic operations on Macintosh

   Steps to Reproduce:

   • We have reproduced one scenario in which the existence of the Documents Font Folder and Contextual Task bar results in some slowness.
   • Other workflows causing slowness are being investigated - No reliable reproducible steps

   Impacted workflows:

   • Switching to InDesign
   • Open/Closing of Document
   • Edit/Scroll/Copy-paste/Highlight operation on Text
   • Text disappears, illustrations disappear
   • Imported or added text turns black until a style is applied.
   • Font menu highlight not following my mouse movement
   • Text will not change fonts until I click the mouse inside or outside the text box.
   • Resize a document window, the corner flies below the screen border
   • Click or Drag of the mouse
   • Switching between tools
   • "Waiting for UXP plugins to finish up remaining tasks."

   Workaround:

   • Disable Contextual Task Bar or remove Documents Font Folder
   • Close the MAGNET application
   • Revert to InDesign 19.5, No performance lag is observed.
   • Restarting the machine and trashing the preferences seems to resolve the issue temporarily
   • Disabling any font manager software seems to resolve the issue. One customer confirmed that disabling "Rightfont" resolved the issue.
   • Uninstall-Reinstall seems to resolve the issue temporarily
   • Turn off Preflight seems to resolve the issue temporarily

   Note:

   1. The issue seems to be specific to the MAC platform only. Impacted macOS (Sequoia, Sonoma, Ventura(maybe), Monterey)
   2. The issue seems to be specific to the MAC devices
      • Apple MacBook Pro M1/M2/M3
      • Apple MacBook Air M1/M2/M3
      • Apple Max Studio M1/M2/M3
      • Apple Mac mini M1/i7 Intel
   3. The issue exists for both old and new documents

   Additional information needed:

   1. Are you opening the indd documents from the folder containing the Documents Font Folder?
   2. Is the "Contextual Task bar" shown? If yes, Disable it from "Window->Contextual Task bar"
   3. Screenshot of Memory usage while the issue is observed
   4. Please follow the below steps for InDesign 20.0.1.32 and InDesign PR 20.1.066 on Macintosh
      • Open Terminal in full-screen mode
      • Drag the InDesign application on the terminal (e.g. "/Applications/Adobe\ InDesign\ 2025/Adobe\ InDesign\ 2025.app/Contents/MacOS/Adobe\ InDesign\ 2025")
      • Copy the logs when you start facing the slowness in a text(.txt) file. Share the file with us at sharewithID@adobe.com.

   Problem: 

   InDesign Performance issues: Delay or beach balls observed on basic operations on Macintosh

   Steps to Reproduce:

   • We have reproduced one scenario in which the existence of the Documents Font Folder and Contextual Task bar results in some slowness.
   • Other workflows causing slowness are being investigated - No reliable reproducible steps

   Impacted workflows:

   • Switching to InDesign
   • Open/Closing of Document
   • Edit/Scroll/Copy-paste/Highlight operation on Text
   • Text disappears, illustrations disappear
   • Imported or added text turns black until a style is applied.
   • Font menu highlight not following my mouse movement
   • Text will not change fonts until I click the mouse inside or outside… more

   •  

   •  

   • 

   165 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

   175 comments  ·  Performance/Usability  ·  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
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   We have made some Performance Improvements in the latest InDesign Release 2025 (Version 20.1), available via Creative Cloud Desktop application. This issue has also been fixed as part of performance improvements.

   
   

   Please let us know if you still face slowdown while doing basic operations in this latest InDesign release.

   
   

   --

   Adobe InDesign team

5. [ID-4246352]NIKKUD (accents/diacritics) selection has become invisible

   InDesign version: v20 (both Mac & PC)

   Hebrew letters can use NIKKUD - vocalization diacritical marks (function like Vowels) under/above the letter.

   • In previous versions (-2023) it was possible to select only the NIKKUD (attached image) of the letter. (in order to specify the position of the NIKKUD using the Diacritic Positioning panel or to change color, etc.)
   • In the current version (2024-2025) the selection is on the entire letter, and there is no visual indication whether the letter or the NIKKUD is selected (attached image).

   Note: Sometimes there are two NIKKUD characters and even in such a case in the past it was possible to choose each separately (attached image)

   InDesign version: v20 (both Mac & PC)

   Hebrew letters can use NIKKUD - vocalization diacritical marks (function like Vowels) under/above the letter.

   • In previous versions (-2023) it was possible to select only the NIKKUD (attached image) of the letter. (in order to specify the position of the NIKKUD using the Diacritic Positioning panel or to change color, etc.)
   • In the current version (2024-2025) the selection is on the entire letter, and there is no visual indication whether the letter or the NIKKUD is selected (attached image).

   Note: Sometimes there are two NIKKUD characters and even in such a case in… more

   •  

   •  

   •  

   223 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

   53 comments  ·  Text/Story/Table  ·  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  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

   We have been able to reproduce the issue and it is currently under investigation. 

   —

   Adobe InDesign Team

6. [ID-4243320] Incorrect cursor movement in RTL text when Harfbuzz text shaping is used.

   InDesign version: v20 (both Mac & PC)

   In right-to-left languages ​​(Hebrew & Arabic) the cursor movement went crazy:
   - Left key - goes up
   - Right key - jumps to the end of the line...
   We can't work that way

   Note: both (23\25 indd) set to 'Visual' in preferences > right-to-left > cursor movement (of course, changing the setting to 'logical' doesn’t solve it)

   • 

   189 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

   46 comments  ·  Text/Story/Table  ·  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
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   Fix for this issue is available in the latest InDesign Release version 20.2, available via Adobe CCD app.

   
   

   --

   Adobe InDesign team

7. [ID-4265002][ExtendScript] Folder.execute() no longer works in Indesign 20.4

   Folder.execute() no longer reveals the folder and activate the Finder. It does nothing. Tested on Indesign 20.4 on MacOS 15.5.

   Steps to reproduce:

   1. Run this ExtendScript:

   
       Folder.desktop.execute();
   
   

   Expected result: activating the Finder, revealing the Desktop folder.

   Actual result: nothing.

   See also this post on the forum.

   •  

   •  

   32 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

   6 comments  ·  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
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.4.1.004). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

8. InDesign Color Settings Are Overwritten by Other Versions

   Summary:
   InDesign is unable to maintain separate color settings for each version. Whenever a different version is activated, the color settings are forcibly overwritten by the last activated version.

   Steps to Reproduce:
   Launch InDesign 2025 and set the color settings to “Preset A” (e.g., a print vendor’s recommended settings).
   Launch and activate InDesign 2024.
   Without any warning, InDesign 2024 will adopt the same Preset A color settings.
   This also occurs in the opposite direction: activating either version will overwrite the other’s previously configured color settings.

   Expected Behavior:
   Like Photoshop and Illustrator, InDesign should maintain independent color settings for each version.

   Actual Behavior:
   InDesign, Illustrator, Photoshop, and Bridge all write the currently selected color setting preset to the shared sync file:
   ~/Library/Preferences/Adobe/Color/ACEConfigCache2.lst
   This file is what allows Bridge to synchronize color settings across Adobe apps.

   However, InDesign is the only application that overwrites the settings record for another version of InDesign, regardless of version.

   Root Cause:
   All apps use the same file, but only InDesign fails to differentiate versions.
   This causes one version of InDesign to overwrite the color settings of another—simply by being activated.

   Commentary:
   This behavior disrupts professional workflows.
   In environments such as print production where different versions of InDesign must use different color settings (e.g., for different clients or print vendors), this is a critical issue.

   InDesign should follow the same behavior as Photoshop and Illustrator:
   Write version-specific entries to ACEConfigCache2.lst, and avoid overwriting other versions’ settings.

   Summary:
   InDesign is unable to maintain separate color settings for each version. Whenever a different version is activated, the color settings are forcibly overwritten by the last activated version.

   Steps to Reproduce:
   Launch InDesign 2025 and set the color settings to “Preset A” (e.g., a print vendor’s recommended settings).
   Launch and activate InDesign 2024.
   Without any warning, InDesign 2024 will adopt the same Preset A color settings.
   This also occurs in the opposite direction: activating either version will overwrite the other’s previously configured color settings.

   Expected Behavior:
   Like Photoshop and Illustrator, InDesign should maintain independent color settings for each version.

   … more

   •  

   31 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  ·  Others  ·  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. [ID-4260604] InDesign with Typeface app is going in Protective Shutdown on document close

   Customer Scenario1

   Brand new Indesign 20.2: open any document, change nothing in it and close it. Indesign gives a warning and then crashes.
   MacOS 15.3.1 (24D70), Macstudio M2, I have reset all personal prefs, I am using Typeface app. This didn't happen with 20.1

   Customer Scenario2

   Doing a data merging of a .CSV file.

   Result

   InDesign is going in Protective Shutdown for few scenarios

   Workaround

   • Deactivate the Typeface app and continue to work with InDesign v20.2.0.36
   • Rolling back to InDesign 20.1.0.71 to continue to work with the Typeface app

   • 

   •  

   • 

   •  

   •  

   • 

   • 

   •  

   26 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  ·  Crash/Freeze/Hang  ·  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
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.3.0.060). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

10. [ID-4264855] Issue with Animated Zoom in GPU

    New PC GPU zoom doesn't seem to centre the zoom on the cursor leading to not super useful behaviour (you have to zoom and then drag with the hand tool to get back to what you were originally trying to zoom into). It's very disorientating.

    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

    15 comments  ·  Performance/Usability  ·  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
    Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    The fix of the issue is now available in the latest InDesign 2025(v20.5.0.048). We recommend you upgrade to the latest version for the fix.

    If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

    —

    Adobe InDesign Team

11. Hyphenation settings see note references as a character

    Hypenation settings consider a note reference as a character, so if you have a footnote callout at the end of a word and hyphenation settings are set to "before last 3" it will make 2-letter hyphenation.

    •  

    19 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  ·  Others  ·  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. [ID-4253441]"Don't Save" and "Cancel" Positions are reversed in InDesign 20.0

    "Don't Save" and "Cancel" Positions are reversed in Indesign 20.0.

    Why in the world would they do this??? Yet another meaningless update to hinder production.

    Not OS related, as I have not updated my OS since updating to Indesign 20.

    Mac Sonoma 14.7

    3.6 GHz 10-Core Intel Core i9

    AMD Radeon Pro 5700 XT 16 GB

    •  

    •  

    •  

    •  

    •  

    46 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

    30 comments  ·  Performance/Usability  ·  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
    CLOSED  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    This option was updated in InDesign 20.0 version to match industry standards and stay consistent. We standardized this behavior to make workflows more predictable across products. 

    We know that changes can take some adjustment, and we appreciate the feedback we received. Over time, users have adapted to this new behavior, which helps us maintain consistency and avoid confusion in future workflows.

    We appreciate everyone’s input and your help in making InDesign better!

    —

    Adobe InDesign Team

13. Deleting an odd number of pages causes the text frame derived from the primary text frame to double

    1. specify a primary text frame for both the left and right pages on the parent page. (figure1)
    2. Delete an odd number of pages. At this time, the parent page is reapplied.
    3. The text frame will be doubled. (figure2)

    Deleting (or adding) an even number of pages will not result in this behavior.
    Deletion/addition of an odd number of pages should not cause doubling.
    Specifically, we would like the text chain of the text frame for which the primary text frame is specified to be retained. (figure3)

    Reference:
    I believe the primary text chain is a feature that was added with the automatic text chain that was in QuarkXPress in mind, but the automatic text chain in QX did not cause duplication when odd number of pages were increased or decreased.

    ページを奇数枚削除した場合、プライマリーテキストフレーム由来のテキストフレームが二重化する

    1.　親ページで、左右ページともにプライマリーテキストフレームを指定しておく。（figure1)
    2.　ページを奇数枚削除する。このとき、親ページの再適用が行われる。
    3.　テキストフレームが二重化する。（figure2）

    偶数枚のページの削除（もしくは追加）では、この挙動にはならない。
    奇数枚のページの削除／追加でも、二重化しないようにしてほしい。
    具体的には、プライマリーテキストフレームが指定されているテキストフレームのテキストチェーンが保持されるようにしてほしい。（figure3）

    参考：
    プライマリテキストチェーンは、QuarkXPressにあった自動テキストチェーンを意識して追加された機能だと思っているが、QXの自動テキストチェーンでは、奇数枚のページの増減で二重化が起きることはなかった。

    1. specify a primary text frame for both the left and right pages on the parent page. (figure1)
    2. Delete an odd number of pages. At this time, the parent page is reapplied.
    3. The text frame will be doubled. (figure2)

    Deleting (or adding) an even number of pages will not result in this behavior.
    Deletion/addition of an odd number of pages should not cause doubling.
    Specifically, we would like the text chain of the text frame for which the primary text frame is specified to be retained. (figure3)

    Reference:
    I believe the primary text chain is a feature that was added with… more

    •  

    •  

    •  

    16 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  ·  Text/Story/Table  ·  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. [ID-4262670][ERROR(RSC-005) in EPUB Checker]InDesign 20.3 creates target attributes to every link in EPUB

    The latest InDesign version (20.3) creates target="_blank" attributes to every link when exported as EPUB. Doesn't matter if the link contains URL or it's a link from a text anchor. The latest EPUB Check version (5.2.1) gives an error with every link that doesn't have href attribute which means every text anchor is invalid.

    For example:
    <h1 id="_idParaDest-1" class="Header-1"><a id="_idTextAnchor000" target="_blank"></a>Foreword</h1>

    In EPUB Check this is an error:
    ERROR(RSC-005): Error while parsing file: element "a" missing required attribute "href"

    •  

    •  

    • 

    11 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

    9 comments  ·  ePub/HTML/Publish Online  ·  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
    FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    Fix for this issue is now available in the latest InDesign Release – InDesign 20.4 Release.

    
    

    Please update to the latest InDesign Release via CCD app to get the fix.

    
    

    ---

    Adobe InDesign team

15. Omitted page ranges are affected by sections

    Summary:
    When describing a page range that omits the first/final page, if there is a starting section in the range, the output results will remain in the page range within the section.

    Verification:
    Create an 8-page document (Figure 1).
    Set the start section on page 5.
    Export the PDF (and print as well) and enter “-6” in the page range (Figure 2).

    Result:
    A PDF of pages 5-6 is exported.
    When the PDF is exported again, the page range is set to “5-6” (Figure 3).

    Ideal result:
    should not be affected by the presence or absence of sections.
    A PDF with pages 1-6 is exported.
    When the PDF is exported again, the page range is populated with “1-6”.

    Note:
    In the above verification, the first page was omitted. Similarly, if the last page is omitted, such as “3-”, only the range of 3-4 pages separated by sections will be exported.
    There is no mention of such a specification in the user guide.

    Verified version and OS:
    InDesign 18.3.0.50
    macOS 14.7.6

    <にほんご>
    概要：
    先頭ページ/最終ページを省略したページ範囲を記載した際、範囲内に開始セクションがあると出力結果がセクション内のページ範囲にとどまってしまう。

    検証：
    8ページのドキュメントを作成する（図1）。
    5ページ目に開始セクションを設定する。
    PDFを書き出し（プリントも同様）でページ範囲に“-6”と入力（図2）。

    結果：
    5-6ページのPDFが書き出される。
    再度PDF書き出しを実行するとページ範囲には“5-6”が入力されている（図3）

    理想とする結果：
    セクションの有無の影響を受けないこと。
    1-6ページのPDFが書き出される。
    再度PDF書き出しを実行するとページ範囲には“1-6”が入力されている

    記：
    上記の検証では先頭ページを省略したが、同様に“3-”のように最終ページを省略した場合もセクションで区切られた範囲3-4ページしか書き出されない。
    ユーザーガイドにはこのような仕様についての記載はない。

    検証したバージョンとOS：
    InDesign 18.3.0.50
    macOS 14.7.6

    Summary:
    When describing a page range that omits the first/final page, if there is a starting section in the range, the output results will remain in the page range within the section.

    Verification:
    Create an 8-page document (Figure 1).
    Set the start section on page 5.
    Export the PDF (and print as well) and enter “-6” in the page range (Figure 2).

    Result:
    A PDF of pages 5-6 is exported.
    When the PDF is exported again, the page range is set to “5-6” (Figure 3).

    Ideal result:
    should not be affected by the presence or absence of sections.
    A PDF… more

    •  

    •  

    •  

    13 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  ·  PDF Export  ·  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. [ID-4257175]Pages Panel: Buttons are hidden behind page number text when window is thin

    When the pages panel is as thin as possible, the buttons such as delete page are behind the text that says the number of pages. It is therefore not possible to click on the buttons. I always use this panel in a thin band, and it is now less practical.

    Version: InDesign 20.0.0

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    32 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

    14 comments  ·  UI/UI Scaling  ·  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
    FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    Fix for this issue is now available in the latest InDesign Release version 20.1 (Build 20.1.0.71), available via Creative Cloud Desktop application.

    
    

    Please update your InDesign application to this latest version to get the fix.

    
    

    --

    Adobe InDesign team

17. [ID-4259367]Error handling dialog shown while placing some TIFF/EPS files

    Error encountered while reading TIFF image. Image may be damaged or incompatible. Resave the image with different settings and try again.

    After I upgraded InDesign 19.5.1 to 19.5.2. Linked images do not show on the page in high quality display settings. I have about 60 linked indesign files into my one file. And I was afraid to upgrade to 20.1 and from Sonoma to Sequoia. Any fixes for this? Perhaps get rid of some of the links.. too many links? 60? 2 page document. Newer M2 MacBook Air.

    Edit: Update: Downgraded back to 19.5.1. Everything is working perfectly. Thanks Adobe for allowing very easy downgrades. EXCELLENT.

    Error encountered while reading TIFF image. Image may be damaged or incompatible. Resave the image with different settings and try again.

    After I upgraded InDesign 19.5.1 to 19.5.2. Linked images do not show on the page in high quality display settings. I have about 60 linked indesign files into my one file. And I was afraid to upgrade to 20.1 and from Sonoma to Sequoia. Any fixes for this? Perhaps get rid of some of the links.. too many links? 60? 2 page document. Newer M2 MacBook Air.

    Edit: Update: Downgraded back to 19.5.1. Everything is working perfectly. Thanks Adobe… more

    •  

    •  

    •  

    •  

    16 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

    9 comments  ·  Performance/Usability  ·  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
    Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    The fix of the issue is now available in the latest InDesign 2024(v19.5.3.144). We recommend you upgrade to the latest version for the fix.

    If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

    —

    Sanyam Talwar

18. OR Operator with Anchors Behaves Incorrectly

    InDesign GREP Bug Report: OR Operator with Anchors Behaves Incorrectly

    Summary
    InDesign's GREP engine does not handle the OR operator (|) correctly when used with anchors (^ and $). This behavior differs significantly from standard regex engines and produces unexpected, inconsistent results.

    Problem Description
    When using the OR operator with anchors in InDesign GREP, the anchors are interpreted with incorrect precedence, causing the pattern to behave differently than expected. This issue has been confirmed as a bug by Peter Kahrel, author of "GREP in InDesign."

    Test Cases and Results

    Test Case 1: ^ab|c
    Text: ab ac bc Expected (standard regex): Matches "ab" at line start AND "c" anywhere Actual InDesign result: Only matches "ab" at line start Issue: InDesign interprets as ^(ab|c) instead of (^ab)|c

    Test Case 2: ^a|bc
    Text: ab ac bc Expected (standard regex): Matches "a" at line start AND "bc" anywhere Actual InDesign result: Only matches "a" at line start Issue: Same precedence problem as Test Case 1

    Test Case 3: (^a)|bc
    Text: ab ac bc Expected (standard regex): Matches "a" at line start AND "bc" anywhere Actual InDesign result: Still only matches "a" at line start Issue: Even explicit grouping doesn't resolve the problem

    Test Case 4: (a$)|bc
    Text: ab ac bca Expected (standard regex): Matches "a" at line end AND "bc" anywhere Actual InDesign result: Only matches "bc" ($ anchor completely ignored) Issue: End-of-line anchor is ignored entirely

    Test Case 5: bc|(a$)
    Text: ab ac bca Expected (standard regex): Matches "bc" anywhere AND "a" at line end Actual InDesign result: Only matches "bc" ($ anchor ignored) Issue: End-of-line anchor ignored regardless of position

    Test Case 6: bc|a$
    Text: ab ac bca ac ab bc a Expected (standard regex): Matches "bc" anywhere AND "a" at line end Actual InDesign result: No matches at all Issue: Pattern completely fails when $ anchor is second in OR expression

    Impact
    * Users cannot rely on standard regex behavior for OR operations with anchors
    * Complex workarounds are required for simple pattern matching
    * Documentation doesn't warn users about this non-standard behavior
    * Patterns that work in other regex engines fail unexpectedly in InDesign

    Technical Details
    * InDesign Version: 20.3.1 x64

    Requested Fix
    Please fix the OR operator precedence to match standard regex behavior:
    1. ^ab|c should match "ab" at line start OR "c" anywhere
    2. (a$)|bc should match "a" at line end OR "bc" anywhere
    3. Explicit grouping should work as expected
    4. End-of-line anchors should not be ignored in OR expressions

    InDesign GREP Bug Report: OR Operator with Anchors Behaves Incorrectly

    Summary
    InDesign's GREP engine does not handle the OR operator (|) correctly when used with anchors (^ and $). This behavior differs significantly from standard regex engines and produces unexpected, inconsistent results.

    Problem Description
    When using the OR operator with anchors in InDesign GREP, the anchors are interpreted with incorrect precedence, causing the pattern to behave differently than expected. This issue has been confirmed as a bug by Peter Kahrel, author of "GREP in InDesign."

    Test Cases and Results

    Test Case 1: ^ab|c
    Text: ab ac bc Expected (standard regex):… 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

    2 comments  ·  Others  ·  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. [ID-4256474]InDesign 2025 removes all PDF export setting files with double-byte and accented characters from InDesign 2024

    During the installation of InDesign 2025, all .joboptions files with PDF export settings were removed, even in the older version 2024! This is absurd!

    41 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

    8 comments  ·  PDF Export  ·  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
    FIXED  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    The fix of the issue is now available in the latest InDesign 2025(v20.0.1.032). We recommend you upgrade to the latest version for the fix.

    If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

    —

    Adobe InDesign Team

20. Workspace is still resetting every document. Latest Update has not fixed this yet

    Workspace is resetting every time I open a new document. I received a notification from Adobe that this has been fixed. I've updated and it is not fixed.

    13 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  ·  UI/UI Scaling  ·  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
    Need More Info  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    We have released InDesign 2025(v20.2.0.036) with many bug fixes. We recommend you upgrade to the latest version (if you’re not already on it) as it is more robust.

    If you still face this issue even after updating, please send the following information to santalwa@adobe.com :

    • Reproducible Steps – What were you doing when the issue occurred?
    • Video recording of the issue?
    • Is(Are) the issue related to a specific document(s)/asset(s)? If yes, could you provide the document(s)/asset(s) to us? Please package the entire document (To package the document, choose File → Package…)

    —

    Adobe InDesign Team