Field codes: TC (Table of Contents Entry) field

The TC (Table of Contents Entry) field defines the text and page numbers for entries in a table of contents and in lists of tables, figures, and similar contents. Insert a TC field immediately before the text you want to include in the contents. To collect the TC field entries into a contents list, use the Table of Contents command in the Table of Contents group on the References tab. Insert a TOC (Table of Contents) field where you want the contents in the document.

The TC field is formatted as hidden text and displays no result in the document. To view this field, click Show/Hide Paragraph mark Button image in the Paragraph group on the Home tab

Security   Because content that is formatted as hidden text can easily be made visible, do not use hidden text formatting to keep sensitive information private.

Syntax

When you view the TC field in your document, the syntax looks like this:

{ TC "Text" [Switches ] }

Note    A field code tells the field what to show. Field results are what’s shown in the document after having evaluated the field code. To toggle between viewing the field code and the field code results, press Alt+F9.

Instructions

"Text"

Text to appear in the table of contents for an entry.

Switches

\f Type

The type of items collected in a particular contents list. Use a unique Type identifier (typically a letter from A-Z) for each type of list. For example, to build a list of illustrations, mark each illustration with a field such as { TC "Illustration 1" \f i }, where "i" indicates only illustration entries. If no type is specified, the entry is listed in a table of contents.

\l Level

The level of the TC entry. For example, the field { TC "Entering Data" \l 4 } marks a level-4 entry, and Microsoft Word applies the built-in style TOC 4 to that entry in the table of contents. If no level is specified, level 1 is assumed.

\n

Omits the page number for the entry.

Applies To: Word 2013, Word 2010



Was this information helpful?

Yes No

How can we improve it?

255 characters remaining

To protect your privacy, please do not include contact information in your feedback. Review our privacy policy.

Thank you for your feedback!

Support resources

Change language