Jump to content

Recommended Posts

This is from APublisher 1.7.0.238 Beta.

Test1-cropped.png.c4d5ad120c5d2b28bf6db83c5666ce49.png

But it is not working properly.
It is not listed properly on my system because the font name is in Chinese and I don't have Chinese installed.
The glyphs do not display properly in the Glyphs Browser.
The export to PDF fails - probably because the PostScript Name is not proper format.

These old fonts were probably not done correctly even to the old TrueType standards.
They are such a mess that I do not see them working properly in any modern app.
How is PDF export ever going to work without a proper PostScript Name?

I only installed the one font so while there are errors there is not the multi-font name duplicates confusion that I am sure you have.
The APub font cache would need to be re-set by un-installing the fonts and restarting.
Your operating system font cache probably has issues and should be re-set.

As I said above, these fonts need to be updated to modern standards.
They may work if just the name fields are fixed.

 

Share this post


Link to post
Share on other sites
On 2/13/2019 at 9:24 AM, mac_heibu said:

My god, William, I know this. But as you said „could be“ not „is“.

Do you have a besser proposal to narrow down the issue?

I swear by the life my grandma, that I will eat up the font after having a look at @Lensman’s issue . (Hope, I am able to do this before Monotype detects this particular thread.) :)

Trust me, Monotype will not care; not one tiny bit. They want people to be able to use their fonts.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×