Non-embedded font with different name across operating systems when printing HTML to PDF

Posted by sennett on Super User See other posts from Super User or by sennett
Published on 2013-11-05T11:05:45Z Indexed on 2013/11/05 21:58 UTC
Read the original article Hit count: 269

Filed under:
|
|
|
|

I create a document using HTML markup. I want to use Palatino, which is called Palatino on Windows and Palatino Linotype on Mac, so I specify my CSS accordingly: font-family: Palatino Linotype, Palatino, serif;. I then print to a PDF using PrimoPDF under Windows. It all looks good when viewed in Windows.

But I want this PDF to look the same on a Mac, and the resulting file size (94KB) would suggest that the font (size 460KB) is not getting embedded by Primo, perhaps because it is a native font. How will this look? Will the PDF file format resolve this, or will the format of my PDF be wang when viewed under OSX?

Please note that I do not want to embed the font. I used a web-safe font to avoid this need, and it just so happens that the one I picked does not have the same name in OSX as in Windows.

© Super User or respective owner

Related posts about pdf

Related posts about fonts