A Technical Writer has to stay up to date on the latest publishing software and trends within our field. We also have to be able to explain those software or trends to our employers or clients. I started to read about DITA about three years ago and I did not pay much attention. I was hired by YESCO Electronics as a technical writer. Their software choice was Adobe InDesign with their publishing choice being PDF. I was okay with this until I started documenting several different types of documentation that consisently required updating.
I started to read more about DITA and how efficient it could be. I tried to find a way to pitch DITA to the company. However, I could not find an article that really delved into the why should I care as a technical writer or why my employer should care; until now. “Why Should I Care About Dita? by Jacquie Samuals, published by TechWhirl, explains why technical writers should care about DITA. It also has some pointers to bring to management that would make any team look into DITA such as consistency and quality.
If you are a technical writer or a student in this field, I highly recommend that you read this article.
There are several different word processors out there, each has advantages and disadvantages. They each use different file tags and will access some of the universal tags differently. This is another area that Technical
Writers should be familiar with in order to survive.
A company will likely send a draft of what they want converted/translated/polished in a format using their preferred word processor. Yes, Word is popular, but there are still diehard Open Office, Wordperfect, and other word processor users out there and the extension (the three letters behind the dot that follows the file name) will be different for each.
Many word processors will convert files from other word processors to their format but the results may or may not be acceptable. PDF is another extension that is universal but typically information is lost and it is difficult to edit a PDF file.
There are two solutions to this dilemma. First, make sure that you have a working copy of every word processor used by any customer. This is the best solution but obviously this is impractical for most writers. The next best solution is to request that customers send files with a .rtf extension. Most word processors have a save as function and will allow users to send files with an RTF extension. The advantage is that RTF files can be opened by most other word processors. They can also be easily edited and saved into the same format without losing graphics and other information.