Microsoft KB Archive/246964

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 12:50, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


WD2000: Non-Breaking Space Appears to Cause Incorrect Word Wrap

Article ID: 246964

Article Last Modified on 12/6/2000



APPLIES TO

  • Microsoft Word 2000 Standard Edition



This article was previously published under Q246964

SYMPTOMS

When you use a field result followed by a non-breaking space, if the text word wraps, the text before the non-breaking space may not word wrap to the next line.

For example, this problem occurs if you have a LISTNUM field followed by a non-breaking space:

We want this action to occur in the following months: 1) November,
and 2) December.
                    

If additional text is added to the paragraph, the numbered list text may word wrap incorrectly to the next line, as in the following:

We also want this action to occur in the following months: 1)
 November, and 2) December.
                    

NOTE: In the above example, the following was used:

{LISTNUM}oNovember


where o represents a non-breaking space.

CAUSE

This problem occurs when you use a field to display a result. As in the example in the "Symptoms" section of this article, the LISTNUM field displays a result of a numbered item. The non-breaking space does not "see" the result of the LISTNUM field as text. Thus, when the numbered item word wraps to the next line, the non-breaking space is not associated with any preceding text to wrap to the next line.

WORKAROUND

To work around this problem, convert the numbered list to text. To do this, select the text that contains the LISTNUM field(s) and then press CTRL+SHIFT+F9. After you do this, the numbered list is not a field any longer, and the result of the LISTNUM field(s) is text. The non-breaking space now works correctly when the numbered list word wraps to the next line.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbnofix KB246964