7107 results found

1. Multiple listings of same font in Find Font menu

   There are multiple listings of the same font in the Find Font menu in CC2019. All information is the same, all applied characters are the same, but there is odd behavior.

   --FileACC2019WithDocumentsfontsfolder.png shows double listing of Trade Gothic LT Pro Roman.

   --FileACC2019WithoutDocumentfontsfolder.png (when I take away access to Document fonts folder, no other changes), one instance switches to "Regular" instead of "Roman"

   --FileACC2017WithDocumentfontsfolder.png shows what happens with I open this file in CC2017 (no double listing)

   --FileACC2017WithoutDocumentfontsfolder.png (Document fonts folder hidden) shows what happens with I open this file in CC2017 (no double listing)

   I process large volumes of files; this is not an isolated incident nor a corrupted file. Packaging results in InDesign only grabbing the single correct font file, so that isn't broken. This behavior with Find Font is seemingly new to CC2019 (I'm working on 14.0.2). The multiple listing of same font, variation of font name when fonts enabled/disabled, and Find Font showing fonts missing that aren't because of what seems to be a name issue in Find Font. Has something changed in the way that InDesign reads fonts/accesses Document fonts folders?

   There are multiple listings of the same font in the Find Font menu in CC2019. All information is the same, all applied characters are the same, but there is odd behavior.

   --FileACC2019WithDocumentsfontsfolder.png shows double listing of Trade Gothic LT Pro Roman.

   --FileACC2019WithoutDocumentfontsfolder.png (when I take away access to Document fonts folder, no other changes), one instance switches to "Regular" instead of "Roman"

   --FileACC2017WithDocumentfontsfolder.png shows what happens with I open this file in CC2017 (no double listing)

   --FileACC2017WithoutDocumentfontsfolder.png (Document fonts folder hidden) shows what happens with I open this file in CC2017 (no… 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

   12 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

   Submit Rating
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2022(v17.0.0.96). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.

   —
   Adobe InDesign Team

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

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

3. Can't delete InDesign color swatch

   Documents inherit a swatch from a picked-up file and the swatch can not be deleted.

   1) This problem has existed for us since at least InDesign CS4 and persists through the current CC 2018 build (13.1).

   2) In the attached file, "Select All Unused" in the Swatches panel. There is no content at all in the file. All objects have been deleted, as have all text and object styles. Try to delete the unused process color swatch, "C=80 M=76 Y=70 K=73."

   3) We expect the unused swatch to be deleted.

   4) Trash can icon in Swatches panel is grayed out and unselectable.

   We have tried renaming the swatch, creating an identical swatch in Illustrator, placing and deleting both .ai and .eps files and merging the swatch with other swatches.

   This issue is also present in other legacy files with different swatches.

   Documents inherit a swatch from a picked-up file and the swatch can not be deleted.

   1) This problem has existed for us since at least InDesign CS4 and persists through the current CC 2018 build (13.1).

   2) In the attached file, "Select All Unused" in the Swatches panel. There is no content at all in the file. All objects have been deleted, as have all text and object styles. Try to delete the unused process color swatch, "C=80 M=76 Y=70 K=73."

   3) We expect the unused swatch to be deleted.

   4) Trash can icon in Swatches panel is grayed… 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

   8 comments  ·  Colors/Swatches  ·  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
   Closed: Fixed  ·  Abhinav Kaushik responded

   Update:
   -————-
   Following upon the comments from the users who had mentioned that the issue is still not resolved for them, we contacted them on email to gather more information.
   It was found that the issue is no longer reproducible for them, hence we are closing the thread.
   If you still have any concern over the fix of the issue, you may directly reach out to sakverma@adobe.com

   ===========

   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

   Update:
   -————-
   Following upon the comments from the users who had mentioned that the issue is still not resolved for them, we contacted them on email to gather more information.
   It was found that the issue is no longer reproducible for them, hence we are closing the thread.
   If you still have any concern over the fix of the issue, you may directly reach out to sakverma@adobe.com

   ===========

   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… more

4. [ID-4259367]Error handling dialog shown while placing some TIFF/EPS files

   Error encountered while reading TIFF image. Image may be damaged or incompatible. Resave the image with different settings and try again.

   After I upgraded InDesign 19.5.1 to 19.5.2. Linked images do not show on the page in high quality display settings. I have about 60 linked indesign files into my one file. And I was afraid to upgrade to 20.1 and from Sonoma to Sequoia. Any fixes for this? Perhaps get rid of some of the links.. too many links? 60? 2 page document. Newer M2 MacBook Air.

   Edit: Update: Downgraded back to 19.5.1. Everything is working perfectly. Thanks Adobe for allowing very easy downgrades. EXCELLENT.

   Error encountered while reading TIFF image. Image may be damaged or incompatible. Resave the image with different settings and try again.

   After I upgraded InDesign 19.5.1 to 19.5.2. Linked images do not show on the page in high quality display settings. I have about 60 linked indesign files into my one file. And I was afraid to upgrade to 20.1 and from Sonoma to Sequoia. Any fixes for this? Perhaps get rid of some of the links.. too many links? 60? 2 page document. Newer M2 MacBook Air.

   Edit: Update: Downgraded back to 19.5.1. Everything is working perfectly. Thanks Adobe… 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

   9 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

   Submit Rating
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2024(v19.5.3.144). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Sanyam Talwar

5. [ID-4258210][MAC]Screen flickering occurs while moving objects in InDesign 2025(v20.X), no issues with InDesign 2024(v19.X)

   Impact

   Screen flickering occurs while moving objects in InDesign 2025(v20.X)

   Steps to Reproduce the issue:

   • Launch InDesign on MAC.
   • Create a new file and add some objects.
   • Attempt to move the objects.

   Workaround

   • Turn ON GPU Performance
   • Downgrade to InDesign 2024

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   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

   11 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

   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

6. "GREP Load Find with selected text" is incomplete on macOS

   version: any OS: any macOS
   Edit menu > Keyboard Shortcuts > Text and Tables > “GREP Load Find with selected text” also “GREP Load Find and Find Next instance”

   If the selected text contains meta characters that are escaped with a backslash, such as "End of Paragraph" (\r) or tab characters (\t), they are all captured as ¥r and ¥t.
   I’m forced to retype the ¥ into a \ before starting the search.
   On Windows, it works without retyping.

   “Forced line break" (\n) is not a problem as a function, but the display is corrupted, which makes me uneasy.

   It is a pity because it is a very useful function.

   〈にほんご〉
   正規表現 選択したテキストを検索文字列に読み込み がmacOSで不完全

   バージョン：どれでも　　macOS：どれでも
   編集メニュー > キーボードショートカット > テキストと表 > 「正規表現 選択したテキストを検索文字列に読み込み」 および「正規表現 検索文字列に読み込み後次を検索」について

   選択テキストに「段落の終わり」（\r）やタブ文字（\t）など、バックスラッシュでエスケープするメタ文字がある場合、すべて¥r, ¥tとして取り込まれる。
   検索を開始する前に¥をバックスラッシュ\ に入力し直す必要に駆られている。
   Windowsでは再入力を必要とせず動作した。

   「強制改行」（\n）は機能としては問題ないが、表示が崩れており不安である。

   とても便利な機能なだけに残念でならない。

   version: any OS: any macOS
   Edit menu > Keyboard Shortcuts > Text and Tables > “GREP Load Find with selected text” also “GREP Load Find and Find Next instance”

   If the selected text contains meta characters that are escaped with a backslash, such as "End of Paragraph" (\r) or tab characters (\t), they are all captured as ¥r and ¥t.
   I’m forced to retype the ¥ into a \ before starting the search.
   On Windows, it works without retyping.

   “Forced line break" (\n) is not a problem as a function, but the display is corrupted, which makes me uneasy.

   … more

   •  

   16 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 2024 lag

   InDesign 2024 is lagging a lot—there's a delay in response when clicking onto a text or content box to edit the content. Even moving from page to page (at typical or fast display) there's a lag.

   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

   2 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

   Submit Rating

8. Reading order issue when a footnote is split over to next page or column

   When a footnote split over to next page or column, the accessible PDF generated from InDesign CC 2023 has notes reading order messed up. The first note reference on the page where the portion of a note comes in from the previous page/column reads the continued note text and likewise the second note reference reads the first note and so on. Eventually the last note is read at the end regardless it's note reference. It's a serious issue because not only the reading order needs to be fixed for the last note on the page that has splitting to the next column or page but also all the notes appearing on that page where the split portion has come in will also need to be fixed manually.

   To my mind It's a critical bug that is making InDesign unusable to create accessible content and needs to be addressed on highest priority.

   When a footnote split over to next page or column, the accessible PDF generated from InDesign CC 2023 has notes reading order messed up. The first note reference on the page where the portion of a note comes in from the previous page/column reads the continued note text and likewise the second note reference reads the first note and so on. Eventually the last note is read at the end regardless it's note reference. It's a serious issue because not only the reading order needs to be fixed for the last note on the page that has splitting to the… 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

   4 comments  ·  Accessibility  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. # in URLs of Hyperlinks in Hyperlinks panel is substituted with %23 when opened in browser from panel

   Hi together,
   when working with hyperlinks with URL destination an URL like:

   https://wiki.selfhtml.org/wiki/HTML/Elemente/a#Siehe_auch

   will not be transferred to the browser as is when the menu command "Go to Destination" is used or if the "green" bullet in the panel is clicked that indicates a correct and connectable hyperlink destination.

   Instead character # will be substituted with %23 like that:

   https://wiki.selfhtml.org/wiki/HTML/Elemente/a%23Siehe_auch

   The implication could be two-fold:
   [1] The browser could show an 404 error
   [2] The browser could not navigate to the named anchor and the view of the page is showing the top part of the page.

   The URL above will show error [2].
   This URL will show a 404 error:

   https://www.histaminintoleranz.ch/en/symptoms.html#zusammenfassung

   For the first error, the 404, I included screenshots and a sample InDesign document from InDesign 2023:

   Here the correct destination when the URL is copied to the browser:
   URL-CopiedToBrowser-CorrectPageView.png

   Hyperlinks panel showing the command "Go to Destination" in my German InDesign 2023:
   GoToURLinInDesign_Hyperlinks-Panel.png

   Result is this 404 error in the browser:
   GoToURLinInDesign_404-Error.png

   Test document where the hyperlink is attached to a rectangle:
   URLWith#ShowsAs%23Example-2CC-2023.indd

   FWIW: Due to restrictions of the UserVoice forum software the InDesign document could not be attached to this bug report. Instead I zipped it and tried to attach the zip file. Also this failed. So I added a *.txt to the file name:

   URLWith#ShowsAs%23Example-2CC-2023.indd.zip.txt

   Regards,
   Uwe Laubender
   ( Adobe Community Expert )

   Hi together,
   when working with hyperlinks with URL destination an URL like:

   https://wiki.selfhtml.org/wiki/HTML/Elemente/a#Siehe_auch

   will not be transferred to the browser as is when the menu command "Go to Destination" is used or if the "green" bullet in the panel is clicked that indicates a correct and connectable hyperlink destination.

   Instead character # will be substituted with %23 like that:

   https://wiki.selfhtml.org/wiki/HTML/Elemente/a%23Siehe_auch

   The implication could be two-fold:
   [1] The browser could show an 404 error
   [2] The browser could not navigate to the named anchor and the view of the page is showing the top part of the page.

   The URL above… 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

   7 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

   Submit Rating

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

11. Load DTD throws error in InDesign 2022 (17.0)

    When using the structure menu to load a DTD , the latest version of InDesign sometimes throws an error with a single period as the message. I'm using the same DTD I've used successfully in previous versions of InDesign.

    Error text:
    .
    Line 941, Column: 18

    In the context of this DTD, line 941 column 18 points to the % sign used to refer to an earlier parameter entity. This has never been a problem for InDesign before:

    <!ELEMENT sam (%paragraph_styles; | table | footnote | endnote)+ >

    Even using the same DTD in the same file, this issue doesn't always occur. I am typically able to get around the issue by scrolling around the document or clicking on text boxes, then simply running the tool again. It's unclear what could be causing this different behavior each time the tool is run.

    This also affects document.loadDtd in the scripting object model.

    When using the structure menu to load a DTD , the latest version of InDesign sometimes throws an error with a single period as the message. I'm using the same DTD I've used successfully in previous versions of InDesign.

    Error text:
    .
    Line 941, Column: 18

    In the context of this DTD, line 941 column 18 points to the % sign used to refer to an earlier parameter entity. This has never been a problem for InDesign before:

    <!ELEMENT sam (%paragraph_styles; | table | footnote | endnote)+ >

    Even using the same DTD in the same file, this issue doesn't… 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

    3 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

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

    The issue was fixed in InDesign 17.2

    Please update to this version or later to get the fix.

    
    

    --

    InDesign team

12. loading TOC-styles between various Indesign-files

    InDesign version 16.4

    When loading a newly created TOC-style from one InDesign-file to an other file, it copies more than just the possible TOC-styles. I loaded the TOC-styles of an InDesign-file with a smaller font and spacing and the load copied these other settings as well.
    It seems that the 'Load TOC-styles' loads all available styles, including Paragraph- and Character-styles.
    The selection-list that is available when loading Paragraph-styles and/or Character-styles is also missing.
    This makes it impossible to load TOC-styles between different InDesign-files which use the same Paragraph-style names.

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

    Submit Rating

13. [ID-4261147] Hyperlinks with alt text added in the accessibility section, the alt text disappears when you save the file as an .idml

    Hyperlinks with alt text added in the accessibility section get lost when saving to .idml.

    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  ·  IDML Export  ·  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

14. InDesign freezes while working with "Scale Tool"

    When using the "Scale Tool", every 4 or 5 times or so the app freezes at the dialog box and there's no way to exit. You have to force quit the app and hope that your work is autosaved. Unacceptable and only started happening recently.

    InDesign 15.1.1 on macOS Mojave 10.14.6

    HELP!

    • 

    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

    21 comments  ·  Crash/Freeze/Hang  ·  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

    We’re reviewing this issue.

    —
    Adobe InDesign team

15. IDML: missing Font Style property in Character Style after export

    Version: InDesign CC 2020 15.0.1

    How to reproduce the bug:
    1. Create a Character Style with "Bold" Font Style and apply it to a word/character range
    2. Save in INDD file format
    3. Export the IDML
    4. Open the IDML and you will notice that the bold property for the Character Style was lost

    Expected result: the Character Style should be the same as in the original INDD file

    Actual result: the "bold" property was lost during the export process. The INDD file is fine.

    I verified that InDesign CC 2019 14.0.3 is not affected by this bug.

    •  

    •  

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

    The fix for this issue is now available in the latest update of InDesign – that is, InDesign 15.0.2.

    Please update your InDesign application to get this fix.

    —
    Adobe InDesign team

16. Adobe Fonts automatically substituting versions of fonts that are document-stalled

    When I open an InDesign file that has been packaged with all the fonts (non-Adobe Fonts) included in the Document fonts folder, if I happen to have the same version of the font activated in Adobe Fonts, InDesign automatically, and without warning, substitutes the Adobe Fonts version. This is a major problem. The heirarchy should be document-installed fonts FIRST, then InDesign can look in Adobe Fonts and suggest replacing it. This should not be done without warning in the background. It means that the person who was working in a package workflow without using any Adobe Fonts can send a file to another person using Adobe Fonts, who unbeknownst to them, substitutes the font, then packages and returns the file, and now the font is missing from the new package when returned. This is a huge licensing issue at the very least.

    When I open an InDesign file that has been packaged with all the fonts (non-Adobe Fonts) included in the Document fonts folder, if I happen to have the same version of the font activated in Adobe Fonts, InDesign automatically, and without warning, substitutes the Adobe Fonts version. This is a major problem. The heirarchy should be document-installed fonts FIRST, then InDesign can look in Adobe Fonts and suggest replacing it. This should not be done without warning in the background. It means that the person who was working in a package workflow without using any Adobe Fonts can send a… 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

    Closed: Not Reproducible  ·  1 comment  ·  Print/Packaging  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    Submit Rating
    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

18. Generic check mark reappears in PDF check box after exporting to Acrobat Pro

    InDesign 14.0.2 and Acrobat Continuous 2019.10.20099

    This issue is about the behavior and appearance of interactive check boxes in documents that have been exported to Interactive PDFs.

    There is a difference in the way that check boxes created in InDesign behave and appear versus those created in Acrobat Pro. The Acrobat Pro Forms preferences are involved in this difference.

    When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is selected, check boxes created in InDesign behave and appear in the following manner.

    When a check box is made active, it first appears the same as the check box that was created in InDesign. When you tab to or select another check box, or when you save the selection in the PDF, the appearance of the check box reverts to a default generic check mark.

    When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is not selected, check boxes created in InDesign behave and appear in the following manner.

    When a check box is made active, it first appears the same as the check box that was created in InDesign and remains as such.

    This degrades the purpose of using the highlighted fields, which is to call attention to fields that need to be filled.

    When the check boxes are created in Acrobat, it makes no difference in appearance or behavior if the “Show border hover color for fields” is selected or not. They always appear as the checkbox style you have chosen to use. They do not revert to a generic check mark.

    This is the way that custom check boxes created in InDesign should behave. Thus, they would allow the use of a highlighted field without the appearance of the “selected” custom graphic changing to an unwanted generic graphic.

    Please refer to the InDesign Forums message at this link for examples:

    https://forums.adobe.com/message/11063952#11063952

    InDesign 14.0.2 and Acrobat Continuous 2019.10.20099

    This issue is about the behavior and appearance of interactive check boxes in documents that have been exported to Interactive PDFs.

    There is a difference in the way that check boxes created in InDesign behave and appear versus those created in Acrobat Pro. The Acrobat Pro Forms preferences are involved in this difference.

    When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is selected, check boxes created in InDesign behave and appear in the following manner.

    When a check box is made active, it first appears… 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  ·  PDF Export  ·  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

    Hi,
    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

19. Unable to package files - program freezes creating IDML

    Unable to package documents since 14.0.2 x64 update. Freezes on create IDML. When you try to cancel app hangs. Have to crash service to get the app to close.

    Windows 10 - 1809 17763.437

    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

    19 comments  ·  IDML Export  ·  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

    Thanks

20. Preserve Image Dimensions when Relinking and "Auto-fit" options do not seem to work.

    I am using Indesign 14.0

    When I relink files, Indesign changes the scale and placement of images automatically, regardless of whether the preserve image dimensions option in the file handling box is checked or unchecked, and whether the "auto-fit" button in the tool menu is checked or uncheked.

    Preferences > File Handling > "Preserve Image Dimensions when Relinking"

    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

    10 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

    Submit Rating
    Need More Info  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    Please describe the issue in more detail.
    What is the state of “Preserve Image Dimensions When Relinking” in Preferences – is it checked or unchecked? What is the state of “Auto-Fit” – is it checked or unchecked?

    —
    Adobe InDesign team