E
Eric F
Pictures that have been assigned paragraph spacing "Before" do not appear
properly at top of pages when following other text paragraphs on previous
pages. The pictures are shifted down by the difference between the "Before
spacing" of the pictures and the "After" spacing of the preceding paragraph.
The document treats the spacing of the remaining document as if the pictures
are properly positioned, so any text following the pictures then cut into the
bottom of the pictures themselves. This occures on-screen and in printing
and in both my 32 and 64 bit Windows XP installations.
Replicate the error in a new document by creating a block of text that fills
most of the first page. Hit return and add an "in-line" picture that then
automatically spills on to the next page. Hit return and add a block of text
after the picture. Finally, go to the paragraph settings of the picture and
assign a "Before" spacing of something large like 100.
Has anybody else seen this? Exhaustive online searches turned up one other
individual having a similar problem, however a responding Microsoft employee
dismissed it as being something wrong with the individual's file. Thanks....
properly at top of pages when following other text paragraphs on previous
pages. The pictures are shifted down by the difference between the "Before
spacing" of the pictures and the "After" spacing of the preceding paragraph.
The document treats the spacing of the remaining document as if the pictures
are properly positioned, so any text following the pictures then cut into the
bottom of the pictures themselves. This occures on-screen and in printing
and in both my 32 and 64 bit Windows XP installations.
Replicate the error in a new document by creating a block of text that fills
most of the first page. Hit return and add an "in-line" picture that then
automatically spills on to the next page. Hit return and add a block of text
after the picture. Finally, go to the paragraph settings of the picture and
assign a "Before" spacing of something large like 100.
Has anybody else seen this? Exhaustive online searches turned up one other
individual having a similar problem, however a responding Microsoft employee
dismissed it as being something wrong with the individual's file. Thanks....