Quote:
Originally Posted by rashkae
3. In Kepub, measurements of physical length are translated to a fixed number of pixels. For a very common example, text-indent 20pt. The number of pixes were adjusted back when devices were 160PPI,,,, on a 300PPI device, 20pt indent is barely distinguishable.
|
That's really poor eBook making to use pt instead of em. 20pt is about 1.6em. Using 1.6em is what works and is proper coding. You cannot know what type of screen/program/system the eBook will be read with so using em will handle this.
Quote:
|
4. In Kepub, page numbering for the whole book jumps around out of order on some books (ie, display progress for whole book instead of per chapter). This is related to the reader using TOC entries instead of the epub spine to determine page numbers, and I realize you're only likely to see on 'unsupported' kepub sideloaded books. But there's no reason for it!.. the calculation for progress by Percent got it right, it should be possible to get page number ordering using the same logic.
|
This is not a bug. If you convert an ePub that does not follow the ToC conventions for kepub, that's your fault, not Kobo.
Quote:
|
5. For epub books, the font used does not fall back if the text has missing glyphs... for books that take advantage of Unicode characters, this means those characters will be missing entirely from the text, even if Kobo fully supports it. (Works fine with Kepub)
|
This again is not a bug. If you chose to use a font that does not support the glyphs in the ePub, that is again your fault. If the ePub has font(s) embedded that handle the glyphs and you override that, again, your fault. Only if the ePub does not have an embedded font that works or the default ePub font doesn't work can it be considered a problem.