InDesign sometimes, seemingly randomly, replaces pairs such as hn, il, io, sy, ek, etc. with completely wrong glyph, such as accented Y, U, etc., when regular Ligature setting is applied. This has been a problem since CS5 and we recently had it occur in CC2015, so it is still there. Affected fonts have been many over the years, including licensed Adobe fonts. Fonts can be Open Type or PostScript. Language setting can be English US, UK, or seemingly anything else. The only thing that works to avoid it is to turn off Ligatures which is generally unacceptable, so the only workaround is a targeted GREP style to apply ligatures to only the pairs that should have them for that file. This is a long-standing problem which has been reported in forums various times and needs to be addressed. There is no sure fire way to reproduce the bug. Only thing that sometimes works is to brute force load/unload fonts until the problem occurs. It seems that once the problem occurs the first time it may then become more frequent on that computer. I know someone who has even seen the effects of this problem in printed material (i.e., in a book they were reading).

Machine: MacBook Pro 13 in mid-2012 (i7, 2.9 GHz, 16 GB RAM)
OS: macOS 10.13.4
App: InDesign 13.1.0.76 (but basically every subversion of 13)

1. I have several INDBs containing from 6 to around 20 INDDs each.




2. Most INDDs contain from 3 to 60 cross-references (since book-spanning TOCs often crash InDesign, but that’s for another topic) – mostly within the respective INDD, but one INDD per book always has CRs to other INDDs within the same book or in other books.
   (My typical INDD contents: 2–48 facing pages with threaded, 1-column text boxes, therein several dozens of “custom” anchored objects, mostly containing text and auto-resizing in height, some containing linked INDDs or dynamic captions. Everything tidily formatted with object, paragraph, and character styles with moderate use of GREP styles.)




3. I try to open more than one (or every) INDD from the book panel in one go (select & shift-select several chapters, double-click on one of the selected).




4. A couple files open, and with the first one to contain modified links …




5. … I click “Don’t update links” (but it’s the same if I click “Update links”).

InDesign reliably crashes faster than the sound waves from the mouse click reach my ear.

This never happens when I open (double-click from the book panel) one INDD at a time from the book panel.

InDesign CC shows obscure behavior for Arabic subtending marks. Some times it kerns these marks towards right as shown in line 1, 3 & 4. Sometimes it adds extra space on both sides of these glyphs as shown in the line five and sometimes it automatically makes the digits size smaller as shown in line 1 & 2. While MS Word 2013 shows the correct shapes for all these marks as required. The Arabic script is written in right to left direction.
Image shows the correct shape in MS Word 2013 and wrong behavior in InDesign CC.
Test font and test document are also attached.

While working on an Arabic font I need to kern the space U+0020 between certain letters. So the required lookup is added to the font, with instructions to apply kerning whether the preceding letter have marks (above or below) or no marks at all i.e. the kerning is not effected by the preceding letter's marks. The Arabic script is written in right to left direction.

Now the MS Word is showing the correct behavior as shown in the image. The first pair (without marks) and the second pair (with brown marks) both are kerned as instructed by font but the InDesign CC is not showing the correct behavior as InDesign is kerning the first pair (without marks) but not the second one (with marks). This problem appears only when we try to kern space U+0020 while the other adjacent letters kerning works fine as instructed by font with marks or without marks.
Image, test document and test font are attached.

Conclusion: In InDesign, the Arabic kerning works fine between paired letters but if you want to kern space U+0020 then the kerning will not work if the preceding letter contains above or below marks.

For experts: The lookup flag is to process all marks with the exception if the letter after space has below marks. So if the letter after space has below marks then the kerning should not work.

system: mac-osx-10.12.6 (sierra)
software: indesign-cs6 ver 8.0
software: indesign-cc(2018) ver 13.0.0

when in gpu-preview mode … center-line 'node' does not appear. when in cpu-preview mode … center-line 'node' does appear. the center-line 'node' has appeared in cs-versions and previous versions … and disappeared in the cc-versions.

i have outlined the steps, and included screen-caps, to reproduce the issue within my post to adobe-forums:
https://forums.adobe.com/thread/2492437

further info about my environment:
Model Name: iMac
Model Identifier: iMac18,3
Processor Name: Intel Core i5
Processor Speed: 3.4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
Boot ROM Version: IM183.0153.B00
SMC Version (system): 2.41f1
Serial Number (system): <<<censored>>>
Hardware UUID: <<<censored>>>

I like to layer different styles of content. I'll have a background layer for images, etc., that I want to not touch later so I can lock/unlock while I work with my content over the top of it. Sometimes, I accidentally am in the background layer and create content that needs to be moved to another layer. I would love for a feature like Illustrator that allows me to highlight an object or group of objects, click an opposing layer, and then right-click > arrange > move to selected layer.

Also, there is a slight bug I've found, but it doesn't crash and I can work around it: When I have grouped objects, and I copy and paste them into a new layer, they appear to be in the new layer; however, if I ungroup them, they automatically de-group back into their original layer before I copied and pasted them. Does that make sense? That feature I mentioned above would fix this, but either way, this bug is kind of annoying because then I have to go back and copy and paste the ungrouped objects back into the new layer I wanted them in. Might be unclear, but I just ran into this issue today.