Post Script fonts and Ejecta

Bugs will be moved here once resolved.

Post » Mon Aug 04, 2014 11:54 am

Problem Description
Construct has an issue with Post Script naming convention, required by Ejecta

Attach a Capx
Not Applicable

Description of Capx
Not Applicable

Steps to Reproduce Bug
  • Create a text object with font Arial
  • Export for Ejecta
  • Test on xcode

Observed Result
CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.

Expected Result
No warning in console.

This is a minor annoyance and so far I'm just doing a search and replace BUT, in case of other fonts (I'm using "Space Age" for example) construct exports as "Space Age" while Ejecta expects "SpaceAge", in this case it's not anymore a performance issue but the font won't simply render. Again it's just a matter of doing a search and replace, but I feel like Construct should export the fonts with the correct naming convention.
Posts: 525
Reputation: 8,329

Post » Tue Aug 05, 2014 4:10 pm

Could you post this to the Ejecta developers? I think the first warning is ignorable and the second issue with recognising fonts is solved if Ejecta is more tolerant of the font names it accepts. This is the same code we export to all platforms after all.
Scirra Founder
Posts: 24,915
Reputation: 198,678

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest