08-14-2014, 11:37 AM | #61 |
Resident Curmudgeon
Posts: 75,840
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
08-14-2014, 02:50 PM | #62 |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
Advert | |
|
08-14-2014, 04:51 PM | #63 |
Resident Curmudgeon
Posts: 75,840
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
08-14-2014, 05:17 PM | #64 |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
08-15-2014, 12:36 AM | #65 | |||
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
Quote:
And you're up to 19 without even doing anything particularly unusual or heinous. That's not even counting fonts that replace missing glyphs in other fonts, for complying with font licenses that don't allow modifications.... What matters is not the number of fonts, but whether they're used sensibly. A work that changes fonts willy-nilly is going to look stupid even if you only have two or three fonts. A work that changes fonts in reasonable ways that make sense given the structure of the content is going to still look reasonable even if there are twenty fonts. Quote:
http://www.w3.org/TR/css3-fonts/#descdef-src It is strongly recommended for web content, but it matters very little for on-disk content, because the files are already downloaded. Either way, I can't imagine it hurting anything. |
|||
Advert | |
|
08-15-2014, 04:49 AM | #66 |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
dgatwood:
No, sadly: I meant families--not faces. ;-) Hitch |
08-17-2014, 04:38 PM | #67 | |
Resident Curmudgeon
Posts: 75,840
Karma: 134368292
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
08-22-2014, 02:16 AM | #68 |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Actually, the full syntax predates CSS 2.1, and most certainly is valid EPUB 2 CSS. The @font-face declaration syntax appeared first in CSS 2.0 (complete with the optional format bits), as shown here:
http://www.w3.org/TR/1998/REC-CSS2-1...ml#referencing Also note that web fonts are not in CSS 2.1 at all. They first appeared in 2.0, but were removed in 2.1, before eventually reappearing in 3.0. The EPUB 2.0 specification explicitly references the older CSS 2.0 documentation for @font-face rules for this reason. As I said, the only HTML user agents I'm aware of that support @font-face without supporting the full syntax are Microsoft Internet Explorer versions 7.x and 8.x. I'd be shocked if you found an EPUB reader that doesn't support the full syntax. If one exists, it is badly broken and is not in proper compliance with the EPUB 2 specification. |
02-01-2015, 02:51 AM | #69 |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Has there been any progress in this area? I just submitted three books to KDP in MOBI format, produced by KindleGen, and the "Preview Copy" that KDP send back had literally every font missing. It looks like for books with significant KF8 content, Amazon KDP's ingest process is broken beyond all repair at this point.
|
02-01-2015, 03:11 PM | #70 | |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
No. I don't actually recall everything discussed in this thread; we're pretty well deep into it, ourselves, as we're one of the few commercial firms that will do fonts at all, so... I can tell you that I just had a replication of the disaster I reported about some messages back, with a book with a serif, a sans-serif, and a "fancy" or display-type font (god help me, Chiller. You can't make this stuff up). All in, 7 total faces (reg, ital, bold for ea. serif and sans-serif) and Chiller. The book was stripped, stem-to-stern. We remade it just under 100x, trying everything we'd learned from the first disaster (not much, mind you, as troubleshooting doesn't seem to provide any sensible answers). Long story short, we ended up doing a serif + Chiller, removing the sans-serif. There seems to be something--and this is pure speculation, as we've never been able to really GET anything from all the weeks of effort on this--that is a limit of some kind. We KNOW, factually, that there's a span limit of some type. We know that from the testing we did before; at some point, X number of spans "breaks" the book. (e.g., "span style="blabbety", at least, for FONT styling spans). We also know, factually, that this makes NO sense, because INDD-output ePUBs-->MOBI are loaded with spans, that don't seem to break the book. My working theory is, there's a bug at the KDP that's triggered by encountering...SOMETHING. But the issue is, with so many variables, it's almost impossible to figure out what the hell that is. We have even gotten the point of testing with 3 paragraphs, one header and STILL can't figure out what triggers this odd behavior. I also don't know if it's something in the CSS. (If you recall the issue that prompted the "help" thread, that was the first around this). We've tried to eliminate all the possibilities, in that arena, as well. It's like bad aviation accidents--there are, I think, 3 things that have to somehow come together, to make it happen, but I don't know what those three things ARE. I never see this behavior with serif fonts, for example; we only seem to run into it when either: --A particular font ITSELF doesn't work; e.g., Papyrus. If you replace the font, the problem is fixed, or, --You have serif, sans-serif, and a display font. When this happens, nothing we try ever seems to "fix" the desired outcome. We see this when we are using two fonts that work perfectly well (the serif and sans) in other books. So...something about adding the third font just causes chaos. n.b.: both of the books that had massive issues with this, the second case in my short list above, had MASSIVE amounts of font interspersion, by which I mean, a lot of bold spans (b or spans) inside regular fonts, and a LOT of switching back and forth between serif and sans. So, many changes from font a to font b, and many changes from font a reg to font a italic or bold. I don't know if this is part of the issue, but our troubleshooting SEEMS to indicate that this stripping behavior persists, even if we are down to 3 paragraphs, one header and nothing else. Therefore, I don't THINK it's the number of changes from a to b, GENERALLY. I'm sorry--I wish I knew more. I'm in the process of preparing yet another lengthy email to Amazon, with all our tests, advising "we tried this, we observed that, this happened, that didn't happen..." to see if they'll get back with us on it. They never did on the last one. Honestly--I think we may actually know more about it than they do, which is sad, because we know, to my mind, next-to-nothing. Oh, a third/fourth instance: OTF is always a problem, so if you've tried OTF, convert them to TTF, and give that a go, or find a "true" TTF that's similar, and try that. Secondly, Adobe fonts are almost ALWAYS stripped, for some reason, I know not why. There's a guy on the KDP that has this quasi-consipiracy theory that all MS and Adobe fonts are being stripped, due to copyright (licensing) issues, but my experience doesn't support that idea; I've tested that pretty thoroughly, and it's not MS, certainly. Sorry--wish I had more for you. What fonts were you trying, if I may ask? Hitch |
|
02-02-2015, 03:18 AM | #71 | |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
Some are OTF, some are TTF. Every font disappeared. Worse, most of them were still referenced, apparently, causing the online previewer to show square boxes where the letters should be. That's just not right.... KDP's import also mutilated my SVG text, changing the font size to approximately one point tall (unreadable). I can't even imagine what would cause that. |
|
02-02-2015, 06:11 PM | #72 | |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Warning: I'm NOT a font expert. Not at all. You're obviously far more of one than I, I couldn't create a font if my life literally depended on it. That being said, I know from unhappy experience that trying to use fonts that have any type of mapping outside of the usual (again, for example, some of the Mandarin font(s)),results in what you've described--the sad look of empty boxes. No font, because the device doesn't have the slot for it. (I think that part is right--can one of you massively geekier guys, like @Diap, etc., jump in here and confirm--it's the firmware, right? Rather than the hardware?) And, again, unless I'm wrong, that SVG is not gunna work, certainly not for text. Not yet. Admittedly, because I have to make books that cover the spectrum, I don't play with SVG a lot (wish I could!), but.... Hitch |
|
02-02-2015, 07:23 PM | #73 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@Hitch: Yep, the K2 is not a good citizen in terms of unicode coverage .
It's much, much better on anything KF8-capable, (i.e., FW >= 3.4), and especially on FW 5.x. Complex script shaping is still touch and go, though, but that's another matter entirely. (Note that I'm speaking solely of eInk devices here, since I have zero experience with anything else in Kindle-land). Speaking of, FW 5.6.1 saw a serious update of the font rendering engine, so some of the weird quirks w/ custom fonts might have been alleviated on those FW. (Pure conjecture, I haven't updated anything to 5.6.x on my end). |
02-06-2015, 01:29 AM | #74 | |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
My best guess is that the KF8 file that came out of KDP actually contained the embedded fonts, but in a badly broken form that caused them to act like they contained no glyphs. On OS X, if you opened the file, it used the Mac font system, which correctly refused to open the broken fonts; the result was that it fell back to default fonts. By contrast, Kindle Previewer on whatever platform the website uses (Linux?) is much dumber, and tried to use the broken fonts from the bundle, resulting in the broken characters. Of course, this still raises the question of why an innocuous line of CSS asking for geometric precision in font rendering would cause KDP to spit out a MOBI containing corrupted font resources, but.... |
|
02-06-2015, 01:34 AM | #75 | |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
My best guess is that the KF8 file that came out of KDP actually contained the embedded fonts, but in such a badly broken form that they effectively contained no glyphs. On OS X, if you opened the file, it used the Mac font system, which correctly refused to open the broken fonts; the result was that it fell back to default fonts, hence it looked like the fonts had been stripped. By contrast, Kindle Previewer on whatever platform the website uses (Linux?) is much dumber, and tried to use the broken fonts from the bundle, resulting in the missing glyph boxes. Of course, this still raises the question of why an innocuous line of CSS asking for geometric precision in font rendering would cause KDP to spit out a MOBI containing corrupted font resources, but now that I know that it does, I've removed that line of CSS for now, and everything goes through cleanly, at least for me. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Custom fonts K4 | artcon | Kindle Developer's Corner | 2 | 05-11-2014 04:34 PM |
Custom fonts | Jellby | PocketBook | 20 | 12-31-2013 09:07 AM |
PRS-T3 T3 fonts & custom fonts | Phil_C | Sony Reader Dev Corner | 5 | 12-22-2013 02:34 PM |
Stripping Fonts | Rob Lister | Calibre | 2 | 10-05-2011 11:32 AM |
Touch Fonts question (special characters in stock and custom fonts) | levil | Kobo Reader | 20 | 09-23-2011 01:51 PM |