Thread: DPI to use when scanning images
View Single Post
Old 07-28-2014, 01:32 PM   #8
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by u238110 View Post
No, I'm going to be custom scanning all the images of the book. And I want the scan output to be the final size. I don't want to compromise the integrity of my images by interpolating them. So, what's your idea about an ideal plain/standard DPI setting for old-fashioned images? 189, 213, etc....
Hmmm perhaps GrannyGrump would be able to give you more info on that one, I know that she works on cleaning up a lot of public domain images.

Although probably all of the advice is, scan images in as high of a DPI as your device can handle. THEN downscale to what is needed as the output.

When higher resolution devices come out in the future, this will allow you to create a higher resolution image from the source.

Always better to go high resolution and downscale, than trying to do the opposite.

300+ DPI for text. Probably something like 600+ DPI for images.

I mean, if you are going to be scanning, you want to get it done right THE FIRST TIME.

Quote:
Originally Posted by u238110 View Post
Totally agree with you about tables. E-readers need to improve. A simple side-scrolling feature would take care of the issue, would it not?
Heh, never going to happen. (At least I don't see it happening in the current generation of ebook formats). :P

And you have to keep in mind the MILLIONS of ereaders out there that don't have that functionality.

And then you have to keep in mind people making the FONT SIZE HUGE, and breaking/overflowing even the most basic of HTML tables.

It is one of the reasons why when we convert to ebooks, we try to "verticalize" the tables. An informal rule that gets passed around is try not to go past "4 column" tables. There is much more vertical real estate than horizontal on ebook readers.

There are SVG Tables as well. MikeWV brought it up recently, and there was some discussion/examples:

https://www.mobileread.com/forums/sho...d.php?t=240980

Now, while that SVG is vector, and DOES look nice (and can scale to fit the entire screen). While theoretically, this would be WAY better than either HTML or bitmap images... sadly, the documentation/support in ereaders is crappy. (I am also not too sure how accessible it is, or how well Text-to-Speech software would handle it).

It would also require a massive amount of testing on a multitude of different devices. For example, as MikeWV figured it out, turns out that Kobo had some weird bug with rendering the fonts in his SVG.
Tex2002ans is offline   Reply With Quote