Koreader running on Kobos (all of them, hopefully!)

[embryo]

Originally Posted by WS64

Actually I think we should open the filemanager at least for images (and of course, display them when clicked).
This way we for sure have an exit for people who accidently did not wait for Nickel to process koreader.png

I did try to open a .png image, but Koreader could not open it.
The 'delete' option worked though.

[WS64]

Yes, funny enough it can open jpg (this is even activated in filemanager by default). But the same routine can't handle png it seems. For the screensaver it doees not matter though, it can handle both, not sure why png does not work here.

[Ken Maltby]

Originally Posted by WS64

Yes, funny enough it can open jpg (this is even activated in filemanager by default). But the same routine can't handle png it seems. For the screensaver it doees not matter though, it can handle both, not sure why png does not work here.

Perhaps it is related to the lib that the new image display method uses? Have all the routines that display images been updated to use the new "showpic" or whatever it is called? Some older routines might still be using Pickel or writing directly to the frame buffer? Just thought that might explain the difference.

Luck;
Ken

[WS64]

I don't know, but Koreader can display png and jpg (and tiff says the code, but I havn't tested it)...
Within epubs it can also display gif (but buggy).

(btw, next version will support cover image of actual epub as screensaver. png and jpg)

[Ken Maltby]

Originally Posted by WS64

I don't know, but Koreader can display png and jpg (and tiff says the code, but I havn't tested it)...
Within epubs it can also display gif (but buggy).

(btw, next version will support cover image of actual epub as screensaver. png and jpg)

Right, I just saw that at GH, I was wondering if all the corrections made it into the 618 version? It looked like you and Chrox had it worked out but I am not sure if the timing would allow it to be in the 618 download.

You are really making some major improvements, at a remarkable pace.

Luck;
Ken

[WS64]

No idea about 618, but if you want to have everything that is already "pulled" you can just download the master from https://github.com/koreader/koreader/archive/master.zip and replace the directories that also exist on your Kobo. Make a backup first in case something goes wrong!

[Ken Maltby]

Originally Posted by WS64

No idea about 618, but if you want to have everything that is already "pulled" you can just download the master from https://github.com/koreader/koreader/archive/master.zip and replace the directories that also exist on your Kobo. Make a backup first in case something goes wrong!

I'll keep that in mind. 618 has the cover screensaver and it looks great. It makes me wonder though, if I could set your cracked image as a default if there is not a good cover image? Maybe a setting to have it override a poor cover image?

Luck;
Ken

[WS64]

That is the default actually.
First it tries to get the cover from the book (if you have it set up like that), then it looks for your custom picture (if you have it set up like that), then it displays "suspend".
You should check if you get different pictures for different books, best to test on search and a long tap on the results. But you can also see it by looking into koreader/temp. If you see an epub directory you are not up to date, if you see something like #mnt#sd#path#book.epub.jpg (a few of them maybe) everything is fine. This directory also holds the metadata.koreader file.

Oh, I overread the word "poor"... What I wrote is the case for "no cover image found"

[Ken Maltby]

Originally Posted by WS64

That is the default actually.
First it tries to get the cover from the book (if you have it set up like that), then it looks for your custom picture (if you have it set up like that), then it displays "suspend".
You should check if you get different pictures for different books, best to test on search and a long tap on the results. But you can also see it by looking into koreader/temp. If you see an epub directory you are not up to date, if you see something like #mnt#sd#path#book.epub.jpg (a few of them maybe) everything is fine. This directory also holds the metadata.koreader file.

Oh, I overread the word "poor"... What I wrote is the case for "no cover image found"

I tried a pdf and going to suspend just crashed me out to the Start Menu. Tried a .txt file with no cover at all, and it also dropped me back to the Start Menu. PDB files crashed also. All the .epub that that I tried worked fine.

Luck;
Ken

[WS64]

Can't reproduce that, when I use pdf or anything not epub it shows me the default cover. What does crash.log say?

[embryo]

Originally Posted by Ken Maltby

I tried a pdf and going to suspend just crashed me out to the Start Menu.

With version 620, pdf files use the custom cover.

@developers
A question about OTA updates now.

Up until recently, every time I was trying the OTA option, after the selection of "OK do the update" question, a brief message was displayed and then nothing happened.
At least visibly, because Koreader had always create a koreader.installed.tar file inside the OTA directory.

Some versions before, after successfully starting up the wifi connection all by itself, it looked that it was downloading something, but after a while the the "..will take some time" message disappeared and nothing again.
Sometimes it also freezes.
Inside the OTA folder now there is the koreader.installed.tar file again, and also a koreader.updated.tar.part file with roughly the same size.

What is to be expected?
What are the steps of OTA update?

[gontofe]

So I had this earlier, it downloaded the part update and nothing more. However, I switched to ak-team and everything worked.

You should see the zsync file in the ota directory (downloaded from ota server) and the installed tar (built locally) when ota starts. Then Koreader uses zsync and package index to determine delta to download (and builds updated.tar). Once download has completed successfully you should see a message saying Koreader will be updated after restart (and you will indeed see the new version after restart).

[ywq111]

How to Use the font fallbacks ?
I want to display tibetan and chinese char together in epub page. I have put one tibet font file "himalaya.ttf" in ".kobo/koreader/fonts/tibetfont" path ,
and then edit the file ".kobo/koreader/frontend/ui/font.lua",
and set the fallbacks like this below:
fallbacks = {
[1] ="droid/DroidSansFallback.ttf",
[2] = "noto/NotoSans-Regular.ttf",
[3] = "droid/DroidSans.ttf",
[4] = "tibetfont/himalaya.ttf", },
but it can not to display tibetan char .
Can any one help me ?

[chrox]

Originally Posted by ywq111

How to Use the font fallbacks ?
I want to display tibetan and chinese char together in epub page. I have put one tibet font file "himalaya.ttf" in ".kobo/koreader/fonts/tibetfont" path ,
and then edit the file ".kobo/koreader/frontend/ui/font.lua",
and set the fallbacks like this below:
fallbacks = {
[1] ="droid/DroidSansFallback.ttf",
[2] = "noto/NotoSans-Regular.ttf",
[3] = "droid/DroidSans.ttf",
[4] = "tibetfont/himalaya.ttf", },
but it can not to display tibetan char .
Can any one help me ?

This fallback is for the UI only, if there is no Tibeten translation of Koreader it will be of no use. EPUB document has a fallback font of "Droid Sans Fallback" which can display Chinese chars you only need to select "Tibetfont" on the "Choose font" menu entry. If it does not help, you may need to disable embedded style of your EPUB document.

[embryo]

Originally Posted by embryo

Some versions before, after successfully starting up the wifi connection all by itself, it looked that it was downloading something, but after a while the the "..will take some time" message disappeared and nothing again.
Sometimes it also freezes.
Inside the OTA folder now there is the koreader.installed.tar file again, and also a koreader.updated.tar.part file with roughly the same size.

With versions 630 - 634 I get a message saying that after a restart Koreader will be updated, and I also get an extra koreader.updated.tar file inside the OTA folder, with the same size as the other two.
After the restart I have the original (not updated) version.
I change the servers but I got identical results.