![]() ![]() Once I refresh the TOC, the numbers are no longer bold in the TOC, but they’re still bold in the body of the document. To do that, I’ll select the numbers within each TC field and either use CTRL-B to toggle off the boldfacing or use the Bold command on the Home tab. Within each of the TC fields, I’ll need to remove the bold formatting from each entry’s numbers. This is something I’ll need to fix within the TC fields themselves. Carol wanted the entire heading to appear in regular text rather than having boldfaced numbers.This is something I’ll need to fix in the TOC2 Style. Carol wanted the headings to appear in small caps.To do that, click the button that looks like a paragraph character on the Home tab: Revise the Styles for the TOC entries to include boldfacing, all caps or small caps as appropriateīefore getting started, I need to turn on Word’s Show/Hide feature so I can see the non-printing characters, which will also include the TC fields.Deal with the content inconsistencies between the headings in the document and the TOC entries.Mark the first- and second-level entries with TC fields.To build this Table of Contents to Carol’s specifications, I’m going to: Granted, TC fields are a little harder to set up, but in situations like this where there are inconsistencies between the way the entries appear in the document versus the way they appear in the Table of Contents itself, these fields give you some needed flexibility. You can include TOC entries that aren’t based on headings.You can also customize at which level your TOC entry will appear, regardless of how it appears in the hierarchy of your document.You can customize the content of the TOC entry in other words, it doesn’t have to match exactly with the text of the document itself.While using Styles to populate a Table of Contents is the preferred method, TC fields offer some advantages: ![]() ![]() table entry fields for Table of Contents, are the legacy way of marking text to include in a Table of Contents left over from pre-Ribbon versions of Word. Other formatting inconsistencies such as the use of all caps and small caps don’t necessarily preclude using Styles to populate the table, but the other two inconsistencies I just mentioned already mandate that we use TC fields rather than Styles to create our Table of Contents. The number in the second level heading is bold in the text but needs to be not bold in the TOC.The Article number and the remainder of the heading (the first level heading) are separated by a soft paragraph break in the text but need to be separated by a tab in the TOC.If you know anything about generating an automatically-updating Table of Contents in Word, though, you immediately see a couple of possible barriers to using Styles to populate that Table of Contents: ![]() Why I can’t use Styles to build this TOC (and what I’m doing instead) Using Styles accomplishes multiple things at once: It gives you consistent, easy-to-update formatting in your document, it enables you to use the Navigation Pane to get a bird’s eye view of your document, navigate it by heading, and even reorganize your document with drag-and-drop. Normally, I tell people that if, at all possible, you should use Heading Styles in your document to populate an automated Table of Contents. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |