LiveCode Forums.

Posted: **Tue Apr 26, 2022 7:59 am**

My Devawriter Pro has an inbuilt font detection routine:

 if "Devawriter" is among the lines of the fontNames then
      add 1 to PHONTS
   end if
   if PHONTS > 0 then
      --do nix
   else
      GO TO CARD "FONT WARNING" of stack "DWPro"
   end if

Yesterday I modified the Devawriter.ttf font and swapped it out with the earlier version on MacOS 12.4,
and it was NOT detected:
-

-
The funny thing is that the stack works perfectly well displaying text inwith its fields using
the Devawriter.ttf font, BUT standalones BREAK because of
non-detection.

Posted: **Tue Apr 26, 2022 8:21 am**

Blast!

The font editing program had changed the INTERNAL name of the Devawriter.ttf font to Devawriter Regular.

So . . . 'Happy People' . . .

What is particularly nasty about this is that there is a mismatch between the font's surface name
and its internal name, which, without opening the font up in a font-editor and poking around
might not be known.
-

-
My sense of humour is not all that elastic-sided in the morning before my second cup of coffee.

Posted: **Tue Apr 26, 2022 11:24 am**

What is even funnier about this is that Fontforge reports my font as Devawriter-Regular,
but LiveCode 'sees' the font as Devawriter Regular (without a hyphen).

https://fontforge.org/en-US/

LiveCode Forums.

Font Detection

Font Detection

Re: Font Detection

Re: Font Detection