Custom font: select font type "thin"

Getting Started Newbie Questions
#21

Hi Kerem,

Thanks for reminding me. I tested this again just now, and there’s basically an error in the “Black” version of the font. Font Inspector for Windows reports an error in the header file. However, I was able to get both the “Thin” and “Regular” varieties working on both Windows and Mac… and oddly, the “Black” version actually works on Mac, but not Windows.

So the summary is, this is an issue with at least one of the font files. @lornz87, if you can get OpenType varieties of this font, it might be worth trying that.

Regards,

Brent

#22

Hi, I’m wondering if there was a conclusion, closure to this case. Thanks for sharing.

#23

Hi Kerem,

Thanks for reminding me. I tested this again just now, and there’s basically an error in the “Black” version of the font. Font Inspector for Windows reports an error in the header file. However, I was able to get both the “Thin” and “Regular” varieties working on both Windows and Mac… and oddly, the “Black” version actually works on Mac, but not Windows.

So the summary is, this is an issue with at least one of the font files. @lornz87, if you can get OpenType varieties of this font, it might be worth trying that.

Regards,

Brent

#24

Sorry to dig up this old thread. 

I like to point out that in Windows, fonts are grouped in “family”. This causes problems to custom fonts in Simulator.

Example: a font named Komica has regular, bold and italic. In window’s font folder its all placed inside another folder named Komica. 

Because windows group them under 1 folder, coronsdk only detects 1 name.

print( "fontname = " … tostring( fontname ) )

will return  fontname = “Komica”

So the only way to make this font shows correctly is to use font = “Komica”

if I use “Komica Bold”, coronasdk returns error unable to load font

if I delete all other fonts in the family except Bold, coronasdk returns no error, but the text will show up as blank.

This is a Windows only problem.

#25

Sorry to dig up this old thread. 

I like to point out that in Windows, fonts are grouped in “family”. This causes problems to custom fonts in Simulator.

Example: a font named Komica has regular, bold and italic. In window’s font folder its all placed inside another folder named Komica. 

Because windows group them under 1 folder, coronsdk only detects 1 name.

print( "fontname = " … tostring( fontname ) )

will return  fontname = “Komica”

So the only way to make this font shows correctly is to use font = “Komica”

if I use “Komica Bold”, coronasdk returns error unable to load font

if I delete all other fonts in the family except Bold, coronasdk returns no error, but the text will show up as blank.

This is a Windows only problem.