InDesign Fonts folder no longer respects symlinks (2019, Mac)
The Fonts folder in the InDesign 2019 application folder no longer follows symlinks, as previous versions did.
I prefer to keep my InDesign fonts separate from my system fonts, and in previous versions placed a symlink to my font folder in the InDesign application folder, titled "Fonts." InDesign would follow that link, and I would have access to all of my fonts within InDesign, without needing to install them user- or system-wide.
In InDesign 2019, no symlinks are followed - not on the top level, and not inside the folder either. (Tested by symlinking one font or one folder inside a new Fonts folder.)
One description of the method: https://glyphsapp.com/tutorials/testing-your-fonts-in-adobe-apps
Thread where others comment on this: https://forum.glyphsapp.com/t/adobe-fonts-folder-for-indesign-cc-2019/9971
Thank you for reporting the issue to us.
We have fixed the issue in the latest version of InDesign, Id 14.0.3
Please upgrade your InDesign application to the latest version to try out the fix.
If you are unable to see the update yet, go to Creative Cloud desktop application, open the menu (three dots) from the top-right corner and click on ‘Check For App Updates’.
If you face any problems with the new update, do let us know in the comments.
You may also follow the below given link for the list of all fixed issues in Id 14.0.3
Will this be corrected in any future versions?
Is there any timeline for this? I would love to switch to the latest version.
Has anyone from Adobe looked at this? I'm stuck in the previous version of InDesign until this is fixed.
As a typedesigner working on more than two computers in the studio, I require possibility of separating the "Fonts" folder from the InDesign application. I'm lacking a feature using symlinks to place a "Fonts" folder on a remote server and share the latest font with my colleagues in no time. This feature is crucial for font testing (using Glyphs) and general workflow during collaborations. Please keep me updated.
I vote up for solving this issue. It is a crucial feature that we can't use anymore..