I just did the 2018 update, so I think it's the most recent version: 13.0 x64

I have a document template that contains many character and paragraph styles with export CSS tags that contain the lowercase ‘i’ in them. This character is being exported as a blank space, which completely breaks the CSS, like this:
should be: <p class="bright"></p>
getting: <p class="br ght"></p>

This problem was easily replicated in a fresh new document, so it’s something with InDesign, rather than my template file.

This workflow involves complex style mapping through to CSS classes. Because so many of the classes contain the character 'i', this problem has brought the workflow to a dead halt.

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.

• 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

I'd like to report a bug. Please follow the scenario below:

1. In a single column with lots of text in it, make two columns for a fragment of text

2. In text within the two-column setup, make a footnote. Add several lines of text to the footnote

3. Turn on the "Span Footnotes Across Columns" feature so that footnote ends up in the same group with the footnotes at the bottom of the page rather than below the two-column fragment

4. Expected behaviour: normal editing can be performed after these manipulations

5. Observed behaviour: any text editing after turning on the "Span Footnotes Across Columns" feature becomes lethargic and near impossible. Turning this option off immediately solves the speed issues.

Please log a bug to fix this behaviour.

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

Hi developers,
this is a longstanding bug:

With facing pages documents on EVERY document page there is a zone where jumping of objects will happen.

I call this the jump zone. All objects on a page that will jump are clearly inside the page's area. The bug has nothing to do with rounding errors where object edges are at the edge of a page.

The objects should not move if pages are added or removed, if numbering of pages is changing. Nevertheless they do. Always. Unless, the zone has a width of zero.

Below all the details.

What is a jump zone?
If horizontal values for left and right margins differ, there is a BUG that in effect forms a zone on the page.
I call this zone JUMP ZONE because objects that touch the zone with their edges could jump horizontally.

When will objects jump?
1. When a left-hand page becomes a right-hand page OR a right-hand page becomes a left-hand page.

1. When a left-hand page becomes a right-hand page and later when a right-hand page becomes a left-hand page again.

This could happen within a single InDesign document open.

WARNING:
It could even happen to InDesign documents that are not visibly open.
That's with InDesign documents that are part of a InDesign book file.
The book file's feature with auto-numbering pages can do this even if no document is visibly open.
The damage is done if auto-numbering took place AND the book file is saved.

How large is the jump zone?
The height of the zone is the height of the page.
The width of the zone can be calculated:
inner margin MINUS outer margin

How large is the jump?
The width of the jump zone.

Where is the jump zone positioned?
Positive value: The zone is at the spine of the page.
Objects that touch the zone jump towards the spine.

Negative value: The zone is at the edge of a page away from the spine.
Objects that touch the zone jump away from spine.

What versions of InDesign are affected?
All versions CC up to InDesign 2020, Mac OS X and Windows.
InDesign CS6, Mac OS X and Windows.

Possibly also InDesign CS5 and CS5.5, Mac OS X and Windows.
I did not test this.

How can I avoid jump zones?
Make right and left margin values the same!

Are there workarounds if I cannot avoid jump zones?

1. Anchor objects
   that touch the jump zone to text frames that do not touch the jump zone.
   Nested objects will not jump if the parent objects are not touching the jump zone.

2. Group an object
   to another one that is touching the top or the bottom edge of the page.
   Tests are showing that objects will not jump if they touch the bottom OR the top of the page.
   ( OR both, bottom and top edges of the page .)

Other things to consider about moving objects?
The following is independently of jump zones:
Objects could move to other pages if their edges touch exactly the horizontal edges on pages in facing pages.
Depending on the version of InDesign this could also happen with objects touching the spine.
Reason: Rounding errors.

What can provoke all this?
1. Add or remove an odd number of pages
so that left-hand pages become right-hand pages and vice versa.

1. Renumber start pages of sections so that left-hand pages become right-hand pages and vice versa.

Note:
Every document has at least one section by default.
The start of that section is the first page in the document.

More details at Adobe InDesign Forum:
https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774458#M166408

InDesign 2020 documents attached here.
See screenshots and further comments at Adobe InDesign Forum:
https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774596#M166420

Download link to all test files on my Dropbox account:
https://www.dropbox.com/s/duov096cu2q481l/Jump-Zones-Explained-Facing-Pages-Documents.zip?dl=0

Regards,
Uwe Laubender

( ACP )

PS: Why does InDesign Uservoice not permit to attach files with suffix .indd ?
Message: "Invalid file type: .indd files not allowed."
Isn't that rather absurd?

Using CC2019 on a Mac running High Sierra

Steps to reproduce:
1) Create a document with a few hyperlinks in it.
2) Whilst this document is open, open a 2nd document, and copy/paste the links from one document to the other.
3) Save both and close.
4) Trash source document

Expected result: hyper links should work in Target document as expected.

Actual result: hyperlinks all appear broken in document. Whilst an exported PDF appears to still work, ID reports all those links as broken.

Other details:
If you retrieve the source document from the trash, it the links in the target document suddenly start working again, meaning your not actually pasting the hyperlink, but theres some sort of link that exists between the source and target document.

Saving target file as a new file, saving as idml, has no effect – those links are still tied to the source document.

This in an absolute tragedy if you are working on large documents with lots of links, and needs fixing ASAP