Publisher 2013 - Print and PDF Quality issue for embedded Excel.

Anonymous
2012-12-04T16:33:41+00:00

When I print or export to a PDF, the embedded Excel documents in my Publisher 2013 document do not have crisp, clear text. However exactly the same document under Office 2010 they look and print fine. I have an example of a PDF created from the same Publisher document, one in 2010 (on the left), one in 2013 (on the right) which I have uploaded that clearly demonstrate the issue. Is this a known bug, or a font issue with Office 2013? I work at a University where we have an enterprise licence for Office 2013 so are only just considering to roll it out to staff currently, but if this is an issue we will have to wait for a fix.

[IMG]http://i48.tinypic.com/308drty.jpg[/IMG]

http://i48.tinypic.com/308drty.jpg

Microsoft 365 and Office | Install, redeem, activate | For home | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

71 answers

Sort by: Newest
  1. Anonymous
    2012-12-17T00:44:31+00:00

    May be that need to fix some registry key to enable display of high-quality Excel objects in Publisher?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-12-11T18:54:22+00:00

    Today there have been some updates for Office 2013, but unfortunately the issue of the excel links  in Publisher 2013 has not been resolved.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-12-09T15:00:49+00:00

    To avoid installing two versions of Office on the same system I installed Office 2010 on Windows virtual machine with Hyper-V for Windows 8.

    When I have to create a PDF I share a folder between Windows 8 and virtual Windows  via HomeGroup, I open Publisher files with Publisher 2010 in Hyper-V and I save in PDF.

    I hope that Microsoft will  release very soon a bugfix.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2012-12-08T20:01:15+00:00

    I understand.

    I decided to install Pub 2013 this afternoon and will continue to look for a solution. In the meantime please leave the images posted.

    Can you import Excel 2013 spreadsheets into Pub 2010 and workaround the problem that way? I know that you said that you don't want to run multiple versions of Office but perhaps you won't have the same problems if you just run multiple versions of Publisher. I know you cannot run multiple versions of Outlook and running multiple versions of Word and Excel can also create problems. I also know that if you want to do a email merge or send a Publisher html formatted email via Outlook that the versions have to be the same. However, I have Pub 2000 - 2010 installed on a couple XP machines, and Pub 2000, 2003 and 2013 installed on a Win 7 machine without any problems. I just install the oldest first and do custom installs of the newer versions and opt out of overwriting the newer versions. Anyway, it is something to consider if the final version of Publisher 2013 does not work the way you want it to.

    DavidF

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2012-12-08T16:23:33+00:00

    The main book I use Publisher for has over 100 pages of active Excel spreadsheets. These are in use by a number of people who regularly update them. The book is published monthly to keep everyone up to date with each others work. As such it simply isn't practical to use images of each sheet for me. I really would like to migrate to Office 2013 given how impressive the Excel changes are, but as it stands Publisher 2013 is next to useless in its current form for me. I also really want to avoid having more than one Office version installed given the problems this has caused in the past. I'll have a look for the suggested way to report bugs when I'm back in work on Monday. It would be useful to find a mechanism to report these bugs directly to the dev team.

    Was this answer helpful?

    0 comments No comments