1038 results found

1. no new tabulator stops before (left of) an existing one

   InDesign 21: After placing the first tab stop, I cannot place another one before it (= to the left of it). Positioning of new tab stops is only possible to the right of it. Moving a tab arrow in the tab palette deletes all tab stops on its right hand side.

   • 

   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

2. Cannot see text

   When using the Text tool, text is only visible when typing and disappears afterwards. I only know text is present through highlighting the text, however still the text is not visible (and I can only highlight text when it is off of the page). I checked layers and updated the application. All fonts are updated. I tried to change the font size, colour and checked through the effects.

   Error states: Overset text (1), although I already tried to adjust the size of the box and text as well as create a new text box.

   Edit: I can't see imported material either (images are invisible however detected). I have tried changing Display/GPU performance and updating the software; this did not work.

   When using the Text tool, text is only visible when typing and disappears afterwards. I only know text is present through highlighting the text, however still the text is not visible (and I can only highlight text when it is off of the page). I checked layers and updated the application. All fonts are updated. I tried to change the font size, colour and checked through the effects.

   Error states: Overset text (1), although I already tried to adjust the size of the box and text as well as create a new text box.

   Edit: I can't see imported material… 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

3. collapsed panels on the right side won't open

   version 21.0 ME
   collapsed panels on the right side don't always open when clicked on, it may work for a while but then stops until I reset my workspace, then it works for a while and then stops again.
   I tried creating a new workspace but still happens.
   The same thing happens to my coworker.

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

   Please send the following information to sharewithID@adobe.com :

   • Reproducible Steps – What were you doing when the issue occurred?
   • Video recording of the issue

   —

   Adobe InDesign Team

4. [ID-4272086]TAB indents are getting removed on dragging the left side

   Good morning, I updated InDesign to version 21 and I'm having problems with the tab stops on both PCs. In the tab settings, if I set three tab stops, for example, the first at 10 cm, the second at 20 cm, and the third at 30 cm, if I move the first one, the other two disappear.
   With the beta version, there were no problems. I tried resetting the preferences, but nothing. A technician connected and checked the problem. He said to report the bug.

   • 

   •  

   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

   14 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. We have been able to reproduce the issue, and it is currently under investigation.

   —

   Adobe InDesign Team

5. When importing tables through tagged text, formatting inexplicably and erratically lost; extra hard returns inserted

   1. Adobe InDesign 20.5
   2. Flow the attached .txt files (tagged text) into an InDesign file. you'll need paragraph styles "TABC", "TABH1", "TABTX", and "TAB" (the paragraph for the table). You'll also need table style "TAB" and a cell style "tabtx".
   3. The last cell in table 19.2 should be empty—no hard return. The the text in row 2, column 3 of table 19.4, "katab" should be italic.
   4. There's a hard return in the last cell of table 19.2; any text in cell R2C3 in table 19.4 is not ital (but note that the text in table 19.2 at R2C3 is italic as expected.
   5. See the attached tagged text and Word files as well as the attached screen shot.

   When importing tagged text, I am seeing some formatting—like italic—dropped, and I'm also seeing extra hard returns inserted in the last cell of the table. These problems seem to be intermittent and unpredictable. For example, in a cell with this text

   <CellStart:><ParaStyle:TAB_TX><cTypeface:Italic>katab<cTypeface:><CellEnd:>

   "katab" is not being italicized, but in a cell with this text

   <CellStart:><ParaStyle:TAB_TX><cTypeface:Italic>qəṭál<cTypeface:><CellEnd:>

   "qəṭál" is italicized just fine.

   If I copy and paste the "qəṭál" cell into the first file replacing the "katab" cell, "qəṭál" is not italicized. I've attached the tagged text and Word files for each.

   The other weird thing I'm seeing is a hard return inserted in an otherwise empty last cell in the table. You can see it in the table 19.4 file.

   If it helps, I can upload the InDesign template as well.

   1. Adobe InDesign 20.5
   2. Flow the attached .txt files (tagged text) into an InDesign file. you'll need paragraph styles "TABC", "TABH1", "TABTX", and "TAB" (the paragraph for the table). You'll also need table style "TAB" and a cell style "tabtx".
   3. The last cell in table 19.2 should be empty—no hard return. The the text in row 2, column 3 of table 19.4, "katab" should be italic.
   4. There's a hard return in the last cell of table 19.2; any text in cell R2C3 in table 19.4 is not ital (but note that the text in table 19.2 at… 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

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

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

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

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

   「検索と置換」で正規表現の検索テキストボックスに入力し、置換テキストボックスに検索テキストボックスからコピーした文字をペーストして、置き換えたい文字に修正する。
   マウスをテキストボックス外でクリックすると修正前の文字列に戻てしまう。
   ＜行った操作操作＞
   １．検索「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

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

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

12. Feature Requests: Table Cell Intersection Styling and Multi-Page Table Cell Support for Merged Cells

    Request 1: Multi-Page Table Cell Support for Merged Cells
    Current Problem:
    InDesign cannot break merged table cells across pages, creating significant limitations for complex hierarchical tables. When a merged cell spans more rows than can fit on a single page, the entire table becomes unviewable or requires manual workarounds.
    Real-World Scenario:
    • Level 1: A main category (e.g., "Strategic Goal") spans 30 rows
    • Level 2: 30 detailed items, each in individual rows
    • Current Issue: The merged cell cannot break across pages, making the table unusable
    Proposed Solution:
    Implement automatic cell threading for merged cells across page breaks, similar to Microsoft Word's functionality:
    • Allow merged cells to split naturally at page boundaries
    • Maintain visual continuity with repeated cell content or indicators
    • Preserve cell formatting and styles across page breaks
    • Optional: Add "Keep with next X rows" setting for better control
    Technical Benefits:
    • Maintains InDesign's superior table styling capabilities
    • Enables complex document structures without design compromises
    • Reduces manual workarounds and increases productivity
    • Aligns with user expectations from other professional document tools

    Request #2: Table Cell Intersection Styling
    Current Limitation:
    Table cells cannot have rounded corners or customized intersection points because cells share borders rather than having independent edges.
    Conceptual Innovation:
    Instead of trying to add "corner radius" to cells (which is geometrically impossible with shared borders), introduce Intersection Point Styling.
    Proposed Feature: "Intersection Styles"
    Similar to current Line Styles, add styling options for where cell borders meet:
    Intersection Style Options:
    • Round: Curved intersection points
    • Beveled: Angled corner cuts
    • Notched: Small decorative cuts
    • Custom: User-defined intersection shapes
    • Weighted: Different styles based on border thickness
    Implementation Details:
    Current: Line Style (solid, dashed, dotted, custom)
    Proposed: + Intersection Style (round, beveled, notched, custom)
    Technical Precedent:
    • SVG supports stroke-linejoin properties
    • CSS has similar capabilities with border-radius and border-collapse
    • Vector graphics software already handles line intersections
    Benefits:
    • Maintains table structure integrity
    • Provides design flexibility without breaking functionality
    • More logical than impossible "cell corner radius"
    • Expandable system for future intersection decorations

    Impact Statement:
    These improvements would:
    1. Eliminate major workflow barriers for complex document design
    2. Distinguish InDesign further from competitors by solving real problems
    3. Maintain InDesign's superiority in professional typography and layout
    4. Address frequent user requests without compromising existing functionality
    Both features leverage InDesign's existing strengths while addressing fundamental limitations that force users toward less capable alternatives for specific use cases.

    Request 1: Multi-Page Table Cell Support for Merged Cells
    Current Problem:
    InDesign cannot break merged table cells across pages, creating significant limitations for complex hierarchical tables. When a merged cell spans more rows than can fit on a single page, the entire table becomes unviewable or requires manual workarounds.
    Real-World Scenario:
    • Level 1: A main category (e.g., "Strategic Goal") spans 30 rows
    • Level 2: 30 detailed items, each in individual rows
    • Current Issue: The merged cell cannot break across pages, making the table unusable
    Proposed Solution:
    Implement automatic cell threading for merged cells across page breaks, similar… 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

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

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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. Strange Characters (e.g., "HNY6") Appear When Pressing Spacebar with Caps Lock On (macOS Sequoia 15.5)

    Title:
    Strange Characters (e.g., "HNY6") Appear When Pressing Spacebar with Caps Lock On (macOS Sequoia 15.5)

    Description:
    I’m experiencing a bug in Adobe InDesign (latest version) running on macOS Sequoia 15.5 using a MacBook Pro. When Caps Lock is on and I press the spacebar while typing, instead of inserting a space, InDesign types a string of random characters like “HNY6.”

    This issue happens consistently and seems isolated to InDesign. Other apps (like Notes or Pages) do not show this behavior. I’ve confirmed the problem still occurs after disabling third-party keyboard tools and checking input sources. It only happens when Caps Lock is engaged and I press spacebar.

    Please investigate and resolve this compatibility issue. It impacts workflow significantly when working with all-caps text.

    Title:
    Strange Characters (e.g., "HNY6") Appear When Pressing Spacebar with Caps Lock On (macOS Sequoia 15.5)

    Description:
    I’m experiencing a bug in Adobe InDesign (latest version) running on macOS Sequoia 15.5 using a MacBook Pro. When Caps Lock is on and I press the spacebar while typing, instead of inserting a space, InDesign types a string of random characters like “HNY6.”

    This issue happens consistently and seems isolated to InDesign. Other apps (like Notes or Pages) do not show this behavior. I’ve confirmed the problem still occurs after disabling third-party keyboard tools and checking input sources. It only happens when… 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

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

16. Find/Replace text (date) after using Convert Date to Text function

    I am trying to replace text in multiple stories throughout the document. Each story is formatted with text and tabs (not a table). The find/change uses the FIND/CHANGE>TEXT option. I am searching for "28 May 2025" to change it to "2 July 2025". When I search, find, find/change, and change all, the results append the page number in triplicate in front of the leading date digit. For example, page 9 (attached) is "0909092 July 2025" and page 42 is "4242422 July 2025". When I copied the text to include in this report (see attached), only date date is captured in the clipboard (2 July 20v25).

    The reason I was doing this is I wanted to change the date to a output date Text Variable. I had hoped text variables were part of find change: the find is available in GREP, but not in the Change To options.

    So, just prior to producing the error above, I added the Output Date in the position I wanted. I could not copy the variable and use it in the Change To field, so I used the Covert Variable to Text that one instance of the output date. I copied the text '2 July 2025", and used the basic Find/Change>Text intending to change "28 May 2025" to change it to "2 July 2025". That's when ID appends the six digits that are three pairs of the page number.

    Everything works as planned if I duplicate the original document, and repeating the process leaving out the Convert to Text option.

    Adobe InDesign 20.0 | MacOS Ventura 13.5.2

    I am trying to replace text in multiple stories throughout the document. Each story is formatted with text and tabs (not a table). The find/change uses the FIND/CHANGE>TEXT option. I am searching for "28 May 2025" to change it to "2 July 2025". When I search, find, find/change, and change all, the results append the page number in triplicate in front of the leading date digit. For example, page 9 (attached) is "0909092 July 2025" and page 42 is "4242422 July 2025". When I copied the text to include in this report (see attached), only date date is captured in… 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

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. Bug: tint remains when applying a different swatch

    Indesign 2025, v20.2, Windows 11
    Steps to reproduce:
    1. Have at leat two swatches in the swatches panel. The 1st with, for instance, 20% tint and the 2nd with 100%
    2. Type some text and select it, then apply the swatch with the 20% tint.
    3. Then apply the other swatch.
    Result: the text isn't display in the color of the 2nd swatch, because the tint is not changed to 100%

    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

19. Allsmall caps won't apply to text set to 'no language' in InDesign 20.4

    Per the title, with the latest update to 20.4, if text is set to 'no language', allsmall caps won't apply.

    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

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