Firmware 2.8.1 ?

[DNSB]

Originally Posted by TechniSol

BWinmill,

If this were a legal forum, I'd say you're ultimately correct based on local laws, federal laws,jurisdiction, etc., but this isn't "The Paperchase", Professor Kingsley is pushing up daisies, and the forum was not hosting the files, only allowing a link to be posted. If I'm not mistaken links are still perfectly legal.

And how many sites for which the defense was that "we don't post files only the links to them" have been shut down? It appears the weight of precedent is coming down on the side that posting a link to illegal content is the same as hosting illegal content.

Regards,
David

[speakingtohe]

Have we all run out of nits to pick

Helen

[DNSB]

Originally Posted by speakingtohe

Have we all run out of nits to pick

Helen

Not for decades yet.

Regards,
David

[byblo]

Originally Posted by byblo

is the long paragraph bug and returning to sleep mode after opening the cover when no page turn fixed?

- To answer to myself, long paragraph bug still there. Returning to sleeping mode bug still there too.

Some others remaining problems:
- Opening a new (unread yet) epub still opening it to its first TOC entrie, instead of opening the book to page 1, like kepub...
- The sort by series still not offered.
- when coming back from a book's detail, the shelves position is reseted to page 1...


Some interesting changes, the virtual keyboard, some little shelves changes, simplified theme (no more rounded buttons, just colored rectangles)


This update seems to be mainly cosmetic, almost no bug fixes.

Bah...

[HansTWN]

Originally Posted by byblo

- To answer to myself, long paragraph bug still there. Returning to sleeping mode bug still there too.

Some others remaining problems:
- Opening a new (unread yet) epub still opening it to its first TOC entrie, instead of opening the book to page 1, like kepub...
- The sort by series still not offered.
- when coming back from a book's detail, the shelves position is reseted to page 1...


Some interesting changes, the virtual keyboard, some little shelves changes, simplified theme (no more rounded buttons, just colored rectangles)


This update seems to be mainly cosmetic, almost no bug fixes.

Bah...

"Returning to sleeping mode" is no bug but protection against accidental turning on of the device. The sleep cover can easily open a little when in a bag or so -- you wouldn't want the device to turn on for 15 minutes each time?

[GeoffR]

Add

Originally Posted by byblo

- Opening a new (unread yet) epub still opening it to its first TOC entrie, instead of opening the book to page 1, like kepub...

It opens epubs at the page the book tells it to. If that is the wrong page then complain to the publisher, or you can edit the book to open at the page you want.

- when coming back from a book's detail, the shelves position is reseted to page 1...

I just tried this and it doesn't happen on my Glo. Closing the book's details page returns the view to the same position in the library I was before I opened the details page.


The top margin in ePubs has gone completely. Now I will have to go through my library in Calibre and add back the @page{margin-top:10pt} that I removed after upgrading to 2.5.2. I don't really mind whether the margin is there or not (since I can add it myself if it is missing), but I hope they they will make up their mind and stop changing it.

Edit: Actually there is a very small side and top margin, it is not quite zero. Picture attached of my Glo with margin slider at minimum. (ePub, 2.8.1)

[davidfor]

Originally Posted by GeoffR

The top margin in ePubs has gone completely. Now I will have to go through my library in Calibre and add back the @page{margin-top:10pt} that I removed after upgrading to 2.5.2. I don't really mind whether the margin is there or not (since I can add it myself if it is missing), but I hope they they will make up their mind and stop changing it.

You know they are listening? I think you just put us in for another change in 2.8.2 or 2.9.0 or whatever it gets called

[DNSB]

Originally Posted by byblo

- To answer to myself, long paragraph bug still there. Returning to sleeping mode bug still there too.

Some others remaining problems:
- Opening a new (unread yet) epub still opening it to its first TOC entrie, instead of opening the book to page 1, like kepub...
- The sort by series still not offered.
- when coming back from a book's detail, the shelves position is reseted to page 1

Long paragraph bug? Somehow, I suspect that Kobo won't get that fixed until they replace the Adobe Reader Mobile SDK code.

The return to sleep mode is not a bug in my opinion. It is by design so that if your sleep cover flops open in your bag, the ereader doesn't wake up for 15 minutes. When the quick return to sleep happened when you weren't using a sleep cover -- that was what more people called a bug though I classified it as a dubious feature.

You call opening at the first TOC entry a bug, I call it a feature. You may enjoy paging forward past the cover, copyright info, author's book list, acknowledgements, dedication, and Great Ghu alone knows what else. I've got ebooks that have 18 pages which take 50 or page turns to get by before getting into the meat of the book.

Sort by series would be nice. OTOH, you can search for a series. John Ringo's Looking Glass series, using look as the search string. David Weber's Bahzell series, bahz finds those. Gail Carriger's Parasol Protectorate series, para finds those. Lois McMaster Bujold's Vorkosigan series? vork find those. Mercedes Lackey's 500 Kingdom series? 500 finds those. They do come up sorted by title but that's really only an issue with series such as the Grantville Gazette which is up to 48 volumes or David Weber's Honor Harrington universe which is hitting up to 26 books.

Shelves? Never use them.

Regards,
David

[byblo]

Originally Posted by GeoffR

Add
It opens epubs at the page the book tells it to. If that is the wrong page then complain to the publisher, or you can edit the book to open at the page you want.

Then why kepub behavior is not the same ? No published on kobo store ? :s

I don't mind to call it a bug or feature.

Whatever it is, it should be optional at least. When I open a book, I like to read who translated the book, when it was published the first time, to read the dedicace, the author's introduction, the author's notes, and so on...

Its irritating to have each time to popup the bottom menu, then page icon, then arrow, then close the thing, just to start it from the beginning of the book...


Also, talking about something else, the French dictionary still unavailable to use (not the only one, Deutch, Japanese, ...), which is completely a dumb, egoistic and mediocre choice from the dictionary's publishers, since sometimes I cannot even know properly what a word is...

For instance, in a book I read the unknown word: "blabla", then click the word for definition, the dictionary opens, and gives me: "blabla: related to blablating"
Thanks, but I still don't know what blabla or blablating means !!!

And of course, theres no links inside the dictionary popup, which could jump from a definition to another by clicking the words.

Nice way to reduce an useful feature. Its like they doing it on purpose to disappoint people the most they can.

Also, I almost forgot the inability to change the font if the ebook specified one. Why giving the options if its to restrict it ? I remember in old firmware pictures there was a check box in the fonts option, something called "Kobo Style" or something like that. Was it an option to force fonts choices? Or what was the purpose of it ?

[Lucas Malor]

@byblo: have you installed the dictionary from the Kobo Desktop application or using the wifi?

[DNSB]

Originally Posted by byblo

Then why kepub behavior is not the same ? No published on kobo store ? :s

Epubs are rendered using Adobe's Reader Mobile SDK code. Kepub.epubs are rendered using ACCESS's NetFront BookReader code. The ACCESS renderer is able to handle a fair chunk of HTML5 and EPUB3 but does not handle Adobe's ADEPT DRM so the Adobe code is still needed to borrow books from your local library or to read a downloaded Adobe DRM ebook. More information on ACCESS is available on their website and also on the Readium website.

http://gl.access-company.com/products/dpub/bookreader/

Originally Posted by byblo

I don't mind to call it a bug or feature.

Whatever it is, it should be optional at least. When I open a book, I like to read who translated the book, when it was published the first time, to read the dedicace, the author's introduction, the author's notes, and so on...

Its irritating to have each time to popup the bottom menu, then page icon, then arrow, then close the thing, just to start it from the beginning of the book...

If your ebooks are editable, use Sigil to put an entry for the cover page in the toc.ncx. As for optional? I can't see them changing a behaviour that was in the original Kobo (the non-touch, non-WiFi) ereader when they are looking towards the future. Check Datalogics page for information on their epub3 support. Datalogics is currently supporting the Adobe Reader Mobile SDK and their path to the future seems to be waiting for the Readium project and then grafting the Adobe DRM code onto it.

Originally Posted by byblo

Also, I almost forgot the inability to change the font if the ebook specified one. Why giving the options if its to restrict it ? I remember in old firmware pictures there was a check box in the fonts option, something called "Kobo Style" or something like that. Was it an option to force fonts choices? Or what was the purpose of it ?

I don't notice an inability to change fonts when reading an ebook but then I strip embedded fonts just to save space (and that I find a lot of the font choices to be crap on an eInk display). "Kobo Style" seemed to be tied to some Javascript embedded in older .kepub.epub books. That code seems to be gone leaving a zero length placeholder behind.

Regards,
David

[GeoffR]

Originally Posted by byblo

Then why kepub behavior is not the same ? No published on kobo store ? :s

kEpubs contain all sorts of changes from the original epub, many have changes the paragraph stye from indented-with-no-margin to non-indented-with-margins for example.

In the original ePub book there is often a line in the guide section of the content.opf file that specifies which page to open at. It is a deliberate choice by the publisher to open the book at that page, so I think devices which ignore that guide are the ones with the bug.

I do agree it would be nice if there was a setting on the device that allowed you to choose whether to follow the book's guide or not.

[Leonatus]

Originally Posted by davidfor

I'm not sure what ini file you are talking about. The file gets unpacked into a partition on the device that you can't access. There are configuration files and a database, but they should be there already.

I mean this:

Originally Posted by KevinShort

From the first post, here's the syntax for kobotweaks.ini:

[CustomCommands]
Reboot=tweaks.executeSystemCmd(\"busybox reboot\")

That is, if I remember right, the way to customize the plugin. Only that I have difficulties in recollecting how the procedure was in detail.

[Leonatus]

Originally Posted by Lucas Malor

A virus for Linux? A voodoo curse is more probable.

Who do that vodoo that you do so well? (from "Mash").

Have you tried to reset Kobo completely (you have to long press the light button and turn on the Kobo if I remember well) (and if I remember well this removes ALL the contents from your Kobo, books included)

Your proposal is an option. But at present, I'm glad to see the device working; and perhaps there will soon come another upgrade (see the present thread).

[ewphoenix123]

Originally Posted by Haesslich

Is it just me, or does it seem faster now at rendering pages after page turns? Not that the Aura was slow before, but it seemed to take a heartbeat longer to redraw text before 2.8.1.

It took a while after the download to finish installing (as if it was doing a full system image update versus a delta upgrade), but it seems to be heads and shoulders above 2.5.1 in terms of responsiveness for me.

It's quite possible.
In 2.6.1 they updated a lot of driver and renderer components to it's latest version and removed outdated codefragments.