Font not showing up in all applications

Get help with FontCreator here. Please do not post feature requests or bug reports here.
Post Reply
Mystii
Posts: 2
Joined: Tue May 20, 2003 10:28 pm

Font not showing up in all applications

Post by Mystii » Tue May 20, 2003 10:33 pm

:oops: Maybe I just don't get it...but I'm having problems with a font. I've read through many of the messages here and don't see this problem discussed.

The font I have difficulty with is one that is available from multiple free sites. It works in Excel, but not in Word. It works in PhotoImpact but not in PaintShop Pro. I have XP and have never had this problem with a font before and it's driving me nuts.

Any suggestions, please, before I lose the rest of my hair??

- Mystii

Richard Hatch
Posts: 6
Joined: Mon May 05, 2003 8:32 am

Re: Font not showing up in all applications

Post by Richard Hatch » Wed May 21, 2003 7:31 am

What is the name of the font? The only font I've downloaded from the free sites that didn't want to show up was Droid. After discovering FCP, I went back and downloaded it again, but I couldn't figure out what was wrong with it.

Bhikkhu Pesala
Top Typographer
Top Typographer
Posts: 8028
Joined: Tue Oct 29, 2002 5:28 am
Location: Seven Kings, London UK
Contact:

Platform Mappings

Post by Bhikkhu Pesala » Wed May 21, 2003 1:17 pm

This kind of problem is often caused by the font not having the correct platform mappings. You could also download and run the Font Folder utility from the download area: fifofo.zip
My FontsReviews: MainTypeFont CreatorHelpFC11.5 Pro + MT8.0 @ Win10 1809 build 17763.437

Mystii
Posts: 2
Joined: Tue May 20, 2003 10:28 pm

Post by Mystii » Wed May 21, 2003 3:11 pm

The problem font is fairydust. I'll give the font utility a try and see what it does.

Thanks.

Erwin Denissen
Moderator
Moderator
Posts: 7953
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Post by Erwin Denissen » Thu May 22, 2003 8:35 am

To fix your font install problem, you should try to use the AutoNaming feature. This ensures correct naming values.
Erwin Denissen
High-Logic
Proven Font Technology

hegedusgy
Posts: 3
Joined: Wed Feb 04, 2004 9:58 am

Post by hegedusgy » Wed Feb 04, 2004 10:11 am

Hi,
I found the same error, again with XP as operating system. I have modified an existing font (added some glyphs to it), installed it without any error.
right now the font seems to be correct (eg. when doube clicking onto it in the fonts folder), the new glyphs can be typed in and seen properly in excel and in most of the other applications (eg. ulead video studio) and fifofo does not report any error either.
However neither ms word nor wordpad does not show my new font (it is the font list, but substituted with some default font.)
microsoft knowledge base said it might be some printer driver issue as ms word and wordpad performs some printer check, while ms excel does not, but my printer driver seems to be ok (hp laserjet).
would be grateful for some explanation.
regards :shock: :shock: :shock:

Bhikkhu Pesala
Top Typographer
Top Typographer
Posts: 8028
Joined: Tue Oct 29, 2002 5:28 am
Location: Seven Kings, London UK
Contact:

Unicode Ranges

Post by Bhikkhu Pesala » Wed Feb 04, 2004 10:26 am

Have you checked the Unicode ranges for the characters you added to the font?

Format, Settings, Ranges, Unicode Character Ranges, Edit and check the character set you have added characters in: e.g. Latin Extended Additional.
My FontsReviews: MainTypeFont CreatorHelpFC11.5 Pro + MT8.0 @ Win10 1809 build 17763.437

hegedusgy
Posts: 3
Joined: Wed Feb 04, 2004 9:58 am

Post by hegedusgy » Wed Feb 04, 2004 10:50 am

yes. originally i started to work with a simple basic font (ie numbers and english letters). originally there were no range settings at all as far as i remember. this original font worked properly in all applications including word.
I added to it some special hungarian letters, mapped them appropriately to my keyboard and set up the correct ranges as well as you mentioned (to extended latin A), I even set up the country details.
everything seems ok, it seems to me that ALL of my applications except word and wordpad works fine with these extended fonts. if i press my special keyboard buttons, my new letters appears, but not in word, where it is substituted. i tried auto renaming the fonts, with no change.
regards, :roll:

fantong
Posts: 20
Joined: Tue Jan 13, 2004 8:12 am

Post by fantong » Wed Feb 04, 2004 12:10 pm

I've downloaded the FairyDust.ttf and checked it. Mystii's font problem results from a missing field in the naming field. FairyDust.ttf doesn't have anything in "Unique font Identifier" field. After correcting this, FairyDust seems to have no problem at all.

But I think "hegedusgy''s problem has something different from Mystii's. What font is it, hegedusgy?

hegedusgy
Posts: 3
Joined: Wed Feb 04, 2004 9:58 am

Post by hegedusgy » Wed Feb 04, 2004 11:23 pm

thanks the hint. i solved it.

the reason (i guess): word expects given postcript names, while excel does not care about them.

i gave my special hungarian fonts some fancy names, so word refused to accept my whole font set. for example: my original postscript name for eg the letter 'a' with acute ('á') was originally something like 'mya'. after i renamed it to 'aacute' (as they were named in a working font set), and after i did it for all of my new characters, it worked finally even in word.
thanks :D

fantong
Posts: 20
Joined: Tue Jan 13, 2004 8:12 am

Post by fantong » Thu Feb 05, 2004 3:56 am

Yes, as hegedusgy mentioned above, "Postscript name" in the naming field must observe the following standard.

"This field should be restricted to the printable ASCII subset, codes 33 through 126, except for the 10 characters: '[', ']', '(', ')', '{', '}', '<', '>', '/', '%'. So it should not contain any spaces. This field should be no longer than 63 characters"

This is described in the help file. :D

Erwin Denissen
Moderator
Moderator
Posts: 7953
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Post by Erwin Denissen » Wed Feb 11, 2004 5:48 am

Although fantong is right about the postscript naming field, I think hegedusgy is talking about the postscript names related to the glyphs.

Adobe recommends a maximum string length of 31 for each glyph related postscript name. Just like the postscript naming field, the post script name should be restricted to the printable ASCII subset, codes 33 through 126, except for the 10 characters: '[', ']', '(', ')', '{', '}', '<', '>', '/', '%'. So it should not contain any spaces.

For more information about glyph related postscript name conventions:
Unicode and Glyph Names
Adobe Glyph List
Erwin Denissen
High-Logic
Proven Font Technology

Post Reply