The “font validator” on the upload does “not pass” on the “Will Install on MAC OS X and macOS” test.
However, it does fine with the Windows platform test.
When I test run the pre-loaded fonts on the FontCreator, it does just fine.
What is it that could be causing this error?
Thanks!
Can you explain what this is all about?
Is it a website where you can submit fonts or an online font validator?
Or is it the font install feature within FontBook on a Mac?
I’ve been trying to upload my submission on to MyFonts.com their admin. sent me to the “Prosper by Monotype” submission site. When Uploaded, their program test the fonts that goes through a automated validation process.
I had run the “font = validate…” button on the FontCreator that had return no errors.
When I run upload on the “Prosper by Monotype” site their validate check process states that the “Will install on Mac OS C and macOS” did not pass.
I’m trying to figure if it’s a needed fix on the FontCreator platform, or perhaps the “Monotype” platform that needs a fix.
I figured I check with FontCreator first before reaching out to Monotype about the problem.
Thanks for your insight…
It seems they have a new tool to pre-analyze fonts when you submit them.
Can you send the font file to me (contact on the right side), so I can look into any issues on our side?
Hello,
I had tried testing the submission process with a pre-loaded font from windows.
The Propser by Monotype “font validator” returned the same MacOS error response,
as stated in the previous posting upon this topic.
I tried another process…
I had ran the FontCreator “validate” without errors.
I had then exported the .ttf file on to FF; and ran the FF validator…
Although it had some warnings, It return a response without errors.
I then had likewise exported that same .ttf file with FF
I then uploaded the .tff file to submit on to the Propser by Monotype,
and NOW their font validator was able to return without errors!
I hope this information helps.
We’ve always been able to successfully install fonts on a Mac, so I’m not sure why that warning occurs. Maybe they test for legacy naming fields, but maybe it is a bug in FontCreator.
Can you send me both font files, so I can look into the differences?
So far we haven’t received any fonts from you to test, while our contact from monotype / myfonts confirms the Propser tool is under development and contains several unforeseen problems and they would like to investigate this issue from their side.
It would be really helpful if you could provide a font for this purpose.
I have the same problem: the .otf file of a new font I tried to submit to the new Myfonts Prosper font upload tool gives an error, stating that the font can’t be installed on Mac OSX. (See image attached.)
It would be great if I could send you the file so you can take a look at it if that’s possible.
The prosper tool seems to have some issues; I expect Monotype will solve them within the next couple of weeks. Most likely the font will install just fine, but it is best to try and install the font yourself.
You can send the font through our ticket system.
Thanks for your reply Erwin.
The font installs just fine on a Windows PC. Unfortunately I do not own a system that runs Mac OS X.
So I understand your advice is to wait on Myfonts to solve this issue? Considering the amount of time it takes for them to reply to a regular e-mail, that may be a while.
I am not familiar with your ticket system. Please advise.
All the best,
Joe
Joe, see submit a ticket.
I wonder if this issue belongs to FontCreator and if it was fixed. For I met the same problem too.
Should I send my font file to your ticket system so you guys can look into it?
I can’t tell if this is the same issue, as the provided information doesn’t reveal the exact problem.
So it seems the new myfonts font uploader known as Prosper still has issues. Even though Monotype told us they plan to fix the issue, they haven’t provided a release date. I guess it won’t harm if you contact them, as the more people complain, the more pressure for them to actually fix it…
Okay, I know what should do. Thank you very much for your advice and have a great day! 
Prosper still seem to have these issues, but FontCreator has an option that might do the trick.
By default FontCreator will only store naming fields in the Windows platform, which is used cross-platform nowadays. If your font must also include legacy naming fields for the Macintosh platform, then uncheck this option.
Let us know if that works!
We’ve just received a message from myfonts to let us know this problem has been fixed by them last week. It seemed there were at least 30 support cases with fonts not working due to this issue, which they tested after the release, and all now work.
Let us know if it works for you as well.
The problem didn’t resolve yet in Version 12。
Since they fixed that issue last year, your problem is most likely another issue. Besides it was not a FontCreator problem.
If you have some problem with our software or with uploading it to myfonts.com, then please clearly explain what fails.