-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
simple navigation does not work as it should #46
Comments
I'll take a look at this issue as well. When you look at the book are you sideloading it as .epub or .kepub.epub? |
Its |
Please find my epub 3.2 demo here: |
Can you retest with the extension .kepub.epub? https://github.com/kobolabs/epub-spec#sideloading-for-testing-purposes |
Hmm. now most of thinks aren't working... Updated a link do my epub. |
So we do have open issues regarding our support of page-break properties (there's a table listing it here: https://github.com/kobolabs/epub-spec#css) and that is a known issue. The EPUB provided did not have bookerly referenced as a font, so I don't know what the problem is there. Publisher Default in this case I believe defaults to Georgia, which is our standard font. I don't understand the "multiple sections in one XHTML" support question, we are rendering the sections, and the text is present, anchors will bring you to them if they're not on the same page. TOC footnote, I will log as a bug as it looks like it's filling all of the backup requirements we set out for footnotes, but we need to possibly create a case where that should not occur if the reference is in a TOC. |
I have sideloaded two fonts: Bookerly and Literata to sdcard. And the first one is set as my default font in the ereader. If I open my demo as Sorry, by multiple sections i mean multiple chapters ( |
The font problem (italic->bold) is moved to #49 |
Simple scenario with link
<a href="#foo">...</a>
to<div id="foo">...</div>
somewhere else.Clicking on the anchor always moves my ereader to the page BEFORE the page where
div#foo
is visible.And if
id
is set on<section>
or<figure>
the landing page is even more "inaccurate".My e-reader Clara HD (latest soft).
The text was updated successfully, but these errors were encountered: