Tips for Publishing Professionals Using Microsoft Word (www.editorium.com)October 3, 2001 – 12:00 pm
Microsoft Word guru Steve Hudson has been sending me some interesting things. Today I’d like to introduce you to his “Editioning” macro, which allows you to use true conditional text in Microsoft Word 97 and above. Conditional text is the thing to use if you need to change a document in different ways for different audiences. I’ve written before about using Word’s Hidden formatting to create conditional text:
http://www.topica.com/lists/editorium/read/message.html?mid=1703011632
Steve, however, has taken the idea to greater heights of power and usability. For your convenience, I’ve placed his template (with its accompanying toolbar and macro) on our Web site, and you can download it here:
http://www.editorium.com/ftp/editioning.zip
After you’ve downloaded it, you’ll need to unzip it. If you don’t already have software to do this, you can get the popular WinZip program here:
http://www.winzip.com/ddchomea.htm
Macintosh users can use StuffIt Expander, available here:
http://www.stuffit.com/expander/download.html
Once the template is unzipped, you’ll need to load it as a global template or add-in, which you can learn more about here:
http://www.topica.com/lists/editorium/read/message.html?mid=1707012536
And here:
http://www.topica.com/lists/editorium/read/message.html?mid=1707100224
Finally, here’s how to use the program:
1. Open or create a document that will be your source document for the various versions you want to create, and be sure to keep a backup of this document.
2. Use Microsoft Word’s Highlighter feature (available on the Formatting toolbar) to highlight the text that will appear only in the various versions you’ll be producing. For example, let’s say you’re writing the documentation for a computer program that will be produced in three versions: basic, intermediate, and advanced. Some of the documentation will apply to all three versions, but some of it won’t. For example, the advanced version will have features not available in the basic version, and you don’t want the documentation for those features to show up in the basic documentation. So let’s say that you highlight the information that applies only to the basic version in yellow, the intermediate in blue, and the advanced in red. Save this document with a new name, such as “Single Source.”
3. With the Editioning template loaded, you’ll see a new Editioning toolbar on your screen. Click the Editioning button to start the program.
4. In the “Color” box, on the right, click one of the colors you want to use, such as yellow.
5. In the “Description” box, on the bottom, type in a description of what that color represents, such as “Basic.”
6. Click the “New” button to add the color and its description to the “Current List of Editions” box. (You can also click the “Delete” button to delete them.)
7. Repeat steps 4 through 6 for each color you want to use.
8. In the “Current List of Editions” box, click the color/description for the type of document you want to produce. For example, if you wanted to create the basic documentation, you’d click “Yellow Basic.”
9. Click the “Publish” button.
10. Click the “Exit” button to close the program. (It will remember your definitions for the next time you use it.)
Now, in the document on your screen, all of your *unhighlighted* text will be preserved (since you want to use it in all of your versions), and the text that was highlighted in the color you selected (yellow) will also be preserved (but now unhighlighted). Text that was highlighted in other colors (blue and red) will be removed. So, you now have the basic version of your software documentation! Be sure to save it with a new name (such as “Basic Documentation”), and be careful not to save it over the top of your previously marked-up file.
That’s it! Rinse and repeat for your other versions. Many thanks to Steve for making this program available.
Search This Blog
Thursday, October 3, 2019
Editioning Software
Can you believe this article was initially published 18 years ago?!?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment