There are multiple listings of the same font in the Find Font menu in CC2019. All information is the same, all applied characters are the same, but there is odd behavior.

--FileACC2019WithDocumentsfontsfolder.png shows double listing of Trade Gothic LT Pro Roman.

--FileACC2019WithoutDocumentfontsfolder.png (when I take away access to Document fonts folder, no other changes), one instance switches to "Regular" instead of "Roman"

--FileACC2017WithDocumentfontsfolder.png shows what happens with I open this file in CC2017 (no double listing)

--FileACC2017WithoutDocumentfontsfolder.png (Document fonts folder hidden) shows what happens with I open this file in CC2017 (no double listing)

I process large volumes of files; this is not an isolated incident nor a corrupted file. Packaging results in InDesign only grabbing the single correct font file, so that isn't broken. This behavior with Find Font is seemingly new to CC2019 (I'm working on 14.0.2). The multiple listing of same font, variation of font name when fonts enabled/disabled, and Find Font showing fonts missing that aren't because of what seems to be a name issue in Find Font. Has something changed in the way that InDesign reads fonts/accesses Document fonts folders?

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

In CC2020 a new function for writing alternate text for links was introduced.
Using this function and generating a PDF Leeds to wrong PDF notation. The alt text in PDF is presented by alt text, which is forbidden in the PDF world, where alt text only should be used for non text elements, e.g. pictures. By presenting only the alt text the accessibility is lost – this is against the goal to hav a better output!
A correct output would lead to a content entry.

Note: Alt text for links is under discussion, as such alt text is not present for all users (it would be read out loud, but you can't read it) – this is not about equal access.

Thanks for fixing, this would be a good step for all people relying on accessible PDFs.

Best, Klaas

Adding Hunspell dictionaries breaks code-signing, and results in the whole of InDesign's spelling system being sand-boxed by OSX.

Steps to reproduce:

1. On High Sierra and InDesign CC, add a Hunspell dictionary, as detailed here: https://helpx.adobe.com/indesign/kb/addcsdictionaries.html




2. Spell-check any InDesign document using the new dictionary and spell-checking then becomes unusable, until InDesign is uninstalled then re-installed.

The following types of errors are produced in the console, showing that it's a code-signing issue, caused by dictionaries being installed within the Hunspell plugin bundle.

Can I suggest that there should be another place to install additional languages, outside the InDesign application.

The only way I can work with Latin and Ancient Greek languages currently is to use an El Capitan Mac, which does not have the sandboxing.

AMFI: Check-fix enabled for binary '/Applications/Adobe InDesign CC 2018/Resources/Dictionaries/LILO/Linguistics/Providers/Plugins2/AdobeHunspellPlugin.bundl e/Contents/MacOS/AdobeHunspellPlugin' with TeamID 'JQ525L2MZD', identifier 'com.adobe.adobehunspellplugin2': broken signature treated as unsigned without privileges. This workaround will not work for software built on or after 10.12.

The Prevent Manual Positioning creates a Locked Object, but unlocking the widget doesn't remove the Prevent manual override.

When you check to "Prevent Manual Override" an anchored object receives a lock adornment. An object Style can be created from this object. If that lock is unlocked the Object style shows as override, but the "Prevent Manual Override" is still checked.

If the object style is redefined. The lock adornment is still unlocked, and the "Prevent Manual Positioning" is still checked. Reapplying the style locks the object.

There should be more consistent behaviour of "Prevent Manual Positioning" and the "Lock". Even though they are similar they are not the same. If checking "Prevent Manual Positioning" activates the Lock. Unlocking should also uncheck "Prevent Manual Positioning".