A Few Type Issues

by Heather Champ

A Designers Dilemma
It's always a quandary for a designer to determine how much type to set as graphics and how much to set in HTML. The creation of set type allows for more control, not to mention a seemingly infinite number of fonts from which to choose, but the addition of each graphic element can add to a prolonged download time for the user. Upon arriving at the "index.html," is it better to download one large image that incorporates subsequent navigation in the form on an image image map or download a number of elements that fit together like a Chinese tangram. I've never found the definitive answer, although not for want of asking, to whether it's better to make one call to the server for a large image or several calls with smaller pieces. I entertain any comments, observations, or treatise on the issue.

Why HTML Text Is So Tricky
A designer can lose control of HTML text so quickly because, even though browser default settings provide a proportional font, typically Times Roman 12 point, and a fixed font, Courier 10 point, users are enabled by the browser's preference settings to change these preferences to whatever they choose. I'm not suggesting that this practice should be ended, and I don't subscribe to the litany of specification--"This site is best viewed with fonts x set to y size"--as choice and freedom are perhaps two of the cornerstones that make the Web uniquely the Web.

Additionally, there are a number of font manufacturers, and each font, like Times for example, is as different as the one that came before it. Not all font families are identical, even if they bear the same name.

This is not to say that text set in HTML is to be avoided. It's advantageous to mix type set as graphics with that in HTML as it will reduce download time. It's also easier to change and update information without having to fire up your graphics application every time something changes.

What can you do to avoid mishaps? Try and not force text with overspecification. Things are less likely to appear out of whack if text is allowed to flow through the document rather than employing the <BR> line break to organize text. If a user has set his or her preference for a font other than the default setting font or to a larger size, unusual or unexpected line breaks can appear.

It goes without saying, and I feel that it's becoming a personal mantra, that viewing a site through as many possible browser/platform variations is essential. I've a list of friends who I regularly annoy with my entreaties of "so, how does it look?" You can also change your own preferences, enlarge and reduce the fonts, and perhaps choose another font entirely to ensure that even with these changes, the original intention may be somewhat retained. A bit of exploration into the differences between platforms and browsers can alleviate most of the pitfalls. Unfortunately, there are far too many variables to be assured that what you see is what everyone is going to get.

Past installments of Design Diary