Skip to main content

[RESOLVED] Fonts have stopped exporting to pdf


I’ve been using frames on a large miro board to render presentation slides as a PDF document. Until a week or so ago Miro’s fonts were passing thru and showing up in the pdf. But now they are not and it is really frustrating.

The rendered files look the same in acrobat and Mac preview and older exports still look fine so I don’t think it is on the reader side. 

Any ideas what could be going on?

 

previous “correct” export”

 

from a current export...

 

Pinned reply

August 21, 2020

Hi there, @Doug Bobenhouse @RiverSong42 @Mark Glenn 

The Support team said that there indeed was an issue and it is resolved now. Will you please confirm that the fonts are being exported as expected now?

Was it helpful?
This topic has been closed for comments

5 replies

Kiron Bondale
Forum|alt.badge.img+7
  • Volunteer Community Moderator
  • 3040 replies
  • July 31, 2020

@Doug Bobenhouse -

I’m assuming you have tried both exporting just a frame with the special typeface and the whole board and got the same result? 

This sounds like a call for Miro support: Submit a request – Miro Support & Help Center

Kiron


Same Issue here!


Forum|alt.badge.img
  • Beginner
  • 4 replies
  • August 10, 2020

Having the same problem here. When exporting frames to PDF all fonts are replaced with strange defaults. Both Roboto Condensed and Caveat are turning into Arial Narrow in the PDF. Exporting to a JPG instead of a PDF avoids the problem, so it seems to be a PDF only issue.

Also tried installing the font files locally to see if that helped. It didn’t.

Native Miro:

 

After export to PDF:

Not ideal.


Marina
Mironeer
Forum|alt.badge.img+5
  • Mironeer
  • 991 replies
  • August 21, 2020
Pinned reply

Hi there, @Doug Bobenhouse @RiverSong42 @Mark Glenn 

The Support team said that there indeed was an issue and it is resolved now. Will you please confirm that the fonts are being exported as expected now?


Forum|alt.badge.img
  • Beginner
  • 4 replies
  • August 23, 2020

Hey @Marina, I can confirm the issue is resolved for me.

Sorted last week.

Hooray!