199 results found

1. [ID-4245219]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

   •  

   • 

   •  

   •  

   • 

   299 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

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

2. [ID-4243320]Cursor moves differently in MENA builds.

   InDesign version: v20 (both Mac & PC)

   In right-to-left languages ​​(Hebrew & Arabic) the cursor movement went crazy:
   - Left key - goes up
   - Right key - jumps to the end of the line...
   We can't work that way

   Note: both (23\25 indd) set to 'Visual' in preferences > right-to-left > cursor movement (of course, changing the setting to 'logical' doesn’t solve it)

   • 

   179 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

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

   •  

   •  

   •  

   177 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

   39 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
   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-4228495]Export Tagging: ‘i’ character in class name exports as blank space

   I just did the 2018 update, so I think it's the most recent version: 13.0 x64

   I have a document template that contains many character and paragraph styles with export CSS tags that contain the lowercase ‘i’ in them. This character is being exported as a blank space, which completely breaks the CSS, like this:
   should be: <p class="bright"></p>
   getting: <p class="br ght"></p>

   This problem was easily replicated in a fresh new document, so it’s something with InDesign, rather than my template file.

   This workflow involves complex style mapping through to CSS classes. Because so many of the classes contain the character 'i', this problem has brought the workflow to a dead halt.

   I just did the 2018 update, so I think it's the most recent version: 13.0 x64

   I have a document template that contains many character and paragraph styles with export CSS tags that contain the lowercase ‘i’ in them. This character is being exported as a blank space, which completely breaks the CSS, like this:
   should be: <p class="bright"></p>
   getting: <p class="br ght"></p>

   This problem was easily replicated in a fresh new document, so it’s something with InDesign, rather than my template file.

   This workflow involves complex style mapping through to CSS classes. Because so many of the classes contain… more

   •  

   •  

   •  

   •  

   • 

   107 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

   25 comments  ·  ePub/HTML/Publish Online  ·  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
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   We are reviewing this issue.

   —
   InDesign team

5. [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
   Under Review  ·  amaarora responded

   Thanks for reporting. We will review it

   -InDesign Team

6. [ID-4208669]QR-Code Generator Problems with Umlauts in vCards

   In the actual version of indesign (16.0) there is still an issue with internal generated vCard-QR-Code scanned by an iphone.

   In germany there are special Characters called "Umlaute" (ü, ö, ä) or the "sharp s" (ß). If these characters are used in an vCard generated within the buildin function from indesign, they are replaced with other symbols on the iPhone QR-Code-Camera Reader.

   I think this is only a Problem of the used vCard-Version. I think indesign uses Version 2.1 if you would just use Version 3.0 this issue does not appear.

   please see attached one example

   Kind regards from germany

   Max

   In the actual version of indesign (16.0) there is still an issue with internal generated vCard-QR-Code scanned by an iphone.

   In germany there are special Characters called "Umlaute" (ü, ö, ä) or the "sharp s" (ß). If these characters are used in an vCard generated within the buildin function from indesign, they are replaced with other symbols on the iPhone QR-Code-Camera Reader.

   I think this is only a Problem of the used vCard-Version. I think indesign uses Version 2.1 if you would just use Version 3.0 this issue does not appear.

   please see attached one example

   Kind regards from germany

   … more

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   92 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

   55 comments  ·  Others  ·  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
   Under Review  ·  amaarora responded

   Thanks for reporting. We will review the issue shortly

   -InDesign Team

7. [ID-4224416]PDF comments: Delete <FEFF> marker after removal of all comments

   After choosing »Delete all comments« from the fly-out menu of the PDF comments panel at every position, where a comment was before the removal, a <FEFF> char is left behind, which shows up as a zero-width colon (:), when special characters are turned on.

   Since this is a useless char after deleting the comments, the <FEFF> should also be removed, when selecting the removal in the fly-out.

   <FEFF> shows up with XML tags, notes and index markers, so we can’t simply do a TEXT search for <FEFF> to remove it.
   BTW:
   \x{feff} doesn’t work in GREP search, which is kind of strange ...

   After choosing »Delete all comments« from the fly-out menu of the PDF comments panel at every position, where a comment was before the removal, a <FEFF> char is left behind, which shows up as a zero-width colon (:), when special characters are turned on.

   Since this is a useless char after deleting the comments, the <FEFF> should also be removed, when selecting the removal in the fly-out.

   <FEFF> shows up with XML tags, notes and index markers, so we can’t simply do a TEXT search for <FEFF> to remove it.
   BTW:
   \x{feff} doesn’t work in GREP search, which is kind… more

   46 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

   9 comments  ·  PDF Comments  ·  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
   Under Review  ·  amaarora responded

   Thanks for reporting. We will review the issue shortly.

   -InDesign Team

8. [ID-4219714]CEPHtmlEngine maxes out CPU to 100%

   macOS Catalina 10.15.5. and InDesign. 15.1.1.

   Massive problem with CEPHtmlEngine Helper. After a while, my MacBook Pro fan is running high and in the activity window, CEPHtmlEngine Helper is running between 90 and 100%. It is no fun to work with a system that runs crazy.
   Why? Solution needed.

   •  

   •  

   •  

   41 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

   52 comments  ·  Performance/Usability  ·  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
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   This issue is being reviewed again.

   —
   Adobe InDesign team

9. [ID-4213629]Indesign performance issue : Slow work of Indesign when editing text with large footnotes

   I'd like to report a bug. Please follow the scenario below:

   1. In a single column with lots of text in it, make two columns for a fragment of text

   2. In text within the two-column setup, make a footnote. Add several lines of text to the footnote

   3. Turn on the "Span Footnotes Across Columns" feature so that footnote ends up in the same group with the footnotes at the bottom of the page rather than below the two-column fragment

   4. Expected behaviour: normal editing can be performed after these manipulations

   5. Observed behaviour: any text editing after turning on the "Span Footnotes Across Columns" feature becomes lethargic and near impossible. Turning this option off immediately solves the speed issues.

   Please log a bug to fix this behaviour.

   I'd like to report a bug. Please follow the scenario below:

   1. In a single column with lots of text in it, make two columns for a fragment of text

   2. In text within the two-column setup, make a footnote. Add several lines of text to the footnote

   3. Turn on the "Span Footnotes Across Columns" feature so that footnote ends up in the same group with the footnotes at the bottom of the page rather than below the two-column fragment

   4. Expected behaviour: normal editing can be performed after these manipulations

   5. Observed behaviour: any text editing after turning on the "Span Footnotes Across… more

   • 

   •  

   38 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

   27 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
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   We’re reviewing this issue.

   —
   Adobe InDesign team

10. [ID-4236204]Using “Paragraph Borders and Shading” on frame grid, it is incorrect to base them on grid attributes possessed by the frame grid

    InDesign Version CC2018 or newer

    1. “Paragraph Borders and Shading” are usually generated based on the outline of the glyphs in the paragraph to which they are applied.
       This is true even if they are grid-aligned on a text frame (Figure 1-a, right).
       However, when the same settings are made on a frame grid, for some reason, they are generated based on the grid attributes of the frame grid, not the glyph outlines.
       This always occurs based on the grid attribute of the frame grid, regardless of whether the text in the frame grid is grid-aligned or not (Figure 1-a left).
       The “Paragraph Borders and Shading” setting in Figure 1-a is the same for both (Figure 1-b).
       In Japanese typesetting, such operation is rarely used.
       In particular, it is never done when paragraphs that are not grid-aligned are mixed within a frame grid.
       For this reason, “Paragraph Borders and Shading”cannot be used when using a frame grid.

    2. Then, it is not so if “Paragraph Borders and Shading” can be somehow operated as long as they are grid-aligned in the frame grid.
       In Figure 2-a, it can be seen that the "Paragraph Border" that occurs in the right and left paragraphs is different.
       Both the right and the left have the same settings (Figure 2-b).
       The only difference is whether it is at the top of the paragraph or in the middle.
       This phenomenon occurs when the “Gyodori”setting is used.

    From the above two points, I believe that the developer does not understand how the “Paragraph Borders and Shading” should occur on the frame grid at all.
    “Paragraph Borders and Shading” should occur on the frame grid, just as it does on a text frame, based on glyph outlines, and should not be affected by grid attributes.

    「段落の囲み罫と背景色」をフレームグリッド上で使用するとき、フレームグリッドの持つグリッド属性を基準にするのは間違っている

    1.　「段落の囲み罫と背景色」は、通常は適用した段落のグリフの外形を基準として発生する。
    これは、テキストフレームでグリッド揃えをしていても同様である（図1-a右）。
    しかし、フレームグリッド上で同じ設定をすると、なぜかグリフの外形ではなく、フレームグリッドの持つグリッド属性を基準として発生してしまう。
    これはフレームグリッド内のテキストが、グリッド揃えをしていてもしていなくても、必ずフレームグリッドのグリッド属性を基準に発生してしまう（図1-a左）。
    図1-aで設定している「段落の囲み罫と背景色」の設定はどちらも同じである（図1-b）。
    日本語の組版上、そのような運用をすることはまずない。
    特に、フレームグリッド内に、グリッド揃えをしない段落を混在させるときには、絶対にしない。
    このため、フレームグリッドを使用している時には、事実上「段落の囲み罫と背景色」は使用できない。

    2.　ではフレームグリッド内でグリッド揃えをしていれば、「段落の囲み罫と背景色」は何とか運用できるのかというと、そうではない。
    図2-aでは、右と左の段落で、発生している「段落の囲み罫」が異なることが見て取れるだろう。
    右も左も同じ設定である（図2-b）。
    違うのは、段落の最上部にあるか、半ばにあるかだけである。
    この現象は、「段落の行取り」設定をしているときに発生する。

    上記の2つの点から、開発者はフレームグリッド上で「段落の囲み罫と背景色」がどのように発生するべきかを全く理解していないと考えられる。
    「段落の囲み罫と背景色」は、フレームグリッド上であっても、テキストフレーム上と同じように、グリフ外形を基準として発生するべきで、グリッド属性に左右されてはいけない。

    InDesign Version CC2018 or newer

    1. “Paragraph Borders and Shading” are usually generated based on the outline of the glyphs in the paragraph to which they are applied.
       This is true even if they are grid-aligned on a text frame (Figure 1-a, right).
       However, when the same settings are made on a frame grid, for some reason, they are generated based on the grid attributes of the frame grid, not the glyph outlines.
       This always occurs based on the grid attribute of the frame grid, regardless of whether the text in the frame grid is grid-aligned or not (Figure 1-a left).… more

    •  

    •  

    •  

    •  

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

11. [ID-4253441]"Don't Save" and "Cancel" Positions are reversed in InDesign 20.0

    "Don't Save" and "Cancel" Positions are reversed in Indesign 20.0.

    Why in the world would they do this??? Yet another meaningless update to hinder production.

    Not OS related, as I have not updated my OS since updating to Indesign 20.

    Mac Sonoma 14.7

    3.6 GHz 10-Core Intel Core i9

    AMD Radeon Pro 5700 XT 16 GB

    •  

    •  

    •  

    •  

    36 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

    20 comments  ·  Performance/Usability  ·  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
    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

12. [ID-4216943]Slow InDesign

    This latest update for late August/September is really really really slow. It lags crazy. It's not efficient to work in. Even with small documents.
    It's the most unpleasant InDesign experience ever!

    36 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

    12 comments  ·  Performance/Usability  ·  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
    Under Review  ·  Abhinav Kaushik responded

    Thank you for reporting the issue to us.
    We are currently reviewing it.
    InDesign Team

13. [ID-4216880]Placed graphic displays and exports outside stroke.

    A placed graphic will show onscreen and in graphic exports like PNG and JPG outside the stroke when the stroke is aligned to the inside of the frame. InDesign 2020 and earlier. To reproduce: place a graphic, add a stroke to the frame, align stroke to inside, export the page to jpg or png. A thin portion of the image is visible outside the stroke. Obviously, this is most noticeable when the stroke is thick and white.

    •  

    •  

    •  

    •  

    35 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

    6 comments  ·  Graphics/Images/Assets  ·  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
    Under Review  ·  Abhinav Kaushik responded

    Thank you for reporting the issue to us.
    We are currently reviewing it.
    InDesign Team

14. CMYK color specified in MathML does not match the set value

    InDesign 20.0 (2025)
    Windows /macOS

    When I apply a preset or a newly created CMYK swatch to MathML, the color does not match the value.
    It appears to be CMYK via RGB color.

    Original text (Japanese):
    MathMLに対し、プリセットや新規作成したCMYKスウォッチを適用しても、その数値どおりのカラーになりません。
    RGBカラーを経由してCMYKになっているように見えます。

    • 

    •  

    32 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  ·  Others  ·  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
    Under Review  ·  AdminVineet (Admin, Adobe InDesign) responded

    Thank you for trying out the MathML feature in InDesign! The math objects created using this feature are placed as SVGs, and hence they exclusively support RGB colours.If you try to apply a non RGB colour (CMYK/LAB/HSV-based), then by design it is converted to RGB before it is applied to the math object. This conversion is designed to enable users to continue using document colours that are not RGB-based for the math object SVGs.

15. [ID-4245422]Underlines are drawn in the space left by "danraku jisage".

    When I use "danraku jisage " in the "mojigumi akiryou settei" , an underline is underlined in the empty space at the beginning of a line.
    Since there are no characters in the empty space, it is correct that underlines are not underlined in the same way as when indentation is used to lower the line.

    「文字組みアキ量設定」で「段落字下げ」を行ったとき、行頭の空いている部分にも下線が引かれてしまう。
    空いている部分には文字はないので、インデントで下げたときと同じように、下線は引かれないのが正しい。

    •  

    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

    2 comments  ·  Adjust Layout  ·  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
    Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Hi,
    The issue is currently under investigation.

    —

    Adobe InDesign Team

16. [ID-4257175]Pages Panel: Buttons are hidden behind page number text when window is thin

    When the pages panel is as thin as possible, the buttons such as delete page are behind the text that says the number of pages. It is therefore not possible to click on the buttons. I always use this panel in a thin band, and it is now less practical.

    Version: InDesign 20.0.0

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    26 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

    10 comments  ·  UI/UI Scaling  ·  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
    Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Hi,

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

    —

    Adobe InDesign Team

17. [ID-4216889]Objects on the page jump if a left-hand page becomes a right-hand page and vice versa

    Hi developers,
    this is a longstanding bug:

    With facing pages documents on EVERY document page there is a zone where jumping of objects will happen.

    I call this the jump zone. All objects on a page that will jump are clearly inside the page's area. The bug has nothing to do with rounding errors where object edges are at the edge of a page.

    The objects should not move if pages are added or removed, if numbering of pages is changing. Nevertheless they do. Always. Unless, the zone has a width of zero.

    Below all the details.

    What is a jump zone?
    If horizontal values for left and right margins differ, there is a BUG that in effect forms a zone on the page.
    I call this zone JUMP ZONE because objects that touch the zone with their edges could jump horizontally.

    When will objects jump?
    1. When a left-hand page becomes a right-hand page OR a right-hand page becomes a left-hand page.

    1. When a left-hand page becomes a right-hand page and later when a right-hand page becomes a left-hand page again.

    This could happen within a single InDesign document open.

    WARNING:
    It could even happen to InDesign documents that are not visibly open.
    That's with InDesign documents that are part of a InDesign book file.
    The book file's feature with auto-numbering pages can do this even if no document is visibly open.
    The damage is done if auto-numbering took place AND the book file is saved.

    How large is the jump zone?
    The height of the zone is the height of the page.
    The width of the zone can be calculated:
    inner margin MINUS outer margin

    How large is the jump?
    The width of the jump zone.

    Where is the jump zone positioned?
    Positive value: The zone is at the spine of the page.
    Objects that touch the zone jump towards the spine.

    Negative value: The zone is at the edge of a page away from the spine.
    Objects that touch the zone jump away from spine.

    What versions of InDesign are affected?
    All versions CC up to InDesign 2020, Mac OS X and Windows.
    InDesign CS6, Mac OS X and Windows.

    Possibly also InDesign CS5 and CS5.5, Mac OS X and Windows.
    I did not test this.

    How can I avoid jump zones?
    Make right and left margin values the same!

    Are there workarounds if I cannot avoid jump zones?

    1. Anchor objects
       that touch the jump zone to text frames that do not touch the jump zone.
       Nested objects will not jump if the parent objects are not touching the jump zone.

    2. Group an object
       to another one that is touching the top or the bottom edge of the page.
       Tests are showing that objects will not jump if they touch the bottom OR the top of the page.
       ( OR both, bottom and top edges of the page .)

    Other things to consider about moving objects?
    The following is independently of jump zones:
    Objects could move to other pages if their edges touch exactly the horizontal edges on pages in facing pages.
    Depending on the version of InDesign this could also happen with objects touching the spine.
    Reason: Rounding errors.

    What can provoke all this?
    1. Add or remove an odd number of pages
    so that left-hand pages become right-hand pages and vice versa.

    1. Renumber start pages of sections so that left-hand pages become right-hand pages and vice versa.

    Note:
    Every document has at least one section by default.
    The start of that section is the first page in the document.

    More details at Adobe InDesign Forum:
    https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774458#M166408

    InDesign 2020 documents attached here.
    See screenshots and further comments at Adobe InDesign Forum:
    https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774596#M166420

    Download link to all test files on my Dropbox account:
    https://www.dropbox.com/s/duov096cu2q481l/Jump-Zones-Explained-Facing-Pages-Documents.zip?dl=0

    Regards,
    Uwe Laubender

    ( ACP )

    PS: Why does InDesign Uservoice not permit to attach files with suffix .indd ?
    Message: "Invalid file type: .indd files not allowed."
    Isn't that rather absurd?

    Hi developers,
    this is a longstanding bug:

    With facing pages documents on EVERY document page there is a zone where jumping of objects will happen.

    I call this the jump zone. All objects on a page that will jump are clearly inside the page's area. The bug has nothing to do with rounding errors where object edges are at the edge of a page.

    The objects should not move if pages are added or removed, if numbering of pages is changing. Nevertheless they do. Always. Unless, the zone has a width of zero.

    Below all the details.

    What is a… more

    •  

    •  

    •  

    26 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  ·  Document/Pages  ·  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
    Under Review  ·  Abhinav Kaushik responded

    Thank you for reporting the issue to us.
    We are currently reviewing it.
    InDesign Team

18. [ID-4252110]Place (cmd+D) can't see tagged folders on mac

    Place command (cmd+D) can't see the tagged folders, so i can't find my documents quickly as it should be...

    All other commands (export cmd+E for exemple) allow me to navigate from my tagged folders.

    Please add the same option to place command.

    •  

    •  

    25 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

    6 comments  ·  Document/Pages  ·  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
    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

19. [ID-4236366]Scripts using BridgeTalk do not work on M1 Macs (regardless of CC version)

    ID version: InDesign CC 2021 (16.3.2)
    OS: macOS Big Sur 11.5.2
    Processor: Apple M1

    When I try to run a script that uses BridgeTalk and works with Photoshop, it does not work.
    Also, a simple script using BridgeTalk will not work as well.
    Those scripts do work in CC 2021 on Intel Mac and macOS Big Sur 11.5.2.

    25 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  ·  Scripting  ·  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
    Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Hi,

    The issue is under review.

    —

    Adobe InDesign Team

20. [ID-4219708]export book to pdf slows the mouse respond

    Every time, when I export whole book into PDF file, my mouse starts to move with steps. Everything else is working more or less normally, but moving cursor is almost impossible.

    Cursors respond with huge lag - around 1 sec, and moves in steps, what makes impossible to use the mouse.

    25 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  ·  Book/TOC  ·  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
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review it

    -InDesign Team