Font swap issue

[Chrisw5]

I've been having a useful discussion on the bug reporting section about APubs ability to match fonts when importing pdfs, but it seems that it isn't a bug - just a limitation. I'm therefore raising this issue here, as it also probably isn't a bug, but it's very strange.

The font manager screen says I’m missing Tahoma,Bold and Vedana,Bold, both of which it replaces with Courier New in Bold, and I've established that the problem is the way the pdf creating software gives the fonts a name with a comma instead of a space. However, that can be usually be overcome, but in this case when I try and change the Courier New to Tahoma in Bold and Verdana in Bold – or indeed, any other font – it accepts the change for 2 seconds and then it jumps back to Courier New. Nothing I do will persuade it to use a different replacement font.

Has anyone got any suggestions on how to solve this ?

[walt.farrell]

Are you Placing the PDF or Opening it?

If you Open it, you might have the opportunity to specify the font names initially, rather than Publisher simply choosing replacements for you.

[Chrisw5]

Walt, thanks for the response. Sorry, I should have been more specific. You're absolutely right, we've worked out that opening a pdf and editing the fonts is a good way to go, but In this case, I'm opening a placed pdf, to edit it.

[walt.farrell]

4 minutes ago, Chrisw5 said:

Walt, thanks for the response. Sorry, I should have been more specific. You're absolutely right, we've worked out that opening a pdf and editing the fonts is a good way to go, but In this case, I'm opening a placed pdf, to edit it.

Still, it might help to try Opening it first, before Placing it. Another user suggested that once you Open a PDF and make your own font-substitution choices, that Publisher will remember them and use them later when Placing PDFs (or Opening other PDFs).

[Gradient_Phil]

On 6/7/2019 at 6:33 AM, Chrisw5 said:

I've been having a useful discussion on the bug reporting section about APubs ability to match fonts when importing pdfs, but it seems that it isn't a bug - just a limitation. I'm therefore raising this issue here, as it also probably isn't a bug, but it's very strange.

The font manager screen says I’m missing Tahoma,Bold and Vedana,Bold, both of which it replaces with Courier New in Bold, and I've established that the problem is the way the pdf creating software gives the fonts a name with a comma instead of a space. However, that can be usually be overcome, but in this case when I try and change the Courier New to Tahoma in Bold and Verdana in Bold – or indeed, any other font – it accepts the change for 2 seconds and then it jumps back to Courier New. Nothing I do will persuade it to use a different replacement font.

 

Has anyone got any suggestions on how to solve this ?

I'm having exactly the same issue. APub will not let me change to another font (changes for two seconds then reverts). Also, it will not change even when I have the correct font it says I am missing (this is because the PDF perhaps gives the font a different name than how it is designated on my system??) Also...APub doesn't always register when the font library is update - I have to restart the program.

Further - sometimes APub lists the same missing font twice - like it has been given two different names within the PDF or something.

The above is with a PDF document that is opened (not placed) in APub.