Topics in this section describe page layout style.
Do not manually break pages in print documents until all art (or art spaces) and textual changes have been added to the manuscript. Page breaks are usually inserted just before the manuscript goes to final production.
The main goal is to keep related material on one page. If this isn’t possible, try to break pages in such a way that it is clear to the user that relevant material continues on the next page. Recto (right) page breaks must be handled more carefully than those on a verso (left) page of a spread. Avoid leaving a recto page so short that it looks like the end of a chapter.
Leave at least two lines of a paragraph at the bottom or top of a page. Do not break a word over a page.
Try to keep notes, tips, important notes, cautions, and warnings with the material to which they refer.
Keep material that introduces a procedure or bulleted list with the list. Keep at least two steps or list entries at the bottom or top of a page. A step’s explanatory paragraph should accompany the step. Try to keep all steps in a procedure on one verso-recto page spread; avoid continuing a procedure from a recto to a verso page.
Try to keep a table from breaking across pages, especially from a recto to a verso page. If breaking is unavoidable, leave the title (if applicable) and at least two rows of the table at the top or bottom of a page. At the top of the next page, repeat the table title, followed by (continued) enclosed in parentheses and in lowercase letters and italic formatting. Repeat the column headings also. If an item is footnoted, the footnote goes at the end of the table. Try to keep a table’s introductory sentence with the table.
Try to keep art on the same page as the material that it illustrates. Always keep an introductory phrase with its art.
Try to have at least five or six lines on the last page of a chapter.
In printed indexes, if the main entry is followed by subentries, do not leave the main entry alone at the bottom of the column.
In printed indexes, if you must break up a list of subentries, at the top of the next column include the main entry followed by (continued) enclosed in parentheses and in lowercase letters and italic formatting.
Note
This topic pertains primarily to printed content. Because users of online content can control the screen resolution, the font size, and the size of the browser window, you cannot control the appearance of screen text by explicitly inserting line breaks. You can prevent undesired line breaks on the screen by inserting nonbreaking spaces, but the effect on the surrounding text is impossible to predict.
Although the right text edge in printed Microsoft documents is not aligned, try to avoid very short lines that leave large amounts of white space at the end of a line. An extremely ragged right edge can distract the reader. If necessary, a copy editor and desktop publisher can break lines manually during the final stages of production.
Follow these basic rules for line breaks in Microsoft printed content:
Do not break a word if it leaves a single letter at the end of the line.
Do not break a word if it leaves fewer than three letters at the beginning of the next line.
Microsoft style
Be sure there are enough le-
tters at the end of a line. Do
not leave fewer than three
letters at the begin-
ning of a line.
Be sure there are e-
nough letters at the end
er than three letters at
the beginning of the next
line.
Avoid leaving fewer than four characters on the last line of a paragraph, especially if a heading follows.
Do not hyphenate Microsoft unless there is no alternative. If you must, the only acceptable hyphenation is Micro-soft.
Do not hyphenate Microsoft product names. Avoid breaking product names at the end of a line, especially on first mention.
Avoid breaking URLs. If you must break them, do so at the end of a section of the address immediately before the next forward slash. Do not include a hyphen.
Microsoft style
For more information, see http://www.microsoft.com/support/products/developer/visualc/content/faq/
Not Microsoft style
For more information, see http://www.microsoft.com/support/products/developer/visualc/content/faq/
For more information, see http://www.microsoft.com/support/products/developer/visualc/content/faq/
Try to keep headings on one line. If a two-line heading is unavoidable, break the lines so that the first line is longer. Do not break headings by hyphenating words, and avoid breaking a heading between the parts of a hyphenated word. It does not matter whether the line breaks before or after a conjunction, but avoid breaking between two words that are part of a verb phrase.
Microsoft style
Bookmarks, cross-references, and captions
Not Microsoft style
Try not to break formulas, data that should be entered without spaces, or program examples. If a break is unavoidable, break between elements.
Microsoft style
In the cell, type =Budget!
$A$H:$C#+1
Not Microsoft style
In the cell, type =Budget!$A
$H:$C$#+1
Try to avoid breaking function names and parameters. If hyphenating is necessary, break these names between the words that make up the function or parameter, not within a word itself.
Microsoft style
WinBroadcastMsg
Not Microsoft style
WinBroadcastMsg
Do not hyphenate a line of command syntax or code. If you must break a line, break it at a character space, and do not use a hyphen. Indent the run-over when breaking a line of syntax or code. Do not use the line-continuation character unless it is necessary for the code to compile.
Microsoft style
void CScribView::OnLButtonDown( UINT nFlags, Cpoint point)
Not Microsoft style
void CScribView::OnLButtonDown( UINT nFlags, C point point)
For general rules about hyphenation and word division, see Hyphens, hyphenation (Chapter 9); American Heritage Dictionary; and The Chicago Manual of Style.
In printed content, marginal notes, often labeled “Tips,” usually accompany procedures to give hints, shortcuts, or background information that the user should know before proceeding. These notes should be easy to read and should help minimize long text or additional steps within the procedure. You can also use marginal notes next to tables and art.
In Help, the equivalent of these notes can be a jump to another step, a pop-up window offering additional information such as a definition, or a tip at the end of a topic.
Begin a marginal note at the first step of the procedure and end it before or at the last step. If possible, place it next to the step to which it refers.
You can include a heading to show the subject of the marginal note, as shown in the first example.
Microsoft style
About file names
Some restrictions apply to file names.
See Saving and Naming Files.
Tip If the
Formatting toolbar does not appear,
click Toolbars on the View menu, and then click Formatting.
The following are some basic guidelines for marginal notes:
Do not clutter a page with too many marginal notes. Even three notes per page should be a rare occurrence.
Try to limit marginal notes to three or four lines. They expand when localized.
Break lines so that they are about the same length.
Follow the design for a specific project to determine whether or not to apply character formatting in marginal notes.