Just updated to ID 2020 15.1 and found a bug which makes the program unusable forcing me to immediately downgrade.
When I open on of my ID documents created in previous version of ID, all of my defined text variables as well as page numbers are corrupted and replaced by the "ss" text. Changing the style has no effect. I can create page number based on the 'Basic Paragraph' style but when i choose any other previously created style, the number changes to 'ss'.
Even the variable field preview shows 'ss' text instead of variable name.
The same document opens in ID 2020 15.0.3 without any problems.

When exporting a PDF with the Japanese version of InDesign for Mac, the Osaka font is used for the characters in the page information. If there are voiced or semi-voiced sound marks of Japanese characters in the file name, an error will be displayed and the characters will be garbled because Osaka does not support those characters.

1. Name the indd file "だじづでど.indd".


2. Export the PDF.


3. An error is displayed and the file name of the page information is garbled.

Osaka is no longer a very old font on the Mac. Don't use Osaka now.

Use a font that supports semi-voiced sound marks to prevent errors. Illustrator already uses KozGoPr6N-Regular to prevent errors.

Japanese:
PDFのページ情報にOsakaフォントを使わないでください

日本語版のMac版InDesignでPDFを書き出すと、ページ情報の文字にOsakaフォントが使われます。ファイル名に日本語の文字の濁音や半濁点があると、Osakaがそれらの文字に非対応なので、エラーが表示され、文字化けします。

1. inddのファイル名を「だじづでど.indd」にします。


2. PDFを書き出します。


3. エラーが表示され、ページ情報のファイル名が文字化けします。

MacではもはやOsakaはとても古いフォントです。今はOsakaを使わないでください。

半濁点に対応したフォントにして、エラーを防いでください。IllustratorはKozGoPr6N-Regularを使ってすでにエラーを防いでいます。

Problem Description:
Querying navigation points inside a movie trigger errors from InDesign 16.

Steps to Reproduce:
1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

var btn = app.activeDocument.buttons[0];
var beh = btn.behaviors[0];
var mov = beh.movieItem;
var navPts = mov.navigationPoints;
try{

alert(navPts.length); /*doesn't exist*/

}catch(err) { alert([err,err.line])}

try{

alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */

}catch(err) { alert([err,err.line])}

alert(navPts.everyItem().getElements().length); /incorrectly says zero, when there are 2 navigation points/

Actual Result:
Each produces two separate errors.

Expected Result::
Both should be valid queries.

Any Workarounds:

No. Expected functionality is simply missing.

movie.navigationPoints.everyItem().getElements().length at least doesn't produce an error, but it also doesn't include navigation points.

This feature was added back to InDesign, but the scripting of it was neglected. I've filed a bug in prerelease as well. Posting here so others are aware.

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.

WHAT THE FONT!?!

Our publishing company recently ran the InDesign update (to 15.0.2) and have discovered some major font issues. I have narrowed it down to InDesign 15.0.2, macOS Catalina 10.15.3, and Suitcase Fusion 21.0.0. I actually don't think Suitcase has too much to do with this, because the problem occurred after the InDesign update, but it's our font management software so I'm including it. Basically it appears system fonts have become problematic with InDesign. Packaged files are suddenly showing up with lots of the dreaded pink. I have tested about everything I can. I even created some very simple type only files that are having system font issues as well. Sometimes the document will open ok and the fonts will appear fine. Then when I go to export, the system fonts turn pink. Sometimes the file can't open the fonts at all and they start out and remain highlighted pink. Other times it will open but them shut off a few seconds later. It's only happening with system fonts. I have included screen shots for reference. I hope this issue can be fixed asap because it's font chaos over here! Thank you.

Color Mode changes from whatever is set in InDesign when switching app from Adobe Photoshop to InDesign (latest versions) ... I am getting the same problem when switching from Photoshop to the latest Illustrator as well.

Problem Occurs even when InDesign (and Illustrator) are both shut down. After launching Photoshop and then shutting Photoshop down, Color Settings in InDesign and Illustrator are both changed to "Emulate".

PLEASE FIX IMMEDIATELY!!!! THIS IS A HUGE PROBLEM and impacts my workflow horribly as I am back-and-forth between these applications regularly.

I have checked Bridge as well... and default is set to North American Prepress 2.

Running:
InDesign 16.1
Photoshop 22.3.0
Mac OS 10.15.7

• InDesign 15.1.2 / Mac OS 10.15.6

• Create an InDesign document with Arabic content. Apply any Arabic font.

• When exporting to EPUB (Fixed Layout) we should see the Arabic text appear in the epub viewer in similar manner as it shows in InDesign document.

• The exported epub document is viewed in Apple's Books application, and Adobes Digital Editions 4.5 with similar problems in both epub viewers, where all Arabic text is either invisible or messed up and shifted from its location.

• Attached images from InDesign document, and epub file which was exported from InDesign.

• Links from InDesign forums on the same topic…
https://community.adobe.com/t5/indesign/arabic-text-no-showing-on-epub-fixed-layout/m-p/11406882?page=1

https://community.adobe.com/t5/indesign/arabic-text-not-showing-upon-export-to-epub-on-version-15-1-1/m-p/11384957?page=1

https://community.adobe.com/t5/indesign/arabic-epub-issue-from-indesign/m-p/10818486?page=1