InDesignSecrets Podcast 209

Click above to play
or click here to open original MP3 in a browser window
(23.4 MB, 44 minutes)

view the transcript of this podcast.

In this episode:

  • AM’s field report from the Edward Tufte one-day course
  • Huge InDesign Magazine issue coming up, all about Adobe DPS
  • Interview with Ben Schott, author of Miscellany and Schottenfreude
  • Hidden uses for Live Preflight
  • Obscure InDesign Feature of the Week: Entry End

News and special offers from our sponsors:

>> PePcon: The Print + ePublishing Conference is the place to be to learn more about using Adobe InDesign for print, PDF, epub, and tablet publication projects. Come to Chicago June 15–18 and join us and hundreds of your hard-working colleagues from around the world, from all sorts of companies and universities, all there for the same purpose: to learn, to share, and be inspired. Special for InDesignSecrets podcast listeners: Use the coupon code CH73G to receive $50 off your PePcon registration!

>> The long-running InDesign Conference is now part of the InDesignSecrets family, and plans are in the works for the next event. We’ll make an announcement in the upcoming few months. Keep an eye on the blog and in your email’s inbox!


Links mentioned in this podcast:

Here are some of examples of Ben Schott’s writing and artwork (click each thumbnail to enlarge):

fd-new-cover schott-sign-dining-custom3 Schottenfreude_P11 Schottenfreude_P21 sgi-new-cover  som-new-cover sqm-new-cover

Comments

8 Comments on “InDesignSecrets Podcast 209

  1. Thank you for the Obscure Feature of the week. We don’t use index much in our workflow and didn’t even know the Generate Index Dialog existed, but for the few times that we have books to do this will be very handy.
    Also the other uses for preflight, never thought of using it that way but now I will be using it a lot more, it should speed things up nicely.

    Well done David and Anne-Marie, another very informative episode!

  2. Best tip ever (for me anyway) –– format tab leaders. I’ve always selected each leader to drop the size, never considered tracking. THANKS.

  3. Listening to Ben, I was convinced that this had to be an April 1 podcast. EPS files? Why can’t he send a PDF? Also, it drives me crazy to hear designers make the excuse that learning styles is too much bother. It perpetuates the notion that it’s less creative to use styles or tables. I would even go so far as to call it irresponsible to promote that point of view, especially given the fact that you have spent your careers trying to teach people how to work smarter.

    Everything he said about his workflow was BAD ADVICE! I wouldn’t want any designer I work with to listen to it.

    InDesign features such as style sheets and tables really do save designers time and free up more of their time to be creative. It takes a very small investment of time to learn these features but they pay off in hundreds of hours saved over the long haul. It’s really unfortunate to hear people advocating wasting precious work time doing it the hard way.

    • Matt: I can understand your point of view, but this is the real world; we didn’t ask him to train people, we asked him what he really does. If people ask him for EPS, then he has to give them EPS (hey, maybe they’re placing it into QuarkXPress 4!)… if he doesn’t want to save himself time by using styles, that’s his business.

      As for using tables, that’s an interesting one… he knows how to use tables, but he finds setting up his tabular data with paragraphs and tabs, old school. That’s not necessarily bad. There are definitely times when that technique is more convenient and efficient.

      • David – your points are well taken, and I agree that Tables are not always preferable to tabbed text.

        Re: EPS, in the interview, his reason for using EPS was that he didn’t want to supply live fonts, which gave me the impression that he didn’t know what a PDF was. I assume he does know, but that’s how it sounded. I agree with not wanting to supply live InDesign files and fonts, but why would a PDF be rasterized by the printer?

        The reason his not using styles bothers me is that it not only takes longer; it makes your work less consistent and more likely to contain formatting errors. And, hearing a celebrity designer say he doesn’t use them gives cover to other designers who don’t want to use them.

        I wage a constant battle with designers who are afraid that using stylesheets will make their job harder or make them less creative. I have had designers undo all of the stylesheets that I had setup in a job, and then complain about how long it takes to make corrections. So, it just seems to me that it would have been prudent to edit out the part where he says he doesn’t use them.

  4. This interview had me from the pronunciation of Miscellany. Ben Schott’s painstaking attention to text and the end product is inspiring – no matter what his method. Thanks for showing examples. Our end product suffered before we followed our printer’s suggestion to distill page PDFs from EPSes. Seemed antiquated, but it’s foolproof with the printer’s Quark 4 workflow.

  5. In the Podcast, this issue about transparency and using outlines was triggered by Ben’s statement that sometimes the fonts got rasterized. I had this happen recently with a PDF and could not find out what happened. Could someone please explain what the connection is.

    • mbesson: There are printers and other publishers out there that (gasp!) open people’s EPS and PDF files in Photoshop, then save them in some format (such as TIFF) and then place in some program (ID or QX or whatever) and print. It’s insane and scary, but somehow they don’t seem to realize the damage they’re doing, rasterizing vector art. I’m not sure if that’s what Ben was referring to, but I’ve heard this from people for years.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>