854 results found

1. Multiple variables in a TOC

   While having headlines with zwo or more variables in the document, the TOC will be horrible wrong - it looks like a variable-puzzle.

   This mistake destroys any dream of creating efficiently catalogues and users are forced to use any kind of dirty-trick or handle on very expensive way a "handmade-process".

   This Bug is known since CS5.x.
   So please: Repair this Bug - now!

   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

   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
   Closed: Fixed  ·  Abhinav Kaushik responded

   Hello All,

   Thank you for reporting the issue to us.
   We have fixed the issue in the latest version of InDesign, Id 14.0.3

   Please upgrade your InDesign application to the latest version to try out the fix.

   If you are unable to see the update yet, go to Creative Cloud desktop application, open the menu (three dots) from the top-right corner and click on ‘Check For App Updates’.

   If you face any problems with the new update, do let us know in the comments.

   You may also follow the below given link for the list of all fixed issues in Id 14.0.3
   https://helpx.adobe.com/indesign/kb/fixed-issues.html

2. problem with optical margin alignment and world-ready paragraph composer

   1. This happens in multiple versions of InDesign. I've reproduced it in ID CS 6 (8.1.0.420), ID CC 2019 (14.0.3.433), ID 2021 (16.4.0.55), and ID 2022 (17.0.0.68).

   2. Steps to reproduce:
      (1) Open InDesign
      (2) Create a new empty document
      (3) Create a text frame that is 100 mm by 100 mm
      (4) Place Text4.txt
      (5) Go Type > Story > check Optical Margin Alignment

   3. Expected result:
      The left margin should be somewhat ragged because the * character needs to be shifted left to make the margin appear straight. The right margin should be completely even because each line ends with the same word.

   4. Actual result:
      The left margin is correctly ragged. The right margin is ragged instead of being even.

   5. Text4.jpg shows the result with the ragged right margin.

   6. Notes:
      (1) This bug occurs with the World-Ready Paragraph Composer. It does not occur with the Adobe Paragraph Composer. Switching the composer produces the expected results.
      (2) This bug is related to soft hyphens (0xAD). If these are removed from the data then the expected results are produced.

   1. This happens in multiple versions of InDesign. I've reproduced it in ID CS 6 (8.1.0.420), ID CC 2019 (14.0.3.433), ID 2021 (16.4.0.55), and ID 2022 (17.0.0.68).

   2. Steps to reproduce:
      (1) Open InDesign
      (2) Create a new empty document
      (3) Create a text frame that is 100 mm by 100 mm
      (4) Place Text4.txt
      (5) Go Type > Story > check Optical Margin Alignment

   3. Expected result:
      The left margin should be somewhat ragged because the * character needs to be shifted left to make the margin appear straight. The right margin should be completely even because each line ends with the… more

   •  

   • 

   24 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

   8 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. Tab indent of RTL Numbered List does not line up

   See two screenshots attached, both are using the exact same settings, (Default, just changed to Hebrew numbering)
   in InDesign 2019 (14.0.3) Everything is nicely aligned, vs in InDesign 2020 (15.0) it's jagged, and I'm not able to align it in any way (Tabs, Indenting, etc.).
   I'm using InDesign 2020 תומך עיברית, on Windows 10

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   22 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

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

   Fix for this issue is now available in the latest update of InDesign 2020 – that is, InDesign 15.0.1

   In the Creative Cloud Desktop application, click on the Updates section on the left. You should be able to see the Update available for InDesign. Please update your InDesign application to this version to try out the fix.

   Let us know in the comments section if you face any problem with the updation process.

   —
   Adobe InDesign Team

4. Find Format and Change Format option unavailable in Find/Change-文字種変換

   Version : Adobe InDesign 2021(ver.16.0.1 ja_JP)
   OS : macOS10.15.6

   1.Steps to reproduce the issues
   1. Open Find/Change Window.
   2. Select "文字種変換" and click "Specify attributes to Find" and Select Style button.
   3. The selected Style does not shown in "Find Format" area and we can't apply it. However, click the button, we can see selected Style we selected previouse step.
   4. The Change Format in "文字種変換" also unavailable.

   2.Expected result
   The selected style is displayed correctly in Find Style area and is correctly apply.
   Also, the replacement style is set correctly in Change Style and replaced as well like InDesign 2021.

   1. Actual result We can't set Find Format and Change Format options in "文字種変換" in Find/Change window. Test file, screenshot, video or GIF capturing the issue (optional)

   Japanese.
   1.問題を再現する手順
   1.検索と置換ウィンドウを開きます。
   2.「文字種変換」を選択し、「検索形式」をクリックして、「検索する属性を指定」ボタンをクリックします。
   3.選択したスタイルが検索形式のエリアに表示されず、適用できません。ただし、再度「検索する属性を指定」ボタンをクリックすると、前の手順で選択したスタイルが表示されます。
   4.「置換形式」のスタイルも利用できません。

   2.期待される結果
   InDesign2021と同様に、選択したスタイルが「検索形式」エリアに正しく表示され、検索対象として正しく機能する。また、「置換形式」も同様に設定できて正しく置換が行える。

   3.実際の結果
   「検索と置換」ウィンドウの「文字種変換」で「フォーマットの検索」および「フォーマットの変更」オプションを設定することはできません。

   Please refer below,
   https://community.adobe.com/t5/indesignフォーラム/文字種変換で検索形式の指定ができません/m-p/11695809

   Version : Adobe InDesign 2021(ver.16.0.1 ja_JP)
   OS : macOS10.15.6

   1.Steps to reproduce the issues
   1. Open Find/Change Window.
   2. Select "文字種変換" and click "Specify attributes to Find" and Select Style button.
   3. The selected Style does not shown in "Find Format" area and we can't apply it. However, click the button, we can see selected Style we selected previouse step.
   4. The Change Format in "文字種変換" also unavailable.

   2.Expected result
   The selected style is displayed correctly in Find Style area and is correctly apply.
   Also, the replacement style is set correctly in Change Style and replaced as well like InDesign… more

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

   The fix for this issue is available in the latest InDesign release 16.2.1
   Please update to this latest version to get the fix.

   —
   Adobe InDesign team

5. ID 2020 - Indent in combination with wrap text around an image not working

   In Indesign 2020, whenever I want to wrap text next to an image, but the text also has an indent the text jumps from the supposed position.
   In Indesign 2019 this did not happen. The text was wrapped nicely next to the image, the way you should expect.

   My guess what happens here, is that the indent specs are applied not the the edge of the frame, but to the edge of the text. Which corrupts the spacing between the image and the text.

   I'm working with the latest 2020 version on iMac with Catalina

   •  

   •  

   •  

   •  

   •  

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

   This issue is addressed with a new option "Honor Text Indents in addition to Text Wrap" in Preferences > Composition dialog. This option is ON for new docs created in ID2023 and needs to be turned ON for docs created in older versions of InDesign when opened in ID2023.

   
   

   --

   Adobe InDesign team

6. Opening Text Wrap panel crashes application

   1. Indesign 2021
   2. Place image, open text wrap panel, does not open panel and crashes.
      Happens with any image and any document. Panel opens fine if pic box empty.

   OsX Mojave.

   Gone back to 2020.

   •  

   19 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

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

   The fix for this issue is now available in the latest update of InDesign – version 16.1
   Please update to this version to get the fix.

   —
   Adobe InDesign team

7. A splitted footnote with three lines violates keep options and makes a widow instead of an orphan

   1. Version of Adobe InDesign
      This issue appears in every InDesign versions since footnotes are supported.
      Bug reports / feature requests (from CS3 up to CS6) have been ignored in the past.

   2. Steps to reproduce the issues
      given:
      a) a footnote with three text lines
      b) splitting footnotes allowed in the footnote options
      c) keep options: at start/end of Paragraph 2/2 (2 lines at start, 2 lines at end)

   Play with the textframes hight so that the footnote is forced to be splitted. It will only split 2/1, not 1/2.

   1. Actual result
      The footnots splits with 2 lines in the textframe within the footnote starts and ends with one single line (widow) in the next textframe.

   2. Expected result
      a) best choice: hold the keep options!
      (e.g. 2 at start / 2 at end; so don't split a footnote with 3 and less lines).
      b) alternative: make an orphan (full line at the start of a footnote paragraph) instead of a widow; widows are absolutely not allowed (because they ony fill a part of a line, maybe only one word)

   3. Test file, screenshot, video or GIF capturing the issue (optional)
      Screenshots appended

   1. Version of Adobe InDesign
      This issue appears in every InDesign versions since footnotes are supported.
      Bug reports / feature requests (from CS3 up to CS6) have been ignored in the past.

   2. Steps to reproduce the issues
      given:
      a) a footnote with three text lines
      b) splitting footnotes allowed in the footnote options
      c) keep options: at start/end of Paragraph 2/2 (2 lines at start, 2 lines at end)

   Play with the textframes hight so that the footnote is forced to be splitted. It will only split 2/1, not 1/2.

   1. Actual result
      The footnots splits with 2 lines in the textframe… more

   •  

   •  

   19 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
   Under Review  ·  amaarora responded

   Thanks for reporting the issue. We are reviewing it

   -InDesign Team

8. Find/change: Search popup—not all options show

   Many times, I have gone to the Find/Change dialog box and not seen any options in the Search popup other than "All Documents or "Document."

   "Story," "End of Story," etc. are missing.

   • 

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

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

   Thanks for reporting. We will review the issue

   -InDesign Team

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

    •  

    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

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

    Thanks for reporting the issue. We will review it shortly

    -InDesign Team

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

12. [macOS] soft return converted to hard return in InDesign Tagged Text

    Affected version:
    14.0.3 [macOS]

    Steps to reproduce:
    In a New document, make a new text container.
    Enter this sample text:
    “line1 \n line2 \r line3 \n line4”
    where \n = shift+return
    and \r = return
    “line1{{shift+return}}line2{{return}}line3{{shift+return}}line4”
    Set space before or space after to 0.125”
    Export as Adobe InDesign Tagged Text, Unicode format.
    Import result using File > Place

    Expected result
    Soft returns and hard returns

    Actual result
    Hard returns only (soft returns converted)

    • 

    •  

    • 

    16 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Closed: Different Product  ·  amaarora responded

    Hi,
    Thanks for your patience all this while. We investigated on this issue and below are our findings. The problem with this bug is related to ages old standards difference between different operating systems.
    On Mac (OS X and later) there is only one way to identify line end i.e by using a single character LF, while on Windows (and DOS before it) uses a pair of CR and LF characters to terminate lines.
    Hence when writing them down to any text file these characters are written as such.
    Windows, can therefore dedicate LF to understand soft return separately while Mac cannot do any
    such thing. Because of this when we read it back from the text file the LF character is interpreted as line break (or new para) on Mac and soft return on Windows.

    These files require conversion when moved from one OS to another

    Consider this article for more information: https://www.oreilly.com/library/view/mac-os-x/0596004605/ch01s06.html
    A same analogy is found in excel when saved as a text file

    Thanks

    Hi,
    Thanks for your patience all this while. We investigated on this issue and below are our findings. The problem with this bug is related to ages old standards difference between different operating systems.
    On Mac (OS X and later) there is only one way to identify line end i.e by using a single character LF, while on Windows (and DOS before it) uses a pair of CR and LF characters to terminate lines.
    Hence when writing them down to any text file these characters are written as such.
    Windows, can therefore dedicate LF to understand soft return separately while Mac cannot do any
    such thing. Because of this when we read it back from the text file the LF character is interpreted as line break (or new para) on Mac and soft return on Windows.

    These files require conversion when moved from one OS to another

    Consider this… more

13. Clicking document-installed font from font list gives error to "activate font" and doesn't change font.

    InDesign 14.0 on Windows 10 x64

    I just upgraded to InDesign 14.0, and there appears to be a bug when clicking a document-installed font from the font list. The font list gives an error message to "Click 'Activate' button to activate fonts" and the text frame keeps the existing font, instead of changing to the new font.

    Expected result:
    The expected result would be the same behavior as InDesign 13.1, where you could click a document-installed font from the font list, and the text frame would update to the newly selected font.

    Actual result:
    In InDesign 14.0, clicking a document-installed font from the font list gives an error message to "Click 'Activate' button to activate fonts" and the text frame font stays the same.

    Steps to reproduce:
    1. Create a new document in InDesign.
    2. Create a new text frame with the word "Test." Save and then close.
    3. In the same location as your new document, create a "Document fonts" folder. Copy an OTF or TTF font file into this folder. In my case, I copied "Sacremento-Regular.ttf" into this folder.
    4. Reopen the new InDesign document you saved in step 2.
    5. Select the text in the text frame. Note the current font (most likely Minion Pro).
    6. From the type list, select the document-installed font you copied into the "Document fonts" folder.
    7. Note the "Click 'Activate' button to activate fonts" error message, and that the font for the text frame has remained the same.

    InDesign 14.0 on Windows 10 x64

    I just upgraded to InDesign 14.0, and there appears to be a bug when clicking a document-installed font from the font list. The font list gives an error message to "Click 'Activate' button to activate fonts" and the text frame keeps the existing font, instead of changing to the new font.

    Expected result:
    The expected result would be the same behavior as InDesign 13.1, where you could click a document-installed font from the font list, and the text frame would update to the newly selected font.

    Actual result:
    In InDesign 14.0, clicking a document-installed… more

    •  

    16 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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
    Closed: Fixed  ·  Abhinav Kaushik responded

    Hello All,

    Thank you for your patience all this while.
    This issue is now fixed in the latest update (Id 14.0.1) of InDesign CC.
    If you are unable to see the update notification yet, open the menu (three dots) from the top-right of Creative Cloud desktop application and click on ‘Check For App Updates’.

    Once the update button is shown against InDesign CC, click on the button to update your InDesign to Id 14.0.1 for the fix of the issue.
    Do let us know in the comments, if you face any problem with the new update.

    List of fixed issues can be found at: helpx.adobe.com/indesign/kb/fixed-issues.html

    Regards,
    InDesign Team

14. Table headers disappear when pasting

    Several times now I've cut & pasted a table from one part of my document to another only to find the headers disappear. Inserting a row makes the headers reappear.

    I'm usig 12.1.0.56 x64 build.

    • 

    •  

    •  

    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

    12 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
    Closed: Fixed  ·  Abhinav Kaushik responded

    Please update InDesign to the latest version, InDesign CC 2018 (13.0) for the fix of the issue.

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

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

    —
    Adobe InDesign team

16. Spellcheck is grabbing the comma after words, causing an error

    Since upgrading to Indesign 2021 v16.0, when I run a spell check, if it catches a word it thinks is misspelled but that word has a comma after it, spellcheck also grabs the comma. If I attempt to Add that word to my user dictionary, I get an error "Words ending in punctuation other than ending periods may not be added into the dictionary". This never happened in previous versions of Indesign. See attached screengrab.

    (MacOS Catalina 10.15.7 // Macbook Pro Mid 2015)

    •  

    •  

    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

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

    The fix for this issue is now available in the latest update of InDesign – version 16.0.1.

    Please update to this version to get the fix.

    —
    Adobe InDesign team

17. Vertical Text Alignment not working correctly in InDesign 2020

    I recently upgraded to InDesign CC 2020 and find all the text in circles not aligned vertically center. Document was last opened in CC 2019 and these were fine. I haven’t modified these since. Rectangles are fine. See attached example - clearly not right and inconsistently so. I have tried every setting and I can’t get them to line up. Thanks!

    •  

    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

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

    Fix for this issue is now available in the latest update of InDesign 2020 – that is, InDesign 15.0.1

    In the Creative Cloud Desktop application, click on the Updates section on the left. You should be able to see the Update available for InDesign. Please update your InDesign application to this version to try out the fix.

    If you have created documents from ID15.0 where you see this issue, please do a Force Recomposition of the Text Frames (Cmd-Opt-/ on Mac, Ctrl-Alt-/ on Win) to make it work correctly.

    Let us know in the comments section if you face any problem with the updation process.

    —
    Adobe InDesign Team

18. World-Ready Composer Is messing up the kerning in Latin fonts

    I have reported a variation of this—back with CS6—but it seems not to have been fixed. I assume it's a bug, but if someone can enlighten me about what I might be doing wrong and how I can fix this, I'd appreciate it.

    I often work on books that include Arabic and Hebrew words and phrases in the middle of English text. They only way to get the Arabic ligatures to form is to use one of the World Ready composers. When I do that, though, the kerning around some English characters often—but not always—is affected. I have tried turning on and off various settings—justification settings, kashidas, etc.—and their effect seems to be random. Sometimes the changes fix the problem until the page redraws, sometimes the errant kerning is corrected in one location but shows up in another location, sometimes nothing happens at all. I'm attaching two screen captures of a book that I have in production now with the word "economics" selected in each. In the shot with the World-Ready Paragraph Composer active, you can see the extra kerning between the "e" and the "c." In the shot with the WRPC deactivated, the word looks as it should.

    Is this a bug? If not, what am I doing wrong? If it is, when might we expect a fix. Unfortunately, I have a deadline on this project now and can't see any reasonable way to fix this. Thanks for considering this problem.

    I have reported a variation of this—back with CS6—but it seems not to have been fixed. I assume it's a bug, but if someone can enlighten me about what I might be doing wrong and how I can fix this, I'd appreciate it.

    I often work on books that include Arabic and Hebrew words and phrases in the middle of English text. They only way to get the Arabic ligatures to form is to use one of the World Ready composers. When I do that, though, the kerning around some English characters often—but not always—is affected. I have tried turning… 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

    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
    FIXED  ·  Abhinav Kaushik responded

    Hello All,
    Thank you for reporting the issue to us.
    We have fixed the issue in the latest version of InDesign, Id 15.0

    Please upgrade your InDesign application to the latest version to try out the fix.

    If you face any problems with the new update, do let us know in the comments.

    You may also follow the below given link for the list of all fixed issues in Id 15.0
    https://helpx.adobe.com/indesign/kb/fixed-issues.html

    -InDesign Team

19. Indents not holding after page break

    1. InDesign CC 2018, though I logged this bug for 2017 as well. It may also have existed as far back as CS6. I had hoped it would be fixed in this release.
    2. Create a paragraph style that has a left indent and set text in that paragraph style. Set enough text to flow onto a second page.
    3. The text should retain the left indent after the page break.
    4. Sometimes, the first line of text after the page break does not retain the indent.

    •  

    •  

    •  

    • 

    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

    9 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
    Closed: Fixed  ·  Abhinav Kaushik responded

    Hello All,

    The fix for this issue is now available in InDesign’s latest version, id 14.0.3.
    Please update your InDesign to try out the fix.

    Note:
    If you open a file which already has this issue, in the new version, you may continue to see the issue.
    To resolve such cases, you may SAVE AS the file or do a force text re-composition as the workaround

    However, all the new files created in the new version will not have this issue anymore.

    You may also follow the below given link for the list of all fixed issues in Id 14.0.3
    https://helpx.adobe.com/indesign/kb/fixed-issues.html

    -InDesign Team

20. Font not working after InDesign 17.2 upgrade

    The font "AlteHaasGroteskBold" worked with the previous version of InDesign. It is open in FontExplorer X Pro (7.3.0) and works in Illustrator and Photoshop (current versions).

    •  

    •  

    •  

    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

    3 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