jcdmbf Posted August 22, 2019 Share Posted August 22, 2019 I am using Publisher v1.7.2 on macOS 10.12.6. I created a very simple Publisher document--just one text box with a few words in it. Part of the text is set to Alte Haas Grotesk Regular and the rest is set to Alte Haas Grotesk Bold. The Alte Haas Grotesk font is freely available from https://www.dafont.com/alte-haas-grotesk.font and I placed the two ttfs in a folder somewhere under ~/Library/Fonts. When I right-click on the font in FontBook and then click "Validate Font", it reports that "No problems were found validating these fonts." Now, everything looks fine in Publisher; the font looks right, and I can see the difference between Regular and Bold. However, when I export to PDF, everything is not fine. Instead of using the Bold font, it uses the Regular weight, so there is no Bold font at all in the PDF--all the text is in the Regular weight. I have attached the .afpub, the exported PDF, a screenshot of the PDF export settings, and a .zip containing the Alte Haas Grotesk fonts downloaded from dafont. I created a similar document in InDesign, and the exported PDF uses both the Regular and Bold fonts as expected. alte_haas_grotesk.zip Untitled.pdf Untitled.afpub Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted August 22, 2019 Staff Share Posted August 22, 2019 Thanks for reporting this, I can reproduce it with that font. Seems to be Mac specific. I've logged it Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
kenmcd Posted August 22, 2019 Share Posted August 22, 2019 When wrong fonts appear in a PDF it is usually because the PostScript Name field is not correct in the fonts. And that is the case here. I fixed the fonts, tested, and it appears to be working properly. Here are the fixed fonts: Alte Haas Grotesk - Fixed PostScript Names.7z Here is the Export to PDF with the fixed fonts: Untitled-fixed-fonts.pdf So just un-install the old fonts, install the fixed fonts, and you should be good to go. You will need to highlight the text and re-select the proper weights. NathanC and jcdmbf 2 Quote Link to comment Share on other sites More sharing options...
jcdmbf Posted August 22, 2019 Author Share Posted August 22, 2019 Thank you for working on this, and for sending me the fixed fonts! Would you be so kind as to elaborate a bit on what was the problem with the PostScript Name field in the Bold font? I had actually considered that possibility, but could not see anything wrong with the font. Here is what I had found in the TrueType Reference Manual on Apple Developer https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6name.html Quote PostScript name of the font. All PostScript names in a font must be identical. They may not be longer than 63 characters and the characters used are restricted to the set of printable ASCII characters (U+0021 through U+007E), less the ten characters '[', ']', '(', ')', '{', '}', '<', '>', '/', and '%'. The PostScript Name in the original font is AlteHaasGrotesk_Bold -- that's not longer than 63 characters, the characters are all printable ASCII, and none of them are from that set of ten that may not be used. So somehow I'm missing what is wrong with that font, but I'd like to learn. Thank you! Quote Link to comment Share on other sites More sharing options...
kenmcd Posted August 22, 2019 Share Posted August 22, 2019 I am used to seeing a particular format -- which coincides with this definition from the FontLab documentation ... The PostScript name (PSN) is a name used internally by a PostScript printer to identify the font within a printing job. Its length cannot exceed 29 characters, and it must only consist of uppercase or lowercase English letters or digits. In addition, one hyphen is used to separate the family name portion from the style name. The family name and style name segments are derived from the TFN and the TSN, but spaces are eliminated. I know that does not jive with the OpenType spec, but it is what I always see, and it always works. My guess is that this is to be compatible with all the older print service bureau equipment. If you look at the fonts in your original PDF they are both listed the same (as the regular). So that tells me the PDF rendering engine is confused by the original names. Original names: AlteHaasGrotesk AlteHaasGrotesk_Bold New "fixed" names: AlteHaasGrotesk-Regular AlteHaasGrotesk-Bold This is what I consider the FontLab recommended "best practices" - and it always works properly. When FontLab, or FontCreator, or TransType automatically build the PostScript Name field from the other font info this is the format used. In virtually all high quality commercial fonts - this is the format used. The important thing is ... its working now! fde101, PaulEC, jcdmbf and 1 other 2 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.