<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Indus</title>	<link>http://tc.eserver.org/publisher/Indus</link>
	<description>A listing of works published by Indus 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>Indus</title>
		<link>http://tc.eserver.org/dir/Indus</link>
	</image>
	<item>
		<title>Open-Source Software for Technical Writers</title>
		<link>http://tc.eserver.org/35220.html</link>
		<guid>http://tc.eserver.org/35220.html</guid>
		<description>For companies that are struggling in the current times because of the economic slowdown, an option that might not compromise on product quality is to switch to open-source software. In this article, I will talk about open-source publishing tools for the writing community.</description>
	</item>
	<item>
		<title>The Voice Speaks</title>
		<link>http://tc.eserver.org/35221.html</link>
		<guid>http://tc.eserver.org/35221.html</guid>
		<description>I learnt that a verb is the most essential part of speech.  So, I thought investing a little time to learn to use it better (if not master it) might not be a bad idea.  But then, there are so many aspects of a verb.  Can I ever say I learnt it? I can try one proven (presumably by the British) method: divide and conquer.  I will start with the voice of a verb, the much-talked-about aspect of a verb.</description>
	</item>
	<item>
		<title>Don&apos;t Lose Your Articles</title>
		<link>http://tc.eserver.org/35222.html</link>
		<guid>http://tc.eserver.org/35222.html</guid>
		<description>One of the difficult concepts to understand in the English language is perhaps the manner in which articles are used in a sentence. Over the course of one&apos;s life history, every student of English has had to face this nightmare at one point of time or another. The verbs are all in place and you know the nouns, the pronouns are fairly obvious, and the prepositions can eventually be worked out, but what comes before the word year and what comes before SMS is tricky.</description>
	</item>
	<item>
		<title>My Journey from Technical Writing to Pharma Quality Management</title>
		<link>http://tc.eserver.org/35223.html</link>
		<guid>http://tc.eserver.org/35223.html</guid>
		<description>Like most people who entered the technical communication profession in India in the mid to late 1990s, I too became a technical writer more by accident than by design. I enjoyed my technical writing career thoroughly, but slowly moved away, and a decade later, I now find myself heading the Quality Management function at a multi-national clinical research and technology company in India. The career paths of no two individuals are similar. And yet, there are always some common themes in successful transitions from one career path to another.</description>
	</item>
	<item>
		<title>Awful Writer or “Awe”full Writer</title>
		<link>http://tc.eserver.org/35224.html</link>
		<guid>http://tc.eserver.org/35224.html</guid>
		<description>If you are reading this article in INDUS, I assume that the majority of you must be technical writers. The peer-review checklist might be firmly etched in your mind. Please make sure this checklist in disabled. If doing so is not possible, just click the X sign at the top-right corner of the screen. Also, if you have no sense of humor, it is mandatory to click the X sign. I make no apologies for the grammatical errors or syntax errors or sentence structure or comma splices or… whew..pant..pant… this ‘or’ is making me breathless.  In fact, I am thriving on these errors because my creative skills are running riot. I have expressed my thoughts in an unconventional manner and, believe me, the feeling is exhilarating and invigorating.</description>
	</item>
	<item>
		<title>At the Touch of a Button</title>
		<link>http://tc.eserver.org/35207.html</link>
		<guid>http://tc.eserver.org/35207.html</guid>
		<description>Are the days of print documentation over? How ‘usable’ is your print documentation?</description>
	</item>
	<item>
		<title>Too Many Inputs Freak Out the Technical Writer</title>
		<link>http://tc.eserver.org/35208.html</link>
		<guid>http://tc.eserver.org/35208.html</guid>
		<description>In such a scenario, this article presents some of the practices that have helped me track and address inputs effectively – regardless of their volume and importance.</description>
	</item>
	<item>
		<title>Don&apos;t Stop Learning!</title>
		<link>http://tc.eserver.org/35209.html</link>
		<guid>http://tc.eserver.org/35209.html</guid>
		<description>This article examines the need for continuous learning and the challenges that working professionals must overcome to invest in learning. It also explores how experience makes us better learners, and analyzes the relative effectiveness of various learning techniques.</description>
	</item>
	<item>
		<title>Web 2.0, and Me</title>
		<link>http://tc.eserver.org/35210.html</link>
		<guid>http://tc.eserver.org/35210.html</guid>
		<description>As help systems continue to evolve, whatever name they are called, we will increasingly have to face responsibility for their content, and bring their expertise to what we write. The new systems provide us with all the required tools that tell us the problems with their content. It is up to us to leverage that information to provide better content, and act as ambassadors for products that we write. If writers can go a step ahead, and use their help information to sell products, and reduce the burden on customer support, we would have truly arrived.</description>
	</item>
	<item>
		<title>Do I Really Need a Style Guide?</title>
		<link>http://tc.eserver.org/35211.html</link>
		<guid>http://tc.eserver.org/35211.html</guid>
		<description>Style guides recommend certain styles. In the domain of technical communication, we refer to guides for writing style, presentation of content in user documentation and technical documents, and graphical user interface of software and web sites.</description>
	</item>
	<item>
		<title>The Personable Manual</title>
		<link>http://tc.eserver.org/35212.html</link>
		<guid>http://tc.eserver.org/35212.html</guid>
		<description>Why do product manuals sound formal and stiff-upper-lipped? Why don’t users read manuals? These questions have haunted the precincts of Technical Writing for quite some time now. From what I have seen in Indian writers, I am forced to conclude that English Composition, as we were taught in school, is the culprit. Our merit was based on how verbose we were. They judged our style based on how ‘formal’ we were. Take for example, the leave letter. I am sure you have written a few in school or college. Rewind and replay one of those leave letters. Right from the salutation (Respected Sir/Madam) to the signature (Faithfully/Obediently yours) it reeks of colonialism. And, we have yet to learn our lessons. In this age of globalization (or globalisation, to my stiff-upper-lip comrades), it is important to pay attention to the three Cs: Consistency, Context, and Culture.</description>
	</item>
	<item>
		<title>Don&apos;t Stop Learning!</title>
		<link>http://tc.eserver.org/34440.html</link>
		<guid>http://tc.eserver.org/34440.html</guid>
		<description>This article examines the need for continuous learning and the challenges that working professionals must overcome to invest in learning. It also explores how experience makes us better learners, and analyzes the relative effectiveness of various learning techniques.</description>
	</item>
	<item>
		<title>Web 2.0, and Me</title>
		<link>http://tc.eserver.org/34441.html</link>
		<guid>http://tc.eserver.org/34441.html</guid>
		<description>How has Web 2.0 affected me as a writer? The ability for users to comment and rate content. Improved help systems. Blogging.</description>
	</item>
	<item>
		<title>Web Application Design Patterns</title>
		<link>http://tc.eserver.org/34442.html</link>
		<guid>http://tc.eserver.org/34442.html</guid>
		<description>Web Application Design Patterns by Pawan Vora provides practical user interface design guidance for developing web applications by offering a &quot;working&quot; starting point that designers can adapt and refine to develop creative solutions. He condenses best practice methods, along with research and solid experience to create a useful reference about designing web applications.</description>
	</item>
	<item>
		<title>Do I Really Need a Style Guide?</title>
		<link>http://tc.eserver.org/34443.html</link>
		<guid>http://tc.eserver.org/34443.html</guid>
		<description>So, after all, I must follow those infernal style guides. I am straight-jacketed. Am I not?</description>
	</item>
	<item>
		<title>The Personable Manual</title>
		<link>http://tc.eserver.org/34444.html</link>
		<guid>http://tc.eserver.org/34444.html</guid>
		<description>Why do product manuals sound formal and stiff-upper-lipped? Why don’t users read manuals? These questions have haunted the precincts of Technical Writing for quite some time now. From what I have seen in Indian writers, I am forced to conclude that English Composition, as we were taught in school, is the culprit.</description>
	</item>
	<item>
		<title>The Systematic Design of Instruction</title>
		<link>http://tc.eserver.org/34445.html</link>
		<guid>http://tc.eserver.org/34445.html</guid>
		<description>The Systematic Design of Instruction is a book on Instructional Design written by Walter Dick, Lou Carey, and James O. Carey. The book introduces the fundamentals of instructional design and explains the concepts and procedures for designing, developing, and evaluating instruction.</description>
	</item>
	<item>
		<title>David Pogue&apos;s Secret Weapon: Patience</title>
		<link>http://tc.eserver.org/34073.html</link>
		<guid>http://tc.eserver.org/34073.html</guid>
		<description>New York Times gadget guy David Pogue, a former Broadway orchestra conductor and MacWorld back-page columnist, is probably the world&apos;s most widely read and watched tech product reviewer. As a fellow contributor to the Times, I can confirm that anything Pogue writes pulls down several times as many page views as my most popular work. How does he do it?</description>
	</item>
	<item>
		<title>Embedded Help System: The Emerging Help Technology</title>
		<link>http://tc.eserver.org/33887.html</link>
		<guid>http://tc.eserver.org/33887.html</guid>
		<description>Embedded user assistance is a cutting-edge approach towards delivering online help that provides dynamic, context-sensitive, task-based information. Such a help system is very different from other types of online help in the sense that it requires very short and focused topics. This article examines embedded help system as an emerging help presentation that offers the potential for users to access information when and where they need it while using a software program. It also evaluates the ability of embedded help systems to overcome usability issues that are inherent in traditional online help systems.</description>
	</item>
	<item>
		<title>Fundamentals of Business Process Documentation</title>
		<link>http://tc.eserver.org/33888.html</link>
		<guid>http://tc.eserver.org/33888.html</guid>
		<description>It is important to identify, understand, and evaluate key business processes to determine how effective they are in accomplishing the business goals of an organization. As a result, end-to-end business process documentation is increasingly becoming a significant initiative for many organizations. Essentially, process documentation should communicate the guidelines to support specific processes, and can be used by a wide range of business units, partners, process leaders, and anyone who is involved in these processes. Interviewing people who follow a business process is an effective method toward understanding how the business process is executed. While interviewing the right people to understand how they execute processes, it is essential that the writers look beyond just recording what they are told about the process. Handling situations like these also provide opportunities for the writers to evolve to business domain analysts or subject matter experts</description>
	</item>
	<item>
		<title>sIFR 2.0: Rich Accessible Typography for the Masses</title>
		<link>http://tc.eserver.org/32828.html</link>
		<guid>http://tc.eserver.org/32828.html</guid>
		<description>Over the last several months, a small group of web developers and designers have been hard at work perfecting a method to insert rich typography into web pages without sacrificing accessibility, search engine friendliness, or markup semantics. The method, dubbed sIFR (or Scalable Inman Flash Replacement), is the result of many hundreds of hours of designing, scripting, testing, and debugging.</description>
	</item>
	<item>
		<title>Sustaining the Readers&apos; Interest</title>
		<link>http://tc.eserver.org/32489.html</link>
		<guid>http://tc.eserver.org/32489.html</guid>
		<description>Sometimes, we come across articles on technical subjects that are hard to put down. They even make us ruminate over their content, and talk about them. Though these articles are just for our information, they end up staying in our heart by chance or by design. It is not possible to get so far a reach through the technical coverage alone. The authors have presented them so nicely that we even resist any demand to stop in the middle while reading them. We find such articles mostly in news papers and magazines. As an editor, I have my own reasons for that &apos;Coup de grâce&apos;! We, the technical writers, can surely pick up some of the clues from our brethren - the journalists.</description>
	</item>
	<item>
		<title>Developing Mentoring Programs for Technical Writers</title>
		<link>http://tc.eserver.org/32490.html</link>
		<guid>http://tc.eserver.org/32490.html</guid>
		<description>Mentoring is an effective strategy that can contribute significantly to the career development of employees. It provides a cost-effective work-based learning strategy to achieve career development outcomes for individual employees. It is an effective method for the transference of professional, technical and management skills.</description>
	</item>
	<item>
		<title>Attaining Review Nirvana with Acrobat 8 Professional</title>
		<link>http://tc.eserver.org/32491.html</link>
		<guid>http://tc.eserver.org/32491.html</guid>
		<description>Getting documents reviewed has always been a tricky proposition for writers. From pleading to coercion to bribery just stopping short of third-degree torture, writers have documented many methods for getting reviews done effectively and in time. For those writers who gave up altogether and for those who just did not care too much for reviews, there is bad news coming – companies are asking for user feedback on the content that you wrote. Users, as we know them, can shame the most cynical movie critic when it comes to commenting. In my quest many a tool tried to lure me, but when Acrobat 8 strut its shared review stuff in front of me, I finally succumbed.</description>
	</item>
	<item>
		<title>Join the (User) Group</title>
		<link>http://tc.eserver.org/32492.html</link>
		<guid>http://tc.eserver.org/32492.html</guid>
		<description>Here’s a complaint I’ve heard from most  of  the  technical writers  I’ve  met:  “I  never  get to meet my users.” User input helps us decide what content to include and in what form, and can confirm whether our books are effective. But getting user input can be difficult—at least I thought so, until I discovered a fun way to meet hundreds of users each year.</description>
	</item>
	<item>
		<title>Interviewing Technical Writers</title>
		<link>http://tc.eserver.org/32493.html</link>
		<guid>http://tc.eserver.org/32493.html</guid>
		<description>Surprisingly, my first experience as an interviewer was as uneasy as my first job interview. I then realized that being on the other side of the table is not as easy as it is made out to be, especially if conducting an interview is unfamiliar territory. Later on, as I matured into this role, I created a style of my own and soon found it to be an interesting and inspiring proposition, though challenging.</description>
	</item>
	<item>
		<title>Simple Cognition Facts!</title>
		<link>http://tc.eserver.org/32494.html</link>
		<guid>http://tc.eserver.org/32494.html</guid>
		<description>Sometimes users find it difficult to perform tasks based on the information provided. Take a minute to understand why this could happen.</description>
	</item>
	<item>
		<title>Sensitivity in Writing</title>
		<link>http://tc.eserver.org/29361.html</link>
		<guid>http://tc.eserver.org/29361.html</guid>
		<description>The biggest impact of globalization is our vast exposure to diversity. Compared to earlier generations, we regularly come across a variety of different people. As professional communicators, it is extremely important for us to recognize this diversity and represent it sensitively in content that we develop.</description>
	</item>
	<item>
		<title>The Fine Art of Editing</title>
		<link>http://tc.eserver.org/28813.html</link>
		<guid>http://tc.eserver.org/28813.html</guid>
		<description>Editing is an art that needs to be cultivated and fine-tuned just like any other. When one is novice, the editing goals are to proofread, to clean up the text, and to correct &apos;grammatical&apos; errors. The entire focus is on words and phrases. So, when they edit, they read the text as it comes and edit the words to make the text read better. What is it that they really miss? They often miss the big picture, the whole idea, and the context.</description>
	</item>
	<item>
		<title>INDLISH: A Book for Every English-Speaking Indian</title>
		<link>http://tc.eserver.org/28814.html</link>
		<guid>http://tc.eserver.org/28814.html</guid>
		<description>At last, a book on what ails English in India! Why do we speak the way we do? Why do we switch to the passive voice in English, though we keep to the active in our mother tongues? Why are our letters long and wordy and yet can&apos;t get the point across? Why are our textbooks so wordy, and yet so vacuous?</description>
	</item>
	<item>
		<title>A Lesson in Usability</title>
		<link>http://tc.eserver.org/28815.html</link>
		<guid>http://tc.eserver.org/28815.html</guid>
		<description>Usability testing brings with it images of sterile usability testing labs...users grappling with tasks set out for them, unsure if the test measured their merits or those of the help system...and experts talking in hushed tones of &apos;cognitivism, constructivism, behaviourism and what-have-you-ism&apos;. A close observation and accurate record of user interaction with the artifact to be tested, in a real-life environment, can often ascertain if the document was worth its screen captures and fonts by establishing the only fact that counts - Did it help or not? As a writer, who began my career in communication at an advertising agency, I have often used a few &apos;tricks-of-the-trade&apos; routinely used by copywriters, (like emphasis on the word FREE in advertisements), with predictably happy results, from the &apos;user-perspective&apos;.</description>
	</item>
	<item>
		<title>The Myth of &quot;The User&quot;</title>
		<link>http://tc.eserver.org/28812.html</link>
		<guid>http://tc.eserver.org/28812.html</guid>
		<description>Instead of becoming computer users, like the cheery protagonists of Star Trek, we&apos;ve become the computer used, like the gloomy inhabitants of Dilbert.</description>
	</item>
	<item>
		<title>Client-Friendly Atmosphere: The Polish and The Lubricants</title>
		<link>http://tc.eserver.org/27086.html</link>
		<guid>http://tc.eserver.org/27086.html</guid>
		<description>During the last few years in projects, I interacted with a lot of clients. All these projects were based offshore, where client interaction was mainly through emails or teleconferences. When you do not work face-to-face with clients, communication is key to win your clients&apos; confidence.</description>
	</item>
	<item>
		<title>Designing a Software User Assistance System</title>
		<link>http://tc.eserver.org/27084.html</link>
		<guid>http://tc.eserver.org/27084.html</guid>
		<description>This article looks at a methodology for developing a software user assistance (UA) system in a structured manner. The software UA system could have both paper-based user manuals and online help systems.</description>
	</item>
	<item>
		<title>Hidden Information for All to See</title>
		<link>http://tc.eserver.org/27085.html</link>
		<guid>http://tc.eserver.org/27085.html</guid>
		<description>While it takes special forensic tools to access most of the hidden information in computers, some of it is in plain view and can be seen without forensic tools. This article is about one of the &apos;plain view&apos; instances: information Microsoft Word saves about you, your company, and the topic you are writing about, all of which can be seen by anyone who has access to your document.</description>
	</item>
	<item>
		<title>Guidelines on Graphics Usage</title>
		<link>http://tc.eserver.org/26066.html</link>
		<guid>http://tc.eserver.org/26066.html</guid>
		<description>Illustrations and technical graphics are essential to any technical documentation. They assist users&apos; understanding by simplifying complex content through clear, understandable and effective information. A primary objective of technical documentation is to ensure that users use products effectively and safely. Graphics and illustrations assist in accomplishing this objective. Striking the right balance between text and graphics enables documentation to be effective support to product use. This article recommends a few guidelines and best practices to adopt when working with illustrations and graphics in technical documents.</description>
	</item>
	<item>
		<title>Microsoft Manual of Style for Technical Publications</title>
		<link>http://tc.eserver.org/26068.html</link>
		<guid>http://tc.eserver.org/26068.html</guid>
		<description>Microsoft is one of the largest software companies in the world. Thus, with their rich experience in documentation it is only natural that they share it with the rest of the IT industry. The Microsoft Manual of Style for Technical Publications, Third Edition (MSTP) is the latest step in this direction and takes care of latest technologies and technical terms.</description>
	</item>
	<item>
		<title>Sentence Types and Sentence Structures Revisited</title>
		<link>http://tc.eserver.org/26067.html</link>
		<guid>http://tc.eserver.org/26067.html</guid>
		<description>Before we discuss sentence types and structures, let us regard writing as a donut. When talking of sentence types, we will consider four building blocks of the donut.</description>
	</item>
	<item>
		<title>Spying for Words</title>
		<link>http://tc.eserver.org/26069.html</link>
		<guid>http://tc.eserver.org/26069.html</guid>
		<description>Want to know more abou words? Or want some more brilliant snippets? Log on to The Word Spy. It is a site maintained by Paul McFedries, the well-known author and word-follower. </description>
	</item>
	<item>
		<title>Implementing Information Architecture Using XML: A Business-Driven Approach</title>
		<link>http://tc.eserver.org/26062.html</link>
		<guid>http://tc.eserver.org/26062.html</guid>
		<description>A few of aspects that are easy to miss in the excitement of trying to implement an XML-based information architecture in an organization.</description>
	</item>
	<item>
		<title>Information Architecture Concepts for the Technical Writer</title>
		<link>http://tc.eserver.org/26063.html</link>
		<guid>http://tc.eserver.org/26063.html</guid>
		<description>Information Architecture (IA) as a discipline practiced by professionals in the information processing and development industry has many definitions and levels of understanding.</description>
	</item>
	<item>
		<title>Microsoft Word 2000 and Readability</title>
		<link>http://tc.eserver.org/26064.html</link>
		<guid>http://tc.eserver.org/26064.html</guid>
		<description>A discussion of th Flesch-Kincaid Grade Level formula, as implemented in Microsoft Word.</description>
	</item>
	<item>
		<title>Project Management for the Technical Communicator</title>
		<link>http://tc.eserver.org/26065.html</link>
		<guid>http://tc.eserver.org/26065.html</guid>
		<description>Tasks need to be managed to be completed on time, with available resources to achieve the required result.</description>
	</item>
	<item>
		<title>The Responsibilities of an Information Architect in the Technical Information-Development World</title>
		<link>http://tc.eserver.org/26061.html</link>
		<guid>http://tc.eserver.org/26061.html</guid>
		<description>In working with information-development groups who want to move into content management and a structured writing environment, I often find that the potential for role of information architect is not well understood.</description>
	</item>
	<item>
		<title>Are Pune Technical Writers the Highest Paid?</title>
		<link>http://tc.eserver.org/26053.html</link>
		<guid>http://tc.eserver.org/26053.html</guid>
		<description>Are Pune technical writers the highest paid of the breed in India? The word on the street doesn&apos;t say so. As a hiring manager, I don&apos;t believe so. But, the salary survey suggests so.</description>
	</item>
	<item>
		<title>Dealing With the Salary Survey</title>
		<link>http://tc.eserver.org/26054.html</link>
		<guid>http://tc.eserver.org/26054.html</guid>
		<description>Thanks to Makarand, Paresh, Mira, and other contributors, some of our questions are answered after a gap of two years and we have some takeaways from the salary survey.</description>
	</item>
	<item>
		<title>Emerging from the Sidelines: The Indian Technical Writing Community in a Global Marketplace</title>
		<link>http://tc.eserver.org/26052.html</link>
		<guid>http://tc.eserver.org/26052.html</guid>
		<description>Comparing trends in India and the U.S. gives a sense that the Indian technical communication community is on a strong footing and can gain a competitive edge by focusing on some key areas.</description>
	</item>
	<item>
		<title>Good Opportunity for Technical Communication Service Providers</title>
		<link>http://tc.eserver.org/26055.html</link>
		<guid>http://tc.eserver.org/26055.html</guid>
		<description>When I tried to look at the salary survey from the point of view of a Technical Communication Service Provider (TCSP), I noticed quite a few interesting points.</description>
	</item>
	<item>
		<title>Listen, the Numbers are Singing</title>
		<link>http://tc.eserver.org/26056.html</link>
		<guid>http://tc.eserver.org/26056.html</guid>
		<description>Among the constant chattering noise that these numbers are making, they also sing some common tunes.</description>
	</item>
	<item>
		<title>One Cannot Live by Salary Alone</title>
		<link>http://tc.eserver.org/26057.html</link>
		<guid>http://tc.eserver.org/26057.html</guid>
		<description>Once our profession is known outside IT, the scope for technical writers will grow in geometric proportions. Clearly, there are good times ahead.</description>
	</item>
	<item>
		<title>Salaries in India: Boom or Bust?</title>
		<link>http://tc.eserver.org/26058.html</link>
		<guid>http://tc.eserver.org/26058.html</guid>
		<description>The movement of jobs from the U.S. and other countries to India has really fueled salary growth.</description>
	</item>
	<item>
		<title>These Numbers Tell Many a Tale</title>
		<link>http://tc.eserver.org/26059.html</link>
		<guid>http://tc.eserver.org/26059.html</guid>
		<description>While there are a few obvious anomalies in the numbers, the average salary of people with less than a year&apos;s experience being more than that of 1-2 years range, mostly the numbers appear to be credible.</description>
	</item>
	<item>
		<title>What Matters the Most</title>
		<link>http://tc.eserver.org/26060.html</link>
		<guid>http://tc.eserver.org/26060.html</guid>
		<description>Employers are not looking for certification or relevant technical writing educational qualifications while hiring or while designing the compensation package.</description>
	</item>
	<item>
		<title>Where Do You Want to Work Today?</title>
		<link>http://tc.eserver.org/25984.html</link>
		<guid>http://tc.eserver.org/25984.html</guid>
		<description>This article explores the work habits of technical writers in different regions of the world. The article is based on a a survey and publishes the results based on the responses of 900+ technical writers worldwide.</description>
	</item>
	<item>
		<title>Creating User-Friendly Documentation</title>
		<link>http://tc.eserver.org/19743.html</link>
		<guid>http://tc.eserver.org/19743.html</guid>
		<description>We often hear that users do not read documents. To lure readers into reading our documents, we must make documents user-friendly.</description>
	</item>
	<item>
		<title>Designing for Accessibility</title>
		<link>http://tc.eserver.org/19745.html</link>
		<guid>http://tc.eserver.org/19745.html</guid>
		<description>Any large audience for a Web site will include users who have physical challenges to accessing your content. Designing for accessibility means that you should be developing Web pages that will remain accessible despite any physical, sensory, and cognitive disabilities, work constraints, or technological barriers. Most mainstream Web sites are so heavily image- and media-intensive that they are not suitable for adaptive devices such as screen readers, voice browsers, and braille translators. Many of the guidelines necessary for developing accessible content naturally lend themselves to creating good design.</description>
	</item>
	<item>
		<title>Designing Usable Technical Documents: Why Bother?</title>
		<link>http://tc.eserver.org/19744.html</link>
		<guid>http://tc.eserver.org/19744.html</guid>
		<description>Many professionals in the field of technical writing involved in the design of instruction guides, will at some point in their career have experienced some doubt whether their efforts to produce high quality documentation really make sense. Do consumers attach some value to the instruction guides for the products they have purchased? Do they use these documents at all, or are most instruction guides thrown away, together with the packing material of the equipment they come with?</description>
	</item>
	<item>
		<title>The Essentials of Effective Communication</title>
		<link>http://tc.eserver.org/19738.html</link>
		<guid>http://tc.eserver.org/19738.html</guid>
		<description>Good writing allows writers to be taken seriously, and being taken seriously is always important in communicating ideas effectively. If a person&apos;s writing is awkward, clumsy, or questionable, readers may get the wrong impression. And, first impressions can determine what people will read and what they will not.</description>
	</item>
	<item>
		<title>The Keys to Clarity, Consistency, and Correctness</title>
		<link>http://tc.eserver.org/19739.html</link>
		<guid>http://tc.eserver.org/19739.html</guid>
		<description>How can you make documentation more clear, consistent, and correct for your users? Following are some guidelines I find effective when documenting concepts and organizing documents.</description>
	</item>
	<item>
		<title>Many Heads Make Work Right</title>
		<link>http://tc.eserver.org/19740.html</link>
		<guid>http://tc.eserver.org/19740.html</guid>
		<description>Writing is popularly considered a spontaneous exercise, and often is. Spontaneous writing, however, does not always result in high quality results. </description>
	</item>
	<item>
		<title>Tools for Authoring Knowledge Products</title>
		<link>http://tc.eserver.org/19741.html</link>
		<guid>http://tc.eserver.org/19741.html</guid>
		<description>Authoring tools are used to create and integrate the components of knowledge products. They include tools used by designers, writers, editors, artists, animators, photographers, videographers, and others involved in producing knowledge products.</description>
	</item>
	<item>
		<title>Usability FAQ</title>
		<link>http://tc.eserver.org/19746.html</link>
		<guid>http://tc.eserver.org/19746.html</guid>
		<description>Usability is an abstract quality by itself. However, it can be divided into measurable attributes.</description>
	</item>
	<item>
		<title>Weaving in the Cultural Context</title>
		<link>http://tc.eserver.org/19737.html</link>
		<guid>http://tc.eserver.org/19737.html</guid>
		<description>If you are reading this you’re probably responsible for preparing print, electronic, or visual materials for a client base that is marketing, selling, informing, and/or teaching in another part of the world. If that doesn&apos;t exactly describe you at this moment, it will be part of your job description in the future.</description>
	</item>
	<item>
		<title>Why Technical Communicators Make Good Usability Advocates</title>
		<link>http://tc.eserver.org/19742.html</link>
		<guid>http://tc.eserver.org/19742.html</guid>
		<description>Usability is rapidly becoming an important skill for technical communicators and a growing interest for those seeking to expand their role as technical communicators into other areas of product development. The STC usability SIG now has over 2000 members, and the conference sessions at STC regional and annual conferences increasingly focus on usability. This year, a new &apos;stem&apos; was created at the annual conference, which combined Information Design and Usability, because they just naturally belong together. It worked so well that it will be continued in future conferences.</description>
	</item>
	<item>
		<title>Freelancing in Technical Writing – Part I</title>
		<link>http://tc.eserver.org/19732.html</link>
		<guid>http://tc.eserver.org/19732.html</guid>
		<description>Freelancing is one of the most lucrative options available to Technical Writers. While being your own boss may sound pleasant, it is not as easy as it sounds.</description>
	</item>
	<item>
		<title>Handling Software Failures: Need For Effective Training</title>
		<link>http://tc.eserver.org/19735.html</link>
		<guid>http://tc.eserver.org/19735.html</guid>
		<description>The cost of software failure in terms of schedule overruns and poor quality are well known.</description>
	</item>
	<item>
		<title>Needless to Say</title>
		<link>http://tc.eserver.org/19731.html</link>
		<guid>http://tc.eserver.org/19731.html</guid>
		<description>The needless repetition of words and the repeating of ideas is everywhere - in newspapers, books, magazines, e-mails, television, and even in conversation. They’re called redundancies and the English language is full of them. In fact, research shows that about 50 percent of English is redundant.</description>
	</item>
	<item>
		<title>Principle-Centered Leadership for IT</title>
		<link>http://tc.eserver.org/19736.html</link>
		<guid>http://tc.eserver.org/19736.html</guid>
		<description>The IT revolution has been a much-needed boon for India. It has not only changed the fiscal reserves ($), ushered a new economy and created numerous job opportunities but also caused worldwide recognition of Indian talent. The revolution has been slow, but never a result of chance accidents. In earlier revolutions, Indians missed the bus and became followers, but the IT revolution is different as we have taken the lead and demonstrated our capabilities in the software sector to the world.</description>
	</item>
	<item>
		<title>Retronyms: Looking Back on Progress</title>
		<link>http://tc.eserver.org/19734.html</link>
		<guid>http://tc.eserver.org/19734.html</guid>
		<description>Technology changes the way we live. It also affects the way we speak. As the gadgets we make and use grow more complex, we’re sneaking in complexities into the words we use too. Like ‘printed book’. What was always called just a ‘book’ (hard cover or paperback) is now called a printed book, simply because now we have e-books. What was once simply a guitar is now an acoustic guitar, because of the growing popularity of electric guitars.</description>
	</item>
	<item>
		<title>Seek and Ye Shall Find</title>
		<link>http://tc.eserver.org/19730.html</link>
		<guid>http://tc.eserver.org/19730.html</guid>
		<description> It&apos;s the information age, you know... it has been for a while. You hear people say that you can find anything on the Internet. What they don&apos;t tell you though, is how. Sure, there are search engines and there are SEARCH engines, but nobody tells you how to use them properly. Well, this is about how to make the most of search engines. While this article is written with a focus on Google (www.google.com), the principles can be applied to other search engines as well.</description>
	</item>
	<item>
		<title>Technical Communication in Power Systems</title>
		<link>http://tc.eserver.org/19729.html</link>
		<guid>http://tc.eserver.org/19729.html</guid>
		<description>A technical writer in power systems must be a perfect jack-of -all trades, with flair to glean information on materials, equipments, systems, applications – and the related skills! A keen eye for detail is critical. The smallest slip can cause a serious mishap. But curiosity never killed a good technical writer! Being a good electrical engineer inherently takes care of most of these requirements - certainly not all.  The scope is limitless to the self-motivated communicator.</description>
	</item>
	<item>
		<title>Technical Writing in 1993 and 2003</title>
		<link>http://tc.eserver.org/19728.html</link>
		<guid>http://tc.eserver.org/19728.html</guid>
		<description> Ten years ago, if someone had asked me about my profession, I would have spent a good 15 minutes explaining what I did for a living. Today, ‘Technical Writing’ is answer enough. This is one notable change in my life. In the last 10 years, I have witnessed many important changes in the field of technical writing. Here are a few.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Indus.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>