Problems with fonts

Alda · 01-31-2015, 01:45 PM

Hello,

I've validated my ePub with Flight Crew and get the following message:

Quote:

This resource is reachable but not present in the OPF <manifest>. "Reachable" means that a reference of some kind that points to this resource exists in the epub.

This is in reference to three fonts that are not embedded in the file but which are referred to in the ePub itself, which was exported from InDesign (I know I know, not a good idea, but I'm hoping to avoid having to redo the whole thing again).

The .mobi book works fine on a Kindle, but when trying to upload the ePub to Smashwords I get those error messages.

Is there any way to fix this issue, e.g. by simply removing the lines of code that make reference to those fonts. An example would be this:

Quote:

Grateful for any advice. Thanks!

theducks · 01-31-2015, 03:00 PM

Quote:

Originally Posted by Alda

Hello,

I've validated my ePub with Flight Crew and get the following message:

This is in reference to three fonts that are not embedded in the file but which are referred to in the ePub itself, which was exported from InDesign (I know I know, not a good idea, but I'm hoping to avoid having to redo the whole thing again).

The .mobi book works fine on a Kindle, but when trying to upload the ePub to Smashwords I get those error messages.

Is there any way to fix this issue, e.g. by simply removing the lines of code that make reference to those fonts. An example would be this:

Grateful for any advice. Thanks!

You have not embedded that font. (NOTE: this font may need to be licensed)

It is not listed in the (Fonts) file browser s being present

BTW you may also need an @fonts statement in the CSS or file <head> block
BTW2 Mobi does not support font embedding
BTW3 the code you show has no Text, so why did you set a font face?

Toxaris · 01-31-2015, 03:01 PM

Big question is, if you want to embed the fonts. If you do, the actions will be different than if you don't. Also, I think InDesign can create an ePUB with a stylesheet instead of inline styles like the example you give. That will make work a lot, and I mean a lot, easier.

Presuming you do not want to embed fonts (as this would not work on mobi files anyway afak), you can just search for font-family: 'Futura Light'; and replace that by nothing. That would work in the example you give.

Alda · 01-31-2015, 04:57 PM

Thank you for the advice Toxaris. That's just what I was wondering about.

I have no particular investment in that font for the ePub. The file was exported from InDesign because a print book was designed in InDesign, and that book uses those fonts. I'm not fussed about it either way.

So if I just delete that particular piece of code, then the ePub would use a default font - is that correct?

DiapDealer · 01-31-2015, 05:03 PM

This line of code alone:

Code:

<span style="font-family: 'Futura Light'; font-weight: normal; font-size: 1em; line-height: 1.083;"><br /></span>

Won't produce the FlightCrew error you indicated (even if there are no font files included in the epub).

The references you probably need to remove are the @font-face declarations in the CSS (in the head of the page or in an external stylesheet). Specifically: any "src: url(...);" statements that are pointing to non-existent font files.

You've only included the error message from FlightCrew. The first column in the error will indicate the resource/file that doesn't exist (but is being referenced somewhere) in your epub. If that first column isn't a font file "OEBPS/Fonts/something.ttf/otf". Then your problem is something else.

Alda · 01-31-2015, 05:14 PM

Aha. Thanks so much DiapDealer. That fixed that particular error.

However, I am still left with this:

Quote:

The <item> element's "media-type" attribute has value "application/vnd.ms-opentype", but the file's media type is "application/x-font-ttf".

Can anyone help with that?

DiapDealer · 01-31-2015, 05:23 PM

Code:

The <item> element's "media-type" attribute has value "application/vnd.ms-opentype", but the file's media type is "application/x-font-ttf".

Sounds like even though you have no font-files included in the epub, there's a manifest entry for one (or more) in the OPF file (either that, or there IS a font file included in the epub and its media-type is simply declared wrong as indicated).

If the font files are truly not included in the epub, then you need to remove the <item /> entry for it in the manifest section of the OPF file (it would be removed automatically if the font files had been deleted from within Sigil).

Notjohn · 02-01-2015, 06:02 AM

I follow the rule of thumb: the fewer design elements in an e-book, the more likely it is to work out to my satisfaction, and to work across all possible devices and apps.

Alda · 02-01-2015, 08:09 AM

Thank you all so much for your help - much appreciated!

01-31-2015, 05:03 PM	#5
DiapDealer Grand Sorcerer Posts: 28,359 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	This line of code alone: Code: <span style="font-family: 'Futura Light'; font-weight: normal; font-size: 1em; line-height: 1.083;"><br /></span> Won't produce the FlightCrew error you indicated (even if there are no font files included in the epub). The references you probably need to remove are the @font-face declarations in the CSS (in the head of the page or in an external stylesheet). Specifically: any "src: url(...);" statements that are pointing to non-existent font files. You've only included the error message from FlightCrew. The first column in the error will indicate the resource/file that doesn't exist (but is being referenced somewhere) in your epub. If that first column isn't a font file "OEBPS/Fonts/something.ttf/otf". Then your problem is something else. Last edited by DiapDealer; 01-31-2015 at 05:14 PM.

01-31-2015, 05:23 PM	#7
DiapDealer Grand Sorcerer Posts: 28,359 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Code: The <item> element's "media-type" attribute has value "application/vnd.ms-opentype", but the file's media type is "application/x-font-ttf". Sounds like even though you have no font-files included in the epub, there's a manifest entry for one (or more) in the OPF file (either that, or there IS a font file included in the epub and its media-type is simply declared wrong as indicated). If the font files are truly not included in the epub, then you need to remove the <item /> entry for it in the manifest section of the OPF file (it would be removed automatically if the font files had been deleted from within Sigil).

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to add alternate fonts without replacing system fonts.(this time this is a guide)	techiemonkey	Kindle Developer's Corner	17	09-12-2012 04:55 PM
An Observation on Fonts - Improving readability by using bold versions of fonts	nesler	General Discussions	12	06-24-2012 12:33 PM
Problems adding fonts on KT	VirgoGirl	Kobo Reader	2	04-16-2012 12:12 PM
need the fonts in /usr/java/lib/fonts of kindle touch5.0.0	hanpal	Kindle Developer's Corner	1	02-20-2012 10:40 AM
Touch Fonts question (special characters in stock and custom fonts)	levil	Kobo Reader	20	09-23-2011 01:51 PM

01-31-2015, 03:01 PM	#3
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Big question is, if you want to embed the fonts. If you do, the actions will be different than if you don't. Also, I think InDesign can create an ePUB with a stylesheet instead of inline styles like the example you give. That will make work a lot, and I mean a lot, easier. Presuming you do not want to embed fonts (as this would not work on mobi files anyway afak), you can just search for font-family: 'Futura Light'; and replace that by nothing. That would work in the example you give.

01-31-2015, 04:57 PM	#4
Alda Zealot Posts: 104 Karma: 22 Join Date: Jun 2010 Device: none	Thank you for the advice Toxaris. That's just what I was wondering about. I have no particular investment in that font for the ePub. The file was exported from InDesign because a print book was designed in InDesign, and that book uses those fonts. I'm not fussed about it either way. So if I just delete that particular piece of code, then the ePub would use a default font - is that correct?

02-01-2015, 06:02 AM	#8
Notjohn mostly an observer Posts: 1,518 Karma: 987654 Join Date: Dec 2012 Device: Kindle	I follow the rule of thumb: the fewer design elements in an e-book, the more likely it is to work out to my satisfaction, and to work across all possible devices and apps.

02-01-2015, 08:09 AM	#9
Alda Zealot Posts: 104 Karma: 22 Join Date: Jun 2010 Device: none	Thank you all so much for your help - much appreciated!