221 results found

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

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

   Hi,

   The issue is under review.

   —

   Adobe InDesign Team

2. [ID-4250752][MAC]Page numbers cut-off in Page panel when viewing in Horizontal mode

   Currently on Mac OS Big Sur using inDesign 16.1

   When viewing the pages panel in horizontal view and the page count exceeds what the panel can hold the scroll bars appear but then the last row of pages seem to have their page numbers hidden behind the UI and are not visible no matter how much you move the scroll bars down.

   I have seen this behavior since inDesign 15 on Mac OS Catalina.

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

   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

3. Crash while export to JPG

   indesign 16.2 (mac version) crashes every time exports jpg and it tries to overwrite existent jpg

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  PNG/JPEG/EPS 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,
   We have been able to reproduce the issue and it is currently under investigation.

   —
   Adobe InDesign Team

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

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

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

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

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

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

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

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

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

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

   … more

   •  

   •  

   •  

   •  

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

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

   —
   Adobe InDesign team

5. Find/Change Text dialog does not show all Search options.

   after making a selection, the Find/Change text dialog sometimes does not offer Selection in the Search dropdown. It will be present under GREP and Object, but not Text and Glyph. Closing/reopening Find/Change does not fix it. Restarting InDesign usually fixes it...until it goes missing again.

   •  

   • 

   40 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Submit Rating

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

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

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

   •  

   13 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Hi,

   Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation. 

   —

   Adobe InDesign Team

7. Serious GREP style bug: ampersands

   Hi, InDesign team.

   I've run into a serious bug with GREP styles. Any GREP expression containing an ampersand character that is entered as a GREP style in a paragraph style will suddenly acquire additional ampersands whenever I scroll through the list of GREP styles.

   STEPS TO REPRODUCE:

   Create a simple GREP style as part of a paragraph style.
   The entire GREP expression should consist of the single character &. (Though this also happens when the & is part of longer expressions.)
   Make enough other GREP styles that you need to scroll in the window to see them all.
   Close the paragraph style window and reopen it.
   Scroll through the list of GREP styles.
   When you scroll, you will see that "&" has become "&&."

   HERE ARE OTHER DESCRIPTIONS OF THIS ISSUE:

   https://community.adobe.com/t5/indesign/ampersand-gets-doubled-in-grep-style/td-p/10329693?page=1

   https://community.adobe.com/t5/indesign/self-propagating-ampersands-in-grep-in-a-paragragh-style/td-p/5881764?page=1

   https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/36196819-paragraph-style-grep-functions-are-unreliable

   I believe I have gotten around the bug by using the Unicode value for an ampersand, but this is not ideal. I need to be able to trust that the GREP style implementation is solid.

   Thank you.

   Hi, InDesign team.

   I've run into a serious bug with GREP styles. Any GREP expression containing an ampersand character that is entered as a GREP style in a paragraph style will suddenly acquire additional ampersands whenever I scroll through the list of GREP styles.

   STEPS TO REPRODUCE:

   Create a simple GREP style as part of a paragraph style.
   The entire GREP expression should consist of the single character &. (Though this also happens when the & is part of longer expressions.)
   Make enough other GREP styles that you need to scroll in the window to see them all.
   Close the… more

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

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

   Thanks for reporting. We’ll review this shortly.

   —
   Adobe InDesign team

8. [ID-4224415]Accessibility Tags order to match in InDesign and PDF

   Accessibility tag tree is not matching as per InDesign XML tag structure. We are doing more manual work to re-arrange the tag tree as per PDF view in Acrobat. We need to fix this bug in InDesign and match the tag tree as per InDesign tag structure for the accessibility PDF.

   Attached sample file and screen shot FYR....

   • 

   •  

   •  

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

   Thanks for reporting. We will review the issue shortly

   -InDesign Team

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

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

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

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

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

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

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

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

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

    A… more

    17 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue

    -InDesign Team

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

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

    1 Version
    16.0.1(macOS10.14/10.15.6)

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

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

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

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

    1 Version
    16.0.1(macOS10.14/10.15.6)

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

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

    4 Actual result
    The indent… more

    •  

    •  

    95 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review it

    -InDesign Team

12. Text formatting can break backlinking endnote texts to endnote refs when exported to PDF (Print)

    Hi together,
    to explain the issue:

    Sometimes backling from endnote text to endnote reference number will not work.

    To make it work at all I found the following minimum requirements for PDF export:

    PDF Export (Print)

    Compatibility: Acrobat 5 (PDF 1.4)

    [x] Create Tagged PDF

    [x] Hyperlinks enabled

    Even with that sometimes only linking from the endnote reference number to the endnote text will work, but not backlinking from the endnote number in the endnote text to the reference in the main text.

    What I found:

    If you want linking back from the endnote number at the start of the endnote text you have to be careful with formatting of that endnote number which in fact is a special character.

    WHAT WORKED:

    The endnote is using a paragraph style without any specialities. No overrides, no character styles applied:

    RESULT: No issue with linking back and forth between endnote reference number and number in the endnote text.

    Now I had the idea to format that special character, the number that starts the endnote text with a character style.

    RESULT: Linking from the endnote reference number to the endnote text worked. BACKLINKING DID NOT WORK.

    MORE DETAILS IN THIS THREAD:

    Endnotes not exporting with links to PDF
    Mr_Wonderstuff, Nov 18, 2020

    https://community.adobe.com/t5/indesign/endnotes-not-exporting-with-links-to-pdf/m-p/11628582#M40545...

    https://community.adobe.com/t5/indesign/endnotes-not-exporting-with-links-to-pdf/m-p/11628643#M40546...

    WHAT BROKE THE BACKLINKING:

    [1] Character style applied through a GREP Style

    [2] Character style applied directly as formatting

    [3] Properties directly applied as overrides without a character style

    WHAT FINALLY WORKED:

    [4] Character style applied as nested style through the applied paragraph style:

    Character style to 1 tabulator character

    I did not test on to eliminate other factors.

    Maybe one of the used properties are the real culprit?

    What I defined in that character style and also tried to apply as character override was:

    Character width and height: 70%

    Baseline Offset: 2 Pt

    Fill Color: "C=100 M=0 Y=0 K=0"

    Regards,
    Uwe Laubender

    ( ACP )

    All InDesign 2021 test documents and the exported PDFs. Also the used joboptions-file can be downloaded from my Dropbox account:
    https://www.dropbox.com/s/k2bwr5ljvhde4vx/201127-1-Backlinking-Endnote-Refs-and%20Endnote-Texts.zip?dl=1

    Hi together,
    to explain the issue:

    Sometimes backling from endnote text to endnote reference number will not work.

    To make it work at all I found the following minimum requirements for PDF export:

    PDF Export (Print)

    Compatibility: Acrobat 5 (PDF 1.4)

    [x] Create Tagged PDF

    [x] Hyperlinks enabled

    Even with that sometimes only linking from the endnote reference number to the endnote text will work, but not backlinking from the endnote number in the endnote text to the reference in the main text.

    What I found:

    If you want linking back from the endnote number at the start of the… more

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Thanks for reporting the issue of backlinking not working for Endnotes with WR Composers.
    We’re going to review this shortly.

    —
    Adobe InDesign team

13. [ID-4260994]The filter in the review panel is automatically changing to "resolved"

    This happens very frequently.

    I will be going through user comments given online in the Indesign Review tab. As I do them I resolve them. This works fine.

    But then suddenly and randomly it will just decide to change my filter to show all resolved! Then all the old issues magically appear in the tab again until I go back to filter and unselect the Resolved button.

    Then it happens again. And again. It happens only when I go to change something in the document but it doesn't seem to matter what type of issue i'm doing. Replacing text. Deleting, etc.

    I'm also finding that comments are taking a few minutes to get from the web into indesign as i keep seeing the little wheel turning a lot.

    This happens very frequently.

    I will be going through user comments given online in the Indesign Review tab. As I do them I resolve them. This works fine.

    But then suddenly and randomly it will just decide to change my filter to show all resolved! Then all the old issues magically appear in the tab again until I go back to filter and unselect the Resolved button.

    Then it happens again. And again. It happens only when I go to change something in the document but it doesn't seem to matter what type of issue i'm doing. Replacing text. Deleting,… more

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  Share for Review  ·  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. Endnotes are tagged incorrectly when exporting to Accessible PDF from InDesign 2021

    In InDesign 2021, endnotes are not nested inside of a <Note> tag like they should be. Now only the Endnote number is in a <Note> tag and everything else is in a <P> tag. Normal behavior is to put each Endnote in its entirety within a <Note> tag. In addition, for several versions Endnotes and Footnotes are in a <Note> tag but then there's a <P> tag within the <Note> tag. The <P> tag is unnecessary and causes an error when trying to validate Accessible PDF. Please remove the <P> tag within <Note> tags when exporting to tagged PDF.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    —
    InDesign team

15. Translation bug : Spread -> Grossi instead of Planche (in french)

    1. Click on publish online button Single Page is well translated as "Un(e) seul(e)" (page) Spread is wrongly translated as "Grossi" Grossi means bigger (or what we had with trapping : spreading inks, so making ink marks bigger) Planche which has been the accepted term in inDesign for ages.

    (also known as 09/01/2017 #ID-4199114)

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting this issue. We will review it

    -InDesign Team

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

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

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

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

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

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

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

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

    PLEASE FIX ASAP!
    Thanks

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

    1. Versions with this bug, tested and confirmed by myself or colleagues:
       InDesign (Standard Version) CS6, CC2015.0
       InDesign (Middle Eastern Version) CC2020… more

    •  

    •  

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue

    -InDesign Team

17. Drop shadow in exported PDF is a different size

    Certain drop shadows have a different size when they appear in an exported PDF.

    In the attached example, the black shapes each have a drop shadow effect in yellow. When exported, the shadows appear shorter and narrower. The difference is approximately 20 pt narrower and 1 pt shorter. (Note the difference in proportion of the yellow drop shadow and black shape in the screenshots.) I've also included the drop shadow effect attributes.

    This occurs with multiple PDF export settings including the default [High Quality Print]. I am able to reproduce this behavior in both InDesign versions 15.1.2 and 16.0.

    •  

    •  

    •  

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Thanks for reporting. We will review the issue shortly.

    -InDesign Team

18. Translation typo

    Your missing a capital on the "commentaires" option in the French translation of window menu

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  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
    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. GREP position marker "^" = Beginning of Paragraph (not beginning of a new line after a forced line break)

    Dear Support,

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

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

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

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

    Dear Support,

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

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

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

    •  

    18 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We will review it shortly

    -InDesign Team

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

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

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

    Thanks for considering addressing this behavior.

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

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

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Hi,

    Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation. 

    —

    Adobe InDesign Team