View Single Post
Old 11-10-2013, 07:46 AM   #775
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Quote:
Originally Posted by jshzh View Post
Based on my rudimentary experience with Koreader, I'd like to suggest three functions the developers may want to consider adding to pdf/djvu (not re-flowed) part of the project. I apologize if they are already available in the current release or others have brought these up before.

1)One extra line from the last screen page in pdf/djvu. Very often, an original page of a book is divided into three parts for landscape mode and the last line of the current screen (same as the first line of the next) may be split in the middle. The result is this line can't be easily read either on the current screen page nor the next screen page. It is necessary for the last split line to get displayed in full in the next screen page.

2)Demarcation that indicates where the last screen page ends in pdf/djvu files. This is very much needed for the last screen section of the original page because there are usually only a few lines remaining to be shown but since the last portion of the original page is so shorter that many lines from the previous screen page are shown on top of the new lines. One has to go through this last screen page and figure out where the few unread lines begin. It would to be of great help to have a dividing line that indicates where the last screen page ends.

3)It would be more convenient if the "fit the width" option become more "sensitive". Pdf and djvu files often contain pages in which the content doesn't lie in the middle. It makes things worse that the left and right margins are often not the same on odd and even pages. For instance, on odd pages the left margin is 1" and right 1.5" while on even pages left 1.5" and right 1", or vice versa. Using the manual cutting option will end up leaving blank space either on the left or right in order for every page to be complete. The auto and semi-auto margin cutting in Koreader - I might be wrong - couldn't fit the width to the maximum possible. That makes the slightly larger screen of Aura HD pointless and text on smaller screens less readable. I think the zoom (fit the width) /edge cutting functions can be optimized. The old Pocketbook software seems to be able to detect the difference in margins and always fit the real content width after the percentage of zoom or "fit width" is set.

Thank you again for the great work done in this project.
Suggested solutions:
1) (no problem in scroll mode) In page mode you need to turn on the "DSHOWOVERLAP" option in defaults.lua by changing line 35 into
Code:
DSHOWOVERLAP = true
2) (no problem in scroll mode) Same as in 1).

3) Manual cropping will remember cropping box for odd page number and even page number so you only need to define page boxes for two pages(an odd page and an even page) if the content boxes are regular in all pages. If not, auto/semi-auto page cropping will be useful to automatically crop the white margins. In auto/semi-auto cropping mode additional page margins are added around calculated content area. Fortunately the additional margin sizes are totally customizable in koreader although its not accessible in the graphic user interface. You can edit the line 64 of "frontend/ui/data/koptoptions.lua" and change
Code:
values = {0.05, 0.10, 0.15},
into comfortable values. And you may also need to change the default page margin at around line 47 in defaults.lua. To make edited options take effect in previously opened books, you need to select corresponding options in the bottom configuration panel at least once.

Last edited by chrox; 11-10-2013 at 07:53 AM.
chrox is offline   Reply With Quote