At the time Adobe InDesign was created, 15 years ago, it was generally impractical to store print-quality assets on web servers. A decade and a half later, however, the maturity of cloud-based file storage and asset management systems is making links from InDesign to assets housed in modern platforms, such as Box, a powerful solution for creative professionals.
Asset storage as of Adobe InDesign 1.0
Adobe InDesign is the tool of choice for the creation of high-quality print documents. It is nearly ubiquitous among those creating newspapers, magazines, books, catalogs, marketing collateral, or almost anything that prints. InDesign started out as a competitor to QuarkXPress, and given the dominance of Adobe in tangential technology (PostScript, PDF, PhotoShop, Illustrator) along with substantial and well-focused investment in the product, it was inevitable that InDesign would take the place of Quark at the center of high-end publishing workflows.
Anybody who works with automating Adobe Illustrator long enough will find some level of flakiness in the behavior of this application. It is very old, and doesn’t enjoy the same level of support for automation as does InDesign, a much more modern application. I got this email this morning, and it seems we are one step closer to taming the Illustrator beast…
We have been automating Adobe InDesign for 12 years, InDesign Server for 7 (since it came out), and it seems that just now we are finally being proven right in our bet long ago that going with the slowest, yet far and away most robust, composition engine would in the long run be the best path. After all, hardware just gets faster and faster. Desktop tools and capabilities do tend to end up on servers.
I have been working with XML since it was a glimmer in the eye of Jon Bosak. In fact, before XML was conceived, there was SGML; this evolution of SGML represented a streamlining for the web, but at its core there was not much functional difference; in fact the new invention was defined as a mere SGML subset. The key concept of semantic markup is central to the core value of SGML as well as its “streamlined for mass consumption” child.
The two main perspectives I have seen are Document-centric and Data-centric. SGML initially appeared in support of document-centric work: managing all the technical documents or contracts of IBM or Boeing, for example. Charles Goldfarb has maintained that “SGML literally makes the infrastructure of modern society possible” and I think he’s right – hmm, should we blame him for the lengths to which humans have gone to destroy the earth?