D-E-F-I-N-I-T-E-L-Y
If ever there was a typo so vile and loathsome that it deserved its own domain, this is definitely it.
If ever there was a typo so vile and loathsome that it deserved its own domain, this is definitely it.
Apparently Adobe has gotten serious about changing their mind about giving up on the technical documentation market. After reviving RoboHelp in response to MadCap’s success with Flare, they’ve just now come out with a new version of FrameMaker, the first release since FrameMaker for the Abacus in 208 B.C.
Among the exciting new features in FrameMaker 8: Support for Flash. Which is great, because I’ve been looking for a way to get animated banner ads into user manuals for years.
Studies have shown that people can remember between five and nine items at a time depending on the information. By using a range of adding two or subtracting two, we get the number seven.
In general, people can only remember seven things at one time. When writing instructions and steps, we should keep the number seven in mind. Try to keep instructions to seven steps or less. If a set of instructions is long, try breaking it down into groups instead of one long list of steps.
It is also good to keep sentences 21 words or less. If a sentence looks complex, it probably is. Do not force the reader to read a sentence more than once to understand its meaning. Studies show that people retain information from sentences no more than 21 words. Can anyone guess what 21 is divisible by?
Here are links to more information about the studies and memory:
http://www.nwlink.com/~donclark/hrd/learning/memory.html
http://www.sheridanc.on.ca/~sherman/rap.dir/weeks1to4/Cutfog.html
With so many image formats to choose from, how do you know which one will work best for your documentation? Here’s a quick primer:
GIF
GIF images are usually very tiny - they are great for web graphics. Also, the GIF format supports transparency, something that also makes GIF images good for web applications (since it makes it easy to place irregularly-shaped images on top of patterned backgrounds). You can also create animated GIFs, which you can use for web applications as well as PowerPoint slides, but be careful - like the blink tag, animated GIFs can be very annoying when they are misused or overused.
Here are a few links to some interesting things I’ve read recently that might be of interest to fellow technical writers:
DrawAnywhere is a cool web-based tool which lets you draw simple diagrams and charts using nothing but a web browser and an Internet connection. This is something that could really be convenient for any technical writers that need to create quick flowcharts or diagrams while working far away from any licensed copies of Visio.I have recently developed some software instructional videos for one of our clients using Camtasia Studio. When developing these videos, I noticed a glitch in the program and I thought I would share what I found and how I managed to work around the error.
Issue - Sync problems in published video
After editing the video and adding callouts, zooms and voice-over audio (recorded separately), I noticed that my rendered video files did not sync with the audio. Callouts would occur after the video had already moved past the point they were supposed to start. The entire video ended before all audio and callouts had occurred. I did not notice any of these issues in the editor, only after I published the video files.
Discovery / Work Around
After much searching, it turned out that the frame rate of the rendered files was 15. Apparently my audio files and some other video components were running at a 30 second frame rate. I have since started explicitly specifying a 30 second frame rate in the output of all my published video files in Camtasia. This seems to solve all of my sync issues.
My research indicated that Camtasia Studio has fixed some bugs related to sync problems in recent releases of the Camtasia Studio software. The version I was using is Version 3.1.0.
I hope this helps anyone finding themselves in the same predicament.
With the best intentions, I’ve wanted to write about the field of technical writing. Having been in the industry for well over 20 years, I thought I might have a tip or two to share with the rest of the community of writers. Alas, my intentions, while good, weren’t sufficient to get me to sit down after a day’s work and write something more! So I felt that a blog, at least the informality of it, would allow me and the people I work with to publish ideas and tips that might be useful to others. That’s our hope.
Welcome to the Shoap Technical Services blog. Our team will be commenting on business, technology, and, of course, technical writing from our own unique perspective as consultants in the high-tech world.
A couple of interesting links from my bookmarks in the past few weeks: