Wiley SD2003 Template Cheat Sheet Installing and Attaching the Template To install the SD template and related files: 1. Unzip all files to a convenient folder on your system. 2. Open the file Install.doc and enable macros when prompted. 3. Follow instructions to install. Alternatively, open the zip file and drag the WileySD.dot and TechTool.dot files to your template folder. In Windows XP or Vista, the path to this folder is usually C:\Documents and Settings\username\Application Data\Microsoft\Templates. Adding the Tech Toolbar We have created a special toolbar to provide quick access to most of the tools and styles you will need. To use the toolbar: 1. Open a document and make sure the WileySD template is attached. 2. Select ToolsTemplates and Add-ins. Check the box next to TechTools.dot and click OK. (If TechTools does not appear in the Add-ins box, click Add, navigate to the folder where you have stored that file, and click to add it to the list.) 3. The TechTools bar will appear in the bottom left corner of your document. Click the Toolbar button to open the main style menu, and use the dropdowns to access most of the styles you will need. Creating a new document In Word 2002/XP or 2003: 1. Choose FileNew. 2. Select „Templates on My Computer‟, then choose WileySD from the General tab. Click OK. In Word 2000 or earlier: 1. Choose FileNew. 2. Select WileySD from the General tab. Click OK. Checking Page Count 1. The page count as determined by Microsoft Word is NOT an accurate estimate. To get an accurate estimate: Click the appropriate series button from the Tech Toolbar (Wrox, Bible, or Wiley Red), and then click Page Count Estimate Only. The macro will run through the document and provide a page count estimate (this estimate does not include any figures, even if they have been inserted). You can run this macro on your document at any time, but be sure to check the final page count. Attaching the template to an existing file 1. Choose ToolsTemplates and Add-Ins. 2. Click Attach and select WileySD. 3. Check the Automatically Update Styles checkbox and click OK. Chapter Opening Items Place chapter number and title on one line, separated by colon (Chapter 9: Web Browsing). Style as ChapterTitle. For books in the Bible series only, add list of Intro bullets headed by “In this chapter” and styled as ChapterFeaturingList before the chapter title. Basic Text Styles Use the following styles for regular text (styles for Features and Code are indicated in the relevant sections). For normal body text, use the Para style. For bullet lists, use the ListBulleted style. This style will automatically insert a bullet before the paragraph. For bullets that contain more than one paragraph, use the ListPara style for the second and successive paragraphs to avoid placing a bullet in front. For numbered lists, use the ListNumbered style. For each item in the list, type the number, followed by a period and a tab, then begin the text. For bullets that contain more than one paragraph, use the ListPara style for the second and successive paragraphs to avoid placing a bullet in front. For subbullets, use the ListBulletedSub style or ListNumberedSub style (for numbered sublists). To start a feature, click the Feature button on the Tech Toolbar and select the series for your book, then select the type of feature you want to create. An XML line will be inserted in your document to denote the beginning of the feature, and the Tech Features menu will open, offering the various Features styles. Use only styles from this menu and its submenus for text, lists, or code within the feature. Use the FeaturePara style for body text within a feature. For code lines within features, use the FeatureCodeSnippet, FeatureCodeScreen, etc. styles, unless the code line is inside a list (see following). For lists within a feature, use the FeatureListBullet, FeatureListNumber, etc. styles. For code lines within a FeatureList, use the FeatureCodeSnippetSub style (this indents the code line to align with the bullets). Figures You must supply each figure as a separate file. Please refer to the Working with Figures document in the online author kit for details on creating and naming figure files. Include a text reference to each figure in the text preceding the figure (“Figure 6-1 illustrates…” Use the Slug style (from the Basics menu) to insert a line for the figure number and caption (note: captions should not be used in Wrox books). You do not need to insert the figures into the document. If you prefer to do so, use the Insert menu to place the figure on a separate line preceding the Slug line. Features Use the Features styles for sidebars, notes and tips, cautions, exercises, Try It Outs (Wrox Beginning series only), etc. Code Do NOT use tabs or hanging indents in code; they will not work as intended in our automated systems. Instead, use the correct number of spaces to indent as needed. Checking code line lengths and breaking wrapped code lines All wrapped code lines must be broken with hard returns (using the Enter or Return key). To check whether any of your code wraps, click the appropriate series button from the Tech Toolbar (Wrox, Bible, or Wiley Red), and then click Check Code Length Only. The macro will go through the document and highlight any wrapped code lines in pink. After that, click the Find Long Code button to locate the first instance of wrapped code. Break the wrap by manually adding a hard return. Click the button again to find the next wrapped line. When you think you have no more wraps, run the macro once more to check. Code styles Use CodeSnippet as the default style for code blocks. (The DE or PE will apply Code80 if needed.) For code within features, use the FeatureCodeSnippet, FeatureCodeScreen, etc. styles. Use CodeScreen for lines that should be emphasized within a code block. For full code listings with headings, use the CodeListing style (and CodeTitle for the heading). Code within other text (InlineCode and variants) Do NOT apply your own Courier or other fonts within the document to create monofont text. Such styles will not work as intended in our automated systems. Instead, use the following styles for inline code terms: To have monofont (code font) used for a term within a line of regular text, a bullet, or other style, highlight the relevant text and apply InlineCode style (from the Inline menu in the Tech Toolbar). For placeholder variables, use the InlineCodeVariable style (this will appear as monofont plus italics). For code terms that the user is to type into an interface, use the UserInput style (this will appear as monofont plus bold). Special Symbols If a symbol appears on your keyboard, you may use it as a regular character. For other symbols, click More Styles and then click Symbols/Math. If the symbol is not on that menu, leave a note for your editor describing the symbol you want. Tables WileySD manuscripts should only contain simple-grid tables: one para per cell, styled TableHead (for column headings) or TableEntry (for table text), no merged or split cells. More complex tables must be submitted as separate files, outside of the manuscript. Do not use hard returns within a table. You may use soft returns (Shift + Enter). If you are pasting in a table from another document, such as Excel, copy the table, and use EditPastePaste Special to insert text without extraneous formatting. Important Items to Note Do not add blank lines in the document to create extra space around figures, tables, code blocks, etc. The extra space will be added automatically during our layout process. WileySD does not reflect your final book layout. Do not modify styles in the WileySD template. Do not override the font styles in the template, or change the font sizes. If you are not sure how to style an element, or think you need a style that is not included in the template, leave a note (styled as QueryPara, from the Basics menu) or discuss it with your editor. To get a report on your document that tells you the estimated page length, whether there are any wrapped code lines, and whether you have used any invalid styles, click the appropriate series button from the Tech Toolbar (Wrox, Bible, or Wiley Red), and then click Generate Chapter Report. The macro will run through the document and provide the information in a separate document. For more information on the template, as well as other reference materials for Wiley authors, please refer to the online Professional Author Resources at http://www.wiley.com/WileyCDA/Section/id301866.html. Creating a New Table 1. From the Tables toolbar click Make New Table. 2. Select the number of columns and rows, and type a title, etc. Click OK. 3. Begin typing data. You can add more rows by clicking the tab key from the last table cell. Converting Text to a Table 1. Type one tab between the text for each individual cell. 2. Highlight all text to be converted. 3. From the Tables toolbar click Convert Text to Table.