What are the pros and cons of working in Books, as opposed to Documents? When should a Document become a Book? Is it determined by the number of pages, graphic content, or something else? To me, it appears that Documents are easier to manage鈥ut I may be wrong. Any thoughts?
Booksbbsydney wrote:
What are the pros and cons of working in Books, as opposed to Documents? When should a Document become a Book? Is it determined by the number of pages, graphic content, or something else? To me, it appears that Documents are easier to manage鈥ut I may be wrong. Any thoughts?
BooksAnything with more than 1 chapter.
I use it for magazine layout. I can keep each article separate for sending to clients/authors/typeseetters/proofreaders etc.
I find it a much more efficient way to handle the file. If you have a 200 page magazine and you're using a lot of InDesign effects it will degrade the performance of InDesign. And if the file becomes corrupt you've lost a whole magazine. If you keep it in separate indesign files you will only have one section to redo if a file becomes corrupt.
It's all about efficiency and splitting your files up into manageable sizes, plus using the book features, like automatic chapter numbering, book page numbering options and there's loads of other things a book can offer than an individual files.
You won't have a tonne of styles to fudge through, you clean up your styles, etc. and speed up your workflow. Plus others that need to work on the document and don't know聽 your system, they will get a file with only the styles used for that section etc.
And don't forget a document with many master pages, and someone says ''I want chapter 25 moved to chapter 3'' and that's a lot of fudging about with master pages and page flow. With a book you can simply move the chapter up to the new position, then update the book numbering and if you've used Chapter Heading numbering and things like that all the chapters automatically change to their new number and so on.
No comments:
Post a Comment