History:
My conventional usage of this program is for reading e-books, producing the image files that copied into an MP4 player's photo or image folder you can read using the photo/image viewer. That is why all default options were wrote to fit ok into a sansa's fuze player.
All camed from my interest in reading Gutenberg Project's books without paper (too disturbing passing pages), money (I'm an occasional reader, I don't have money, so I don't need an e-book reader) and weight (my hands are lazy enough to hold a book long time resting at bed, and reading incorporated was not made for me, between other things).
The initial idea was coding a txt file viewer for fuze's rockbox driver, sounds good, but very complicated to my knowledge.
But some time later I, with some pleasure, get inside a thought of mine that described with naive details how a 100 KB ascii text could be put in ~ 200 jpeg 10 KB images... 2M, not quite bad to release me from a software intervention obbey!
The idea was convert a file with only ascii characters, a common txt plain english file, like a Gutenberg project book, for example, into a series of jpeg images with sequential names with the title of the book as the base that represent the pagination of it, prepared to be copied to a device for my own reading pleasure.
Then fuze seemed to have a 220 * 176 pixel screen matrix, I did not count them, but I assumed this fact as nice, like if the universe were not infinite, let's say... :-) And then, happily, I assumed with a lesser extent satisfacion that the only format that is capable to read from is JPEG, because GIF or PNG produced lesser size image files for text rendering...
And then I thought that could be interesing to produce anywhere in the future a splitted mozilla rendering output, in another child program that will surely be called renderhtml.
So I made a first try (called fuzetxt2jpg), and then this project starts with new name and renewed ambition (kidding...) where fuzetxt2jpg was left.
