Monday, May 15, 2017

Two Separate Font Areas To Deal With


Many of us use 3rd Party Software for our Multilevel Outlines.  Some of us, on the other hand, use the generic MS Word Multilevel Outline feature.  It works well, but people do forget to take care of both Font areas.  They are the Font areas controlling the Numbering and Textual Aspect of each Heading Level.  

It is common to forget to take care of the Font that controls the Numbering Aspect.  This results in the Numbering text having a different look from the remainder of the particular Heading.

Another scenario that occurs because the Numbering Font was not checked, is the Invisible Level Number problem.  Below, I take you through that scenario.

The Invisible Article 1

Scenario:  Level Heading 1 Centered

Article 1 (soft return)
Introduction  (Hard Return) (12 Pts. After)

When Heading 1 was set up using the Multi-Level Outline Dialog Box using the configuration "Article 1" as the Numbering Aspect, the following occurred:

1. After implementing Heading 1, it came in in the following manner:

An Empty Soft Return
Introduction  (Hard Return)

There was an empty soft return followed by the textual aspect of Heading 1.  The numbering aspect DID NOT come in.

2.  Thinking we have overlooked  something in the Multi-Level Dialog Box we went back in.  Article 1 was in place and we checked that Level 1 was in fact "Linked" to Heading 1.

3.  Going back to the Heading 1 text in the actual document we stripped it back to Normal style (Control Shift N). We reapplied Heading 1 and again, it came in with an empty soft return and the textual aspect of Heading 1.

4.  Going back to the Multi-Level Dialog Box we went into the Font Button and the CULPRIT was staring at us.  Under Font Color, it read "No Color".  We switched it to "Automatic" and Article 1 was now visible.  Problem solved.

5.   Remember to deal with both the Numbering Aspect Font and the Textual Aspect Font of each individual level Heading you implement.

Top-Tier Style Training
www.advanceto.com


No comments:

Post a Comment