View Single Post
Old 06-21-2018, 12:49 PM   #2925
hfpop
Addict
hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.hfpop knows how many angels can dance on the head of a pin.
 
Posts: 250
Karma: 136662
Join Date: Apr 2011
Device: N/A
Thank you all for your help. I have one more question in the actual file names scheme. The base name of the files have to match the internal font name. In the case given in the cited wiki, I have the following, in FontForge:

Element / Font Info / PS Names:
Fontname: AmazonEmber-Regular
Family Name: Amazon Ember
Name For Humans: Amazon Ember
Base Filename: Same as Fontname

Element / Font Info / TTF Names:
Family: Amazon Ember
Styles: Regular
Fullname: Amazon Ember

The file is saved as AmazonEmber-Regular.ttf, but the windows font viewer sees the font name as Amazon Ember. Question: I should rename the file to read Amazon Ember-Regular.ttf, even if it is saved as AmazonEmber-regular.ttf, right ?

Thank you.

Last edited by hfpop; 06-21-2018 at 12:57 PM.
hfpop is offline   Reply With Quote