As a matter of fact, I liked InDesign up to version 5 and stopped using it after an update to 5.5, because it was extremely buggy and crashed around 50 times a day. But - and this was a good thing - it never, ever corrupted any of my files, even with the largest number of crashes I had in any program I've ever seen...
Andreas Weidner
Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
Packaging the document to include all assets and fonts etc ( like InDesign) is a feature that would be 100% mandatory for me to be able to switch from InDesign to Affinity Publisher. and oh boy do I ever want to switch to affinity Publisher!!!
