Wierd page breaks

CB

Okay:

MSWord has always been good to me, but recently, I don't know, maybe she's just under a lot of stress lately, but she hasen't been quite as, well... loving as she used to be.

Here's the thing:

Recently she started breaking my pages at strange places. At first I thought some strange 'never split a paragraph between pages' option had been turned on, but then I noticed that even if that were true, these breaks are still wrong (see example taken from my 'print preview' screen).

Look, please don't anybody report this, I know she still loves me and she doesn't mean to hurt me.. it's just that, well... I don't know... What should I do?

BlackHawk

Repair installation?

ryko

insert manual page breaks and see if the 'strange' page breaks keep on happening

shwaip

do they show up when you actually print the paper?

Straight_Man

If you do get the same thing when printing, turn on the code reveal options, and then look for any of the following:

Section headers that always begin on a new page, for multi-section docs. word can force a page for sections.

Soft page or multiple line feeds, you give it too many at end of paragraph as far as line feeds, it will think it has them as part of a paragraph.

Soft page is like when you hit CTRL-Enter, and make a manual page break in WordPerfect, your Word code will vary, but probably will show as a soft page.

Inserting manual line feeds, or a doc template with bunch of blank line feeds in it can do this, unless you delete them before starting your doc. they hang as pragraphs.

Only other thing I can think of is an oddball page size in printer that Word is not using, like using legal paper in printer and letter size (or 4A instead of 5A in european paper sizes). In this case, I think two or more things are playing into this doc, or you have a corrupt template file or macros that are acting strange.

Something like <paragraph>many line feeds<end paragraph> can give you a nice big paragraph of WHITE space, too.

Get Word to look at in code revealing mode, or run the doc into Open Office and fix, reimport into Word and see if issues vanish (this last is an experiment, but OOo 1.1 is good for this, it shows literal text for oddball things it cannot grok, and also will exaggerate some errors so they are visible). OOo 1.1 can parse Word 2000 and back quite well, 2002 fairly well, and for this paper, probably Word 2003 files as well as most of the XML is used by both other than MS extensions. When you get done in OOo or WordPerfect, which can also parse MS Office stuff, export as Word doc type but with a different name. WP is also a nice tool to fix broken docs, it imports and converts the codes to visiblity with its own notation.

John D.