Epub conversion does not embed WOFF font

[iliakan]

My CSS rule is as follows:

@font-face {
  font-family: 'FontIcons';
  src: url("icons.woff") format('woff');
  font-weight: normal;
  font-style: normal;
}

The path is given relative to CSS. The stylesheet is provided by --extra-css=/path/to/my.css, and the font is at the same dir with the stylesheet.

But ebook-convert cannot find it, it shows:

Failed to find fonts for family: FontIcons not embedding

What have I done wrong or WOFF is not supported?

[kovidgoyal]

No epub readers support woff, keep your fonts in otf or ttf format.

[nkalvi]

I've tested it on iBooks on iPad and Mac. I'll test on Kindle HDX later.

Sigil 0.8.4 also displays the book properly with embedded woff fonts (on Mac).


http://www.idpf.org/epub/30/spec/epub30-overview.html

2.8 Fonts

EPUB 3 supports two closely-related font formats — OpenType [OpenType] and WOFF [WOFF] — to accommodate both traditional publishing workflows and emerging Web-based workflows. Word processing programs used to create Publications are likely to have access only to a collection of installed OpenType fonts, for example, whereas Web-archival EPUB generators will likely only have access to WOFF resources (which cannot be converted to OpenType without undesirable, and potentially unlicensed, stripping of WOFF metadata).

EPUB 3 also supports both obfuscated and regular font resources for both OpenType and WOFF font formats. Support for obfuscated font resources is required to accommodate font licensing restrictions for many commercially-available fonts.

[eschwartz]

Now find an E-Ink ereader that supports EPUB3.

Bringing EPUB3 as a proof is a bad move. It is vastly undersupported.

calibre does not support EPUB3. This is by design, since it is not worth supporting useless formats.

Expecting calibre to generate EPUB3-specific features during standard conversions is just asking for MASSIVE trouble in the vast, vast majority of EPUBs and ereaders.


Note that the Editor will throw a warning/error, but will allow you to use whatever you want (it will in fact never do anything of its own volition, only when told). I do not hold out tremendous hope that any automated tools will provide explicit support for EPUB3 anytime soon.

[eschwartz]

And Sigil embeds webkit to render previews, so it is arly surprising it supports a lot. But I assume it doesn't pass validation.

I wouldn't be surprised if calibre also displays it fine, for the same reason, in the Editor preview pane, and the Ebook-Viewer.

And it is STILL a horrible idea to actually do it.

[nkalvi]

While it is not supported 100%, good level of support is there already (half full ) :
http://epubtest.org/results/

Also, Pandoc (http://johnmacfarlane.net/pandoc/epub.html) has very good support for EPUB3.

I'm not sure why EPUB 3 is a 'useless format' - could you please elaborate?

Originally Posted by eschwartz

Now find an E-Ink ereader that supports EPUB3.

Bringing EPUB3 as a proof is a bad move. It is vastly undersupported.

calibre does not support EPUB3. This is by design, since it is not worth supporting useless formats.

Expecting calibre to generate EPUB3-specific features during standard conversions is just asking for MASSIVE trouble in the vast, vast majority of EPUBs and ereaders.


Note that the Editor will throw a warning/error, but will allow you to use whatever you want (it will in fact never do anything of its own volition, only when told). I do not hold out tremendous hope that any automated tools will provide explicit support for EPUB3 anytime soon.

[eschwartz]

The ability for pandoc to create EPUB3 is neither here nor there.

epubtest is a pipe dream. I will be impressed when I see just one eink device anywhere that is EPUB3 compliant. It is an unwise move to cut yourself off from all the devices that don't support whichever insignificant shiny-ness of the day is being enthused about.

So yes, if you are designing fixed-format/multimedia books, then by all means target iBooks as a virtual exclusivity.

calibre and Sigil are not iBooks creation tools, they are ebooks creation tools. There must be an actual benefit to putting in the work to handle EPUB3.

And for all your excitement about halfway support (really? ) the vast majority of books aren't using a single feature that necessitates EPUB3, which is probably why they keep making EPUB2, which is probably why few have bothered to make apps (and none have made e-ink ereaders) that handle them.