<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Radecki, Steven Lewis</title>	<link>http://tc.eserver.org/authors/Radecki,_Steven_Lewis</link>
	<description>A bibliography of works by Radecki, Steven Lewis 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>Radecki, Steven Lewis</title>
		<link>http://tc.eserver.org/dir/Radecki,_Steven_Lewis</link>
	</image>
	<item>
		<title>Practical Hypermedia: Using Hypertext and Multimedia in the Real World</title>
		<link>http://tc.eserver.org/30539.html</link>
		<guid>http://tc.eserver.org/30539.html</guid>
		<description>Multimedia and hypertext are two of the hottest topics in technical communications today. Multimedia, in one form or another, has been around for decades—so has hypertext. Both have been of enormous interest to the technical communicator specifically, and the computer user in general. Lately, we have seen advancements in computer technology that can allow a computer user to produce presentations of considerable quality. Just as the advent of the Macintosh ushered in the era of desktop publishing, the rapidly falling prices of digital video cards and image editing software are about to pave the way for another revolution in desktop computing.</description>
	</item>
	<item>
		<title>Developing Online Help for OS/2 Applications</title>
		<link>http://tc.eserver.org/30430.html</link>
		<guid>http://tc.eserver.org/30430.html</guid>
		<description>One of the biggest problems facing Help developers is that of providing users with adequate methods of navigation through what can be huge amounts of information. After more than a two or three jumps, users can find themselves in topics that might be useful, but with no clear indication of how they got there or how to return to where they started. OS/2 gives the Help developer extraordinarily flexible tools for creating online documentation that can prevent this situation and provide users with a clearer path through online information than many other platforms can provide. However, this enhanced usability is not without its cost.</description>
	</item>
	<item>
		<title>Designing Information for the 21st Century</title>
		<link>http://tc.eserver.org/22866.html</link>
		<guid>http://tc.eserver.org/22866.html</guid>
		<description>In the past, documentation meant printed books. Then along came online help. Online books soon followed. Now we have the Internet and web pages.&#xD;Developing a documentation plan today means&#xD;more than planning how books are going to be&#xD;structured, reviewed, and printed. It needs to take&#xD;into account the possibilities that these new media&#xD;have to offer. Achieve the most effective results by&#xD;making delivery in these media part of your&#xD;documentation planning.</description>
	</item>
	<item>
		<title>HTML: Making the Move</title>
		<link>http://tc.eserver.org/20166.html</link>
		<guid>http://tc.eserver.org/20166.html</guid>
		<description>HTML is perhaps the most discussed topic in technical communications since the invention of the word processor. Interest in the Internet and&#xD;the World Wide Web has exploded beyond anyone’s expectations (and perhaps their imagination as well). Microsoft has announced&#xD;that they are moving away from Rich Text Format&#xD;(Rw) as the source format for their Windowsbased&#xD;online help systems, and Netscape is in the&#xD;process of developing a cross-platform online help&#xD;API that is also based on HTML. The question&#xD;seems no longer to be whether or not to make the&#xD;move to HTML, but when to make the move.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Radecki,_Steven_Lewis.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>