<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Editorial Eye, The</title>	<link>http://tc.eserver.org/publisher/Editorial_Eye,_The</link>
	<description>A listing of works published by Editorial Eye, The in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Editorial Eye, The</title>
		<link>http://tc.eserver.org/dir/Editorial_Eye,_The</link>
	</image>
	<item>
		<title>Fonts on the Web</title>
		<link>http://tc.eserver.org/24057.html</link>
		<guid>http://tc.eserver.org/24057.html</guid>
		<description>One of the original ideas behind the Web is that readers should have control over how things look, since only they know what color combinations, point sizes, and so on they find easiest to read on their particular combination of hardware and software. That said, there&apos;s a difference between designing for the World Wide Web, where your documents can be read by anyone, and designing for an intranet, an internal network that&apos;s accessible only to people within your organization. On an intranet, you can (theoretically) know exactly what hardware and software your readers are using, so you can control the look to a much greater extent.</description>
	</item>
	<item>
		<title>Handling Internet Addresses in Text</title>
		<link>http://tc.eserver.org/24062.html</link>
		<guid>http://tc.eserver.org/24062.html</guid>
		<description>How to present complete and intelligible Internet addresses and where to break long strings of letters, digits, punctuation, and symbols on the page.</description>
	</item>
	<item>
		<title>How Careful Should Editors Be?</title>
		<link>http://tc.eserver.org/24058.html</link>
		<guid>http://tc.eserver.org/24058.html</guid>
		<description>Three recent incidents prompt me to ask, How careful do editors have to be in checking facts? Is it possible for publications people to be too careful?</description>
	</item>
	<item>
		<title>How Do Editors Do It?</title>
		<link>http://tc.eserver.org/24063.html</link>
		<guid>http://tc.eserver.org/24063.html</guid>
		<description>Do you ever feel you&apos;d like a second opinion on a particularly miserable paragraph you&apos;ve been editing?</description>
	</item>
	<item>
		<title>Keeping Things Consistent When You&apos;re the &apos;Guest&apos; Editor</title>
		<link>http://tc.eserver.org/24061.html</link>
		<guid>http://tc.eserver.org/24061.html</guid>
		<description>Consistency is the cornerstone of intelligent editing. In these days of leaner staffs and smaller budgets, however, many organizations don&apos;t employ full-time editors and depend on contract or freelance editors to make sure their publications are written in a consistent — and thus coherent — manner.</description>
	</item>
	<item>
		<title>The Key to Mayo&apos;s Successful Publications? Dave Swanson</title>
		<link>http://tc.eserver.org/24059.html</link>
		<guid>http://tc.eserver.org/24059.html</guid>
		<description>Mayo wants to give people actionable, not merely interesting, information.</description>
	</item>
	<item>
		<title>Links: What&apos;s Kosher?</title>
		<link>http://tc.eserver.org/24056.html</link>
		<guid>http://tc.eserver.org/24056.html</guid>
		<description>If your organization has a Web site, it can be useful to see who else has made links to your site. By tracking down those links, you can find out what people are saying about your site, what pages are particularly useful, and how people are finding your site.</description>
	</item>
	<item>
		<title>Total Immersion Editing</title>
		<link>http://tc.eserver.org/24060.html</link>
		<guid>http://tc.eserver.org/24060.html</guid>
		<description>In 1977 Judith Tarutz, author of Technical Editing: The Practical Guide for Editors and Writers, rebounded from teaching into her first editing job. She soon discovered that she was having fun. Like many editors, Tarutz learned editing by total immersion.</description>
	</item>
	<item>
		<title>The Curse of Yocto</title>
		<link>http://tc.eserver.org/24033.html</link>
		<guid>http://tc.eserver.org/24033.html</guid>
		<description>Several years ago, four new prefixes, for representing very large and very small measurements, were introduced into the International System of Units (Système International d&apos;Unités, or SI): yotta, zetta, zepto and yocto.</description>
	</item>
	<item>
		<title>Editing a Moving Target</title>
		<link>http://tc.eserver.org/24047.html</link>
		<guid>http://tc.eserver.org/24047.html</guid>
		<description>I&apos;d like to assume that most of us find ourselves having to edit a moving target only occasionally, but from the horror stories I&apos;ve been hearing, it seems that more and more people are being expected to edit well in a ridiculously short time.</description>
	</item>
	<item>
		<title>Editing All the Legalese the Law Allows</title>
		<link>http://tc.eserver.org/24046.html</link>
		<guid>http://tc.eserver.org/24046.html</guid>
		<description>Strictly speaking, legalese isn&apos;t intended for use outside a judicial context, but quasi-legalistic writing, with its officious tone, wordiness, and complex terms, percolates into business, government, and public interest documents. It&apos;s a parroting of the real thing -- which is already hard to swallow -- and there&apos;s a lot of it around. That kind of legalese demands to be edited, because people will do almost anything to avoid reading it.</description>
	</item>
	<item>
		<title>Essential Home Page Details</title>
		<link>http://tc.eserver.org/24048.html</link>
		<guid>http://tc.eserver.org/24048.html</guid>
		<description>Every home page should display certain key information -- an e-mail address and full identification of the publisher/author of the Web site -- that can appear at the bottom of the page, where it&apos;s easy to find but doesn&apos;t interfere with the main content.</description>
	</item>
	<item>
		<title>Figuring Out the Definition</title>
		<link>http://tc.eserver.org/24052.html</link>
		<guid>http://tc.eserver.org/24052.html</guid>
		<description>How can a homograph be the same as a heterograph? And how can heterograph, which comes from roots meaning &apos;different writing,&apos; be applied to a word that differs in every way except the way it is written?</description>
	</item>
	<item>
		<title>Free Guide to Color Printing</title>
		<link>http://tc.eserver.org/24043.html</link>
		<guid>http://tc.eserver.org/24043.html</guid>
		<description>3M Imaging has come out with a pamphlet that explains these color anomalies and more. And best of all, it&apos;s free.</description>
	</item>
	<item>
		<title>The Front Door</title>
		<link>http://tc.eserver.org/24049.html</link>
		<guid>http://tc.eserver.org/24049.html</guid>
		<description>First impressions count for a lot online. What users see when they arrive at your front door can determine whether they ever open that door and step inside.&#xD;&#xD;Realizing this, many Web publishers seem to have concluded that it&apos;s best to hang everything they&apos;ve got on that front door — their home page. The aim, apparently, is to make sure users see it all, but the effect may be the opposite of what the publisher intended.</description>
	</item>
	<item>
		<title>Hand-Picked Descriptive Words</title>
		<link>http://tc.eserver.org/24034.html</link>
		<guid>http://tc.eserver.org/24034.html</guid>
		<description>Writing a good description is fun, but it&apos;s delicate work. We recognize vivid writing when we come across it, and we know the bad stuff, too -- it makes us squirm instinctively. Here are some types of descriptions the world can do without.</description>
	</item>
	<item>
		<title>Necessary Transition</title>
		<link>http://tc.eserver.org/24042.html</link>
		<guid>http://tc.eserver.org/24042.html</guid>
		<description>As writers and editors, we understand instinctively that readers need transitions, but we also work at getting rid of unnecessary words.</description>
	</item>
	<item>
		<title>Scientific Style Manual Aspires to International Scope</title>
		<link>http://tc.eserver.org/24031.html</link>
		<guid>http://tc.eserver.org/24031.html</guid>
		<description>Despite what some U.S. editors may see as flaws or debatable recommendations, sooner or later anyone who edits scientific writing will consult &lt;i&gt;Scientific Style and Format.&lt;/i&gt; Some may disagree with its style conventions, but they can be defended as serving the editors&apos; stated goal of achieving a uniform international style for scientific publications. </description>
	</item>
	<item>
		<title>SGML: The Chameleon of Publishing Technology</title>
		<link>http://tc.eserver.org/24045.html</link>
		<guid>http://tc.eserver.org/24045.html</guid>
		<description>SGML (Standard Generalized Markup Language) is an international standard publishing technology that&apos;s increasingly being used in government, industry, and academia. Despite this growth, SGML is perhaps the most misunderstood technology around.</description>
	</item>
	<item>
		<title>Taking Stock of Paper</title>
		<link>http://tc.eserver.org/24044.html</link>
		<guid>http://tc.eserver.org/24044.html</guid>
		<description>Paper stock makes a big difference in the appearance of a product, and even though prices have come down recently, it&apos;s probably the most expensive element in your print run, so you need to make it count. Though budget is probably the biggest factor in choosing stock, here are several other considerations.</description>
	</item>
	<item>
		<title>Verbs with -ize: Efficient or to Be ... Ostracized?</title>
		<link>http://tc.eserver.org/24032.html</link>
		<guid>http://tc.eserver.org/24032.html</guid>
		<description>A discussion of whether neologisms such as &apos;prioritize&apos; have &apos;arrived&apos; yet.</description>
	</item>
	<item>
		<title>Web Site Sections: Art and Practice</title>
		<link>http://tc.eserver.org/24051.html</link>
		<guid>http://tc.eserver.org/24051.html</guid>
		<description>On a Web site with very few pages -- as in a small art gallery -- what you see as you enter can reveal all you need to know to successfully navigate the space. If the home page acts as a front door, then it can display hypertext links to all or most of the pages (up to 10, say) on a small site. Web sites have a way of growing larger, though, and not many sites stay under 10 pages for long. If visitors can&apos;t see everything from the front door, how will they know what you have to offer? How will they find what they&apos;re looking for?</description>
	</item>
	<item>
		<title>Apocalypse? Not Now: Three Myths of New Media</title>
		<link>http://tc.eserver.org/24012.html</link>
		<guid>http://tc.eserver.org/24012.html</guid>
		<description>The Internet explosion has spawned quite a few popular myths, and some Eye  readers may not know what to believe. I&apos;d like to offer my dismantling of what may be the top three misperceptions.</description>
	</item>
	<item>
		<title>Beyond Gutenberg</title>
		<link>http://tc.eserver.org/24015.html</link>
		<guid>http://tc.eserver.org/24015.html</guid>
		<description>Editing must change for the Web, but perhaps not so much as you think. In paper publishing, different documents require different rules and procedures: An annual report requires more editing and more attention to detail than an office memo. Similarly, not all Web documents are equal.</description>
	</item>
	<item>
		<title>Black Eyes</title>
		<link>http://tc.eserver.org/24016.html</link>
		<guid>http://tc.eserver.org/24016.html</guid>
		<description>Humorous malapropisms taken from various popular locales.</description>
	</item>
	<item>
		<title>Catching Errors in Internet Addresses</title>
		<link>http://tc.eserver.org/24018.html</link>
		<guid>http://tc.eserver.org/24018.html</guid>
		<description>Internet addresses have been proliferating in publications, and they&apos;re not going to go away. Editors unfamiliar with the Net may see these addresses as incomprehensible blocks of characters that can&apos;t be understood or analyzed into components. But learning a little about their structure can help prevent you from publishing erroneous addresses.</description>
	</item>
	<item>
		<title>Cookies: Just a Little Data Snack</title>
		<link>http://tc.eserver.org/24019.html</link>
		<guid>http://tc.eserver.org/24019.html</guid>
		<description>To read the New York Times Web site, you must open a free user account and log in each time you visit. That means yet another user name and password to remember. Fortunately, if you always use the same computer, you can set up your account so that you&apos;re logged in automatically whenever you connect to the site. The site does that by using cookies  -- another of those silly-sounding bits of programmers&apos; vocabulary that have crept into mainstream coverage of the Internet. But over the past year or so, this practice has become controversial because some people view it as an invasion of privacy. Others have bought into rumors or read inaccurate press reports suggesting that cookies threaten the security of their hard drives.</description>
	</item>
	<item>
		<title>A Copyeditor&apos;s Adventures in Multimedia Land</title>
		<link>http://tc.eserver.org/24020.html</link>
		<guid>http://tc.eserver.org/24020.html</guid>
		<description>Publication in the 1990s encompasses worlds that most copyeditors never dreamed of when, with a mixture of delight and mistrust, we cautiously approached the first spell checkers. At least we could relate to the idea of mechanically checking spelling. The whole idea of multimedia is a little more unnerving. </description>
	</item>
	<item>
		<title>A Handful of New Style and Usage Guides</title>
		<link>http://tc.eserver.org/24013.html</link>
		<guid>http://tc.eserver.org/24013.html</guid>
		<description>Style and usage guides seem to have proliferated, and it&apos;s not always easy to discriminate between the valuable and the less so at a glance. Here are three that have come to hand recently and deserve mentioning for different reasons.</description>
	</item>
	<item>
		<title>It&apos;s Not Fowler</title>
		<link>http://tc.eserver.org/24017.html</link>
		<guid>http://tc.eserver.org/24017.html</guid>
		<description>The debate over The New Fowler&apos;s Modern English Usage has the potential to become more interesting because there are personalities involved.</description>
	</item>
	<item>
		<title>Of Robots and a New Search Engine</title>
		<link>http://tc.eserver.org/24011.html</link>
		<guid>http://tc.eserver.org/24011.html</guid>
		<description>On July 1995, shortly after the EEI Web site opened, it began to be accessed by a computer named scooter.pa-x.dec.com . At first I thought that someone at Digital Equipment Corporation had an extraordinary interest in editorial subjects, but it soon became clear that Scooter was a robot, a computer program set up to retrieve Web pages. In some months, Scooter accessed more of our pages than any other visitor. I was curious, but since it wasn&apos;t doing any harm, I never investigated it. On December 15, 1995, the AltaVista Web site opened, and we finally got to see what Scooter had been up to.</description>
	</item>
	<item>
		<title>Taking Words to the Bank</title>
		<link>http://tc.eserver.org/24014.html</link>
		<guid>http://tc.eserver.org/24014.html</guid>
		<description>Lexicographers call a collection of writing and speech samples used to analyze words, meanings, grammar, and usage a corpus. Since 1991, Cobuild (a special division of HarperCollins Publishers in Glasgow) and the University of Birmingham, England, have been working together to assemble an electronic corpus. The intent was to acquire contemporary (post-1975) samples that illustrate the everyday English most people read, write, and speak.</description>
	</item>
	<item>
		<title>Telecommuting: Practical Option or Management Nightmare?</title>
		<link>http://tc.eserver.org/24021.html</link>
		<guid>http://tc.eserver.org/24021.html</guid>
		<description>Telecommuting can be a wonderful benefit for your editors and can save your department money -- as long as you set clear terms and carefully monitor the results. It doesn&apos;t have to be the management nightmare you may be imagining.</description>
	</item>
	<item>
		<title>When You and Your Employee Clash: Clarifying Expectations</title>
		<link>http://tc.eserver.org/24022.html</link>
		<guid>http://tc.eserver.org/24022.html</guid>
		<description>Will you have to fire this employee? Maybe. First make sure that she understands your expectations and the requirements of the position. Start fresh, and give her the opportunity to perform the duties you define to the level you require. Set specific, measurable goals for her to accomplish, and set a date to evaluate her progress. If she still doesn&apos;t meet your expectations, accept the fact that this was simply not a good match and give her — as an applicant once described his termination — &apos;the green light to pursue other opportunities.&apos;</description>
	</item>
	<item>
		<title>Beware: Generic Words Can Indeed Be Trademarked</title>
		<link>http://tc.eserver.org/20028.html</link>
		<guid>http://tc.eserver.org/20028.html</guid>
		<description>In article by Sabra Chartrand in the New York Times (March 13, 1995), makes it clear that the name of electronic products — books, photos, music, and titles — can be a bone of contention. Did you know that the Microsoft Corporation owns the rights to use the word bookshelf as applied to any CD-ROM product? In 1991, the software giant trademarked the term to cover its collection of reference books, Microsoft Bookshelf.</description>
	</item>
	<item>
		<title>Complementary Undertow</title>
		<link>http://tc.eserver.org/20025.html</link>
		<guid>http://tc.eserver.org/20025.html</guid>
		<description>In this introductory paragraph to a column by the &lt;i&gt;Washington Post&lt;/i&gt;&apos;s Stephen S. Rosenfeld, the subject seems to be paddling helplessly against a strong undertow of contradictory wording in the complement:&#xD;&#xD;To look in on current official and expert thinking about the world population problem is to become aware of a disappearing act that has transformed and mooted much of the common public understanding of this issue.&#xD;&#xD;There&apos;s enough happening in this sentence to make parsing helpful. Nothing&apos;s grammatically wrong with the parallel infinitive phrases: the subject is to look in and the complement is to become aware -- no mixed construction here (for more about that, see Test Yourself). But some mixed-up thinking is tugging the adjective-heavy prepositional phrases away from the infinitives they modify. And what&apos;s being equated is sunk by the fact that the complement is itself qualified by a paradoxical statement.</description>
	</item>
	<item>
		<title>Crossing a Bridge of Shyness: Public Speaking for Communicators</title>
		<link>http://tc.eserver.org/20027.html</link>
		<guid>http://tc.eserver.org/20027.html</guid>
		<description>Americans in general are more afraid of speaking in front of others than they are of snakes, heights, or death itself. That&apos;s the finding of one widely cited survey and, asked to step outside the written word, many writers, editors, and publications managers certainly would say they share that fear.&#xD;&#xD;Communication expert Nusa Maal Gelb says there is &apos;a culture of fear&apos; surrounding public speaking. It&apos;s almost as if we believe we&apos;re supposed to be afraid. Yet it&apos;s clear that effective interpersonal communication -- and that mostly means speaking -- correlates highly with personal and professional success. </description>
	</item>
	<item>
		<title>Did Somebody Say &apos;Duh&apos;?</title>
		<link>http://tc.eserver.org/20026.html</link>
		<guid>http://tc.eserver.org/20026.html</guid>
		<description>The year 2000 is a big duh for computers. But 2020 is when today&apos;s kids will rule the universe, as they already seem to rule the language. We&apos;ll have a State of the Union address consisting of &apos;duh!&apos; with a rebuttal of &apos;DUH-uh&apos; followed by the analysis, &apos;Excuse me?&apos;&#xD;&#xD;I&apos;m not sure whether this is a bad thing, given the present state of adult rhetoric and the occasional charms of juve-talk, or kid-lish. Concise and animated, the sardonic/ moronic idiom of school kids can slice through our stale officialese. Some of it -- the more cuddly terms, not the hard-edged hip-hop -- tickles that laugh-spot recently located in the brain. Yet, when millions of grown-ups, even those who communicate for a living, start aping little people in baggies, one has to fear for the range of human expression.</description>
	</item>
	<item>
		<title>Editorial Esoterica</title>
		<link>http://tc.eserver.org/20022.html</link>
		<guid>http://tc.eserver.org/20022.html</guid>
		<description>Test your knowledge of a range of writing, editing, and publishing topics.</description>
	</item>
	<item>
		<title>Leaving Copyediting for Computing</title>
		<link>http://tc.eserver.org/20021.html</link>
		<guid>http://tc.eserver.org/20021.html</guid>
		<description>A copyeditor for a computer publication wants to change careers. She&apos;s thinking of taking a few computer language courses with an eye toward moving into UNIX system administration -- a wide-open field. As someone who has changed careers once or twice, I&apos;ll offer a coaching session.</description>
	</item>
	<item>
		<title>Loose Ends: Standards and Styles</title>
		<link>http://tc.eserver.org/20029.html</link>
		<guid>http://tc.eserver.org/20029.html</guid>
		<description>Several readers have sent me e-mail comments and questions recently that might be of interest to others. (Even Eye readers who don&apos;t spend much time on the Web tell us they&apos;re interested in picking up this kind of information.) </description>
	</item>
	<item>
		<title>Seven Habits of Highly Perfect Writers</title>
		<link>http://tc.eserver.org/20020.html</link>
		<guid>http://tc.eserver.org/20020.html</guid>
		<description>For a long time, I&apos;ve thought English to be far too wordy. Indeed, precious forests have been slaughtered in the name of printing dictionaries and -- of all the useless things in this world -- thesauruses. But it goes beyond the sheer number of words.</description>
	</item>
	<item>
		<title>Unicode: Making the Web Safe for Furriners</title>
		<link>http://tc.eserver.org/20024.html</link>
		<guid>http://tc.eserver.org/20024.html</guid>
		<description>I think that Internet and World Wide Web are capitalized because they are proper names. Many names are capitalized common nouns: the White House, the Ninth Circle of Hell, the Heritage Foundation, the Civil War. I&apos;ve heard arguments for lowercasing Internet and World Wide Web from people who compare them to things like the telephone system, but lowercase is certainly not the predominant style for these terms. At least 90 percent of the time, they&apos;re capitalized, and I don&apos;t think you should ignore actual use completely.</description>
	</item>
	<item>
		<title>Usage Experts Change Their Minds, Too</title>
		<link>http://tc.eserver.org/20023.html</link>
		<guid>http://tc.eserver.org/20023.html</guid>
		<description>Many terms and constructions frowned on a generation ago have been admitted, like many new words, into mainstream parlance and have gained wider acceptance than before. An example is tycoon, in the sense of a wealthy businessman, labeled &apos;informal&apos; in the first edition of AHD but accepted in the third. Another example is balding, called &apos;entirely vulgar&apos; in a usage note by panelist Katherine Anne Porter in the first edition but entered without stigma in the third.</description>
	</item>
	<item>
		<title>Using Editors Where and When It Counts, Part II: How to Edit Instructions</title>
		<link>http://tc.eserver.org/20019.html</link>
		<guid>http://tc.eserver.org/20019.html</guid>
		<description>When I teach courses on editing, I devote about one-third of the sessions to editing instructions. Why? True, there&apos;s always a demand for someone who can edit technical manuals or cookbooks, but my real reason is that working on instructions gets you into editorial shape. It hones your ability to keep readers and their needs always in mind, to weigh each word for accuracy, and to be sure that every sentence means what the writer intends.</description>
	</item>
	<item>
		<title>Can You Edit a Direct Quotation?</title>
		<link>http://tc.eserver.org/20006.html</link>
		<guid>http://tc.eserver.org/20006.html</guid>
		<description>A TV network would never put words in a person&apos;s mouth, of course, but print journalists take this liberty all the time.</description>
	</item>
	<item>
		<title>Encryption Basics Decrypted</title>
		<link>http://tc.eserver.org/20005.html</link>
		<guid>http://tc.eserver.org/20005.html</guid>
		<description>Most people sending e-mail nowadays take no steps to prevent their messages from being intercepted. That&apos;s fine for many types of messages, but just as there are written messages that you wouldn&apos;t want to put on a postcard and would prefer to have protected by an envelope, there&apos;s a need for encryption in electronic communication. Besides, encryption can do more than keep things secret.&#xD;&#xD;The concepts on which encryption is based can be difficult, and most of the complication is handled behind the scenes by software. Nevertheless, it&apos;s useful to have a general understanding of how encryption works.&#xD;&#xD;Encryption software (often part of a Web browser or server, e-mail client, or other program) is built around the use of a special number, called a key, to convert information into a form that can be read only by someone who has the key needed to decrypt it. </description>
	</item>
	<item>
		<title>The Reference Book That &lt;i&gt;Editorial Eye&lt;/i&gt; Built</title>
		<link>http://tc.eserver.org/20002.html</link>
		<guid>http://tc.eserver.org/20002.html</guid>
		<description>About three years ago we were asked whether we would be interested in writing a new and different kind of style manual:&#xD;&#xD;    * In addition to covering all the traditional style topics, such as capitalization and punctuation, it would have chapters on grammar, confusable words, usage (including bias-free language), and all aspects of production, from design and typography to desktop publishing and printing.&#xD;    * Its audience would be the vast majority of working writers and editors, not just those who work with scholarly manuscripts.&#xD;    * It would be written and organized in a friendly, easy-to-read style and reflect the impact of the computer on every aspect of the publishing process. &#xD;&#xD;Although we were a bit cowed at the thought of tackling such a big project -- it turned out to be 836 pages -- we didn&apos;t see how we could turn down the chance to create a guide that was truly useful.</description>
	</item>
	<item>
		<title>Shifty Adverbs</title>
		<link>http://tc.eserver.org/20004.html</link>
		<guid>http://tc.eserver.org/20004.html</guid>
		<description>Decide where to place the adverb in parentheses in these sentences to best advantage -- for the sound of it and for best sense. That is, place it near the word in the sentence you wish to emphasize. One sentence doesn&apos;t involve a decision about placement next to the verb at all.</description>
	</item>
	<item>
		<title>The Struggle for Gender-Free Language: Is It Over Yet?</title>
		<link>http://tc.eserver.org/20003.html</link>
		<guid>http://tc.eserver.org/20003.html</guid>
		<description>All current style manuals address in one form or another the need for bias-free, inclusive language. Most writers and editors deal with this issue regularly — we&apos;ve installed mental alarm systems that go off when we sense bias or something that can be construed as bias. In fact, some commentators say we&apos;ve gone too far toward what social commentator Christopher Cerf calls, with grave facetiousness, &apos;content-free writing,&apos; lest language offend anyone, anywhere.&#xD;&#xD;Does gender-free writing still present problems, and if so, how are most of us resolving them? After all these years of practice at being evenhanded, consider several litmus tests. </description>
	</item>
	<item>
		<title>Citing Internet Sources</title>
		<link>http://tc.eserver.org/19999.html</link>
		<guid>http://tc.eserver.org/19999.html</guid>
		<description>Citation styles for Internet publications are still evolving. Printed style manuals offer little guidance, and few even mention the World Wide Web. But that&apos;s no excuse for failing to credit your sources.</description>
	</item>
	<item>
		<title>Foolproof Your Files, Part 1: Proofing</title>
		<link>http://tc.eserver.org/19998.html</link>
		<guid>http://tc.eserver.org/19998.html</guid>
		<description>After weeks or months of preparation, review, and production, it can be cathartic to package up a job and send it to the print shop. If files have been too quickly or carelessly assembled, however, sending that final disk to print means crossing your fingers and hoping that nothing goes wrong.</description>
	</item>
	<item>
		<title>Half the Truth and Something Like the Truth</title>
		<link>http://tc.eserver.org/19995.html</link>
		<guid>http://tc.eserver.org/19995.html</guid>
		<description>As an art director, I&apos;m an avowed secret handshake guy from way back. They teach it to us in design school when they make us swear on a stack of Pantone color selectors and old type specimen books that we&apos;ll never reveal the secrets of the design world, especially to editors and writers (word people). Early reviews of Type &amp;amp; Layout have been ecstatic, so I had wondered whether someone had finally sold the secret handshake to the enemy. I shouldn&apos;t have worried. This is not really a design book, and it is not a book that most designers are going to care for. What worries me is that nondesigners won&apos;t know that.</description>
	</item>
	<item>
		<title>Humor in the Workplace?</title>
		<link>http://tc.eserver.org/19996.html</link>
		<guid>http://tc.eserver.org/19996.html</guid>
		<description>Over the years, I&apos;ve been accused of not taking life seriously enough. Although life certainly is no joke, it&apos;s not all Sturm und Drang or Weltschmerz, either. Mostly, I think, it&apos;s like Mozart: exhilarating and joyous except when it&apos;s not.</description>
	</item>
	<item>
		<title>Open-Source Software: Gaining Ground</title>
		<link>http://tc.eserver.org/19997.html</link>
		<guid>http://tc.eserver.org/19997.html</guid>
		<description>Have you ever run across a bug in your word processor that interfered with your work? Or perhaps you&apos;ve wished that your graphics program had a certain feature that would make your life easier.&#xD;&#xD;With most commercial software, you&apos;re at the mercy of the company that created it. All you can do is call the technical support line, explain the situation, and hope that there&apos;s a work-around or that your issue will be addressed whenever the next version is released.&#xD;&#xD;With proprietary software, the company owns the software and doesn&apos;t allow anyone else to modify it or even see the source code -- the human-readable (well, programmer-readable) instructions used to create the executable file that the computer runs. Some people have likened such software to a car with the hood locked shut so that only the manufacturer can service it.&#xD;&#xD;But with open-source software, you have other options because you have the source code. If you have the knowledge, you can modify the program yourself. If not, you can hire a programmer to make the changes you want. </description>
	</item>
	<item>
		<title>Untangling the Web: Hoaxes, Scams, and Rumors</title>
		<link>http://tc.eserver.org/19994.html</link>
		<guid>http://tc.eserver.org/19994.html</guid>
		<description>If you&apos;ve had an e-mail address for long, you&apos;ve probably received a message (forwarded through a long chain of people) warning you about some dangerous computer virus that can infect your computer through e-mail. Some warnings even say that the virus will physically damage your hard drive or monitor. But they aren&apos;t true.</description>
	</item>
	<item>
		<title>The Editorial Eye</title>
		<link>http://tc.eserver.org/10811.html</link>
		<guid>http://tc.eserver.org/10811.html</guid>
		<description>The Eye is a resource for writers, editors, designers, project managers, communications specialists, and everyone else who cares about contemporary publishing practices. Any aspect of effective printed, electronic, visual, or spoken communication is likely to appear as a topic in the Eye.</description>
	</item>
	<item>
		<title>Estimating Editorial Tasks: A Five-Step Method</title>
		<link>http://tc.eserver.org/10813.html</link>
		<guid>http://tc.eserver.org/10813.html</guid>
		<description>Everyone would agree that publications work is subject to many unknowns, but it&apos;s still possible to pin down key aspects of a project, apply educated guesswork, and calculate a relatively accurate time estimate. Here&apos;s a five-step method for arriving at that elusive number.  </description>
	</item>
	<item>
		<title>Getting Ducks in a Row: The Rules for Displayed Lists</title>
		<link>http://tc.eserver.org/10814.html</link>
		<guid>http://tc.eserver.org/10814.html</guid>
		<description>When is a list not a list? When it&apos;s not recognized as such by the reader. A good displayed list is the mental equivalent of a line of cheerful ducklings behind their sensible mom on their way to an invigorating dip. A short series of items can often be run smoothly into text, but lists longer than eight lines or so tend to stray in the reader&apos;s mind from the preceding thoughts. A run-in list that becomes estranged from its lead-in context is worthless. </description>
	</item>
	<item>
		<title>One Last Look: The Final Quality Control Review</title>
		<link>http://tc.eserver.org/10818.html</link>
		<guid>http://tc.eserver.org/10818.html</guid>
		<description>Virtually everyone in the publications field has a story to tell about &apos;the one that slipped through&apos; -- a horrible, glaring, embarrassing error that went undetected and made it into print. My personal worst was the time the company I was working for was sending a proposal to the Joint Chiefs of Staff at the Pentagon, only our proposal cover said &apos;Joint Chefs....&apos; There is always plenty of blame to go around when these errors occur, but usually it is the error-prevention system that is faulty. </description>
	</item>
	<item>
		<title>The Editor from Hell</title>
		<link>http://tc.eserver.org/10796.html</link>
		<guid>http://tc.eserver.org/10796.html</guid>
		<description>This morning I woke up in a cold sweat -- which was odd, because I usually wake up in bed. In my dream, or rather nightmare, I was reviewing a manuscript that was due to be returned to a client that very morning. As I recalled the dream, I realized why I was sweating -- the manuscript had been edited by someone who combined the worst characteristics of every copy editor I&apos;d ever known. &#xD;</description>
	</item>
	<item>
		<title>Going International</title>
		<link>http://tc.eserver.org/10724.html</link>
		<guid>http://tc.eserver.org/10724.html</guid>
		<description>For many people, setting up a Web site is their first experience with publishing documents for an international audience. It&apos;s true (for now) that most of the computers on the Internet are in the United States, but the Net includes computers in more than a hundred countries. If you put information on the Web, people from all over the world can read it. At least 15 percent of the visitors to the EEI Web pages are from outside the United States. In the first few days of the new year, pages were viewed by people from two dozen countries, including Croatia, Malaysia, the United Arab Emirates, and Venezuela. It&apos;s not called the World Wide Web for nothing.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Editorial_Eye,_The.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>