Office 2007 SP2: PNG, Textboxes and Postscript Printing

[Alex]

We use a fair number of older Word documents that contain PNG images and text
boxes i.e. hierarchical charts. The document appears fine in print preview,
but when it is printed to a Postscript printer, text in the text boxes is cut
off almost like the image or its margins overlap.

For example, if there is a PNG image on the left and a text box on the right
and they do NOT visually overlap in any way, then the 50%+ of the text in the
text box will be cut off from the left.

The kicker?? The same documents print fine when printed to the same printer
from even the same computer WHEN OFFICE 2007 SP2 IS UNINSTALLED.

Any ideas? Given the number of documents, replacing the images is not
feasible. It is unlikely the users will be willing to re-create these
charts with SmartArt as well. There is a good chance that the users will
eventually have to have SP2 or later if not a newer version of Office, so I
hope to find a solution
to the problem.

Many thanks and if there are any questions, feel free to ask! Thanks.

Alex

 

[Robert M. Franz [RMF]]

Hello Alex

We use a fair number of older Word documents that contain PNG images and text
boxes i.e. hierarchical charts. The document appears fine in print preview,
but when it is printed to a Postscript printer, text in the text boxes is cut
off almost like the image or its margins overlap.

For example, if there is a PNG image on the left and a text box on the right
and they do NOT visually overlap in any way, then the 50%+ of the text in the
text box will be cut off from the left.

The kicker?? The same documents print fine when printed to the same printer
from even the same computer WHEN OFFICE 2007 SP2 IS UNINSTALLED.

[..]

tough one!

I would investigate this directly with MSFT CSS. Maybe they can find out
what the underlying problem is (Chart/Escher enhancements in SP2, I'd
wager).

As a workaround: I'd try to get hold of a PCL driver for your printer
and see whether the problem is still there.

0.2¢
Robert

 

[Alex]

Robert-

Thanks for the reply. I was supposed to be alerted to response, but I never
received an alert. Thus I am late in thanking you. How does one investigate
a bug with Microsoft Customer Support? I looked at connect.microsoft.com,
but didn't really find any help there. The other option is to get on the
phone with MS to the tune of $35 USD to report an apparent bug.

Thanks again for your help and I apologize in advance for the delay!

Take care,
Alex

Hello Alex

We use a fair number of older Word documents that contain PNG images and text
boxes i.e. hierarchical charts. The document appears fine in print preview,
but when it is printed to a Postscript printer, text in the text boxes is cut
off almost like the image or its margins overlap.

For example, if there is a PNG image on the left and a text box on the right
and they do NOT visually overlap in any way, then the 50%+ of the text in the
text box will be cut off from the left.

The kicker?? The same documents print fine when printed to the same printer
from even the same computer WHEN OFFICE 2007 SP2 IS UNINSTALLED.

[..]

tough one!

I would investigate this directly with MSFT CSS. Maybe they can find out
what the underlying problem is (Chart/Escher enhancements in SP2, I'd
wager).

As a workaround: I'd try to get hold of a PCL driver for your printer
and see whether the problem is still there.

0.2¢
Robert
--
/"\ ASCII Ribbon Campaign | MSFT |
\ / | MVP | Scientific Reports
X Against HTML | for | with Word?
/ \ in e-mail & news | Word | http://www.masteringword.eu/
.

 

[Robert M. Franz [RMF]]

Hello Alex

Thanks for the reply. I was supposed to be alerted to response, but I never
received an alert. Thus I am late in thanking you. How does one investigate
a bug with Microsoft Customer Support? I looked at connect.microsoft.com,
but didn't really find any help there. The other option is to get on the
phone with MS to the tune of $35 USD to report an apparent bug.

yeah, I'm not sure there's much on connect for this type of problem. I'd
probably start somewhere around http://support.microsoft.com/kb/295539/
and work my way through (unless somebody in this group has a better
suggestion).

I've never had to do this myself, but if your problem gets resolved, the
35 bucks seem a good investment (or even if you get another workaround
or at least know there's none).

Thanks again for your help and I apologize in advance for the delay!

You're welcome -- I wasn't very timely in answering myself!

Greetinx
Robert