go to Adobe InDesign go to Adobe GoLive
Adobe InDesign & GoLive Product Reviews

When Adobe announced their new "Creative Suite", my first reaction was (of course) to immediately purchase the new upgrade for Photoshop. I did and it is fantastic, if for nothing other than improvements on existing functions, but the new features were absolutely perfect for my new direction: DIGITAL CAPTURE & WEB WORK.

My business had traditionally been photography done for reproduction in magazines, catalogs, flyers, etc. Mostly print work, and sometimes images ended up on the web, but I wasn't putting any sites together, not even my own.

My capture medium was film, and then this was digitized, either drum scans or flatbed scans in my studio. The difference in quality of the scans was noticeable on the screen and high end printing, but sometimes lost in poor printing.

Then I would design and layout the ad or catalog using Quark. Quark has been the mainstay in the print world, mainly because every printer in the world had their workflow set up through Quark's products and they DEMAND A QUARK DOCUMENT! Photoshop would handle all the imagery requirements and Illustrator 9 seemed more than enough for my needs.

THINK ABOUT THIS

Postscript is what everything is eventually distilled to. From that glorious moment of creative inspiration in my clients mind (or my noodle), through the camera, the drawing board, the scanners, the page layouts, the disks on down the line, it ends up as code in a postscript file!

So what?

BIG PROBLEMS

Quark has to convert everything (or sort of convert) into Postscript, using either "export" to postscript or "print to PDF" or be filtered through a raster algorithm to finally get to the press. In this process there are many considerations, many compromises and many workarounds. I pity the pressmen, because ultimately they are at the end of this long process and everyone seems to blame them if it doesn't quite come out the way it was originally conceived.

Another major issue is Color Management in this work flow. If every step of the way is either not color managed, or managed incorrectly, the results can be unpredictable and maybe very costly. You have the scanners working in sRGB, the photoshop users working in Adobe RGB, the digital capture in Raw format, the Quark users turning off their color management because of conflicts with other program's CMS, the printers working in CMYK, and then the web has its own color space.

How does anything really work at all with this confusing and disordinate technology?

Why must the world of print and graphics design conform to the one odd duck in the system? In the past its has been because the printers have established a hand-holding bond with this big duck and they won't let go!

BIG SOLUTIONS

adobe CREATIVE SUITE 

Lets start out with the basic idea for a magazine ad.


  1. Ad concept. Maybe a sketch, maybe a full fledged color comp with ten versions. This gets approved.

  2. Photographic capture, let's say digital raw.


  3. Conversion of image to usable appropriate color space.


  4. Graphics for logos, embellishments.


  5. Page Layouts



  6. Final composite file to be rasterized and printed.
Disclaimer:

All statements made in this review are my opinion and only my opinion. I have chosen to express my opinion so possibly others may benefit from my experience.

My opinions are subjective and are based on my understanding or misunderstandings regarding this technology. I am not a software developer, I am a software user, therefore my evaluation is based on my user experience and not on any evaluation of underlying software codes.

I may be wrong in my assumptions about software technology, please use your own judgement when making a choice about software.

Please feel free to discuss these issues with me via emails in a constructive manner, but do not send communications you would not be proud to have possibly displayed on this web page.

I endorse the Adobe Creative Suite because I feel it is the finest system for the graphics and photographic artist that exists!


For the graphics designer, Quark has been the program of choice in the past, but I feel the graphic print designer has been taken for granted by Quark in the last two upgrades.

They have made strides in what they refer to as a "Project", or the coordination of elements of a bigger "project", which may cover both print and web exposure. And their expansion to integrate web and print work into one program is a great plus. But, this may be the issue that has irked print designers.

The print design working interface and functionality has basically been the same in Quark for versions 4 through 6. What has been developed has been the web design functions. In the meantime, InDesign has overwhelmingly surpassed Quark as a designers tool for the print medium.

Quark's web tools are quite easy to use and their built in Javascript Cascading Menu building interface is the best I've seen, but they have no support for external CSS styles, which is a major issue. So, to sum this up, Quark has fallen behind for the print designer, and for the web designer they are not at the top of the heap or even close.

This column will show various possible products used in workflow.

  1. Color pencils, cutouts, markers.


  2. Digital camera, many using proprietary image color calibrations.

  3. Photoshop (or multitude of other image software with different color management calibrations).

  4. Illustrator, Freehand, Corel Draw, all with proprietary file formats.

  5. Quark, Publisher, Pagemaker, InDesign CS, each with its own proprietary file systems.

  6. Acrobat Distiller, InDesign, Illustrator, Postscript emulators...

It all ends up here, guys, a Postscript file!

All of these other software packages just provide an interface for you, the consumer, to produce, arrange and calibrate the elements for the final package, the Postscript file. So, the obvious glaring issue is one of MAKING THE PATH TO POSTSCRIPT a predictable and manageable one.

In my estimation the most LOGICAL way to do this is use the ADOBE CS software package THROUGHOUT the process! Why introduce all these proprietary confusing elements into the mix?

Your job is about getting your concepts and images on a page in the most efficient and logical fashion, not about heralding one interface vs another interface. The same thing on the web, it's about making the html code, using the logical and useful interface.

Adobe InDesign CS
First of all, I like the title, InDesign, because that's what this is all about. It is about taking all kinds of existing elements, placing them together, for the page or web, and sending it into the world for review. The beauty of this software is that it is a designers environment. I would say this is the main reason for using InDesign.
How many Quark users out there can see what the colors really look like, or how they look side by side with another color. Only the latest version of Quark offers anything other than "NEON COLOR" for CMYK images. The Color Management System used across all the Adobe CS products is the industry standard, developed by Adobe in association with the ICC (International Color Consortium). of which Adobe, Kodak, Apple, Sun, and Agfa are the founding members! Why introduce unknown factors into the particle flow?
When I design something, and this is one of the greatest features, I can just export a PDF directly from InDesign, email it (color managed) to my client for evaluation. Try this with Publisher, oh that's right, you can "print to PDF" if you have Acrobat on your computer. You can do that with Quark also, if you have Acrobat. Or, you could export to EPS (postscript again) then use Adobe Distiller, or open the EPS in Illustrator and "save for the web". Get the picture?
Then, your client can view the work proof on their computer using Acrobat viewer, which is distributed free. If your client has the full Acrobat Professional, they could open your proof document and "MARK UP" the document with all kinds of tools that could include "post its", notes, arrows, etc, just like marking up a printed proof. Then when they are done commenting, they just email this marked up doc back to you for your next round of revisions.
How about PC users that have to listen to the PCPhobes at their Service Bureau about PC fonts, PC this, PC whatever? Well, InDesign can convert fonts to outlines, then your PC InDesign file can be opened on a Mac with no font issues. In Quark I guess you could export to EPS, open it in Illustrator, then convert the fonts to outlines, then send out a very large EPS file. Or, you could create an Illustrator EPS file of just the text, convert the text, then import it into your Quark page (preview is horrible) then send your Quark page out with an EPS overlay. This is all wasteful workarounds that take time and money and provide many opportunities for mistakes.
Here's one feature that may make the difference, InDesign can open Quark files. That's right. I have opened easily over a hundred old files, flawlessly. The only problems may be finding the old links to images, but that is my image storage issue and not the software conversion.
Another great thing about the CS product group is that InDesign has an export function (Package for GoLive) that will group and convert (per your specs) all the elements in a page design for use in GoLive for the web presentation. This function will "Optimize" automatically all images and elements for web use, then put them in a special folder for easy and organized access in GoLive. Very powerful time saver.
The inter operational functions between the different programs in the suite are unparalleled in the graphics industry. The only other suite with this level of inter-program functioning is the Microsoft Office Suite, which for it's purposes is phenomenal. The "soul" of this Creative Suite (subjective opinion) is Acrobat Professional. Ultimately, all the software components are preparing elements for the final composite PDF file, which is essentially a "cross-universe" format. Everyone can view or use a PDF document, bound only by the the original file saving parameters.
I would not be surprised if the first human-alien communication is with a form of the PDF document.
There are many designer functions built into InDesign that are just too numerous to discuss in depth here, so I will list a few:
  • Object drop shadows. Try to get drop shadows in a large document consistent for both bitmaps and vectors (text or EPS graphics) any other way! You cannot do it without hours of extra work and extra programs. Bitmaps with clipping paths can easily have a drop shadow that looks exactly like the drop shadow on the text headline above it!
  • Object feathering, again bitmaps or vectors. Easy to use, very effective on text backgraounds.
  • Path editing tools that function just like illustrator and photoshop.
  • Sophisticated table editing features.
  • Color Management support for not only high end printers, but desktop thermal and ink jets. Also, this color management system is easily calibrated for your printer and your scanner.
  • EPS and CMYK high rez display. See what those EPS files really look like on your page next to your CMYK files that are displayed correctly! There are many Quark 4 & 5 users who cannot experience this important feature.
  • Ability to change color space on the fly for different output destinations, such as change a high rez CMYK image to print correctly to your desktop inkjet in RGB, without changing the source file!
GoLive CS

GoLive is the HTML editing program that is an integral part of the Creative Suite. I won't talk a lot about HTML editing, but more on why GoLive as opposed to the program I started out with, Dreamweaver.

GoLive is comparable in function to Dreamweaver, that is to say it functions as an interface for the production of HTML code. You can write HTML code in a simple word processing program if you like, but GoLive offers so much more. The reason one chooses any interface over another is based on functionality and purpose. I would hate to produce web sites for a living using a word processor, but there are people who do this. In the beginning that was all there was for editing HTML.

The main reason I like GoLive over Dreamweaver is the CS package that gives GoLive a powerful interface with InDesign, Photoshop, Illustrator and Acrobat. All of the programs can create a PDF file that GoLive can use in so many ways on the web. Downloadable, printable, animation, slide shows, interactive elements in the PDF, all usable directly in GoLive.

Illustrator can create SVG files which are the next generation of elements for the web. Vector based graphics that can be scaled interactively with no resolution loss. Scale a jpg larger than 100% and watch the image come apart very quickly. Scale an SVG and it will not lose any detail. But the great thing about SVG graphics is the use of "VARIABLES".

Create a graphic banner in Illustrator, with color backgrounds, gradients, boxes, text, or whatever. Then say you want the Logo text to stay the same, but you want subheads that are different for every page. Such as "contacts", "services", "products", "goals", "links". With VARIABLES, you create only one graphic file with all the elements, then indicate within that one main file the "variable" which can be text or graphic (in this case the subheads). Save this file as an ".SVG" file (not eps). When this file is linked to your GoLive document and placed through the "Smart Objects" function (explained next), you can CHANGE THE VARIABLE WITHIN GoLive. One master file used on multiple pages, with multiple subheads that are easily changed within GoLive.

SMART OBJECTS

This is why I choose GoLive. Objects created by other programs in the Creative Suite package can be used through an import system called "SMART OBJECTS". When they are placed on a GoLive web page, this becomes a Master File that can be changed or redefined in any place within the document using the original file for a link. Any changes made to the original Smart Object will be reflected throughout the document automatically.

For example, say you have a Photoshop PSD file with layers. Text is on the top layer, with an image on the bottom layer. This is a CMYK image that was used in a brochure for your client. He likes the image and wants it on his site in 20 pages! When you place the image on your web page in GoLive as a "Smart Object", GoLive will open a "save for the web" interface to format the linked file for your web page. Great!

Let's say on the home page the graphic is used at 200x300 pixels, but on 3 other pages you want the graphic at 400x600, and on ten pages you want the graphic at 100x150. Traditionally, you could just scale the graphic differently for each use, which would look very bad in the upscale, and be wasteful in the downscale, or you could go back to Photoshop and re-export the graphic specifically for each size. This is very time consuming especially on a big project.

By using Smart Objects, the GoLive interface would automatically optimize the graphic for each separate placement. Now, here is the beauty of this system. Say your client wants to change the font weight on the text within the original graphic. This would normally make a web designer lose sleep, but with GoLive and Photoshop, you make ONE FILE CHANGE and it is updated automatically throughout the web site on all uses and sizes of the graphic.

Plus, and this goes back to "Variables", the Photoshop layered document top layer is a variable (or whatever you may designate a variable). So when you bring in the PSD file as a Smart Object, like an Illustrator variable) you can make specific changes without altering the original PSD file.

Smart Objects are extensive and include Photoshop files, Illustrator files, PDF files, component (explained next) and "generic files" which can be non-Adobe files.

COMPONENTS

These are web elements the are constructed, then saved for re-use on various pages as needed. This could be a menu, graphic, footer, header, or virtually anything that could be used on HTML pages. When they are placed on a web page, they are dynamically linked. I mean that changes made to the original will be reflected through the site.

If you spend hours developing a menu, you save this as a separate HTML page as a component. Then, say you have 20 pages that need this menu, you place this "component" as needed on the 20 pages.

These 20 pages are dynamically linked to that component, so if your client wants to add one more link to that menu, you make ONE CHANGE to the COMPONENT and it will be reflected to all the pages using that component! Dreamweaver does not offer anything like this, other than a template page (also in GoLive), which is a little different!

CSS SUPPORT

GoLive supports CSS external style sheets, but with some reservations. ID styles have to be added manually through the Source Code editing or Visual Tag editor, while other things like element style and class styles can be applied directly through the CSS interface. Why this ID style application has to be manual I can't begin to understand. Someone may have an answer, so if you do let me know! This is the only shortcoming I can see to GoLive's support of CSS styles, while Dreamweaver offers greater support and application within the document for external style sheets.

The CSS editing (create a new div, class, element) is top notch. This function offers real-time displays of what a paragraph or block or element would look like when applied. This is unmatched anywhere as far as I know.

To sum this up GoLive is my choice for HTML web design because of the CS package. This along with some nifty unique functions that would take a 400 page manual to explain, is why I have used GoLive to build my own site!

This next file is from an ad that will run in the Bal Harbour magazine in Nov. 04. (No, that is not a young Kelly LeBrock!) This was exported directly from InDesign as a high rez press PDF at 25MB (zip compression not jpg) for magazine printing. Then this PDF file has been placed in my Smart Objects directory. Then I link to this original file and convert it (2ok) for the link pic below, directly within GoLive!

I want a bigger file for an enlargement, so I again go to Smart Object and save a second file (converted fresh from the original) to 70k for the target enlargment.

How can you do that from Quark? I guess you could export to a massive EPS file, open that in Illustrator, then save for the web multiple times for multiple places. Too much confusion, too many steps, and too many files!

Or, if you know exactly what you want for compressed images, export the document directly from InDesign as a JPG (not available in Quark).

And the third option would be to "package for GoLive" from InDesign, which would place the document elements compressed and ready for web use. The only reservation in this case would be that this function would place the elements separately (image file, text file, etc) not keeping the document as one composite image.

jw cooper ad

The next downlaodable file is a six page exert from a Gift Guide Spread that is running in Cowboys & Indians magazine, Nov 04, with Tommy Lee Jones on the cover! This is a beautiful magazine with the highest standards of design and printing! This 20 page spread was produced entirely in InDesign, sent to the magazine as a high rez PDF, along with the original InDesign file and tiff files, just in case there were last minute changes at the press.

This example file for download was exported from InDesign as a 1MB PDF, placed in my Smart Objects directory, where I just grab it and place it here, automatically producing a small 20k "link image". Then I place another file for downloading in my download directory. Both versions are freshly compressed from the same MASTER file, but to different compression specs!

Beware of converting or resaving a JPG, this results in even fiuther image compression & degradation, whereas using Smart Objects in GoLive allows a fresh JPG coversion for each use of the file!

Please click on image for a PDF download. This is a 1MB file, so if you have a slow connection it may take awhile.

VERY IMPORTANT! PLEASE READ THIS!

When I was producing ads and catalogs in Quark on a PC, one of the major issues was the font problems. They are not cross platform compatible, so I would export the file from Quark to an EPS, open it in Illustrator 9, convert the fonts to paths, and resave the document as an EPS.

Then I would FTP this massive file, usually around 100MB, to the printers or magazines, thinking I was really doing everything in the most proper fashion! Little did I know what happens in the typical magazine or printers production department.

They take these EPS files and run them through a PDF Distiller to their specs, which is usually a medium quality JPG compression, getting the print workflow down in MB! This results in significant image quality loss!

DON'T SEND MAGAZINES OR PRINTERS EPS FILES! 

Here is what I do now:

  • Design the ad in InDesign.
  • Export to a XA1 PDF, with zip compression specified as opposed to JPG. This makes for a smaller file that is predictable for me and for the printer WITH NO LOSS OF IMAGE QUALITY. This is directly from InDesign. A full page ad with a full page image comes out at around 25MB, not bad considering a comparable EPS page would be about 100MB!
  • The XA1 specification produces a file with NO transparency, CMYK inks only, and embeds the fonts, or if you specify you can have the fonts converted to paths as part of the flattener process. Then you LOCK the file so it cannot be edited. They have to run this version of the file. If you do not lock the file requiring a password, they can take it and compress it even more using lower resolution JPGS. They will do this! (The "Robb Report" does NOT do this. In fact, they pick PDF files apart and ask for a higher rez image replacemnt if the PDF conversion has produced a JPG. The high quality of their production standards results in superb printing with no compromises).
  • This of course means the Buck Stops with You! But at least you know what the file will not change after it leaves your shop.
WHY XA1?
  • CMYK colors only. If you send the file out with linked EPS files that have spot colors you're looking for a disaster or expulsion in preflight check. So this specification will convert the colors or alert you about the spot colors. Forgot to convert an image to CMYK, it will tell you so!
  • No transparency. This forces InDesign to flatten the document within InDesign before it becomes a PDF with transparency. PDF files with transparency are not necessarily a problem, if the printer has the latest and greatest rasterizing software that works with no glitches. But if they don't, watch out! All those beautiful gradations and dropped shadows will get ugly. Again, this makes you the final judge of how the file prints. The XA1 file format can be printed from Postscript Level Two, which means almost every one in the modern printing industry can print it.
  • Fonts are embedded, or you can specify in your transparency flattener defaults to have the fonts converted, which is recommended in a file with transparency. Automatic conversion without losing the fonts in the original document. The best of both worlds.
  • Here is something that I have heard about but can't verify if this is true, so take it as third party heresay. Quark does not support transparency, it supports clipping paths and limited support of 8-bit B/W alpha channels.

    So, if you send a PDF doc, or any doc (EPS) with unflattened transparency effects to your printer or magazine (using Quark as a workflow kingpin), Quark does not know what to do, and should EXPELL the document during the preflight check.

    Or, (here is the hersay) it will ignore what it doesn't support, there will be no preflight alerts, and the transparency will not be applied. Always check your linked EPS graphics for transparency or spot colors!
  • Acrobat and InDesign have preflight checks built in, so you can verify a file's predictabilty before it leaves your shop!

In the world of $10,000 and up (way up) ad placements, do you want the responsibility of a major mistake?

Download some Files!

This first file is a catalog, and we are featuring the first five pages here. This was designed in InDesign (16 pages total), for web offset press printing with 300dpi cmyk images. Then the five pages, featured here, were exported to a PDF file directly from InDesign, using the jpg compression parameters in the export interface. It compresses nicely to a 311k file. I could have gone smaller, but download this and see what you think. This could easily be emailed to a client list!

Please click on image to download the PDF multi-page document, this is 300K document so it may take awhile if you have a slow connection.

 jw cooper catalog