The complete set of glyphs in any installed typeface and style can be viewed in its entirety. When the viewed font is an OpenType with extra embedded features, subsets become available, including: small capitals, discretionary ligatures, historical forms, lining figures, stylistic alternates, swash, or anything else defined in the font. Loading Adobe’s Minion Pro Med OpenType into the Glyphs palette, for example, will yield 19 individually viewable glyph subsets. XPress’s Glyphs palette also includes pop-ups of glyph variations included in some OpenType fonts–for instance, all the different versions of a lowercase a, all compiled onto the flyout menu accessible by clicking and holding on any one a. If it’s in your font, the Glyphs palette makes it easy to access. Once found, double-clicking any glyph inserts into the current text box at the cursor position.
XPress also uses the Glyphs palette in an interesting new way. Instead of placing commands to insert symbol, space, and break characters on a menu or leaving it up the user to find glyphs (many of which are effectively invisible) inside individual fonts, the Glyphs palette includes a couple of global glyph sets. Loading one such set gives instant access to commonly used type marks and symbols such as the trademark, registered trademark, copyright, and dagger symbols, as well as the middle dot bullet, ellipsis, and em and en dashes (if present in the font). Other global glyph sets assign visual indicators or icons to such things as breaking and non-breaking versions of a hair space, 6‑per-em-space, em space, flexible space, and indent here, discretionary hyphen, and discretionary new line markers. Placing these items on the Glyphs palette is a fantastic idea and incredibly convenient, although I do wish XPress also allowed the user to assign keyboard shortcuts to the most common symbols, spaces, and breaks. Fortunately, you can manually find glyphs you use often just once, and then add them to the Favorite Glyphs area, which is handily always in view at the bottom of the palette.
The special breaking and non-breaking spaces and markers are extremely useful, but the list is far from exhaustive. Missing are the usual complement of story-level breaks, such as column, page, and odd- and even-pages, and layout-level dynamic characters like page number, next page number, and previous page number. The last three are in XPress, but buried on the new Utilities > Insert Character menu. All of the other special characters and spaces on the menu are in the Glyphs palette, making it much more likely users will forget–or never find–the menu.
Font Fallback
Font Fallback, currently included in 6.5 but largely ignored, is enabled by default in 7. Font Fallback is XPress’s method of dealing with missing glyphs. For example, without Font Fallback, importing or pasting copy that uses glyphs not present in the current font will beget familiar empty boxes. With Font Fallback enabled, however, XPress searches for an active font that does contain those glyphs, automatically replacing the white boxes. How do you know you’ll get the same glyphs–that a registered trademark symbol won’t be replaced by an umlaut? Well, you don’t, unless you use OpenType fonts. OpenType fonts have a specific and inviolable position for every assigned glyph. Only an A is allowed in the slot assigned for the A; if an OpenType font doesn’t include an A–a symbol font, for instance–then the A slot must be left empty. This is the rule and law of OpenType font development. XPress 7’s new Unicode support for OpenType fonts means Font Fallback will move through the list of active fonts until it finds one with a glyph in the correct slot; OpenType means that that glyph must be the one intended for that position–the A in this case.
Use OpenType fonts whenever possible, and think of Font Fallback as your safety net against falling through empty type boxes.
Color Level-Transparency
Next to Composition Zones and OpenType support, XPress 7’s promise of color-level transparency has been the most eagerly anticipated feature of this new release–perhaps even ahead of all else. Knowing a little about how difficult it is to get software to affect transparency and flatten it correctly for print, I had strong doubts Quark could pull it off the first time out of the gate. XPress 7 would be a good first effort, I thought, but they wouldn’t get it right until version 8 or 9.
I was wrong.
Color-level transparency is, in most cases, more accurately thought of as attribute-level transparency. Opacity doesn’t work like tints; you can’t create a 50% transparent blue swatch any more than you can make all instances of blue across all types of objects 50% transparent in one fell swoop. Instead, you manipulate the opacity of colored attributes of objects.
Given a standard picture box, the opacity of both the box’s frame and background colors are independently adjustable. The box can have a 25% opaque background color while the frame is 75% or 100% opaque. Simply change the opacity percentage beside the Tint field on the Colors palette. And, even with transparency applied to the box’s attributes, box contents remain wholly opaque–unless you change them too.
Select the Picture Color button on the Colors palette to reveal that it too has an opacity setting. Want a colored gel effect on a photograph? Don’t take it back to Photoshop; just color the picture box background and reduce the opacity of the picture itself. Text, too, can be rendered partially or wholly transparent–and on a per-character basis. The next time you have a headline that trails off into the distance, really trail it off with diminishing opacity!
Wait. Here’s the best part: It prints.
And, oh, boy, is it fast! In 45 seconds XPress 7 printed a transparency-heavy document while InDesign required nearly three minutes to print a comparable document. Subsequent tests produced similar speed gaps on both Mac and Windows computers.
Flattening is handled in the updated print dialog, and is just a simple matter of choosing the output resolution for rasterization. XPress rasterizes on the fly and hands the flattened document off to the printer. When you would rather XPress didn’t handle the flattening internally, a simple checkbox in the print dialog outputs the document with transparency intact.
Knowing that color-level transparency was the big, important XPress 7 feature in the minds of most designers, I planned to test it in round after grueling round of production-level conditions, ferreting out every nuance of the feature–the good, the bad, and the ugly. Then, I knew, I would write extensively about my experiences. It would become the centerpiece of my review. My editorial about all the other new features would drop hints about transparency, building up to the climax of the deepest coverage possible on XPress 7’s color-level transparency. But, I can’t turn this into a centerpiece–there isn’t even enough to the feature for a decent hook!
I ran color-level transparency through all it’s paces; I produced the projects I intended. I printed–a lot. I made PDFs. Then I printed the PDFs. I tore the PDFs apart to see how XPress flattened transparency. I even recreated in XPress 7 some of the projects I had previously built in other applications–not just layout applications but drawing programs, too. I did all that, but it’s not worth reporting the details because nothing went wrong, and nothing revolutionary happened. It. Just. Worked.
I wish I could say more, but this is such a direct feature that there’s nothing more to say. It works exactly as Quark said it would, and exactly as any designer would think it should. Pick a background, frame, picture, or text color, change it’s opacity, print, go home for the night. It’s uncomplicated and unassuming. The only thing revolutionary is the fact that there’s nothing more to it. It just works–and it’s seriously cool.
Blend to Transparency
Where color-level transparency is the most accurate description is another feature of XPress 7 you simply won’t believe until you try it for yourself: solid-to-transparent blends (a.k.a. gradients). Certain drawing applications have had the feature for years, but some still don’t. Moreover, no other layout tool can do it.
Blends are made the same way as in previous versions of XPress–on the Colors palette. Choose your blend type, and then pick your two colors. The difference now is, you’re no longer stuck faking a blend to transparency by dropping tints down to 0% (solid white or paper color). Beside the tint field is a new Opacity field. Merely type in an opacity percentage or drag the slider, and objects behind that color’s side of the blend will pop into view through the blend. You can’t even do this in Illustrator without the extra work of building opacity masks!
Alpha Channel Masks
Alpha channels have long been supported for determining clipping and runaround areas. However, they’ve always been treated as no better than common clipping paths–one-bit transparency, 100% there or 100% invisible. Now that XPress supports truly transparent objects, alpha channels, with their full range 256 levels of opacity, are used to vary the visibility of images.
Let’s say, for example, that you have a portrait atop a transparent background. In Photoshop, you feathered the stray wisps of hair–some strands are even 25, 50, or 65% opaque to enable realistic blending the background. Photoshop automatically creates an alpha channel to store this opacity data. Placing that image into any earlier version of XPress, with its limit of one-bit support for clipping, would have left a solid color halo in the feathered areas. In 7, however, simply open Modify, and, on the Picture tab, choose the alpha channel embedded in the Photoshop document. Ta da! Now the image blends in XPress exactly as it does in Photoshop, with feathered edges and 25, 50, or 65% opaque strands of hair.
Alpha channel masks are also independent of object-level transparency–an alpha channel mask can be handling internal opacity variations while XPress is making the entire picture 50% more transparent.
Single Layout Mode
XPress 6 introduced the metaphor of projects–multiple, distinct or related layouts in a single document. One project could, for example, contain an entire identity package across several layouts–a business card layout, letterhead in an 8.5x11-inch layout, #10 envelopes in a third layout, and so on. Both print and Web projects could happily co-exist in a single project, with all layouts in the project represented as tabs at the bottom of the document window. Projects are, of course, a very cool concept. Throwing in Synchronized Text made the project-layouts metaphor a big step forward in document production.
Apparently the tabs were something of an inconvenience for some XPress users when working with single layouts. So, in the New Project dialog of XPress 7 is a new Single Layout Mode option, which hides the tabs unless you later insert another layout from the Layout menu. A preference setting toggles whether Single Layout Mode should be the default.
Append
If you enviously read the previous section about multiple layouts in one project, thinking about your catalog’s twenty different documents and wishing you would have known about that option last month, rejoice. XPress 6 may have introduced the project-layout metaphor, but XPress 7 takes it to the logical next step (several next steps, actually; keep reading). In addition to importing style sheets, colors, H&Js, and all the usual items from one XPress project into another, Append now appends layouts, too. Got a folder full of related .QXP files that should be together? Just open XPress 7’s Append dialog from the File menu, grab your first project, and select Layout from the list. All available layouts in the project will appear in the first list to the right. Selectively append them, or click Include All to append all layouts at once. XPress automatically resolves conflicts with identically named layouts by prefixing a non-unique layout name with an underscore.
NOTE: It has been reported in other media that the Append (Layout) function will actually insert pages from one project (.QXP) into another layout–for example, adding project A’s 10 pages to project B’s 10 pages to result in 20 contiguous pages. This is not the case, nor, I have been told, will it be so in the shipping version of the product. Appending layouts is just that–appending one layout into another project; it is not appending pages.
Next: Job Tickets and Job Jackets
Correction: This article was supposed to have more than 25 screenshots and figures. Unfortunately, a disk corruption ate them (and other things). Rather than wait until new screenshots and figures were built, we decided to run the article without them.
I really enjoyed this well-balanced article. Well done and keep up the good work.
Frankly, i like this article. I will say that this is unbiased except for the opening statement under “Buying Advice”
‘InDesign CS2 is still a superior product in many of the ways that count, but the list has grown significantly shorter…’ – that would be a matter of opinon! So I shall respect yours but not agree with it. And its a little odd to add the application icon under “The Bad”. That is topic that shouldn’t have been covered here…
But all in all – well done! The screenshots, would be nice for those who haven’t used 7 Beta. So do try adding them if you get the chance. These are the kind of articles I would like to read and not a Quark-bashing review on their reviewer guide. It would be even better if you could write articles on how Quark’s and InDesign’s handle features comparted to each other and which is more efficient from your point of view.
THIS IS A GOOD ARTICLE
Cheers
PS: Please excuse the gramatical errors and typos in my previous comment – the hangover seems to have kicked in… lol
Ehm, what about PDF import? Can Xpress 7 import complex (spotcolor), PDF’s with more than one page? Will it understand and respect the trapping inside the pdf? (If you adressed this and I somehow missed it, my apologies. I have to read your story between differnt tasks, at work).
I haven’t reads the rest of the article but if the complete rubbish you wrote about pdf production is anything to go by I don’t think I’ll bother.
XPress 6 and 6.5 produce perfect print ready and web pdfs that are only marginally bigger than those produced by Acrobat, the only time it fails to produce one is when the resulting filename is too long. The only problem is the way the preferences work which doesn’t appear well documented but tonly takes five minutes to work out. Once you use the manual compression options rather than the useless automatic ones life becomes simple.
Wow! I din not know Quark marketing managers also visited yor site, Burke! This guy obviously never really used the fantastic JAWS technology to produce bloated pdf files!
An interesting article though it is obvious that you have succombed to Adobe’s marketing machine and are biased toward indesign. I am a fan of adobe-always will be but Indesign is not completely new it is basicly a repositioned pagemaker. Pagemaker failed bcause it just became too cumbersome. Quark’s strength is that it stick with the basics. It is a designb and compositing tool for print (and a whole lot more). It doesn’t depend on gimmicks to sell. It’s one weakness was with tech support not an old user interface. Many designers forget what their profession is-Signmaking-framing content. While the design may become art, that is not its purpose. Quark has a straightforward layout that is practical and clean. I am interested in looking at the layout I am creating not some crazy new interface. Change for the sake of change is a marketing ploy. Quark users are the majority for a reason. The program works and everyone in the world uses it. I still find indesign to be a bit clunky-especially how it deals with picture boxes. It’s intersting to see how the palettes start to mimich Quarks interface. Don’t get me wrong indesign is a great program but it is just a little heavy trying to do everything. All quark needs is layers and it would be just about perfect. I use quark to bring all my ideas together. I find it easier tothink in a clean room. InDesign is just to cluttered with to many features. Somewhere in all the gimicks the idea of the designer just gets lost.
Hi, Michael.
QuarkXPress has layers.
oh man, after reading that whole post by michael walberg with my mouth hanging open in disbelief and then he finally loses all weight to his argument by saying
“All quark needs is layers and it would be just about perfect. I use quark to bring all my ideas together. ”
oh man.…..
Pingback: peterbeninate.org » QuarkXPress 7 Review