Clara HD Standard books epub vs kepub and calibre

[Aleron Ives]

Originally Posted by DNSB

They are intended for Kobo's epub3 Webkit based renderer so do not have a toc.ncx which will cause issues if you try reading on an epub2 renderer.

Is there a certain expected behaviour when you have both toc.xhtml and toc.ncx? I thought an EPUB2 renderer would just ignore toc.xhtml and use toc.ncx, whereas EPUB3 renderers would prefer toc.xhtml.

[veysey]

Originally Posted by Cactus Chef

As someone who was too young to have participated in the vim vs emacs wars of yesteryear, I am thrilled to be present to witness the EPUB vs KEPUB wars of today. Thank-you, internet!

Staying on topic, though:


Having tried both, for the average user I really don't think there's much of a difference. I tend to stick with KEPUBs, but YMMV.

Also, unless you have a compelling reason to have SE books in your Calibre library, you could just download the books directly from SE onto your Kobo using the experimental browser. Since my Calibre library was meant to be a reflection of ebooks I had "bought" and stripped the DRM from, I stopped bothering to keep local copies of SE books.

Hey, those wars are alive and well! I think? You can't let the vi people win? (n.b. Vi, not "Vi improved" ... how does that get you the vim acronym anyway? Vi people ...)

Or use Ed. To quote the famous Patrick J. Lopresti: "When I log into my Xenix system with my 110 baud teletype, both vi and Emacs are just too darn slow. They print useless messages like, ‘C-h for help’ and ‘“foo” File is read only’. So I use the editor that doesn't waste my VALUABLE time. Ed, man! !man ed"

If anybody here knows what I'm talking about, can I get get a mid-90's meme in return?

Thanks!

Also following this thread with interest as I just got a Kobo. ☺

This post edited in emacs.
Hey, those wars are al

[nabsltd]

Originally Posted by Quoth

All correctly rendering engines simply regard 12pt = 1em

Any renderer that does this is wrong. 1em is a unit a measurement that means "the current font size". So, 1em could mean to render an entity to 4pts or 3000pts...or any size in between.

Now, if you meant to say "most renderers set the default font size to 12 points", then that's as may be, but it's not the same thing as saying "12pt = 1em" or "1em = 12pt".

[Quoth]

Originally Posted by nabsltd

Any renderer that does this is wrong. 1em is a unit a measurement that means "the current font size". So, 1em could mean to render an entity to 4pts or 3000pts...or any size in between.

Now, if you meant to say "most renderers set the default font size to 12 points", then that's as may be, but it's not the same thing as saying "12pt = 1em" or "1em = 12pt".

That's in wikipedia. But it's not true for ebooks.

There are only two choices for pt in an ebook:
1) Render a certain number of pixels = 1pt. That's bonkers for an ereader as the font can be scaled by the user.

2) Convert Pt to em by /2. The body font is recommended to be 12pt if using a Wordprocessor to make ebooks. There is no em style. The options in styles for margins are cm, inches, pica (obsolete) anf point. The cm or inches should only be used for PDFs. The point size of fonts isn't even absolute, a different family at 12pt (or 1em on web or ereader) will be a different size.
So 18 pt should be interpreted as 1.5em, which makes sense.

There is no third option of physical size as with PDFs, because we never can be sure on screen size and DPI, and even with PDF, the font metrics decide the physical size, not pt directly.

The problem with kepub is that font sizes in pt are treated differently to margins in pt. That makes no sense.
Also kepub and epub on a kobo don't render the fonts at the same size at the same font scale slider.

Cm and Inches don't work on Web or ebook as reported screen size / dpi / resolution may be wrong. So images for web or ebook should be px (which not always = 1 pixel) or %, never cm or inches (except for PDFs, because they have a fixed known paper size for each page), nor pt or em.

The pt and em can be used interchangeably as 12 pt =1 em for fonts and margins. The cm, inch, pica and rem should never be in ebooks. Images can use px or % (but only on one axis, the other axis then needs to be auto).

We also never need line height in ebooks, because the user can vary that and the default line spacing is decided by the font metrics. A bigger size font (either at same pt/em or say 2em) will automatically use bigger spacing. We use styles in WP, which become CSS in ebook that only set paragraph margins and padding. So on conversion, even epub to epub I automatically strip all line-height.