<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Meyer, Eric</title>	<link>http://tc.eserver.org/authors/Meyer,_Eric</link>
	<description>A bibliography of works by Meyer, Eric 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>Meyer, Eric</title>
		<link>http://tc.eserver.org/dir/Meyer,_Eric</link>
	</image>
	<item>
		<title>Five Ways To Make Sure That Users Abandon Your Forms</title>
		<link>http://tc.eserver.org/33123.html</link>
		<guid>http://tc.eserver.org/33123.html</guid>
		<description>What do you really need to know in your form process? Be brutal. Don&apos;t include stuff that your sales team would like. Completing a form is rarely (if ever) the goal in and of itself. The goal is to entice the user into a deeper relationship (of some sort) with your web site. Notice that I didn&apos;t say that the goal was to complete a transaction or make a sale. That is evidence of the deeper relationship, not the vehicle by which you persuade your users.</description>
	</item>
	<item>
		<title>Formal Weirdness</title>
		<link>http://tc.eserver.org/32498.html</link>
		<guid>http://tc.eserver.org/32498.html</guid>
		<description>Explains some of the technical reasons for form controls being so hard to style consistently across platforms with CSS. Also asks a lot of good questions related to how various CSS properties should affect form controls if browsers would let them.</description>
	</item>
	<item>
		<title>Acid Redux</title>
		<link>http://tc.eserver.org/32438.html</link>
		<guid>http://tc.eserver.org/32438.html</guid>
		<description>I fully acknowledge that a whole lot of very clever thinking went into the construction of Acid3 (as was true of Acid2), and that a lot of very smart people have worked very hard to pass it. Congratulations all around, really. I just can’t help feeling like some broader and more important point has been missed.</description>
	</item>
	<item>
		<title>From Switches to Targets: A Standardista&apos;s Journey</title>
		<link>http://tc.eserver.org/32444.html</link>
		<guid>http://tc.eserver.org/32444.html</guid>
		<description>Version targeting allows browsers to much more easily develop new features and fix bugs and shortcomings in existing features, which has the potential to speed up the evolution of web design and development. That alone is reason enough to give it a chance.</description>
	</item>
	<item>
		<title>Color Blender</title>
		<link>http://tc.eserver.org/25748.html</link>
		<guid>http://tc.eserver.org/25748.html</guid>
		<description>Supply two color values in either hex, short hex, RGB percentages, or RGB decimals and get as many as ten colors shades between the two you supplied. Great for finding a color halfway between two shades you like, or mixing two colors together in various proportions.</description>
	</item>
	<item>
		<title>S5: A Simple Standards-Based Slide Show System</title>
		<link>http://tc.eserver.org/25749.html</link>
		<guid>http://tc.eserver.org/25749.html</guid>
		<description>A simple slide show system that uses one (X)HTML file, some CSS, and a bit of JavaScript. You can have your presentation slides and printed handouts generated from the same file.</description>
	</item>
	<item>
		<title>Cascading Style Sheets: HTML and CSS</title>
		<link>http://tc.eserver.org/21653.html</link>
		<guid>http://tc.eserver.org/21653.html</guid>
		<description>In many ways, the Cascading Style Sheets (CSS) specification represents a unique development in the history of the World Wide Web. In its inherent ability to allow richly styled structural documents, CSS is both a step forward and a step backward--but it&apos;s a good step backward, and a needed one. To see what is meant by this, it is first necessary to understand how the Web got to the point of desperately needing something like CSS, and how CSS makes the web a better place for both page authors and web surfers.</description>
	</item>
	<item>
		<title>CSS Design: Going to Print</title>
		<link>http://tc.eserver.org/13542.html</link>
		<guid>http://tc.eserver.org/13542.html</guid>
		<description>One of the wonderful things about CSS is that it allows authors to create media-specific styles for a single document. We’re pretty used to styling for the screen, but thinking about other media isn’t a habit yet. And as all the “printer-friendly” links attest, our thinking about the print medium has been limited to recreating a document in a different way. Why bother, when the power to offer your readers a better view of your material in print is no further away than a well-structured document and a media-specific style sheet?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Meyer,_Eric.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>