Librerator - multi-format e-reader, fork of KPV

[Kai771]

@corrin18

Thank you very much for your report. I wasn't fast enough to see the link before the moderator removed it, but even if I did, I wouldn't be able to help you. I didn't change anything regarding the reflow mode (as far as I know). The latest KPV is newer than Librerator-R2, so if KPV behaves better (faster) with the PDF in question, that's probably because it uses newer version of k2pdfopt library. If I publish a new release of Librerator, I'll try incorporating the newest libraries at the time. But don't hold your breath. Except for some very rare cases, I think the version that shipped with R2 works quite good.

Regards,
Kai

[troyme]

Is there anyway to add some blank margin to the fit content mod ????
under the fit content mod ,the text is too close the the edge of the screen.

[Kai771]

@troyme

I suggest you manually set BBox first, and then use fit-to-content-width mode. You might find this page helpful:
https://github.com/kai771/kindlepdfv...User%27s-Guide

Regards,
Kai

[dider]

Hi again!
I'm really enjoying Librerator, but unfortunately I have to report quite a major bug.

Kindle 4NT crashes (restarts) while using PDF Reflow on some specific pdf files. It doesn't happen while reading a proper, simple structured pdf book.

It does happen while reading pdf files created with Send to Kindle extension (for Chrome in my case). This addon transforms a web page (an article, for example) into pdf file, which then often contains pictures and looks very patchworky. These files load fine, but crash when you turn the page several times. Kindle then goes straight into this screen:



Then it goes to the Kindle starting screen and it loads the list of books. Then when I try to use the pad to select any book from the Kindle's list, it instantly switches to the last page I was viewing in Librerator (I thought Librerator is killed during the restart, but it appears it's loaded in the background).

I attached a sample file that crashes my Kindle (this article can be accessed by anyone, it's not behind any paywall)

I know that this file looks horrible and I honestly didn't expect being able to read it, but I wonder if this happens on every Kindle. Cheers!

[Kai771]

@dider

Hi dider,

Thank you for your report. I downloaded the file that you attached and tried it out on my K3. I opened it in reflow mode, default options. It doesn't crash on K3. I was able to go through all the pages and back. But, it takes 10s or so to render a page. Also, pressing Alt-Back does cause a crash (it should just close the file, and go back to FileChooser). It goes back to Kindle software, but doesn't refresh the screen. Alt-G fixes that, but the title bar is not updated anymore. To get it back, you need to start Librerator again, and exit normally.

So, no framework restart on K3. There's definitely some problem there, but it's highly unlikely to be fixed by me. Sorry. I neither have K4NT nor time. I also lack motivation . The file you attached can comfortably be read manually setting bbox and using fit-to-content-width mode.

For improvements in Reflow mode, wait for koreader to add support for K4NT. Users of K2/KDX/K3 may have more luck with the newest version of KPV, because it uses newer libraries than Librerator-R2.

Regards,
Kai

[twobob]

Ill test on a k4 in the morrow while running SSH. looks like the memory cap is being tripped.

(That is WAY Johnny Mnemonic / Total Recall..)

[knc1]

Originally Posted by twobob

Ill test on a k4 in the morrow while running SSH. looks like the memory cap is being tripped.

(That is WAY Johnny Mnemonic / Total Recall..)

A lot of the application is Lua -
Lua's garbage collector can be "fine tuned" to do a better job in small memory devices than its stock settings.

Might have a look at those settings in the application.

[twobob]

I could dig around...

*goes back to bed*

[hawhill]

While the garbage collection could be tuned, I don't think it would help. The actual rendering of the PDF seems to be the culprit, and that is part of the (C language) dependent library MuPDF. Some corner cases will probably always trigger a high memory usage, seems to be one of them.

Some day (TM) I hope I have the time to make the rendering backends work in subprocesses that can be better controlled in terms of memory usage. A bit like the Chrome/-ium browser does.

[knc1]

Originally Posted by hawhill

While the garbage collection could be tuned, I don't think it would help. The actual rendering of the PDF seems to be the culprit, and that is part of the (C language) dependent library MuPDF. Some corner cases will probably always trigger a high memory usage, seems to be one of them.

I know your using LuaJIT, but it should have maintained compatibility with the standard lauconf.h (one can hope anyway).

LUAI_GCPAUSE is set at 200 out-of-the box - -
redefine as: 110, re-build.

From: Lua Programming Gems, chapter 26

Give that a try - it may leave enough memory room for the C backends to work.

[troyme]

Thanks, it's working !!!!!

I love your app !!!

Originally Posted by Kai771

@troyme

I suggest you manually set BBox first, and then use fit-to-content-width mode. You might find this page helpful:
https://github.com/kai771/kindlepdfv...User%27s-Guide

Regards,
Kai

[dider]

Originally Posted by Kai771

@dider
The file you attached can comfortably be read manually setting bbox and using fit-to-content-width mode.

This whole bbox thing sounded like Latin to me. And then I read troyme's post and followed the link.

Many pdf files don’t have defined bounding box (bbox), or they have it defined incorrectly, so it’s best to define it manually. Since first page is usually the cover, and the few pages after are table of contents etc, navigate to the page with normal text using next page/previous page buttons first, and then:

Press Shift-X, or select Menu/Settings/Manually set BBox. A dialog saying “top left bbox” will appear. Press fiveway right and down, and you’ll see a crosshairs. You can change the step of moving them pressing Q for large, A for normal and Z for small on K3/KDX, and ScreenKB for small, Menu for normal and Home for large on K4NT.
Move the crosshairs to the top left corner of the area you want selected. Press fiveway center.
Do the same for the bottom right corner. When you press fiveway center, your selection will blink.
[4]. Many books have different margins for odd and even pages. In the previous step, you set BBox for one of them - it said which one in the “top left bbox” dialog. Press next page button, and repeat what you did in the previous step.

[5]. Navigate back to the page you want to start reading from, and then choose Menu/Zoom & Rotate/Fit-to-content-width (or press “S”) if it’s a one-column text. If it’s a two-column text, select Menu/Zoom & Rotate/2-column mode (or press “F”) instead.

I've just tried it. This is absolutely amazing. I never knew I could do that in Librerator.

[mosiclover]

I couldn't install Librerator on my Kindle 3 wifi, firmware 3.4.
When I copy all files from Librerator to customupdates directory:
1. press Shift - Shift - I: success
2. press Shift - Shift - Space: success
3. press Shift - L - L: nothing happened

Please help me!!!

[rashi]

Thank you very much, installed Librerator and it works like a charm for my math books. It was my first Kindle modification, too - yay!

[Kai771]

Originally Posted by mosiclover

I couldn't install Librerator on my Kindle 3 wifi, firmware 3.4.
When I copy all files from Librerator to customupdates directory:
1. press Shift - Shift - I: success
2. press Shift - Shift - Space: success
3. press Shift - L - L: nothing happened

Please help me!!!

You need to copy the file librerator-R2.zip to customupdates directory, not the files that the archive contains. Then, pressing Shift-Shift-I will unpack the archive and copy the files to the right places.

Regards,
Kai