Quote:
Originally Posted by AnthonyPaulO
Hi!
Yes, during my tests I had already given thought to the aspect ratio but that's definitely not it since the small border exists all around, not just either vertically or horizontally... had it been the aspect ratio then it would have used up all the remaining space for either the vertical or horizontal edges, see what I mean? It was interesting to see my Kindle 2 go into sleep mode, it displays a picture on the screen and even that picture had a small white border around it so I *believe* that's hard-wired, but I wanted to make sure.
|
It may well be a hard-coded margin or else maybe the max screen size is being displayed and THEN the hard-coded margin kicks in...
Quote:
|
Regarding landscape mode, personally I prefer not to chop the page in half, I want to be able to see the full page all at once, and as long as I can get rid of as much margins as possible I think it's pretty readable for me. Landscape would mean that things would get chopped in half, including sentences.
|
If it works in portrait mode, then go with that. You really don't split sentences in landscape mode since there usually is some overlap between pages to allow you to continue with the non-sliced sentences on the next page.
Quote:
|
Regarding the max res, you may be right, I was simply going by their official specs. I can email you the PDF and .prc file if you like... I'll see if I can get your email from your profile when I get out of this editor.
|
I'll check it out for you once I receive them.
Quote:
I just tested by removing the 600x800 override, no difference.
 But as I'm typing this, something funny just happened... I was converting a full PDF using the settings I posted (654 pages) and something weird happened... the dos process finished and windows explorer opened up to the temp page holding all the png files (is it supposed to do this? How come this never happened before). Being curious I looked through the png's and they are perfect, I mean not a single white border to be found, they are all shaved to the bone. This means something's definitely up, if the png images are perfect then either the process that's packaging these png's into .prc is adding a border or the kindle has a built-in border of its own. Anyway, I close out of this temp folder I realize that the output file isn't there. That's two weird things in a row, I've spent the past 6 hours testing and this hasn't happened before. Fishy!
|
That happens by design when the creation of the .prc fails. Perhaps it couldn't write to a file that was write-protected or opened by you somehow. Anyways, this can also be forced to occur even with a successful build if you place a file called "debug" in the PDFRead install directory. Good for debugging/investigation purposes!!!
Quote:
Also, I've noticed an artifact... on my Kindle reader, there seems to be a blank page inserted here and there in places where there's no blank pages. I checked the generated png's and they're fine, no blank pages there so either it's something in the .prc generation or it's a Kindle bug.
Regards,
Anthony
|
Sometimes, a perfectly normal image created from the pdf page becomes "lost" when converted to .png. I've seen this
happen before and don't know what's causing it. Another reason this may happen is when the size of the image is too tall and thus forces a pagebreak, but maybe not. If you can reproduce it with different settings, then it may be more evident which type of error it is. Report back here with some "insights" if you can.
Did you try any other interesting 'unpaper' options?