08-21-2018, 08:53 PM | #1 |
Junior Member
Posts: 8
Karma: 10
Join Date: Aug 2018
Device: Kobo Aura ONE
|
ePub3, Woff not valid
Hi all.
I have an ePub3 I've created with embedded DroidSerif fonts (regular, italic, bold and bold/italic). They are in WOFF format (not WOFF2). In the editor, when I run a check on the ePub, I receive the following error for each of the fonts I've embedded: "Not a valid font: Not a supported font, has no name table" These embedded fonts appear to work correctly on my Kobo Aura One. I'm wondering if the editor does not yet understand WOFF files, or if I've done something wrong. I used the online service "Transfonter" to convert them from TTF to WOFF. In the IDPF EPUB 3 Core Media Types, Section 2, it lists WOFF as a supported media type. So I'm thinking I did something wrong in my ePub. Thanks! |
08-21-2018, 11:12 PM | #2 |
creator of calibre
Posts: 43,776
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
calibre in general has no support for woff. And while the epub 3 spec allwos them, I'd strongly recommend against using them. Use otf instead.
|
Advert | |
|
08-22-2018, 02:33 AM | #3 |
Junior Member
Posts: 8
Karma: 10
Join Date: Aug 2018
Device: Kobo Aura ONE
|
Thank you!
|
08-22-2018, 12:55 PM | #4 |
Junior Member
Posts: 8
Karma: 10
Join Date: Aug 2018
Device: Kobo Aura ONE
|
This is just a point of discussion...
I was just re-reading that "EPUB 3 Core Media Types" document again and it says they're deprecating *both* TTF and OTF, it seems like, in favor of WOFF and WOFF2. I assume this means if/when EPUB 4 is out it'll only be WOFF-based fonts. I'm curious what the motivation is there. I mean, why would other font types be deprecated? Does TTF and OTF fall short of what WOFF can provide? Why wouldn't they just specify TTF, OTF, WOFF and WOFF2 as supported? Why would they need to remove them from the spec? eReaders already seem to universally support TTF and OTF, why not continue to take advantage of that? What's IDPF's motivation for *removing* them? |
08-22-2018, 01:35 PM | #5 | |
Grand Sorcerer
Posts: 6,470
Karma: 84000001
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
You can read more here: Replace application/vnd.ms-opentype with the standardised application/font-sfnt in Core Media Types. |
|
Advert | |
|
08-22-2018, 03:26 PM | #6 |
Junior Member
Posts: 8
Karma: 10
Join Date: Aug 2018
Device: Kobo Aura ONE
|
Thanks! That link helps a lot because the IDPF document is not clear at all. They mark the whole row as DEPRECATE without being clear what is being deprecated.
You know, as I read it now, I think it's just a typo combined with formatting. It should read "Deprecates application/vnd.ms-opentype", on the same line. Instead of "OpenType and TrueType fonts. Deprecate" |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
epub3 app with epub3 dictionary support | Doitsu | ePub | 0 | 01-21-2017 09:38 AM |
Sigil does not recognize WOFF | nkalvi | Sigil | 8 | 02-07-2015 07:54 AM |
Epub conversion does not embed WOFF font | iliakan | Conversion | 6 | 02-06-2015 01:42 AM |
New Errors Converting epub3 -> zip -> epub3 | Lola25 | ePub | 2 | 11-12-2013 09:37 PM |
Valid ePub, but not valid enough for iBooks | MichaelGray | ePub | 46 | 01-14-2011 08:22 AM |