1045 results found

1. Outlining Texts when grouped

   For exporting print PDFs i often have to convert all texts into paths. That does not work if a Text is grouped with any objekt.
   I hope for an option to convert all texts into paths, even if they are grouped with other objects.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

19. Not able to set default font when it comes from Adobe Fonts library

    Purista font family is installed but when I try tu pick it from menu as default font (in type panel or top app menu) it is visible in brackets with name changed - as a missing font.

    When I create a document it is still missing (screenshot _31). Then I have to reactivate adobe fonts by turning off Adobe fonts for a while (screen _32) and after it it works like it should (screen _33).
    Plase help with this issue.

    InDesign 20.3.1 x64
    Windows 11 Pro 24H2 26100.3476

    •  

    •  

    •  

    •  

    •  

    •  

    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. Some Cyrillic RTF files exported from Indesign are broken if a non-breakable space was used

    Indesign 20.3.1 x64 release.

    Attached is the Indesign file. Both frames are identical, except for the topmost has one non-breaking space and the bottommost has a regular space instead. The export from the top frame produces the buggy RTF (a screenshot of the glitch location is attached), while the bottom one is ok. If we put any non-breaking space there - it will fail as well.
    The bug was reported as font-dependent as well, i.e. the text set in Arial may have the bug while the text set in Minion Pro may not have it.

    •  

    • 

    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