196 results found

1. QR-Code Generator Problems with Umlauts in vCards

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

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

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

   please see attached one example

   Kind regards from germany

   Max

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

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

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

   please see attached one example

   Kind regards from germany

   … more

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   78 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

   48 comments  ·  Others  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under Review  ·  amaarora responded

   Thanks for reporting. We will review the issue shortly

   -InDesign Team

2. Anchored text box in a table cell with text threads crashes when cutting

   As the title says. It sounds similar to past bugs.

   First, create a text box and add a table.
   Create a separate, new text box and add a single character in it.
   Anchor the text box to any cell in the table.
   Enable "Show Text Threads" from the View > Extras menu.
   Selecting and attempting to cut the table will lead to a long hang and crash.

   This is on the latest version of InDesign at the moment, 17.0. I am on Windows 10 20H2 19042.1288. I can verify this occurring on two separate systems.
   I've included a video walking through the steps to reproduce the crash.

   As the title says. It sounds similar to past bugs.

   First, create a text box and add a table.
   Create a separate, new text box and add a single character in it.
   Anchor the text box to any cell in the table.
   Enable "Show Text Threads" from the View > Extras menu.
   Selecting and attempting to cut the table will lead to a long hang and crash.

   This is on the latest version of InDesign at the moment, 17.0. I am on Windows 10 20H2 19042.1288. I can verify this occurring on two separate systems.
   I've included a video walking… 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

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

   • 

   •  

   •  

   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

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

   Thanks for reporting. We will review the issue shortly

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

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

   —
   Adobe InDesign team

5. object style override plus-sign when multiple elements selected

   Object style made. Works fine.
   Multiple items on page need same style. When applied to ONE item, styles menu looks "normal." When applied to multiple items, with items selected, the styles menu shows plus-sign after style name.
   All of "clear overrides" options tried. Does not fix. Cannot verify that use of style is correct if styles panel gives false feedback.
   In the past, earlier versions, I don't remember ever seeing this apparent conflict.
   MacOS 11.5.2
   InDesign 17.0.1

   •  

   •  

   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  ·  Styles  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   Thanks for reporting this issue.

   We are going to review this shortly.

   
   

   --

   InDesign team

6. CEPHtmlEngine Helper

   macOS Catalina 10.15.5. and InDesign. 15.1.1.

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

   •  

   •  

   •  

   39 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

   51 comments  ·  Performance/Usability  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   This issue is being reviewed again.

   —
   Adobe InDesign team

7. JPG 300dpi export with horizontal lines

   When I export photo albums as JPG with the latest version, some images have horizontal lines. I've had the problem since macOS 10.14. (now catalina) and with older Indesign versions. If I change the size or position of the image, the stripes may disappear. If I use the DPI e.g. set to 301, the lines will also disappear.

   •  

   •  

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

   Thanks for reporting. We will look into the issue shortly.

   -InDesign Team

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

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

   10 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
   Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, 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

10. Exporting to ePub (reflowable) when document has endnotes containing hyperlinks causes InDesign to hang

    Version of Adobe InDesign: 15.1.2 / macOS 10.15.6

    Steps to reproduce the issues: When exporting a document with endnotes containing hyperlinks to ePub (reflowable), InDesign hangs and needs to be force quit. Have tested removing all hyperlinks to tests, and document exports correctly. Have tested putting hyperlinks outside of endnotes and document exports correctly. The bug is specific to hyperlinks which are part of the endnote text.

    Expected result: Successful export with endnotes reciprocally linked to text, and hyperlinks in endnote text active to respective URLs.

    Actual result: InDesign hangs and needs to be force quit.

    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

    13 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
    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. Shortcuts for view at 200% 400% & 50% not working correctly

    Windows 10 - Indesign CC 16.4 (only just updated today 8/10)

    Issues - shortcuts
    Ctrl+5 (view @ 50%)
    Ctrl+2 (view @200%)
    Ctrl+4 (view @400%) not working properly.

    Ctrl+5 is now view @ 33.33%
    Ctrl+4 is now view @ 266.67%
    Ctrl+2 is now view @ 133.33%

    The issue doesn't seem to be a thing for Mac, they work fine.

    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  ·  Document/Pages  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

    Thanks for reporting this issue.
    We are going to review this shortly.

    —
    Adobe InDesign team

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

13. Exclude color fields in book synchronization synchronized nevertheless

    I have book files and do not want to synchronize the colors. I disable this in the synchronization options.
    The colors will still be transferred/synced to all synchronized documents.
    ID CC 2018/2019/2020

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

    Thanks for reporting the issue. We are reviewing it

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

    • 

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

    We’re reviewing this issue.

    —
    Adobe InDesign team

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

    Thanks for reporting. We will review the issue shortly.

    -InDesign Team

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

    Thanks for reporting this issue. We will review it

    -InDesign Team

17. PDF comments: Delete <FEFF> marker after removal of all comments

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

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

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

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

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

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

    34 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 Comments  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue shortly.

    -InDesign Team

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

    •  

    •  

    10 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. We will review the issue

    -InDesign Team

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Styles  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Under Review  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

    Thanks for reporting. We’ll review this shortly.

    —
    Adobe InDesign team

20. Exporting accessible PDF – wrong BoundingBox

    InDesign Version: All

    Background:
    An accessible PDF needs for all graphics and pictures a bounding box.
    This is used by AT e.g. to set a focus to a visual impaired user.
    Using the PDF export a bounding box is defined for all linked images.

    Problem:
    Often the bounding box does not fit to the visible area.
    AT user get wrong information, in fact the file is not accessible.

    Steps to reproduce the issues:
    Place an asset, where only a part of the linked asset is visibily placed in InDesign, the rest is cropped.

    Expected result:
    Bounding box fits to visible area

    Actual result:
    The bounding box is bigger than the visible area, if the assets content is bigger than the area show.

    Workaround:
    You can fix this in Acrobat theoretically, but this is nor real workaround as you only edit values and dont have visual feedback.

    Attachement:
    InDesign sample files and accessible PDF with bounding box example + visible error.

    InDesign Version: All

    Background:
    An accessible PDF needs for all graphics and pictures a bounding box.
    This is used by AT e.g. to set a focus to a visual impaired user.
    Using the PDF export a bounding box is defined for all linked images.

    Problem:
    Often the bounding box does not fit to the visible area.
    AT user get wrong information, in fact the file is not accessible.

    Steps to reproduce the issues:
    Place an asset, where only a part of the linked asset is visibily placed in InDesign, the rest is cropped.

    Expected result:
    Bounding box fits to visible… 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

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

    Thanks for reporting the issue. We will review the bug shortly

    -InDesign Team