Cant read books from fictionwise

[nrapallo]

Originally Posted by tompe

The thing is that nearly all files with large images generated by MobiPerl has these problems but files generated with MobiPocket Creator with the same images generally do not have the problem.

tompe:

I had a similar problem when writing mobi2imp.pl where the resulting images would fail to show up in the ereader. What I did was, using GD, just copyResized the images but not actually resize them. What this did was rewrite the images using the GD library and those images would then load and show up properly. Maybe Mobipocket Creator does something similar, internally.

Sample code (you originally wrote this!) fixing this issue in mobi2perl.pl:

sub fix_image_tags {
    my $tree = shift;
    my @imgel = $tree->find ("img");
    foreach my $img (@imgel) {
	my $recindex = $img->attr ("recindex");
	my $ind = int ($recindex);
	my $filename = $image_index_to_filename{$ind};
###################################################################
#For .IMP start - just rewrite .jpg/.png/.gif image files (fixes non-stnd pics)
#
 if (defined $opt_verbose || defined $opt_debug){ print "FIXED IMAGE/TAGS: $recindex - $ind - $filename\n"; }
 
 my $imagefile = "$explodedir/$filename";
 my $supportedimage = 0;
 #my ($body,$path,$ext) = fileparse("$imagefile",'\.\w+');
 
 my $im = $imagefile;
 $im =~ /\.jpe?g$/i and $im = GD::Image->newFromJpeg($imagefile,1) and $supportedimage = 1;
 $im =~ /\.gif$/i   and $im = GD::Image->newFromGif($imagefile) and $supportedimage = 1  and $im->transparent(-1);  #use only non-transparent .gifs;
 $im =~ /\.png$/i   and $im = GD::Image->newFromPng($imagefile) and $supportedimage = 1;
 #$im =~ /\.bmp$/i  and next; # not yet implemented in GD, but hopefully not needed here!
 
 if ($supportedimage) {
     my ($width, $height) = $im->getBounds();
 
     my $target_im = new GD::Image($width,$height,1);
     $target_im->copyResized($im,0,0,0,0,$width,$height,$width,$height);
     
     open(IMAGE, "> $imagefile");
     binmode(IMAGE);
     if ($imagefile =~ /\.jpe?g$/i){
         print IMAGE $target_im->jpeg(85);
     } elsif ($imagefile =~ /\.gif$/i) {
         print IMAGE $target_im->gif();
     } elsif ($imagefile =~ /\.png$/i) {
         print IMAGE $target_im->png();
     } #elsif ($imagefile =~ /\.bmp$/i) {
       #  print IMAGE $target_im->bmp();
       #}
     close(IMAGE);
 }
#
#For .IMP end
###################################################################
	$img->attr ("recindex", undef);
	$img->attr ("src", $filename);
    }
}

Just a thought!

[tompe]

I have kind of tested this since I resized to different sizes to try to find if there was a limit. So just saving them again was not enough.

[HarryT]

Originally Posted by nrapallo

By the way, do any Cybook Gen 3 users have issue with any of the HarryT Jane Austen Classics in .prc format? Those use large images!

They all work. Do you think I'd post a book for the Gen3 which didn't?

[nrapallo]

Originally Posted by HarryT

They all work. Do you think I'd post a book for the Gen3 which didn't?

Touche, I forgot that you have a Gen 3!

[nrapallo]

Originally Posted by tompe

I have kind of tested this since I resized to different sizes to try to find if there was a limit. So just saving them again was not enough.

Ok we are getting somewhere!

Can you try creating a simple ebook (.html with a few large images known to crash the the Gen3) and produce a .prc with Mobipocket Creator and 'html2mobi.exe' with no resizing and compare the internals of the .prc? Obviously, there is something different.

It could be a database entry is missing, misinterpreted or the images are different. This would be a start.

Also, if you explode the two .prc's prepared above using 'mobi2html --rawhtml', and post the results here, I and others can help locating the source of this "bug"; be it firmware or mobiperl related.

[tompe]

Originally Posted by nrapallo

Can you try creating a simple ebook (.html with a few large images known to crash the the Gen3) and produce a .prc with Mobipocket Creator and 'html2mobi.exe' with no resizing and compare the internals of the .prc? Obviously, there is something different.

It could be a database entry is missing, misinterpreted or the images are different. This would be a start.

Actually, I think I misstated or misremembered. For some reason the images I had as test cases caused problems. Bur when I took one of the problematic files and used mobigen the result was still a file that crashed the Cybook. So it might just be that the images I used was more problematic than images other people use in Mobipocket Creator. I can no longer test for this problem since I have updated the firmware.

[DixieGal]

I can't praise Fictionwise's customer service highly enough. Click thru to their support email and ask them for advice. I'm sure you will get a quick answer.

[nrapallo]

Originally Posted by tompe

Actually, I think I misstated or misremembered. For some reason the images I had as test cases caused problems. Bur when I took one of the problematic files and used mobigen the result was still a file that crashed the Cybook. So it might just be that the images I used was more problematic than images other people use in Mobipocket Creator. I can no longer test for this problem since I have updated the firmware.

So to resolve this, why don't you offer your 'mobi2mobi' solution for Gen3 users with the old firmware and allow the switch to not resize for those users, like yourself, that have updated the firmware.

Obviously, i don't have a Gen3, but I do use mobiperl to create .prc and I too would not need the resizing.

Seems like a win-win to me.

[tompe]

Originally Posted by nrapallo

So to resolve this, why don't you offer your 'mobi2mobi' solution for Gen3 users with the old firmware and allow the switch to not resize for those users, like yourself, that have updated the firmware.

Obviously, i don't have a Gen3, but I do use mobiperl to create .prc and I too would not need the resizing.

Seems like a win-win to me.

Why would people have to install MobiPerl programs just to read a file they have downloaded from some site?

[nrapallo]

Originally Posted by tompe

Why would people have to install MobiPerl programs just to read a file they have downloaded from some site?

I thought that if a downloaded .prc file crashed the Gen3, then there was a solution that 'mobi2mobi --gen3imagefix' offers in that the images are resized and thereby allowing those Gen3 users to now properly use that file (that they downloaded elsewhere and maybe was created by others using say mobigen). I believe the original poster above found this solution useful.

I personally don't use .prc files, but I would like to generate them for others to use. I have installled my own work-around so for me it's a moot point.

However, your MobiPerl suite of programs, by default, resize images, even if the .prc file has no issues displaying on the Gen3 or any other ereader supporting this Mobipocket format. Imagine the (poor) iLiad user that has a 768x935 screen and it only shows 480x640 images!

I guess, the only ones that would have to install mobiperl, now, would be those Gen3 users that have not updated their firmware.

Time will tell what is truly needed here (or not)!