Aura HD Considering Aura HD, supplementing KPW1

[Katsunami]

For some time, I've been considering an Aura HD, but the price was too high to justify, taking into account that I already have a Kindle Paperwhite 1 which is perfectly fine. Now that the AHD price has come down to ~€145, I'm considering it again, because of the font adjustments, and the larger screen.

Even though I can go take a look at the reader in a nearby store, I will not be able to side-load my own EPUB/KEPUB books; I don't even know if I'll be able to actually get it in hand and turn it on.

Therefore, I have some questions that I cannot answer by searching the web, and can't find out on my own. I would greatly appreciate some help resolving them to see if the AHD is a good addition to (or maybe even replacement) for the KPW1.

First: I like to make clear that I will always side-load any books, even the ones I buy at Kobo. My base format is EPUB, and I use Calibre to convert to AZW3 for the KPW1 (I even go as far as converting Amazon books to EPUB, and then working from there), and would also use the KEPUB plugin to convert to KEPUB.

Second: I am only interested in book statistics: time to read per chapter, per book, and page numbers. I'm not interested in any overall reading statistics, or any online capabilities whatsoever. After registering the reader, any synced books will be deleted, and Wifi will be turned off, probably forever (except if it's needed to accomplish something special).

Third: I will not be hacking or jailbreaking the device.

The questions:

1. I'm seeing complaints in reviews that the Kobo readers always have space between paragraphs and no indentation. Is this true? If so, for EPUB, KEPUB, or both?

2. Does the AHD monitor and display Time To Read for the chapter and book for EPUB, or does it only do this for KEPUB? If it's the latter, does it work with Calibre-created, side-loaded KEPUB?

3. Do the font adjustments (weight, sharpness, etc) work on side-loaded EPUB / KEPUB books?

4. Is the "leave half of the screen blank at random locations"-bug resolved?

5. The Kindle driver is able to send the page numbers calculated by the Count Pages plugin to the Kindle. So, the Kindle displays the same page numbers as Calibre does. I have chosen a custom page count, setting the plugin to count using 2400 characters per page. (This is the average for an English Del Rey Paperback.) Can the Kobo or KoboTouchExtended driver also send the page numbers created by Count Pages to the Kobo, or does the Kobo always use the Adobe algorithm? (In this case, I'd need to recount the page numbers in my library.) Also, is there a difference between EPUB and KEPUB in this regard?

And last, a request. I've attached a free public domain book, which I acquired at Feedbooks.com; the ZIP-file contains the EPUB as it is posted at FeedBooks.com, and a KEPUB created with the Calibre plugin. After converting it to AZW3, it displays perfectly on the Kindle, and I would like to see a comparison with regard to display on the AHD.

I would like to request that someone does the following:


0. (Preferably: Update the AHD to the latest firmware available, as that's what I would do.)
1. Load the attached EPUB and KEPUB books into the Aura HD.
2. Set the font to a SERIF font, and set weight, sharpness and size in such a way that it would be comparable to a well-printed paperback.
3. Display the first page of the tale "The Golden Bird" on screen, using the EPUB, and take a picture.
4. Flip the page once, take another picture.

Please repeat steps 2, 3 and 4 using the KEPUB file.

5. Attach the pictures to a post.

Thank you very much for all efforts.

[davidfor]

Originally Posted by Katsunami

For some time, I've been considering an Aura HD, but the price was too high to justify, taking into account that I already have a Kindle Paperwhite 1 which is perfectly fine. Now that the AHD price has come down to ~€145, I'm considering it again, because of the font adjustments, and the larger screen.

Even though I can go take a look at the reader in a nearby store, I will not be able to side-load my own EPUB/KEPUB books; I don't even know if I'll be able to actually get it in hand and turn it on.

The Aura HD has a micro SD card slot. If you have a card, put a few books on it and take that with you. If they have a demo model, insert the card and the books will be listed in the library.

Therefore, I have some questions that I cannot answer by searching the web, and can't find out on my own. I would greatly appreciate some help resolving them to see if the AHD is a good addition to (or maybe even replacement) for the KPW1.

First: I like to make clear that I will always side-load any books, even the ones I buy at Kobo. My base format is EPUB, and I use Calibre to convert to AZW3 for the KPW1 (I even go as far as converting Amazon books to EPUB, and then working from there), and would also use the KEPUB plugin to convert to KEPUB.

Second: I am only interested in book statistics: time to read per chapter, per book, and page numbers. I'm not interested in any overall reading statistics, or any online capabilities whatsoever. After registering the reader, any synced books will be deleted, and Wifi will be turned off, probably forever (except if it's needed to accomplish something special).

Third: I will not be hacking or jailbreaking the device.

But it's so much fun

The questions:

1. I'm seeing complaints in reviews that the Kobo readers always have space between paragraphs and no indentation. Is this true? If so, for EPUB, KEPUB, or both?

Kobo do a good job of displaying the epubs as per the code and CSS in the book. If they are coded to have spaces as you describe, they will be displayed that way. The same goes for kepubs but I think Kobo have changed the base CSS used for these so that new kepubs are less likely to look like this.

2. Does the AHD monitor and display Time To Read for the chapter and book for EPUB, or does it only do this for KEPUB? If it's the latter, does it work with Calibre-created, side-loaded KEPUB?

There are two sets of stats. The in-book stats are for purchased kepubs only. These are the ones that have the time for the current and next chapter. The other stats are for all books, but ar just counters of the reading so far.

3. Do the font adjustments (weight, sharpness, etc) work on side-loaded EPUB / KEPUB books?

These work on either type of books when using the supplied fonts.

4. Is the "leave half of the screen blank at random locations"-bug resolved?

I can only think of two things this could mean. One is the widows and orphans, which I consider to be working correctly. The other is a bug in epub rendering where paragraphs that are longer than a screen will start at the top of the next screen. This is still there but is an epub only problem.

5. The Kindle driver is able to send the page numbers calculated by the Count Pages plugin to the Kindle. So, the Kindle displays the same page numbers as Calibre does. I have chosen a custom page count, setting the plugin to count using 2400 characters per page. (This is the average for an English Del Rey Paperback.) Can the Kobo or KoboTouchExtended driver also send the page numbers created by Count Pages to the Kobo, or does the Kobo always use the Adobe algorithm? (In this case, I'd need to recount the page numbers in my library.) Also, is there a difference between EPUB and KEPUB in this regard?

For epubs, Kobo uses the Adobe algorithm. For kepubs, the page count is per chapter and is how many screens there are for the text in the chapter. Changing the font size, changes the number of pages in the chapter.

I can't help with the test as I don't have an Aura HD.

[cybmole]

rather than asking folks to spend hours making your test files, why not just buy a K HD from a store with a good returns policy. take it/send it back if you are not happy.

it took me a couple of frustrating days to master all of the HD fonts/spacing/margins options & to learn how to tweak my epubs to maximise freedom of use of those, but I could not now comfortably go back to an older reader with a poorer display!

for example I both mine ( UK) from W H smith - they have a 14 day returns window.
(and when I bought a original kobo from them when first launched - 3-4 years ago? - they took it back for a full refund even after a couple of months when I complained that it did not charge properly)

[taming]

The only difficulty with testing in the store is that, at least here, the demo models don't ever get updated. That means they have whatever firmware was on the device when they were put on display.

[soulfuldog]

Originally Posted by cybmole

for example I both mine ( UK) from W H smith - they have a 14 day returns window.
(and when I bought a original kobo from them when first launched - 3-4 years ago? - they took it back for a full refund even after a couple of months when I complained that it did not charge properly)

When I was considering buying an Aura one of the reasons I opted for the Paperwhite instead was that the staff I spoke to in WH Smith said they couldn't accept returns of the Aura unless it was faulty. This is because it you would obviously have set it up/registered it etc, therefore it wouldn't be in 're-sellable' condition, and they would have to return it to Kobo.

[cybmole]

Originally Posted by soulfuldog

When I was considering buying an Aura one of the reasons I opted for the Paperwhite instead was that the staff I spoke to in WH Smith said they couldn't accept returns of the Aura unless it was faulty. This is because it you would obviously have set it up/registered it etc, therefore it wouldn't be in 're-sellable' condition, and they would have to return it to Kobo.

i did not use the high st store i used the on-line store & there was absolutely no quibble.

obviously the in-store muppets have not heard of factory reset

+ an advantage of using on-line stores is customer friendly distance selling regulations - more generous returns policy

[arspr]

Originally Posted by davidfor

I can only think of two things this could mean. One is the widows and orphans, which I consider to be working correctly. The other is a bug in epub rendering where paragraphs that are longer than a screen will start at the top of the next screen. This is still there but is an epub only problem.I can only think of two things this could mean. One is the widows and orphans, which I consider to be working correctly. The other is a bug in epub rendering where paragraphs that are longer than a screen will start at the top of the next screen. This is still there but is an epub only problem.

As davidfor says NOPE, it's not fixed... Blame Adobe.

In kepubs, this bug doesn't exist buuuut then neither widows and orphans, nor page-break-whatever, nor @page settings work. Don't ask me why. See this thread. Every other CSS setting works as expected (or I haven't located other unsupported/broken ones).

[Katsunami]

Originally Posted by davidfor

Kobo do a good job of displaying the epubs as per the code and CSS in the book. If they are coded to have spaces as you describe, they will be displayed that way. The same goes for kepubs but I think Kobo have changed the base CSS used for these so that new kepubs are less likely to look like this.

None of my EPUBs have any spacing between paragraphs (except for the intentional <br /> for a scene break), and they are all indented. If they're not, I change it.

So, the Aura HD would respect this, both in EPUB as well as KEPUB?

There are two sets of stats. The in-book stats are for purchased kepubs only. These are the ones that have the time for the current and next chapter. The other stats are for all books, but ar just counters of the reading so far.

I've seen a thread with regard to the reading stats and re-enabling them for sideloaded KEPUBs. This implies that they are now disabled.

Does this mean that reading stats:

- Do NOT work for EPUBs?
- Do NOT work for sideloaded, Calibre-created KEPUBs?

These work on either type of books when using the supplied fonts.

This is still there but is an epub only problem.

Crap.

For epubs, Kobo uses the Adobe algorithm. For kepubs, the page count is per chapter and is how many screens there are for the text in the chapter. Changing the font size, changes the number of pages in the chapter.

So, no "hard setting" the page count of a book, like it's possible on the Kindle, using Count Pages? Pity.

Thanks for the trouble of answering

[Katsunami]

Originally Posted by arspr

As davidfor says NOPE, it's not fixed... Blame Adobe.

In kepubs, this bug doesn't exist buuuut then neither widows and orphans, nor page-break-whatever, nor @page settings work. Don't ask me why. See this thread. Every other CSS setting works as expected (or I haven't located other unsupported/broken ones).

I've been looking at the pictures in this post

Those are all KEPUBs, with the header on top and the footer? Does reading time per chapter and per book work with your side-loaded KEPUBs?

The first and last picture are ridiculous. Talk about screen waste. Bleh. That's a useless book display IMHO.

The second and third look okayish, but they only display 24 lines of text. The Kindle Paperwhite when using Palatino size 3 or 4 (depending on the book) displays 26 to 28 lines of text, on a 6 inch screen.

Do you have any more pictures of the Aura, or are you inclined to take the ones I mentioned in the first post?

=====

At this point in time I have this image of the Aura HD:

1. Book stats (reading time per chapter/book) doesn't work on side-loaded EPUB nor KEPUB.
2. Uploading the page number calculated by Count Pages is not possible.
3. The Aura HD displays less lines per screen, but some more text per line compared to the Kindle PW2; there may not be more text on screen as compared to the Kindle.

Is this correct?

I could live with omitting nr. 1 and 2, but 3. would be a huge dealbreaker. In that case, upgrading to the Aura because of the larger screen is of no use (to me).

[soulfuldog]

Originally Posted by cybmole

+ an advantage of using on-line stores is customer friendly distance selling regulations - more generous returns policy

Yep, this was the only way I'd have bought it having spoken to a couple of people instore (not sure I'd call them muppets mind you!). Easier online returns with Amazon though, which is one of the reasons I went with the PW instead. It put me off trying the Aura a little bit, though perhaps if I'd try to buy the Kindle PW instore somewhere I'd have had the same kind of response.

[jackie_w]

I believe time-to-read type reading stats used to work in sideloaded kepubs up to fw 2.6? or 2.8? but don't work in the current 3.x fw.

As far as fonts are concerned, font thickness and sharpness settings are, by default, restricted to most (not all) of the built-in fonts. In addition:
- if you 'cheat' and name your sideloaded fonts (internally and externally) with one of a few (4 at last count) font names. Then thickness/sharpness adjustment is also available. I wouldn't call this cheat 'hacking'.
- There is also a real hack which does make thickness/sharpness available to all sideloaded fonts. If you're not interested in hacking, fair enough, but don't assume applying a Kobo hack is anything like as complicated as jailbreaking and layering hacks on a Kindle. To a technical guy, such as yourself, it's done in a couple of minutes (maybe a bit longer the first 'nervous' time).

Finally, also be aware that a correct Kobo answer today may be an incorrect Kobo answer next week, and vice versa, if there's a firmware upgrade in the middle

[Katsunami]

Originally Posted by jackie_w

I believe time-to-read type reading stats used to work in sideloaded kepubs up to fw 2.6? or 2.8? but don't work in the current 3.x fw.

Meh. It works on the KPW1, with AZW3/MOBI files created by either Calibre or Kindlegen. If it worked with 2.x and not with 3.x firmwares, I suspect that Kobo doesn't care about side-loaded books and so doesn't care if this feature is broken on non-Kobo books.

As far as fonts are concerned, font thickness and sharpness settings are, by default, restricted to most (not all) of the built-in fonts. In addition:
- if you 'cheat' and name your sideloaded fonts (internally and externally) with one of a few (4 at last count) font names. Then thickness/sharpness adjustment is also available. I wouldn't call this cheat 'hacking'.
- There is also a real hack which does make thickness/sharpness available to all sideloaded fonts. If you're not interested in hacking, fair enough, but don't assume applying a Kobo hack is anything like as complicated as jailbreaking and layering hacks on a Kindle. To a technical guy, such as yourself, it's done in a couple of minutes (maybe a bit longer the first 'nervous' time).

I just don't want to hack the thing and (possibly) het into trouble updating later on. Just BECAUSE Kobo updates the firmware that often, I don't want to hack it, lest I would have to miss out on important bugfixes.

Finally, also be aware that a correct Kobo answer today may be an incorrect Kobo answer next week, and vice versa, if there's a firmware upgrade in the middle

So it is still the case that you are bug-swapping over here; fix one bug, get another one in return, or see an old already fixed bug turn up again?

That's... not funny.

Thanks for answering.

I have a feeling that I'm going to stick to my Kindle and suck it up with regard to the small font selection, and just hope that there will be a larger Kindle and/or a newer one with more fonts, at some point.

(Yes, I know, USE_ALT_FONTS enables extra fonts, but only on the KPW1, and if I REALLY want to, I can just embed the wanted font into the book during the AZW3 conversion. Many fonts don't work well on the KPW however: way too thin.)

The only thing I'd like to have, from the KPW2, is the permanent page number display on the bottom line; but maybe, that feature will be backported one day.

[jackie_w]

Originally Posted by Katsunami

So it is still the case that you are bug-swapping over here; fix one bug, get another one in return, or see an old already fixed bug turn up again?
That's... not funny.

That's not really what I meant. It's not necessarily bugs that come and go. Sometimes they are deliberate decisions by Kobo.

For instance, I believe it was stated at the time, that the time-to-read stats were removed from sideloaded kepubs because they were inaccurate. Conspiracy or fact - I don't know (or much care, because personally, I have no use for them).

[Katsunami]

Originally Posted by jackie_w

That's not really what I meant. It's not necessarily bugs that come and go. Sometimes they are deliberate decisions by Kobo.

For instance, I believe it was stated at the time, that the time-to-read stats were removed from sideloaded kepubs because they were inaccurate. Conspiracy or fact - I don't know (or much care, because personally, I have no use for them).

Hm, ok. LOL. It's not that difficult to calculate.

Screen swaps = (Nr. of chars to end of book or paragraph) / (Nr. of chars on screen with current settings)

And one can obviously measure the time it takes the user to swap the screen (average it over 5-10 swaps or so).

Screen swap * time per screen = time needed to end the chapter.

Maybe I should e-mail this algorithm to Kobo

(The Kindle calculates this in a different way, because it does NOT change the number of pages when changing font settings, and it does not need to recalculate if you make the font bigger or smaller; so it does not use screen swaps to calculte.)

[jandrew]

Here are the pics you requested - note, the supplied kepub didn't want to work, so I generated one from the epub via calibe. (epub then kepub):