How do I get rid of Table of Contents?

[Hitch]

Originally Posted by JSWolf

Speaking of smallcaps. I am not a fan of them to start the chapters/section break.

If you use a font that has small caps in it and the program that's displaying the eBook supports font-variant: small-caps; then all is good as the small caps will look good and not simulated.

But most books don't use small caps too much so simulated is easy enough to ignore. As to the size, I use 0.8333em. I don't know if that's the correct size or not, but it looks good enough to me.

Wolfie, my one Twoo Wuv:

And let's recap: exactly how many devices--not software, browser-based readers--have you seen that support "font-variant," exactly? "font-variant" is supported, in ET (Enhanced Typesetting) in KDP, but that's for KFX only, then. Just sayin'.

You either split the baby and go for smallcaps where you can, and pray a lot, or you do a faux font-variant, by using all-caps smooshed. Them's the realities.

Hitch

[bookman156]

Publisher Font only is selectable if the eBook you are viewing has at least one embedded font.

Obviously, I would have thought, but mine doesn't show it for files I know have embedded fonts, so it's just too old. When did Paperwhites start supporting embedded fonts?

[Hitch]

Originally Posted by bookman156

Obviously, I would have thought, but mine doesn't show it for files I know have embedded fonts, so it's just too old. When did Paperwhites start supporting embedded fonts?

Well. Hell, as far as I know, always? I honestly don't remember them not supporting it. Are you absolutely certain that's a PPW? Could it be instead a K4 or "newer" k3 or the like?

Let me ask you this--how do you "know" that they have embedded fonts? Not being argumentative, genuinely asking.

Hitch

[bookman156]

And let's recap: exactly how many devices--not software, browser-based readers--have you seen that support "font-variant," exactly? "font-variant" is supported, in ET (Enhanced Typesetting) in KDP, but that's for KFX only, then. Just sayin'.

It is possible to subset the small caps out of an open type font to make a small-caps-only font (you can use Squirrel) and embed that and then use it as a span class. But only if embedded fonts are used by the device, of course. But it's a possibility given that font-variant doesn't appear to be widely supported at the moment, if at all, on hardware devices, for all it is in some web epub readers.

[bookman156]

Well. Hell, as far as I know, always? I honestly don't remember them not supporting it. Are you absolutely certain that's a PPW?

No, mine doesn't show them in the list at all, and I've tested with my own files. I was under the impression embedding was a very recent thing with them.

[Hitch]

Originally Posted by bookman156

It is possible to subset the small caps out of an open type font to make a small-caps-only font (you can use Squirrel) and embed that and then use it as a span class. But only if embedded fonts are used by the device, of course. But it's a possibility given that font-variant doesn't appear to be widely supported at the moment, if at all, on hardware devices, for all it is in some web epub readers.

Not to be obscenely lazy, but at that point, I say to myself, "Self, what typeface can I use, instead of this, that already has a smallcaps font?," and that's what I use.

Hitch

[Hitch]

Originally Posted by bookman156

No, mine doesn't show them in the list at all, and I've tested with my own files. I was under the impression embedding was a very recent thing with them.

Sorry, if I'd seen this, I'd have multi-replied. I hate replying over and over. Duh.

Okay, so you're saying that you correctly embedded fonts, in a (what?) file--an ePUB, a MOBI?--and you xferred them how to your PPW and you don't see them? For what classes and elements are you embedding them?

Hitch

[bookman156]

Not to be obscenely lazy, but at that point, I say to myself, "Self, what typeface can I use, instead of this, that already has a smallcaps font?," and that's what I use.

That's what I would use too if font-variant was supported. But clearly span class is supported and embedding on some devices. So a span class small caps subset font works, especially if mapped to upper case characters, because if embedded fonts aren't picked up it just falls back to full caps rather than lower-case, which would be bad for BC/BCE etc.

[bookman156]

Okay, so you're saying that you correctly embedded fonts, in a (what?) file--an ePUB, a MOBI?--and you xferred them how to your PPW and you don't see them? For what classes and elements are you embedding them?

In an EPUB. The embedded fonts show perfectly well in Kobo, for instance.

It's a Paperwhite 3, 7th gen, so I assume it doesn't support embedded fonts (or Calibre unembeds them in conversion I suppose). Again, I thought it was recent models only that supported embedding, but I couldn't give you a model/year.

[bookman156]

For what classes and elements are you embedding them?

On the body.

[Hitch]

Originally Posted by bookman156

On the body.

Okay, do you mind explaining a bit--you're making these mobis with what, Calibre and then sideloading them to your Paperwhite? In what format, EXACTLY? Do you mean MOBI? or do you mean that AZW3 format?

AND, are you running them through (not now, you can't, but you used to be able to) the KDP upload and then downloading a then-MOBI copy? Did you put that font tag ON the "body" CSS?

Hitch

[bookman156]

Okay, do you mind explaining a bit--you're making these mobis with what, Calibre and then sideloading them to your Paperwhite? In what format, EXACTLY? Do you mean MOBI? or do you mean that AZW3 format?

Sideloading via Calibre, which makes a MOBI.

Did you put that font tag ON the "body" CSS?

Not always, but yes, font family on body.

[Hitch]

Originally Posted by bookman156

Sideloading via Calibre, which makes a MOBI.

Well, for one thing--the first honker--you're building an old-style MOBI (KF7) which doesn't support embedded fonts. That's the first part.

Not always, but yes, font family on body.

Well, from a KDP standpoint, that practice=bad. Firstly, if you did that with a file you were uploading to the KDP platform, the font would be stripped, immediately.

Secondly, if it did slip past, it would make the body font unchangeable, which is VERBOTEN on KDP.

So, you have 3 issues going on there and hells, no, that PPW is not going to show Publisher fonts from a KF7 mobi.

Hitch

[bookman156]

Well, for one thing--the first honker--you're building an old-style MOBI (KF7) which doesn't support embedded fonts. That's the first part.

Ah, interesting. Didn't know that.

So how to load an EPUB onto the Kindle such that it does show embedded fonts?

Well, from a KDP standpoint, that practice=bad. Firstly, if you did that with a file you were uploading to the KDP platform, the font would be stripped, immediately.

Secondly, if it did slip past, it would make the body font unchangeable, which is VERBOTEN on KDP.

I don't use KDP at all. Are there any repercussions for putting font-family on the body otherwise? Or will it also interfere with sideloading the EPUB to a Paperwhite?

Is it better to put font-family on the p tag and h tag then? Or is this just KDP weirdness?

[Hitch]

Originally Posted by bookman156

Ah, interesting. Didn't know that.

So how to load an EPUB onto the Kindle such that it does show embedded fonts?

Well, hell, if you're me, you just open Kindle Previewer 3 (you can download it from Amazon) and then drag-drop the working ePUB (the one showing you fonts in Kobo) onto it. It will process it and display the result. You can then use File-->Export-->MOBI and side-load the resulting file to your PPW and you should, assuming everything else is according to Hoyle, see your embedded (Publisher) fonts.

FYI, some users' devices are already able to process/accept ePUB files, emailed to the Kindle dedicated email address--what used to be and to some extent, still is--the Document Queue. You could try that first, with your working ePUB.

I don't use KDP at all. Are there any repercussions for putting font-family on the body otherwise? Or will it also interfere with sideloading the EPUB to a Paperwhite?

Well, SSDD--it means that those whom have the ePUB inflicted upon them likely shan't be able to override your font choice. I'm only mostly-cranky--as opposed to terminally cranky--but that can get right up my nose, as a reader. (OR, forced text alignment. It drives me ape**** when someone forces ragged-right!)

Is it better to put font-family on the p tag and h tag then? Or is this just KDP weirdness?

Define "better"? Not being a wiseass, but for what purposes precisely?

Hitch