Quote:
Originally Posted by JSWolf
But, nobody with 538 has said that large images are an issue and if they are, then they can always run mobi2mobi with it resizing to fix it.
But what I want is to be able to use mobi2mobi to fix the metadata where needed and if there are images, I don't want them possibly reduced in size. I don't want to have to check every mobi format eBook for possible images that might be resized.
What is the problem with putting in a switch to prevent image resizing? The default would be to resize and if anyone wants them not resized then that's ok too. The Gen3 is not the only implementation of a mobipocket reader. So please don't go by the bugs it has only. Give people the choice how they want things where possible.
|
I have explained my position before. MobiPerl is distributed as perl code so it is trivial to change if you need it. This is something I do in my spare time and the primary goal is to minimize support questions.