New News / Old News

• New News
•  64060 File(s) 533,402,861,838 bytes is my count.
• Old New: 
  Recently on Techwr-L, there was a question about whether you use tables in your documentation. I responded with this:

---

What is your delivery format? PDF? HTML? Something else?

Speaking about Word docs, I worked for a company that had numbered procedures within a three column table. The first column was an empty square (the thought being that the user could print the procedure and check the box when they were done), the second column was a numbered step, and the third the actual content.

I remember this time in my career with fondness because as I began the massive task of converting that Word content to HTML (during the WinHelp to HTML conversion), I was also learning HTML and about this amazing technique for controlling format called "Cascading Style Sheets." With the three column format, I learned that you couldn't do a continuous OL within a table without adding start="N"
so, essentially, it was manually numbering. I also learned that code like this:
[ol start="2"] 1. Complete the ....
2. Complete the ....
Should be rewritten to: [ol]
[li]Complete the[/li]
[li]Complete the [/li]

And if I did that, adding a step prior to step 1 in a long procedure would not require manual renumbering. All of this was also at the time when the tables in the Word docs were being used to control formatting. The big buzz about *not* using tables to control formatting was deafening at the time.

Around this time, I talked to Dave Gash @ WinWriters in 2004 in Boston about using tables in documentation and the takeaway from that discussion was that if your content is tabular, then yes, use a table. If it's not, don't use one.

All that to say I do not have procedures in tables in any content I work with on a regular basis.

---

Off-list, I was reminded that my example is irrelevant to how content is presented. If a table is the best way to present the data, then use a data; if it's not the best way to present the data, then don't use a table. The tool & the format is not nearly as important as the content.