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

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

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

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




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

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

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




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




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

So there is a bug with Indesign 2020 causing Spell Check to not function.

This issue can be replicated by taking a file that was previously created in Indesign 2019 and opening it and saving in with Indesign 2020. Spell checking that document will not work. No matter what settings you try it doesn't recognize any of the text.

If you open the original document before converting it or working on it with 2020 spell check works perfectly.

You can also take a page from the 2020 document that isn't spell checking, Open a new file in 2020, cut and paste everything from that page and then spell check works.

The document behind in the attached screen shot is the cut and pasted page, showing spell check working. Both pages are in Indesign 2020.

This is a huge problem as you can't open 2020 files in 2019 without converting them, running spell check in 2019 and one by one going to the 2020 document and fixing each word. This is a total nightmare!

Anchored textframe with auto-sizing/auto-adjusting "height", text aligned to baseline and anchored object settings "anchored position: custom", "anchorPoint: bottom left/center/right" causes InDesign 2020 (15.0.1) to freeze (on Mac and PC).

1. create an new document (size doesn't matter)


2. create an new textframe (dimensions doesn't matter)


3. create a second textframe (dimensions doesn't matter)


4. insert some text in second generated textframe


5. select the text and apply the option "align to baseline".


6. anchor second textframe into the first created textframe


7. set anchored object settings of the anchored textframe to: "anchored position: custom" and "anchorPoint: bottom left or bottom center or bottom right"



8. select the anchored textframe




9. choose the textframe fit option "frame to content" or use the shortcut "strg + alt + c" on PC

InDesign 2020 freezes.

or repeat steps 1. to 8. and choose auto-sizing type "height" or "height and width" or "height and width proportionally" for the anchored textframe

InDesign 2020 freezes.

see attached screenshot. I can't attach a .indd or .idml file cause this is not allowed (error: invalid file type)

In previous versions (CC 2018, CC 2019) auto-adjusting "height" works as expected

Environment: InDesign 2020 (15.0.2 Japanese version) + macOS (confirmed with 10.15.3 and 10.14.6)

• create and connect two text frames


• set Auto-Sizing "Height and Width" on Text Frame Options


• Insert text into two frames full


• overlay graphic frames with Text Wrap settings ON


• move the graphic frame appropriately (drawing is not normal at this point)


• close documents with Command + W

During this operation, you will usually be asked to confirm the save, but suddenly InDesign will end and the application will crash.
Also, if you try while overwriting with Command + S without Command + W, you may not be able to save eventually.

This problem does not occur on Windows version.
As a comparison, the same operation was performed with the English (North America) edition on macOS, but no problem occurred.
Therefore, it is highly possible that the problem is unique to the Japanese edition.

Original trouble posted Adobe Community.
(There is a other post about User Voice, but this is a different issue.)
https://community.adobe.com/t5/indesign/indesign2020%E3%81%AE%E4%B8%8D%E5%85%B7%E5%90%88%E3%81%A7%E3%81%AF/m-p/10935672

InDesign file is prepared separately.
https://adobe.ly/3agg1u8

The inclusion of ~F in a character class invalidates grep expressions in endnotes.

InDesign version: 14.0.2.324 (with the GREP fix installed)

Steps to reproduce:

1. Open the attached document. It contains a single page with text and an endnote.


2. In the GREP tab of the Find/What window, enter the following GREP expression:

\d[^.,;~F]+

And target the document. The expression matches from a digit up to the next period, comma, semicolon, or footnote marker.

Expected result: The expression should match some text in the main text and in the endnote.
Actual Result: The expression does not match anything in the endnote.

To show that it's ~F that's the problem, use this expression:

\d[^.,;]+

It matches in the main text and in the footnote, as expected.