1033 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

   • 

   •  

   •  

   • 

   • 

   133 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

   59 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

   •  

   • 

   •  

   •  

   •  

   • 

   408 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

   172 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

   351 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-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

5. [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

6. 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

7. Hyphenation zone settings override discretionary hyphen exclusivity

   Adobe InDesign Hyphenation Bug Report

   Summary

   Conflict between discretionary hyphen behavior and "After First / Before Last" hyphenation zone settings, where InDesign ignores discretionary hyphens that fall within the prohibited hyphenation zone.

   Product Information

   • Product: Adobe InDesign
   • Component: Text Composition / Hyphenation Engine
   • Feature Area: Automatic Hyphenation and Discretionary Hyphens

   Problem Description

   Expected Behavior

   According to Adobe's documentation, discretionary hyphens should have absolute priority over automatic hyphenation rules. Specifically:

   "Entering a discretionary hyphen in a word does guarantee that the word can be broken only where the discretionary hyphen appears."

   When a word contains a discretionary hyphen that falls within the "After First X Letters" or "Before Last X Letters" prohibited zone, InDesign should:
   1. Respect the discretionary hyphen's exclusivity (only break where discretionary hyphen appears)
   2. Refuse to break the word at all since the only allowed break point falls within the prohibited zone
   3. Not apply automatic hyphenation anywhere else in the word

   Actual Behavior

   InDesign ignores the discretionary hyphen when it falls within the prohibited hyphenation zone and applies automatic hyphenation rules instead, breaking the word at algorithmically-determined positions that fall outside the prohibited zone.

   Conflicting Features

   Feature 1: Document Hyphenation Preferences

   • Location: Paragraph Panel Menu > Hyphenation Settings
   • Setting: "After First [X] Letters / Before Last [X] Letters"
   • Purpose: Defines minimum character zones at word beginnings/endings where hyphenation should not occur
   • Example: With "After First 3 Letters / Before Last 3 Letters", the word "aromatic" may hyphenate as "aro-matic" but not "ar-omatic" or "aromat-ic"

   Feature 2: Discretionary Hyphens

   • Location: Type > Insert Special Character > Hyphens And Dashes > Discretionary Hyphen
   • Keyboard Shortcut: Ctrl+Shift+- (Windows) or Command+Shift+- (macOS)
   • Purpose: Manually specify the only allowable break point in a word
   • Expected Behavior: Word can only break at the discretionary hyphen location, regardless of other settings

   Steps to Reproduce

   1. Create a new InDesign document
   2. Set up hyphenation preferences:
      • Go to Paragraph Panel Menu > Hyphenation Settings
      • Enable "Hyphenate"
      • Set "After First [3] Letters"
      • Set "Before Last [3] Letters"
   3. Create a text frame with justified text
   4. Insert a word where a discretionary hyphen would fall within the 3-letter prohibited zones
      • Example: Insert discretionary hyphen in "example" as "ex•ample" (where • represents the discretionary hyphen)
      • This discretionary hyphen falls in the "Before Last 3 Letters" zone
   5. Force line break to require hyphenation of this word

   Expected Result

   Word should not hyphenate at all, since the only allowed break point (discretionary hyphen) falls within the prohibited zone.

   Actual Result

   InDesign ignores the discretionary hyphen and hyphenates the word using automatic rules at a different location (e.g., "exam-ple").

   Impact

   Severity: Medium to High

   • Typography Quality: Undermines precise typographic control
   • Workflow Disruption: Manual intervention required to fix each occurrence
   • Consistency Issues: Unpredictable behavior between discretionary and automatic hyphenation
   • Professional Publishing: Affects quality of professional publications where precise hyphenation control is critical

   User Groups Affected

   • Professional typesetters and designers
   • Book and magazine publishers
   • Technical documentation teams
   • Any users requiring precise hyphenation control

   Technical Analysis

   Root Cause

   The hyphenation engine appears to process the "After/Before Letters" rules after or independently of discretionary hyphen evaluation, rather than respecting the documented hierarchy where discretionary hyphens should override all other hyphenation rules.

   Proposed Solution

   Modify the hyphenation algorithm to:
   1. First check for discretionary hyphens in the word
   2. If discretionary hyphen found: Evaluate if it falls within prohibited zones
   3. If in prohibited zone: Do not hyphenate the word at all
   4. If outside prohibited zone: Use only the discretionary hyphen break point
   5. Only if no discretionary hyphen: Apply automatic hyphenation rules with zone restrictions

   Workarounds

   Current Workarounds (Inefficient)

   1. Manual intervention: Individually edit each problematic word break inserting discretiona hyphen at start of word to prevent it from breaking.
   2. Character Style with No Break: Apply No Break character formatting to words with problematic discretionary hyphens
   3. Adjust zone settings: Reduce "After/Before Letters" values (compromises typography for other words)
   4. Remove discretionary hyphens: Use only automatic hyphenation (loses manual control)

   Limitation of Workarounds

   All workarounds require manual identification and correction of each instance, making them impractical for large documents or automated workflows.

   Documentation References

   Adobe InDesign Help: Text Composition

   • URL: https://helpx.adobe.com/indesign/using/text-composition.html
   • Relevant Quote: "Entering a discretionary hyphen in a word does guarantee that the word can be broken only where the discretionary hyphen appears."

   Hyphenation Settings Documentation

   • After First / Before Last Letters: "Specify the minimum number of characters at the beginning or end of a word that can be broken by a hyphen."

   Additional Information

   Related Features That Work Correctly

   • Discretionary hyphens function properly when they fall outside the prohibited zones
   • "After/Before Letters" settings work correctly with automatic hyphenation
   • No Break character formatting consistently prevents hyphenation

   Test Case Suggestions

   Adobe should test various combinations of:
   - Different "After/Before Letters" values (2, 3, 4, 5 characters)
   - Discretionary hyphens at different positions within words
   - Various word lengths and compositions
   - Different paragraph composers (Adobe Paragraph Composer vs. Single-line Composer)

   ---

   Request: Please prioritize this bug fix as it affects fundamental typographic control and contradicts documented behavior. The fix should ensure discretionary hyphens always take absolute precedence over automatic hyphenation rules, including zone restrictions.

   Adobe InDesign Hyphenation Bug Report

   Summary

   Conflict between discretionary hyphen behavior and "After First / Before Last" hyphenation zone settings, where InDesign ignores discretionary hyphens that fall within the prohibited hyphenation zone.

   Product Information

   • Product: Adobe InDesign
   • Component: Text Composition / Hyphenation Engine
   • Feature Area: Automatic Hyphenation and Discretionary Hyphens

   Problem Description

   Expected Behavior

   According to Adobe's documentation, discretionary hyphens should have absolute priority over automatic hyphenation rules. Specifically:

   "Entering a discretionary hyphen in a word does guarantee that the word can be broken only where the discretionary hyphen appears."

   When a word contains a discretionary hyphen… more

   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

   0 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

8. The first letter typed in is English even when my system is set to Hebrew

   I'm using Indesign 20.5 on an Intel Mac Pro running Mac OS Sequoia 15.6.
   Here are the steps to reproduce the issue:
   1. Insert a new text box and enter some English text.
   2. Select the text
   3. Change the keyboard input to Hebrew.
   4. Start typing in Hebrew.

   The resulting text will be an English letter (corresponding to the Hebrew letter typed in) followed by the correct Hebrew letters typed.
   Two things to note:
   1. You must select all the text in the text box for this issue to take place.
   2. For some reason Adobe fonts are immune to this issue

   I'm using Indesign 20.5 on an Intel Mac Pro running Mac OS Sequoia 15.6.
   Here are the steps to reproduce the issue:
   1. Insert a new text box and enter some English text.
   2. Select the text
   3. Change the keyboard input to Hebrew.
   4. Start typing in Hebrew.

   The resulting text will be an English letter (corresponding to the Hebrew letter typed in) followed by the correct Hebrew letters typed.
   Two things to note:
   1. You must select all the text in the text box for this issue to take place.
   2. For some reason Adobe fonts are immune… more

   2 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

9. [ID-4257735]One Frame Grid Remains Unchanged When Modifying Multiple Selected Frame Grids

   InDesign CS4 (v6) and Later

   When changing the “Number of Characters per Line” or “Number of Lines” for multiple selected frame grids, one of the frame grids always fails to update. This bug, first observed in CS4 (v6), remains unresolved.

   Steps to Reproduce:
   1. Select multiple frame grids.
   2. Go to the menu and choose “Object > Frame Grid Options...”
   3. Modify the “Number of Characters per Line” or “Number of Lines” settings.

   Result: Changes are not reflected in one of the frame grids. It appears that the frame grid with the smallest object ID does not get updated.

   Expected Result: All selected frame grids should reflect the changes.

   Bug Recording
   https://mega.nz/file/k5BVTIDa#IQAzAETDuxzmmmDDfdDDVcDTb302hy0sCR4IJcnVllc

   ---

   選択した複数のフレームグリッドを設定変更すると常に1つだけ変更されない。

   InDesign CS4（v6）以降

   選択された複数のフレームグリッドの「行文字数」「行数」を変更すると、常に1つだけ変更が反映されません。このバグはCS4（v6）で発生し、現在も直っていません。

   再現手順
   1. 複数のフレームグリッドを選択
   2. メニュー「オブジェクト > フレームグリッド設定...」を選択
   3. フレームグリッド設定で「行文字数」「行数」を変更する

   結果：
   1つだけ変更が反映されない。オブジェクトIDが最も小さいフレームグリッドだけ変更されないようです。

   期待する結果：
   選択されたすべてのフレームグリッドに変更が反映される。

   InDesign CS4 (v6) and Later

   When changing the “Number of Characters per Line” or “Number of Lines” for multiple selected frame grids, one of the frame grids always fails to update. This bug, first observed in CS4 (v6), remains unresolved.

   Steps to Reproduce:
   1. Select multiple frame grids.
   2. Go to the menu and choose “Object > Frame Grid Options...”
   3. Modify the “Number of Characters per Line” or “Number of Lines” settings.

   Result: Changes are not reflected in one of the frame grids. It appears that the frame grid with the smallest object ID does not get… more

   28 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  ·  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,

   Thank you for reporting the issue. It is currently under investigation. 

   —

   Adobe InDesign Team

10. Bizarre issue: footnote appearing in middle of text frame

    Never seen this one before! Changing some text to a style that uses split columns caused one of the footnotes in the text frame to jump to ABOVE the styled text. I can't even understand how this is possible given the logic of the software. See screenshot. I would like my footnotes to stay at the foot of the frame, please.

    •  

    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  ·  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

11. Critical Bug Report: InDesign 2024 ME ExtendScript Fails to Set RTL Properties

    We are experiencing a severe and persistent bug in Adobe InDesign 2024 Middle Eastern Edition (ME) where basic Right-to-Left (RTL) text properties cannot be set via ExtendScript, even though the same actions work manually through the UI.

    This issue effectively prevents any automation or workflow scripting for Farsi/Arabic content, despite using the designated ME version.

    1. Environment & Problem Summary Detail Value InDesign Version 2024 (Middle Eastern/ME Edition) Issue Scripting fails to set paragraphDirection, storyDirection, and justification to RTL values. Root Cause The ExtendScript Object Model exhibits a fundamental contradiction (a "Catch-22") when trying to set RTL properties.

    صادر کردن به «کاربرگ‌نگار»
    The core problem is that the application does not accept either of the two standard methods for setting an enumerated property: the string name or the numeric ID.

    1. Technical Breakdown and Error Logs The script attempts to set the properties to their RTL values (e.g., Farsi/RTL). We have confirmed the official numeric values for these properties:

    RIGHTTOLEFT_DIRECTION = 1920290924

    RIGHT_ALIGNMENT = 1852796515 (for justification workaround)

    WORLDREADYPARAGRAPHER = 1969449826

    The following errors were logged when attempting to apply the settings:

    A. Failure to Set Justification (Alignment)
    The script attempted to use the numeric value for Right Alignment as a workaround, but was rejected.

    Property Targeted: basicParagraphStyle.justification

    Value Used: 1852796515 (Right Alignment numeric value)

    Error Received: Script Alert: Invalid value for set property 'justification'. Expected Justification enumerator, but received 1852796515.

    Conclusion: The application refuses the numeric ID for justification, demanding the non-working Enum name (ParagraphAlignment.RIGHT_ALIGN).

    B. Failure to Set Paragraph Direction (The Core Issue)
    Previous tests showed that when attempting to set paragraphDirection using the numeric value, a similar error occurred:

    Property Targeted: basicParagraphStyle.paragraphDirection

    Value Used: 1920290924 (RTL Direction numeric value)

    Error Received (from earlier test): Invalid value for set property 'paragraphDirection'. Expected ParagraphDirectionOptions enumerator, but received 1920290924.

    Conclusion: The application insists on the Enum name (ParagraphDirectionOptions.RIGHTTOLEFT_DIRECTION) but simultaneously fails to recognize or accept that Enum when used in the script.

    C. Failure to Set Composer
    In earlier tests, even fundamental properties like the composer failed, suggesting a deep configuration issue:

    Property Targeted: basicParagraphStyle.composer

    Error Received (from earlier test): TextComposer is undefined

    Conclusion: This confirms a failure to recognize even basic object names for text engines.

    1. Final Conclusion and Call to Action The consistent failure across multiple RTL-specific properties, coupled with the application's rejection of both standard methods (Enums and numeric IDs), points to a critical bug in the ExtendScript API implementation of the InDesign 2024 ME edition.

    Action Required:

    Please investigate the internal mechanism that handles the conversion of Enums/Numeric IDs for RTL properties (specifically paragraphDirection, storyDirection, and justification) in the ExtendScript Object Model for InDesign ME versions.

    The bug must be patched to ensure that these properties can be reliably set using either the documented Enum names or their corresponding numeric IDs.

    This fix is essential for any developer relying on automation for Middle Eastern publishing workflows. Thank you for your urgent attention to this matter.

    We are experiencing a severe and persistent bug in Adobe InDesign 2024 Middle Eastern Edition (ME) where basic Right-to-Left (RTL) text properties cannot be set via ExtendScript, even though the same actions work manually through the UI.

    This issue effectively prevents any automation or workflow scripting for Farsi/Arabic content, despite using the designated ME version.

    1. Environment & Problem Summary Detail Value InDesign Version 2024 (Middle Eastern/ME Edition) Issue Scripting fails to set paragraphDirection, storyDirection, and justification to RTL values. Root Cause The ExtendScript Object Model exhibits a fundamental contradiction (a "Catch-22") when trying to set RTL properties.

    صادر کردن به… 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  ·  Text/Story/Table  ·  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

    Submit Rating

12. unicode devnagiri font text error in hindi text in indesign 2025, the worst /buggy indesign version

    in the newer version of indesign devnagiri font glyps are showing 0 like thing before maatra, please check screenshot, in indesign 2023 it is showing ok, there are many such bugs in indesign 2025, I think no improvement is there in this version of indesign

    •  

    •  

    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  ·  Text/Story/Table  ·  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

    Submit Rating

13. Variable Fonts in inDesign show different hinting results when compared to other environments

    InDesign v20.3.1 x64, Windows 11

    It appears that inDesign is maybe not able to correctly variate CVT values, causing unexpected hinting results. It seems as though CVT values that are used depend on the variable font’s default style/source. A possible way to recreate the issue: Compare the same variable font built in the same way but with a different default source set for each. If Hair (weight: 100) is set as the default, then it will appear in inDesign as if the Regular (weight: 400) is maybe using the CVT values of the Hair. This is shown in the first screenshot. It is not possible to recreate this issue in another environment such as Chrome. You would expect the choice of default style to not have any effect on the hinting result.

    Also attached is a screenshot that looks at the difference between a static and variable version of a Windows font: Segoe UI. Although this example is less valuable as it does not show as stark of a visual difference as the first screenshot and the static and variable versions are not exact matches, it stands to show a difference in variable font hinting that I found difficult to recreate in other environments outside of inDesign, possibly alluding to inDesign doing something unique with how it handles hinting in variable fonts.

    The screenshot examples use 18pt size text.

    InDesign v20.3.1 x64, Windows 11

    It appears that inDesign is maybe not able to correctly variate CVT values, causing unexpected hinting results. It seems as though CVT values that are used depend on the variable font’s default style/source. A possible way to recreate the issue: Compare the same variable font built in the same way but with a different default source set for each. If Hair (weight: 100) is set as the default, then it will appear in inDesign as if the Regular (weight: 400) is maybe using the CVT values of the Hair. This is shown in the first… 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  ·  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. BUG Track Changes

    Track changes leaving the cyan blue background even when switched off and greyed out for accepting changes.

    have tried switching track changes on

    oh yes i've switched it off and on again :)

    Version: ID (Beta) 20.6 x64 CI #60e4896

    •  

    •  

    •  

    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  ·  Text/Story/Table  ·  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

    Submit Rating

15. 検索と置換で置換文字列のテキストボックスに入力した文字が勝手に変わる

    「検索と置換」で正規表現の検索テキストボックスに入力し、置換テキストボックスに検索テキストボックスからコピーした文字をペーストして、置き換えたい文字に修正する。
    マウスをテキストボックス外でクリックすると修正前の文字列に戻てしまう。
    ＜行った操作操作＞
    １．検索「Taro: 」と入力
    ２．「Taro: 」をコピーして置換のテキストボックスにペースト
    ３．置換で「Taro: 」を「taro:\t~(」に修正
    ４．ポインターをテキストボックスから外し、クリックすると「Taro: 」に戻る。
    文字列が戻るだけで、実行結果は指定した通りになります。
    この現象が発生する確率は10％程度です。
    OS:Win11Pro
    Indesign:ver.20.5

    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  ·  Text/Story/Table  ·  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

    Submit Rating

16. Highlighting text and trying to change font or color of font is not working.

    Highlighting text and trying to change font or color of font is not working.

    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

    1 comment  ·  Text/Story/Table  ·  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

    Submit Rating

17. Bug: Wrong centered text justification in round text frames

    Center-aligned text in round text frames is misaligned, i.e. too far to the left. Please see screenshots for all details.
    As soon as you convert the frame to a rectangular one, text is aligned to center correctly.
    This is simply a calculation bug which should be fixed now finally - it persists for years already.

    •  

    •  

    •  

    2 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  ·  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

18. [ID-4263586] Adobe InDesign 2025 text justify buttons issue

    In the latest update of InDesign 2025 (as of writing this), there is a problem with the text justification buttons in the toolbar.

    Previously, you could click these buttons and then just keep typing into your currently active text frame, which is what one would expect from previous versions of InDesign.

    With the latest update, keyboard focus instead shifts over to these buttons, taking focus away from the text frame and your current text cursor position.
    This is completely useless, and makes it more difficult than it should be to, say, change the justification at a certain line of text and then keep typing or navigating the text in the frame.

    Would appreciate a fix for this, as it is causing severe interruptions to my workflow, and the feature/bug benefits no one.

    In the latest update of InDesign 2025 (as of writing this), there is a problem with the text justification buttons in the toolbar.

    Previously, you could click these buttons and then just keep typing into your currently active text frame, which is what one would expect from previous versions of InDesign.

    With the latest update, keyboard focus instead shifts over to these buttons, taking focus away from the text frame and your current text cursor position.
    This is completely useless, and makes it more difficult than it should be to, say, change the justification at a certain line of text… more

    •  

    2 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
    Under Review  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    We're reviewing this issue.

    
    

    --

    Adobe InDesign team

19. InDesign Strips Formatting When Pasting Text from Google Docs

    Description:
    When copying formatted text from Google Docs and pasting it directly into Adobe InDesign, all formatting (such as bold, italics, font size, and links) is lost. However, if the same text is first pasted into Microsoft Word or TextEdit, the formatting is preserved and can then be successfully pasted into InDesign. This suggests the issue is specific to InDesign’s handling of clipboard data from Google Docs. As a workaround, I currently have to use an intermediate application like Word, which slows down my workflow.

    Steps to Reproduce:

    • Copy any formatted text from Google Docs (e.g., bold, italic, links).

    • Paste directly into InDesign text frame.

    • Observe that all formatting is lost.

    • Paste the same text into Word or TextEdit — formatting is preserved.

    • Copy from Word/TextEdit and paste into InDesign — formatting is preserved.

    Expected Result:
    InDesign should retain formatting when pasting directly from Google Docs, just like it does when pasting from Word or TextEdit.

    Description:
    When copying formatted text from Google Docs and pasting it directly into Adobe InDesign, all formatting (such as bold, italics, font size, and links) is lost. However, if the same text is first pasted into Microsoft Word or TextEdit, the formatting is preserved and can then be successfully pasted into InDesign. This suggests the issue is specific to InDesign’s handling of clipboard data from Google Docs. As a workaround, I currently have to use an intermediate application like Word, which slows down my workflow.

    Steps to Reproduce:

    • Copy any formatted text from Google Docs (e.g., bold, italic, links).

    • Paste… more

    2 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  ·  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

20. Generating Index Problem v20.5

    Generating INDEX gives a blank text frame with only a title INDEX. What's going on?
    Never had this problem in previous versions.

    •  

    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  ·  Text/Story/Table  ·  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

    Submit Rating