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

JanG

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by JanG

  1. I would have loved to be able to replace this strange Font (0) - but unfortunately, this does not work either. Unfortunately, the file is under copyright protection - so I cannot make it public here.  But I will try to reduce the file to the critical passage - which I could not identify either. (It is a ridiculous issue, indeed: looking to get rid of something that is not there, should not be there, and cannot be deleted - but seems to corrupt your file ... 😞 ).

  2. I have already posted the issue in the general forum on 'Publisher on Mac', although without being able to resolve the issue.

    I am now reporting this as a bug. So here it is a link: Report about a strange 'Font (0)' that appeared out of nothing and cannot be deleted (or in any other way be resolved).

    Please help, as this is my first major project with Publisher - and I do not know whether the persistent error message will affect printing.

    Thanks!

  3. Hello everyone!

    As this is my first post here, I think I should introduce myself. My name is Jan, I am from Germany, and I am right at the beginning of working with Affinity Publisher (so, please, be gentle if I should be asking too stupidly - this is all new to me - thanks).

    I am working on my first book to be made ready for print in Affinity Publisher. Everything seems to be going well, except for one issue. When checking the afpub-file before exporting to pdf with 'preflight checking' I get a strange error message (the only serious one I am getting). You can see it in the first attached photo and it translates to English as "Missing Font (0)". If I click on 'Fix' a window opens that presents a list of fonts and their replacement fonts (see image #2). The strange font (0) is reported as missing, but I have enabled its replacement by 'Garamond'. Closing the window and re-running the preflight check changes - nothing. The condition of the file remains red. And the error message is unchanged.

    My question is, whether this is a serious error message and whether it will affect the printing?

    On my Mac there is no 'Font (0)'. Also I have no idea how this font was created. The text of the book was set to Garamond even in the 'placed' docx-file. Although this docx-file itself was generated in Libre Office by export.

    So, what to do about it?

    Also, as I am just starting my business, I am still lacking any reports or feedback from the printing house. Yet, I would much prefer not to begin our relationship with a file that reports an unresolvable(?) error.

    Thanks for your time and thoughts.

    Bildschirmfoto 2020-11-02 um 12.50.52.jpg

    Bildschirmfoto 2020-11-02 um 12.51.07.jpg

  4. Hi, everyone!

     

    My name is Jan Groh. I am from Berlin, Germany. I am a hobby photographer - and photography is the main reason why I use Affinity Photo. Thanks for this outstanding program, Affinity team. Great job. If I may ask for something which I would probably love even more than AP it would be a "successor"/alternative to Apple's Aperture. A RAW developer with great DAM and - if possible - deep integration into the system so that digital assets would be available from within many if not all other programs on my Mac. And - having a tendency towards prosopagnosia - I would very much appreciate if a face recognition was included in this program.

     

    Looking forward to further programs by Affinity.

     

    Best,

     

    Jan

×
×
  • 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.