This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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]
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
Today there have been some updates for Office 2013, but unfortunately the issue of the excel links in Publisher 2013 has not been resolved.
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.
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.
I already tried to change the quality for print in PDF, the problem also occurs in XPS files.
Also if I use Adobe Acrobat or Bullzip the results are the same, bad quality in Publisher 2013, high quality in Publisher 2010.
If I open a file in Publisher 2010 I see excel linked objects in high quality, if I open a file in Publisher 2013 I see excel linked objects in low quality.
There is a display problem of low quality for the excel linked objects in Publisher 2013.
I don't have a good answer for you. Perhaps if you save the Excel object as a higher resolution image and insert it into Publisher rather than linking you will at least get the quality you seek. Yes, I realize that updating will be more tedious.
Is there any possibility that you can affect the object quality directly from Excel? In other words is Excel 2013 output lower quality than Excel 2010 and older? Is there a setting that changes that?
I don't know if this will be fixed or changed before the final version of Publisher is released to the public. From what I understand there is still a built-in method of submitting 'bugs' from each program that you might try. Look under Help??? With Office 2013 at the RTM stage I suspect you won't see significant changes to Publisher in the near future.
Sorry I am not of more help but for a variety of reasons I have opted to not install Pub 2013 yet and thus my knowledge about this version is minimal.
DavidF
Any news for a hotfix from Microsoft?
