Quote:
Originally Posted by davidfor
Quote:
Originally Posted by arspr
I haven't called it a bug but an issue... 
Nevertheless, unless they have other ways to make kepubs work fine, (methods which we do not know), this is "serious" trouble for Kobo. I mean, at least in common epubs, every time you have a new html file you have a page jump. Because of that if you want a new chapter BUT you don't want a page jump, you need using the structure I've told where each file has several chapters in it.
Maybe Kobo can avoid that structure with some kind of untold trick, or they can make that structure work with some kind of untold setting. But it doesn't look really promising, although as you say we must be cautious. |
Sorry, but you missed PeterT's point. A kepub is not an epub. It might look like an epub, and appears to share a lot of the specs. But, Kobo define those specs. Unfortunately, they haven't published those specs, or at least nowhere that I have seen them. The specs might be that there is a one-to-one relationship between TOC entries and files. We don't know. The conversion that we have is based on guesses made when looking at DRM free kepubs from the Kobo shop. |
What I missed is not PeterT's point but my English lessons...
You don't seem to have understood me so I re-explain (and I also copy my own original post in your quote).
I had already thought about what you are saying (each chapter must have its own file in Kepubs, and each file must have its own ToC entry too). But if that is the situation, and
if there's no other hidden/unknown/Kobo private/undocumented feature, that situation is a clear STEP BACKWARDS from our old, well established, well known common epubs. Because, and the book "Las legiones malditas" is a good and
real-world example, in either kepubs and epubs, a new html file always means a page break (unless, in kepubs, there were a hidden option to make it otherwise). So if the ebook author/editor DON'T want a page break before each chapter he is already forced to put them in the same html file. But then this situation leads to a lot of cross troubles and side effects in ACCESS,
unless, I repeat,
we are missing something hidden about kepubs.
But, do you
really think that's the situation (missing info about kepub and ACCESS features in this particular issue)?
Of course that's always a possibility but if I were to create an enhanced epub format because I feel it's good for my device and shop, (a brand new
Kobo epub format), I suppose I would have copied
ALL the existing features epubs already have and then I would have added the new things I thought interesting. So if something that works in epubs doesn't work in kepubs, of course, maybe the reason is that it has to be done in a different (and unknown, unpublished) way. But I'd really bet money on the alternative possibility of something being broken during the "enhancement" process.
And now I'm going a bit offtopic. And sorry if I don't express fine myself. English is not my mother language and my English knowledge is what it is...
So maybe it's because of my said level of English, because I'm missing some info, or because I'm just dumb. More over, I would really like to think that the fault is in me. But in the little time I've spent in these forums, (since I got my Aura HD), I'm getting the feeling that there's some kind of
fear about directly saying
something-doesn't-work-in-kepubs/ACCESS. It's like if you are afraid of Kobo getting angry about that kind of posts and then completely dropping sideloaded kepub support. It's something in the air, an unwritten rule, about forum users somehow being forced to say the same sentence in a
something-doesn't-seem-to-work-in-kepubs/ACCESS,-but-please-please-please-don't-get-it-wrong-because-Kobo-is-fantastic-and-PROBABLY-the-problem-is-something-I-did-wrong way.
Of course, trolling about Kobo should not be admitted. Posts about ACCESS-is-rubish should be always avoided, but I really think that
Kobo should be really pleased when people post the troubles their software or devices have (or seem to have), they explain them, and post a way to make those troubles arise, (even if they happen because of the user's fault).
Maybe my way of speaking (of writing) is a bit harsh (and maybe it also happens because of my English knowledge level), but I always try to explain step by step what the problem is. And I only post what I find while reading my
real life books. And so far, I don't say that ACCESS is bad, (I'm currently on ACCESS, so I do think RMSDK is worse), but nevertheless ACCESS shows some flaws. I've detected at least:
Of course they can be caused by:
- I am doing something wrong.
- TRUE bugs in ACCESS.
- Things that have changed and should be made in a different way inside kepubs.
And of course Kobo can take the following approaches in either of them:
- Ignore them. Spending any attention in them is worthless.
- Fix them (if they were a bug or just an undesired behaviour).
- Explain them to the world, (if they are kepub changed behaviours from the standard epub), if they thought that allowing the users know how kepubs work is interesting for their business (which is selling ebooks, but also devices which can read books from other places, enhanced by the ACCESS renderer).
But if Kobo is not informed about the issues ACCESS suffer (or seems to suffer), they cannot take ANY decision...
