1029 results found

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

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

   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

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

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

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

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

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

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

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

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

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

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

13. vertical alignment within a text box is ignoring the space taken up by a wrap object

    I'm on Adobe InDesign 20.3.1 on an M1 Max MacBook Pro currently running Sequoia 15.5, but I always keep my system and apps up to date within a day or two of an update being released.

    The text wrap isn't affecting the vertical centering of text box content in the way it should. The vertical alignment within the text box seems to be ignoring the space taken up by the wrapped object, leading to the content being centered within the entire text box rather than just the available space above the wrapped object.
    In the screenshot, you can see that the text box that overlaps with the wrapping object is centering to the entirety of the text box. A 2nd text box on the left is shortened to show where it SHOULD be aligning to. The warping object is on top of the text box, and the text box does not have "Ignore Text Wrap" checked. Any ideas on a fix?

    I'm on Adobe InDesign 20.3.1 on an M1 Max MacBook Pro currently running Sequoia 15.5, but I always keep my system and apps up to date within a day or two of an update being released.

    The text wrap isn't affecting the vertical centering of text box content in the way it should. The vertical alignment within the text box seems to be ignoring the space taken up by the wrapped object, leading to the content being centered within the entire text box rather than just the available space above the wrapped object.
    In the screenshot, you can see that… 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

14. MathML: Fehler der Bedienung sowie weitere Schrecklichkeiten

    MathML hat das Problem, dass, wenn man die Grundformel eingefügt hat, beim nächsten Mal im Editor keine mehr zur Verfügung steht. Problematisch ist das, wenn man den ersten Eintrag im Dokument gelöscht hat. Man sollte immer an die Grundformel kommen, auch wenn man tausendmal klickt, um es im übertragenen Sinn zu sagen. Außerdem ist die verwendete Schriftart des MathML fürchterlich ausgeführt: verschobene Ankerpunkte, ungenaue Kurven etc. Dazu kommt noch, dass die Zeichen am Rand teilweise beschnitten werden. All das ist im typografischen Sinn – unangemessen.

    Bezüglich der Kurvenführung sehen Sie sich als Beispielglyphe das y an! Ich habe einige fürchterliche Teile des y nochmals mit einigen Pfeilen an den zumindest auffälligsten Stellen hervorgehoben. Solche Schriftarten sollte man nicht im Traum für Designsoftware anbieten. Hunderte ähnliche Fehler habe ich Dutzenden Designern und Monotype gemeldet; und sie sind bis zu Nur-noch-online-Plattform dieses Konzerns auch verbessert worden. Durch die Onlinegier ist das jetzt anders und sie bieten ihren Schrott an, den ahnungslose Kunden kaufen. Diese Methode scheint uramerikanisch zu sein: Marktbeherrschung zwar, aber zunehmend schlechter werdende Qualität.

    MathML hat das Problem, dass, wenn man die Grundformel eingefügt hat, beim nächsten Mal im Editor keine mehr zur Verfügung steht. Problematisch ist das, wenn man den ersten Eintrag im Dokument gelöscht hat. Man sollte immer an die Grundformel kommen, auch wenn man tausendmal klickt, um es im übertragenen Sinn zu sagen. Außerdem ist die verwendete Schriftart des MathML fürchterlich ausgeführt: verschobene Ankerpunkte, ungenaue Kurven etc. Dazu kommt noch, dass die Zeichen am Rand teilweise beschnitten werden. All das ist im typografischen Sinn – unangemessen.

    Bezüglich der Kurvenführung sehen Sie sich als Beispielglyphe das y an! Ich habe einige fürchterliche… 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. 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

16. Interaction between Text Wrap, Optical Margin Alignment and Numbered List

    When a text frame with activated Optical Margin Alignment containing numbered list wraps around another text frame the numbering is incorrectly aligned. The affected numbers noticeably stick outside of the text frame and thus create unpleasant left margin. Only numbering on wrapped lines is affected, numbering below the wrap behaves as expected.

    Similarly, if the text frame is modified so as its border lays entirely outside of the area affected by wrapping offset, the optical alignment of the numbering behaves as expected. This at least provides some workaround.

    I am attaching a screenshot of the behaviour as well as a test file with described situations.

    When a text frame with activated Optical Margin Alignment containing numbered list wraps around another text frame the numbering is incorrectly aligned. The affected numbers noticeably stick outside of the text frame and thus create unpleasant left margin. Only numbering on wrapped lines is affected, numbering below the wrap behaves as expected.

    Similarly, if the text frame is modified so as its border lays entirely outside of the area affected by wrapping offset, the optical alignment of the numbering behaves as expected. This at least provides some workaround.

    I am attaching a screenshot of the behaviour as well as a… 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. 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

18. Title Case Is Not Actually Title Case

    I'm editing book with over 1,000 pages. I am selecting copy, changing case to Title Case, but it just capitalizes first letter in all words. There needs to be another case option. Title case needs to be setup so it makes a "title" of a book so words like "of" are not capitalized. New option can be called First Letter Caps, and Title case can be fixed to address words that should not be capitalized in a title of a book or headline.

    The Old Man and the Sea (Actual Title Case) The Old Man And The Sea(Not Title Case)

    I have been going to a website to copy and paste content so it will generate correct Title Case results. Total waste of time. Please fix this!

    I'm editing book with over 1,000 pages. I am selecting copy, changing case to Title Case, but it just capitalizes first letter in all words. There needs to be another case option. Title case needs to be setup so it makes a "title" of a book so words like "of" are not capitalized. New option can be called First Letter Caps, and Title case can be fixed to address words that should not be capitalized in a title of a book or headline.

    The Old Man and the Sea (Actual Title Case) The Old Man And The Sea(Not Title Case)

    … 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

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

    • 

    •  

    • 

    •  

    • 

    132 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

20. Unable to type letter "g"

    every time I type "g" in a textbox, the font automatically changes to a different paragraph style and the "g" does not type in the textbox

    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