Microsoft KB Archive/285390

From BetaArchive Wiki
Knowledge Base


PUB2002: Rotated Objects Are Not Rotated in Web Page

Article ID: 285390

Article Last Modified on 11/5/2003



APPLIES TO

  • Microsoft Publisher 2002 Standard Edition



This article was previously published under Q285390


SYMPTOMS

When you rotate some objects and graphics in Microsoft Publisher 2002, they do not appear rotated when you publish your file as a Web page and view it in certain Web browsers. Also, depending on the browser that is installed on your computer, the object or graphic may not appear rotated when using the Web Page Preview command (on the File menu) in Publisher.

The following items will not rotate correctly on a Publisher Web page:

  • Tables created in Publisher.
  • Tables created in Microsoft Excel or Microsoft Graph.
  • Any Windows Metafile (*.wmf) image, such as clip art from Microsoft Clip Organizer.
  • AutoShapes containing textured fills.
  • AutoShapes containing preset fills.


CAUSE

Microsoft Internet Explorer 5.x does not properly interpret the tags Microsoft Publisher uses to identify some rotated objects and graphics in Publisher Web pages.

WORKAROUND

To work around this problem, capture the rotation in the object or graphic rather than having the browser handle the rotation. In Publisher, apply the rotation to the object or graphic, and then save that information with it. When you paste the object or graphic into your presentation, use one of the following formats:

Joint Photographic Experts Group (.jpg)
Portable Network Graphics (.png)
Windows Bitmap (.bmp)
Graphic Interchange Format (.gif)


To do this, follow these steps:

  1. Select the rotated object.
  2. On the Edit menu, click Cut.
  3. On the Edit menu, click Paste Special.
  4. In the Paste Special dialog box, select the format you want, and then click OK.


The rotated object or graphic will now display correctly in browsers that do not support Publisher tags that identify the rotation properties of the object or graphic.

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 KB285390