nTables are difficult to read online, so don’t overuse them.In Help 3.1, you can create simple tables (tables without borders or shadows) using the Word for Windows table formatting features. Table design varies depending on content. The following sections discuss design principles and authoring strategies for working with tables.
Note:
Windows Help 3.0 does not support true tables. To create a table, you must use hanging indents or side-by-side paragraph formatting.
nTables are difficult to read online, so don’t overuse them.
nYou can use bold or plain text for your table heads.
Use bold for table heads when the table contains commands or options that the user must choose. The bold text directs the user’s eye to the options. Use 10-point bold (style Th).
Use 8-point bold (style Th3) when the topic already contains a 10-point bold heading.
Use a plain head with a rule for tables that contain lists of information (style Th2).
nYou do not need to use a rule beneath the table heading.
If you do use a rule, define either a broken or solid, single-line rule.
If you don’t use a rule, your heading must be bold and you must add 3 points of white space after the table heading.
nUse plain text for table text, and capitalize the first word in each column.
nDo not use a rule above the table heading.
nAlign tables left with text that appears directly above the table. Tables with numbered or procedural lists should also be left aligned. Table heads should be aligned with table columns.
nIn a table created using a hanging indent, avoid column headings that are much longer than the text within that column. If possible, the column heading should not be wider than the widest item in the column.
nThe gutters between table columns should be narrow, based on the way the table is being used.
Too small a gutter makes the text crowded and illegible; too large a gutter makes the table difficult to read horizontally. For example, a table designed to be read from left to right should have 1 to 2 picas of space between columns.
A table whose information is grouped to be read vertically may need more space.
A table used to position text and graphics precisely may need more space between columns.
nIf possible, avoid nested tables (a table within a table). If necessary, follow the same guidelines as regular tables.
nIf a topic has more than one table, format all the tables with the same column widths.
nDivide long tables into two or more smaller tables, whenever possible.
nTables provide a way to lay out text in more precise positions, for example, they are a good way to create a gutter between bitmaps and text.
nA table is designed to be read from left to right. The exception to this might be a table with graphics (such as icons or other bitmaps), where the user would scan a table vertically (read down or up). In this case, the graphics would still be placed in the left column.
nIf you are creating a two-column list, you can use either the table feature in Word for Windows or hanging indents. However, for lists with three columns or more, use the table feature.
nBe aware of “crowdedness” in table text versus table columns. Localized versions of Help tend to increase by 30 percent or more.
nRelative tables should not be used if the precise layout of your information within the table is critical. For example, if syntax statements should not wrap, do not use a relative table.