Word includes a wide range of fields you can use to perform special functions within your documents. One such field is the Symbol field. This field allows you to insert virtually any character you can think of in your documents.
In effect, the Symbol field duplicates the functionality provided by using the Symbol dialog box to insert a symbol in your document. The difference between the two is that when you use the Symbol dialog box, the actual symbol character is inserted in your document. When you use the Symbol field, the actual character is not inserted. Instead, the field is maintained in your document and simply replaced with the symbol character when the document is printed or the field is calculated. (This is a fine distinction, to be sure, but it does make a difference in how Word operates behind the scenes.)
The syntax for the Symbol field is as follows:
{ Symbol 123 }
Note that the field name is followed by a number. This number represents the ANSI value of the character you want inserted. You can use either the decimal value (as shown here) or the hexadecimal value, which is signified by prefacing the number with 0x, as in 0xA7. You can also use the actual character, within quotes, if desired.
There are other switches you can use with the Symbol field, as well. You can use the \f switch to specify the name of the font in which the symbol should be rendered. You can also use the \s switch to specify a point size for rendering the symbol. For instance, if you wanted to use a 17-point Webdings font, you could put the field together as follows:
{ SYMBOL 100 \f “webdings” \s 17 }
When you use a larger point size, it is possible for the symbol to mess up the line spacing (vertical spacing) of your paragraph. This can ruin an otherwise perfect layout. If you want to force Word to ignore any spacing dictated by the symbol size, you can add the \h switch to the field. The result is that as the symbol size increases, it starts to encroach on the line directly above, and could possibly overwrite it.
Comments
0 comments
Article is closed for comments.