To provide the best experiences, we and our partners use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us and our partners to process personal data such as browsing behavior or unique IDs on this site and show (non-) personalized ads. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Click below to consent to the above or make granular choices. Your choices will be applied to this site only. You can change your settings at any time, including withdrawing your consent, by using the toggles on the Cookie Policy, or by clicking on the manage consent button at the bottom of the screen.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Thank you David for publishing it! I’m looking forward to meet you all in person at PePcon!
–Haeme
Thanks, Haeme. Great job!
Love it! Thanks Haeme for sharing it…
Haeme, can you explain “You can temporarily disable a GREP Style by adding * at the beginning of the code”? In what way is it temporary? How is the GREP Style reengaged?
Jamie, adding a “*” at the start of a GREP style expression makes it an Invalid Syntax, and so it will not be executed any more. GREP styles are ‘run’ virtually continuously, and more than a few slow down ID immensely. To re-enable the GREP style, remove the asterisk at the start again. It’s “temporarily” in the sense that you actually want the GREP styles enabled.
Nice, but lacking two biggies:
(1) Avoid split and span columns unless you have to use them
(2) Avoid very long stories. (Long docs are mentioned in the chart, but I’ve found that long docs do not actually slow down InDesign so much as long stories. A book containing 15 chapters will be really slow if all those chapters are threaded. But if each chap. is a separate story, there shouldn’t be a problem.)
Thanks Ariel for your input with span columns. We have to pick up in for further versions of the list.
Thanks for shared very good information. Please continue if you get new innovative ideas.
Thanks Haeme!
Thank you, very helpful!
David,
Where did you find the RAM requirements for indesign Cc?
All I can find are in Adobe site and they claim for indesign Cc 2015 the minimum RAM 2 GB (ridiculously low) and recommended is 8 GB, and makes no mention of GPU or VRAM requirements.
Thank you.
[Voice recognition software was used to compose this email. The technology is far from perfect; please excuse any mistakes.]
Great list. Here’s a Mac-specific gotcha: I had dragged an eps from an email (in Mail) into InDesign long ago, and in earlier versions of MacOS this worked fine. InDesign showed the path somewhere deep in ~/Library. But in Big Sur, this brought ID to an absolute crawl, even when the eps was on a hidden layer. Relinking it to the same file in ~/Documents fixed it.
Wow! I wouldn’t have expected that. I wonder if that’s an ID limitation or if Mac is doing something weird in the background. Thanks for letting us know!