Thread: Kobo Firmware 2.6.1
View Single Post
Old 06-12-2013, 12:21 PM   #369
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,141
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Lily7 View Post
I have been trying to keep up with this thread in order to stay well informed but it is quite honestly information overload. My comprehension is not very sharp today, so I hope someone doesn't mind answering a couple of questions:

1. Is the current epub format about to go obsolete? I don't understand this epub2 vs epub3 and ACCESS renderer stuff. WAY over my head. I guess I just want some reassurance that I haven't built up a huge collection of epub ebooks only to have their formats go obsolete!
Epub3 is basically a superset of epub2. If you read an epub2 book on an epub3 device, you should see very few differences and most of those are the differences you would see reading an epub2 ebook using multiple epub2 renderers. The Kobo ereaders use two different renderers, one is the Adobe Reader Mobile used for epub2. My opinion, for what it is worth, is that the ARM renderer is there only to continue support for Adobe ADEPT DRMed epubs. The ACCESS Netfront BookReader is a (mostly) epub3 compliant renderer used to read Kobo's .kepub.epub ebooks. If you rename a .epub file to .kepub.epub, it will be rendered by the ACCESS renderer. There seem to be few differences in the actual text display. You do need to add an epub3 extension to properly identify the cover image.

Quote:
Originally Posted by Lily7 View Post
2. This latest FW release, again information overload. I read the gist of the pros and cons and bugs that have been posted but so far all I've gleaned is that there is a space at the top that most don't like. Are there any common major usability problems with this release? I can't decide whether or not to upgrade from 2.5.1, which has been my favorite release and the one I consider most stable so far. Help?
The 2.5.2 firmware update added a top bar with the book title similar to what is seen when reading .kepub.epub ebooks. This caused a large number of complaints in this forum. 2.6.1 removed the title but did leave about a 5mm wide top margin compared to the 3mm top margin seen with 2.5.1. There is an issue with .png cover images which I consider to be a more serious issue than that loss of 2 mm on the top of a page. So updating is your choice but I don't consider updating from 2.5.1 to 2.6.1 to be an critical update.

Regards,
David
DNSB is offline   Reply With Quote