Font Mystery

UrbanR · 05-06-2014, 10:43 AM

Hi,
I am creating an ebook that contains two unicode opentype fonts, both purchased from the same font foundry. I have the otf font files and have successfully embedded them into the epub file. However there is a strange problem: one of the fonts embeds successfully (even in the in-application reader in Sigil it works, in ebooks and Adobe Digital Editions it also works) but the other one just doesn't work at all. I have tried various different changes to the css file, the content.opf file and the font filenames.

So I guess I want to know: are there any features or properties of a font that would prevent it being embedded? Is there anything else I can check to get some more information on what's happening?

thanks,
Robin

DiapDealer · 05-06-2014, 10:59 AM

There are some font property settings that could keep certain fonts from working with Adobe Digital Editions (v2 at least). There are also some Qt quirks that could keep fonts from rendering properly in Sigil. But if they just don't work anywhere, I have to lean toward a css mistake being the culprit. Hard to tell without a "hands-on" inspection, though.

UrbanR · 05-06-2014, 11:40 AM

Hi DiapDealer

one thing I don't quite understand is the relation between (1) the font filename (2) the id it is assigned in the content.opf file (3) the "font-family" property in the CSS. That is, whether some or all of these need to be the same, or if (2) and (3) are just arbitrary names.
Having said that, I have tried almost every combination I could think of...
Because these are commercial fonts I don't want to post the file but I will try to send it to you in a private message if you're prepared to take a look

thanks
R.

mrmikel · 05-06-2014, 11:57 AM

Having purchased the fonts for your own use may not be the same as contracting with the foundry for use in an ebook. You might check exactly what rights you bought. Typically ebook authors don't buy the right to use in ebooks because the cost could be prohibitive.

DiapDealer · 05-06-2014, 12:03 PM

Will take a look when I get home to a PC. For now though:

1) the opf manifest id can be safely ignored for this exercise.
2) the @font-face declaration in the css effectively maps a font-family name (of your choosing) to the physical font file.
3) that font-family name (from the @font-face) is then used as the font-family property value for whatever element/class you want the font used for.

Jellby · 05-06-2014, 12:18 PM

Quote:

Originally Posted by UrbanR

one thing I don't quite understand is the relation between (1) the font filename (2) the id it is assigned in the content.opf file (3) the "font-family" property in the CSS.

(1) can be anything, you can change it and it shouldn't matter, as long as you change all references.
(2) can be anything, you can change it and it shouldn't matter, as long as you change all references (and most likely there are none).
(3) can be anything, you can change it and it shouldn't matter, as long as you change all references.

So the relation is "none at all". The only caveat is that some readers want (3) to match the internal name of the font, and calibre will warn you if it doesn't. The internal name of the font is probably not the filename, and it's not obvious how to find it, because there may be a few of them. Other readers (and most web browsers) are not so picky and then the above holds.

grumbles · 06-10-2014, 12:53 PM

Quote:

Originally Posted by Jellby

(1) can be anything, you can change it and it shouldn't matter, as long as you change all references.
(2) can be anything, you can change it and it shouldn't matter, as long as you change all references (and most likely there are none).
(3) can be anything, you can change it and it shouldn't matter, as long as you change all references.

So the relation is "none at all". The only caveat is that some readers want (3) to match the internal name of the font, and calibre will warn you if it doesn't. The internal name of the font is probably not the filename, and it's not obvious how to find it, because there may be a few of them. Other readers (and most web browsers) are not so picky and then the above holds.

The Windows utility "Typograf" will display all the font information. In particular the full font name as well as the font family. If I remember correctly, the unregistered version of the program will do this. If you work with many fonts and you are using Windows, you really do need this program!

grumbles · 06-10-2014, 12:59 PM

You can also open the font with FontForge. The name information is available under Element=>Font Info. If the font is protected, FontForge will complain and ask you if you are authorized to play with the font. Say yes but remember that you can look but your not supposed to touch!

Toxaris · 06-10-2014, 03:18 PM

While you are running FontForge, also check the OS/2 version of the font. That must be 3 or lower...

Hitch · 06-11-2014, 02:22 PM

Quote:

Originally Posted by grumbles

The Windows utility "Typograf" will display all the font information. In particular the full font name as well as the font family. If I remember correctly, the unregistered version of the program will do this. If you work with many fonts and you are using Windows, you really do need this program!

+1 for Typograf. I have the paid edition, but it's an excellent program, FWIW.

Hitch

05-06-2014, 10:43 AM	#1
UrbanR Junior Member Posts: 8 Karma: 10 Join Date: Jan 2012 Device: kindle	Font Mystery Hi, I am creating an ebook that contains two unicode opentype fonts, both purchased from the same font foundry. I have the otf font files and have successfully embedded them into the epub file. However there is a strange problem: one of the fonts embeds successfully (even in the in-application reader in Sigil it works, in ebooks and Adobe Digital Editions it also works) but the other one just doesn't work at all. I have tried various different changes to the css file, the content.opf file and the font filenames. So I guess I want to know: are there any features or properties of a font that would prevent it being embedded? Is there anything else I can check to get some more information on what's happening? thanks, Robin

05-06-2014, 11:40 AM	#3
UrbanR Junior Member Posts: 8 Karma: 10 Join Date: Jan 2012 Device: kindle	Hi DiapDealer one thing I don't quite understand is the relation between (1) the font filename (2) the id it is assigned in the content.opf file (3) the "font-family" property in the CSS. That is, whether some or all of these need to be the same, or if (2) and (3) are just arbitrary names. Having said that, I have tried almost every combination I could think of... Because these are commercial fonts I don't want to post the file but I will try to send it to you in a private message if you're prepared to take a look thanks R. Last edited by UrbanR; 05-06-2014 at 11:42 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Free - Scam (Stanley Hastings Mystery, #12) Parnell Hall (Mystery) [Amazon] (US)	NightBird	Deals and Resources (No Self-Promotion or Affiliate Links)	4	06-29-2012 04:05 AM
Determine font and font size on incoming epub?	peaceridge	Calibre	4	01-30-2012 03:35 PM
Seeking advice on good mystery mystery series.	Billsuits1	Reading Recommendations	26	11-30-2011 01:26 PM
ttc font file can't be put into font folder	droople	Sigil	2	08-21-2010 10:05 AM
feed to lrf, how do I change font (or have default font)	lovemov	Calibre	3	03-16-2009 10:57 PM

05-06-2014, 10:59 AM	#2
DiapDealer Grand Sorcerer Posts: 28,570 Karma: 204127028 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	There are some font property settings that could keep certain fonts from working with Adobe Digital Editions (v2 at least). There are also some Qt quirks that could keep fonts from rendering properly in Sigil. But if they just don't work anywhere, I have to lean toward a css mistake being the culprit. Hard to tell without a "hands-on" inspection, though.

05-06-2014, 11:57 AM	#4
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	Having purchased the fonts for your own use may not be the same as contracting with the foundry for use in an ebook. You might check exactly what rights you bought. Typically ebook authors don't buy the right to use in ebooks because the cost could be prohibitive.

05-06-2014, 12:03 PM	#5
DiapDealer Grand Sorcerer Posts: 28,570 Karma: 204127028 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Will take a look when I get home to a PC. For now though: 1) the opf manifest id can be safely ignored for this exercise. 2) the @font-face declaration in the css effectively maps a font-family name (of your choosing) to the physical font file. 3) that font-family name (from the @font-face) is then used as the font-family property value for whatever element/class you want the font used for.

06-10-2014, 12:59 PM	#8
grumbles Addict Posts: 238 Karma: 1500000 Join Date: Nov 2009 Location: Toronto Device: Pandigital Novel (Black), T-2 and 3, Nexus 7	You can also open the font with FontForge. The name information is available under Element=>Font Info. If the font is protected, FontForge will complain and ask you if you are authorized to play with the font. Say yes but remember that you can look but your not supposed to touch!

06-10-2014, 03:18 PM	#9
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	While you are running FontForge, also check the OS/2 version of the font. That must be 3 or lower...

Advert

Advert