Jump to content
You must now use your email address to sign in [click for more info] ×

RobLonely

Members
  • Posts

    12
  • Joined

  • Last visited

  1. Whow!, Alex, you're a Pro! Thumbs up! 👍 Thank you so much for your effort with explaining and going into details of this rather complicated stuff. I appreciate this indeed. Rob
  2. Thank you very much for pointing to PDF format and for the link. So to avoid using variable fonts with APub or InDesign or whatever, it would be helpful to KNOW which fonts are variable and which ones are not. To be quite honest I haven't thought about this separation of fonts up to now. As Dov Isaacs writes it could take years until the PDF specification takes care of variable fonts. So there is no other way than avoiding these fonts, isn't there?
  3. Yes, Thomas, they completely handle it in a different way. So the only warning can be: hands off of variable fonts with APub as long as they don't support them. It seems this topic is not one of Serif's favourites.
  4. Yes. Skia .fontinfo files don't name the weight but have numbers of weight and width, instead. Which means that the file names are of no meaning except the font name itself. By the way: I found a rather clumsy workaround for my problems with Skia. Since I use it for headlines only I made a character style with a small outline of the same colour ...
  5. APub doesn't show the different weights? - Really odd. In my case I can change the weights, APub displays them correctly but the exported PDF only knows the regular font type.
  6. @thomaso: Sounds very interesting! If there would be a way to extract out of the .fontinfo file the bold-face style into a .ttf file ... Yes, I agree with you. It's a bit weird that APub can display every font weight but is incapable of exporting it properly. Let's hope version 1.9 will have a solution ...
  7. @Alfred: Well, that seems to be the only possible explanation. Thank you for looking into this. Do you have any idea if Serif folks are fixing this bug (or adding the new feature "properly dealing with variable fonts", respectively)?
  8. @Old Bruce: location might be different depending on upgrade paths of MacOS? Just tested: The exported PDF always shows Skia font with plain regular style, independent of which style I really had used in Publisher (italic, bold, bold italic etc). But with other fonts like Helvetica New everything is all right after exporting the document. Grrrrrr..... Don't know if there is any way to extract a font style out of its .ttf file? This would be helpful. Unfortunately, I cannot use a different font type than Skia because this would destroy my layout completely.
  9. Thank you, Alfred. The internal app of MacOS named "Font Book" reports that all 10 font styles of Skia are located in the same single .ttf file which is located in the system area of MacOS: /System/Library/Fonts/Supplemental/Skia.ttf So there must be another reason for Publisher's bad behaviour with font styles of Skia.
  10. Yes, of course I can. Please find attached both Publisher file and PDF. ExportsWrongTypeface_X4.pdf ExportsWrongTypeface.afpub
  11. ==> (MacOS 10.15.5, Publisher 1.8.3, error is reproducible) Hi, for headlines, I use a bold-face font style. Publisher displays it correctly. But after exporting it to PDF it is no more bold-faced but regular style instead! So headlines look differently from what was done within Publisher. See attached screenshot (in case I can upload this file). It does not depend on the PDF type I export into (PDF 1.7 or PDF X.4). The font's name is Skia. Apparently, Publisher here only exports the font face but not its style. So the PDF just contains the regular instead of the bold font type. Of course, all fonts were embedded. Any help will be appreciated. Rob
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.