Hi, kiddles:
Well, are we having fun yet?
You all know how often, here at MR, we're seeing that John or Jack or Harriet is trying to solve some typographic issue, and s/he decides to use "display: inline-block?" Well, guess what? That is ixnay with Advanced or Enhanced Typography.
We actually received our first-ever KQN, for formatting, today. 3500+ books, and we get this BS:
Quote:
Error Category: Formatting-Others; Comments: We noticed that your eBook which is currently in high demand with the customers is not enabled with enhanced typesetting.
Issue: The epub file consists of tag/property "display: inline-block;" that is not currently supported in Enhanced Typesetting conversion.
Issue location: The tag/property is present in CSS file inside the Epub.
Associated Class: .spa2, .spa1, .spa.
Proposed Solution: The "display: inline-block" property has been used to give block property to an inline entity. Change the property from "display: inline-block;" to "display: inline;". Adjust the margin to retain the alignment as of the source. This will solve the issue and enable with Enhanced Typesetting feature.
|
So, kids, display:inline-block is NOT supported, and moreover, you can get slapped on the wrist for using it.
We'd used it to create bulleted lists, with the obligatory hanging indents, for this person's book, that didn't use the ;bull character, but used squares, some little faces, and a directional sign, instead. But, IXNAY on the Inline-Block-ay.
Needless to say, the client is underwhelmed. He's being reasonable, thank GOD, but he's not a happy camper.
We also got a rasher of s**t about using line-heights, but I explained that we use varying fonts, and those use different x-heights, and have different tail/descender and ascender heights/sizes. I mean, are they KIDDING? I replied, "thank GOD that they can't adjust the damn line heights!" As most of you know, if you set the line-height, in MOBI, the end user can't adjust the line-heights, on the K4PC/K4Mac, etc., apps. Now, I'm all in favor of the user being able to do that, for the BODY fonts and main narrative, but for special elements, like headings and the like? Eff, no!!!
I thought that you kids may want to know this!!! Interferes with enhanced typography. I checked--just in case I'd missed something--I ran the source through KP 3.10, again, just to see if a warning came up, or anything like it, and it sailed through.
You'd think that if there's CSS that's going to interfere, with ET, they'd bloody well tell you, wouldn't you?
BU**ER!!
Hitch, whom, today, is
(grumpity, grump, grump grump)