42 results found

1. [ID-4260027] “Change Case” option does not refresh when opening saved search

   “Change Case” option does not refresh when opening saved search
   When a “Change Case” option is set on the GREP tab of the Find/Change dialog, it remains active until it is manually cleared or InDesign is restarted. This is a problem since it means that saved searches are producing unexpected results. Other options in the “change format” refresh as expected, so this appears to be a bug. It is especially problematic when running a chain of GREP searches because incorrect capitalization can result in numerous errors.

   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

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

2. [ID-4258070]Disappearing Punctuation Marks in Hebrew RTL Justified Text in Exported PDF

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

   Bug Description

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

   Technical Context

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

   Affected Punctuation Marks

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

   Specific Behavior in RTL Context

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

   Known Workarounds and Their Limitations

   1. Legacy Composition Engine Option:

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

   2. Temporary Layout Workaround:

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

   Technical Impact

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

   Priority Level

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

   Steps to Reproduce

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

   Technical Investigation Request

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

   Request

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

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

   Bug Description

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

   Technical Context

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

   Affected Punctuation Marks

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

   Specific Behavior in RTL Context

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

   •  

   • 

   •  

   •  

   •  

   • 

   401 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

   165 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

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

   —

   Adobe InDesign Team

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

   InDesign version: v20 (both Mac & PC)

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

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

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

   InDesign version: v20 (both Mac & PC)

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

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

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

   •  

   •  

   •  

   221 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   53 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

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

   —

   Adobe InDesign Team

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

   InDesign CS4 (v6) and Later

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

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

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

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

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

   ---

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

   InDesign CS4（v6）以降

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

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

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

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

   InDesign CS4 (v6) and Later

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

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

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

   28 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

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

   —

   Adobe InDesign Team

5. Incorrect ligatures in InDesign 2024

   In Indesign 19.0.1, ligatures are replaced incorrectly in German. Comparing these with the same document in 18.5.1, where they appear correct, this appears to be a bug in the new version. One screenshot is from INDD 2023 and the other from INDD 2024.

   •  

   •  

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

   The issue is currently under investigation.

   —

   Adobe InDesign Team

6. When adding a list to a Right to Left Paragraph, tab leader disappers

   1. InDesign (Middle East) 18.1.0.51

   2. In a Right to Left Text Frame type a few words in a Right to Left Paragraph direction, following by tab with a period leader definition and then type a any any number so you will get dots between the last word and number (like in TOC). See in the attached image. Selceet one of the list options (numbering or bullets) to see the tab leader disaapers.

   3. Numbers or Bullets should be added at the begining without change the rest of the text.

   4. The Tab leader disappers (see attached image)

   An ID prepared documnet can be d/l here:
   https://www.dropbox.com/s/dnrclcb4369wloa/Bullets-Leader-Bug.indd?dl=0

   1. InDesign (Middle East) 18.1.0.51

   2. In a Right to Left Text Frame type a few words in a Right to Left Paragraph direction, following by tab with a period leader definition and then type a any any number so you will get dots between the last word and number (like in TOC). See in the attached image. Selceet one of the list options (numbering or bullets) to see the tab leader disaapers.

   3. Numbers or Bullets should be added at the begining without change the rest of the text.

   4. The Tab leader disappers (see attached image)

   An ID prepared documnet can be… 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
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

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

   —
   Adobe InDesign team

7. PDF/X-1a運用において、危険度が高い「画像の配置方法」を発見しましたので報告させていただきます。

   Indesign （15.1.3）（16.4）（17.3）などで以下の現象を確認できます。
   表を作成し、「セルをグラフィックセルに変換」という機能を使用せずに、空のままのセル内に画像を配置します。
   配置方法は、何も選択していない状態で「ファイル」、「配置」、画像を選択して「開く」、配置先のセルをクリックといったものです。
   この配置方法でドキュメントを作成し、「プリント」より出力して確認したところ何の問題もありません。
   印刷会社へ渡すためのPDF/X-1aを「書き出し」より出力します。
   期待する結果としては、「プリント」からの出力結果と同等のPDFが作成されることです。
   実結果は、Illustratorのドロップシャドウが黒ベタに、同ぼかし効果が無効に、Photoshopのレイヤマスクが黒ベタになったPDFが作成されてしまいます。
   以上です。

   •  

   •  

   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

   0 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

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

   —

   Adobe InDesign Team

8. WorldReady settings go missing in [Basic Paragraph] style

   Adobe InDesign (ME) 2021, 2020, CC 2019, ..., CS6
   macOS and Windows

   InDesign's WorldReady settings (Paragraph Direction, Kashidas, etc.) are being stripped from a document's [No Paragraph Style] style when opened on a machine with a missing 3rd-party plug-in (like Em Software's InCatalog). This appears to happen with any 3rd-party plug-in that adds a text attribute with a prefix that's lower than the WorldReady plug-in's prefix. While the following steps use the Middle Eastern app (English Arabic), where there's a UI to see the style's empty/blank WorldReady entries, we've confirmed that this problem affects all app variants (including English (Roman)).

   To reproduce:
   1. Install ME version of InDesign 2021 (English Arabic).
   2. Install Em Software's InCatalog plug-in (http://emsoftware.com/products/emcatalog/ ) or any plug-in that adds a text attribute with a prefix ID below that of WorldReady's 0x50f00. (The SDK's BasicTextAdornment sample will work if its kBscTAPrefixNumber is changed to something like 0x43a00.)
   3. Restart InDesign while holding down Shift-Control-Option/Alt (to ensure the session workspace's [Basic Paragraph] style is rebuilt to include the new plug-in's text attribute).
   4. Create a new document and add a text frame containing a few paragraphs using the [Basic Paragraph] style. This text should compose as right-to-left (the ME version's default direction, as specified by WorldReady's kParagraphDirAttrBoss). Create a numbered list, since that's a great way to see the problem.
   5. Save the document.
   6. Quit InDesign.
   7. Remove InCatalog (or whatever plug-in was installed in step 2).
   8. Restart InDesign.
   9. Open the document that was saved in step 5.

   Alternatively:
   1. Install ME version of InDesign 2021 (English Arabic).
   2. Restart InDesign while holding down Shift-Control-Option/Alt (to ensure a clean session workspace)
   3. Open the attached SavedWithInCat(2021ME).indd file. (Well, UserVoice won't let me upload it. Ask & I can send directly.)

   Notice that the text frame in the opened document incorrectly flows left-to-right and the numbered list's numbers wrongly show on the left rather than the right. Edit the [Basic Paragraph] style and note that the WorldReady settings in the Middle East Character Formats and Indents and Spacing panels are blank/empty. (See attached before-after screenshots.) One would expect a style to survive intact even when opened on a machine with a missing 3rd-party plug-in, but instead some of its settings may be at risk of being lost.

   We've used WorldReady as the victim here, but this problem affects any plug-in, Adobe or 3rd party, that adds a text attribute with a prefix that's higher than the missing plug-in's prefix (such as Em Software's InData).

   Details: We've isolated what looks like a long-standing problem (bug?) with the SDK's AttributeBossList::CopyInto(), where it stops the copy when it encounters an attribute whose plug-in is missing. Instead, the copy should continue after the missing plug-in's entry order to produce a complete list of non-missing attributes. Copies produced by AttributeBossList's Duplicate(), ApplyAttributes(), and its copy-constructor are all affected.

   Adobe InDesign (ME) 2021, 2020, CC 2019, ..., CS6
   macOS and Windows

   InDesign's WorldReady settings (Paragraph Direction, Kashidas, etc.) are being stripped from a document's [No Paragraph Style] style when opened on a machine with a missing 3rd-party plug-in (like Em Software's InCatalog). This appears to happen with any 3rd-party plug-in that adds a text attribute with a prefix that's lower than the WorldReady plug-in's prefix. While the following steps use the Middle Eastern app (English Arabic), where there's a UI to see the style's empty/blank WorldReady entries, we've confirmed that this problem affects all app variants (including English (Roman)).

   … more

   •  

   •  

   •  

   •  

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   Thanks for reporting this issue.
   We’ll review this shortly.

   —
   Adobe InDesign team

9. [ID-4261011] In Find/Change, search for font style (eg "Book") incorrectly selects "Regular" style text, even if "Book" style isn't present

   In InDesign 2021 (the latest version both on Mac and Windows), I add a text frame and fill it with placeholder text which is set, by default, to Minion Pro - Regular.
   Then I go to the find-change dialog box and set 'find format > basic character format > font style' to Book.
   And guess what happens when I hit the ‘find next’ button? It selects all the ‘regular text. (The document has no text with the 'book' font style applied!)
   Selecting another style — e.g. Bold, Italic, etc. — results, as expected, in the 'cannot find match' alert.
   Looks like a bug to me!
   The same problem occurs with GREP search as well.
   Also, other users reported me that it happens in CS6, CC 2017, 2019 and 2020.

   In InDesign 2021 (the latest version both on Mac and Windows), I add a text frame and fill it with placeholder text which is set, by default, to Minion Pro - Regular.
   Then I go to the find-change dialog box and set 'find format > basic character format > font style' to Book.
   And guess what happens when I hit the ‘find next’ button? It selects all the ‘regular text. (The document has no text with the 'book' font style applied!)
   Selecting another style — e.g. Bold, Italic, etc. — results, as expected, in the 'cannot find match' alert.
   Looks… more

   •  

   13 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Text/Story/Table  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  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

10. GREP search failed to match all text in a story

    We use to be able to search all text in a story by using this (?s).+ code. It’s working fine in CS6. But in CC2019, 2020, and 2021 on both Mac and Windows it will fail to select all text in the story if there is more than ~ 50000 character. Only the first ~ 50000 will be selected.

    This might be related to an old bug that was introduced in 14.0.2 that was fixed in 14.0.3.

    Steps to Reproduce:
    1. Create a document with one story containing more than 50000 characters
    2. Do a GREP Find using (?s).+

    A similar issues when trying to use \X+ to select all text in a story. Only some portions of the text over multiple of ~ 50000 text will be selected.

    We use to be able to search all text in a story by using this (?s).+ code. It’s working fine in CS6. But in CC2019, 2020, and 2021 on both Mac and Windows it will fail to select all text in the story if there is more than ~ 50000 character. Only the first ~ 50000 will be selected.

    This might be related to an old bug that was introduced in 14.0.2 that was fixed in 14.0.3.

    Steps to Reproduce:
    1. Create a document with one story containing more than 50000 characters
    2. Do a GREP Find using (?s).+

    A… more

    17 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue

    -InDesign Team

11. [ID-4206781]Text wrapping has changed to before 2019 use textFrame based indent

    To place a graphicItem with text wrap, it is not an object-based indent like 2020, but a text frame-based indent before 2019.

    1 Version
    16.0.1(macOS10.14/10.15.6)

    2 Steps to reproduce the issues
    1. Make TextFrame. To places graphicItem above the textFrame and set text wrap.
    2. The indent set in the textFrame does not take effect for the object for which wrap text is set like before 2019.

    3 Expected result
    Indent set in the textFrame does take effect for the object for which wrap text is set like 2020.
    Please refer below Community article.
    https://community.adobe.com/t5/indesignフォーラム/indesign2020ではできていた回り込み時のインデント設定の維持が2021ではなくなっている/m-p/11677071

    4 Actual result
    The indent set in the textFrame does not take effect for the object for which text wrap is set like before 2019.

    To place a graphicItem with text wrap, it is not an object-based indent like 2020, but a text frame-based indent before 2019.

    1 Version
    16.0.1(macOS10.14/10.15.6)

    2 Steps to reproduce the issues
    1. Make TextFrame. To places graphicItem above the textFrame and set text wrap.
    2. The indent set in the textFrame does not take effect for the object for which wrap text is set like before 2019.

    3 Expected result
    Indent set in the textFrame does take effect for the object for which wrap text is set like 2020.
    Please refer below Community article.
    https://community.adobe.com/t5/indesignフォーラム/indesign2020ではできていた回り込み時のインデント設定の維持が2021ではなくなっている/m-p/11677071

    4 Actual result
    The indent… more

    •  

    •  

    95 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

    21 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  ·  amaarora responded

    Thanks for reporting. We will review it

    -InDesign Team

12. BUG (since CS6!): Nonbreaking Space (^S) Issue with World-Ready-Composer

    Issue:
    When using the ›World-Ready Composer‹, the character ›Nonbreaking Space‹ (^S) behaves exactly like the character ›Nonbreaking Space (Fixed Width)‹ (^s); i.e.: in justified paragraphs, its width does not adjust (like regular spaces do), but it is fixed and unchanging.
    This only occurs with the ›Adobe World-Ready Composer‹ (both ›Paragraph‹ and ›Single-line‹) and not with the regular ›Adobe Composer‹ (neither ›Paragraph‹ nor ›Single-line‹).
    It is not related to the font used, it has been tested with many different fonts.

    1. Versions with this bug, tested and confirmed by myself or colleagues:
       InDesign (Standard Version) CS6, CC2015.0
       InDesign (Middle Eastern Version) CC2020 (15.1.2), CC2021 (16.0)
       I suppose it occurs in all versions since CS6 (when the ›World-Ready Composer‹ was first introduced, afaik)!

    2. Steps to reproduce this issue
       Enter a few lines of text and insert the character ›Nonbreaking Space‹ somewhere. Choose any of the ›Justify‹ paragraph styles and select the ›World-Ready Composer‹. Switch to the regular ›Adobe Composer‹ with the same setup and compare the result.

    3. Expected Result:
       The ›Nonbreaking Space‹ should adjust its width just like any other of the regular spaces.

    4. Actual Result:
       The ›Nonbreaking Space‹ does not adjust its width.

    5. Example as Screenshot attached.
       (Menu is in German: ›Globaler Adobe-Absatzsetzer‹ = ›Adobe World-Ready Composer‹; ›Adobe-Absatzsetzer‹ = ›Adobe Composer‹)

    As far as I know, this issue has been reported only once before (https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/39403822-non-breaking-space-is-smaller-than-regular-space-w). But in this report, it is stated incorrectly that the Nonbreaking Space would be smaller than a regular space. It can, in fact, be larger as well (e.g. in a tight line with regular spaces smaller than their 100% optimum). The real nature of the issue is that it does not vary its size.

    PLEASE FIX ASAP!
    Thanks

    Issue:
    When using the ›World-Ready Composer‹, the character ›Nonbreaking Space‹ (^S) behaves exactly like the character ›Nonbreaking Space (Fixed Width)‹ (^s); i.e.: in justified paragraphs, its width does not adjust (like regular spaces do), but it is fixed and unchanging.
    This only occurs with the ›Adobe World-Ready Composer‹ (both ›Paragraph‹ and ›Single-line‹) and not with the regular ›Adobe Composer‹ (neither ›Paragraph‹ nor ›Single-line‹).
    It is not related to the font used, it has been tested with many different fonts.

    1. Versions with this bug, tested and confirmed by myself or colleagues:
       InDesign (Standard Version) CS6, CC2015.0
       InDesign (Middle Eastern Version) CC2020… 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

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

    Thanks for reporting. We will review the issue

    -InDesign Team

13. GREP position marker "^" = Beginning of Paragraph (not beginning of a new line after a forced line break)

    Dear Support,

    with the GREP position marker "^" for "Beginning of Paragraph", the GREP-search should consider the position of the beginning of a paragraph.
    But this marker does not only recognize the beginning of a paragraph, but also the beginning of a new line after a forced line break (SHIFT-RETURN).

    This is not correct: A forced new line is not the beginning of a paragraph.
    The only correct way would be to consider the beginning of a paragraph (RETURN).

    Sometimes you can use "(?=\r)\w+" to look for a word behind a Return instead of "^\w+" to find only the hits at the beginning of a paragraph. However, a combination with the search for a paragraph format can be disturbing here: with the lookbehind combined with a paragraph style only those places are found, where two consecutive paragraphs have the same paragraph style.

    Please correct the effect of ^ to only beginning of paragraph (and not forced line break).

    Dear Support,

    with the GREP position marker "^" for "Beginning of Paragraph", the GREP-search should consider the position of the beginning of a paragraph.
    But this marker does not only recognize the beginning of a paragraph, but also the beginning of a new line after a forced line break (SHIFT-RETURN).

    This is not correct: A forced new line is not the beginning of a paragraph.
    The only correct way would be to consider the beginning of a paragraph (RETURN).

    Sometimes you can use "(?=\r)\w+" to look for a word behind a Return instead of "^\w+" to find only the hits… more

    •  

    18 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

    4 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  ·  amaarora responded

    Thanks for reporting the issue. We will review it shortly

    -InDesign Team

14. [ID-4261000]Hebrew Text with Vowel Points Reorders Incorrectly When Pasted from InDesign to Word

    When keying (or importing) Hebrew text, InDesign often misplaces vowel points when two or more vowel points are attached to a single base character unless the base character and vowel points are keyed in a specific order. I don't totally understand it, but it has something to do with Unicode normalization. Microsoft Word gets around this problem, but I can't say how. It would be nice, however, if InDesign could get around it, too.

    One Hebrew font, SBL Hebrew, has written Unicode features (?) to prevent the normalization problem, but most fonts cannot do this on their own in InDesign. Times New Roman, for example, sets fine in Word, but the same file in InDesign shows vowel points displaced. The user guide for SBL Hebrew (available easily online) explains the problem better than I can.

    Thanks for considering addressing this behavior.

    When keying (or importing) Hebrew text, InDesign often misplaces vowel points when two or more vowel points are attached to a single base character unless the base character and vowel points are keyed in a specific order. I don't totally understand it, but it has something to do with Unicode normalization. Microsoft Word gets around this problem, but I can't say how. It would be nice, however, if InDesign could get around it, too.

    One Hebrew font, SBL Hebrew, has written Unicode features (?) to prevent the normalization problem, but most fonts cannot do this on their own in InDesign.… more

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Text/Story/Table  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  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

15. Underline with variable font

    When the underline of a variable font is activated, the underline takes the whole height of the page. (Indesign 15.1.2)

    •  

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    The issue has been fixed in the latest release of InDesign – InDesign 2021.
    Please update to this new version of InDesign to get the fix.

    —
    Adobe InDesign team

16. Menu item "Convert footnotes and endnotes" missing

    Although my software is up to date, the option "Convert footnotes to endnotes" is missing from my "Type" menu item (image). The interface is in portuguese, but you can see there are only four itens on the footnote/endnote area, the fifth ("Convert footnote to endnote") is really missing...
    I tried unistalling and installing InDesign again from Creative Cloud but it didn´t solve this issue. This menu item is also unavailable on Edit>Menus...
    System: Windows 10 / 64 bits
    Adobe Indesign (2020): 15.1.1 x64

    •  

    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

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

    Thanks for reporting this issue. We are reviewing this.

    —
    InDesign team

17. placing text at cursor jumps in rtl in InDesign 15.1.1.103

    When placing a story at cursor using a right-to-left story frame, the cursor is in the wrong place.

    This has also been filed as Bug ID-4219127

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

18. GREP Beginning of STORY not Working in InDesign 2020 15.0.3

    GREP (Beginning of STORY) not Working in InDesign 2020 15.0.3

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Text/Story/Table  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting. We are reviewing the issue

    -InDesign Team

19. BUG: spell-checker not automatically applied after pasting text

    When pasting text into a new frame, the correct language (german 2006 in my case) for spellchecker is selected, but not applied to the new text. I need to select the the text and choose a different language for spell-check and then change back to the correct language, then it works.

    A pain in the a**, if you have to copy-n-paste many snippets from different documents to single frames.

    INDD 15.0.3 x64 on Win 10 x64 (1909)

    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

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

    Thanks for reporting. We are reviewing it

    -InDesign Team

20. Nonbreaking Hyphen is ignored on import from DOCX

    • 

    • 

    • 

    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

    Under Review  ·  10 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