Mobiperl Mobiperl - Perl tools for handling MobiPocket files

[Gudy]

Originally Posted by DMcCunney

Might want to check that exists, first. On my machine, the boot drive is normally D:, and Perl is in D:\Perl\Bin. (I dual booted Win2K and XP, and C: is the 2K drive.)

Right, so it should probably be %HOMEDRIVE%\Perl\bin then, or %SystemDrive%\Perl\bin?

[kovidgoyal]

@tompe

version 0.29 of mobi2html still has a bunch of <mbpagebreak> elements in the output and doesn't create <a name> elements, when converting the attached mobi file (Created using mobigen -c1 -s0)

[nrapallo]

kovidgoyal:

I noticed the same thing and have compensated for poorly constructed anchors (as used in SpaceEncyclopedia.mobi and a lot of feedbooks.com .prc's) in version 3 of my 'mobi2imp.pl' perl script.

The following code snippet (from mobi2html), now allows the hyperlinks to work properly (changes in bold):

print STDERR "Adding name attributes\n";
foreach my $pos (sort keys %fileposmap) {
#    print STDERR "NAMEPOS: $pos\n";
    my $a = substr ($text, $pos+$offset, 2);
    if ($a eq "<a" or $a eq "<A") {
	substr ($text, $pos+$offset, 2, "<a name=\"" . $pos . "\"");
	$offset += (8 + length ($pos));
	next;
    }
    if ($a eq "<h" or $a eq "<H") {
	# Put an empty acnhor before any '<'
	substr ($text, $pos+$offset, 2, "<a name=\"" . $pos . "\"></a><h");
	$offset += (15 + length ($pos));
	next;
    }
#For .IMP start - Kludge mainly for feedbooks.com .prc files (ignore warning)
#
    if (substr ($a, 0, 1) eq "<") {
	# Put an empty acnhor before header
	substr ($text, $pos+$offset, 2, "<a name=\"" . $pos . "\"></a>$a");
	$offset += (15 + length ($pos));
             print STDERR "FIXED: $pos - Not an anchor: $a\n";
	next;
    }
    print STDERR "WARNING: $pos - Not an anchor: $a\n";
}

More information can be found in the Fictionwise eBookwise forum thread 'Using perl scripts to produce .IMP ebooks and more... ' at https://www.mobileread.com/forums/sho...48&postcount=3

-Nick

[kovidgoyal]

@nrapallo
Thanks.

[JSWolf]

nrapallo can you please attach a fixed version of mobi2html for us? Thanks!

[nrapallo]

JSWolf:

If you mean the code where this fix is in, namely, 'mobi2imp.pl', then it can be found at https://www.mobileread.com/forums/sho...48&postcount=3 (1st attachment in post#3). I maintain this perl script.

If you mean, change 'mobi2html' to include this fix, then I would prefer to have tompe apply my suggested fix, as he is the maintainer of that script.

Either way, it would be helpful, to have this 'fix' incorporated.

-Nick

[tompe]

Originally Posted by kovidgoyal

@tompe

version 0.29 of mobi2html still has a bunch of <mbpagebreak> elements in the output and doesn't create <a name> elements, when converting the attached mobi file (Created using mobigen -c1 -s0)

For the attached file 0.0.29 did not give a result file with mbpagebreak in it. I have fixed the other problem. I wonder why the attached file hade two <mbpagebreak/> in a row. I did a fix that works for "<m" or "<M". I do not want to just put an anchor before "<" since I would like to detect the different ways this can be done since some of them might require special handling.

There is a 0.0.30 available and if I can get mobi2imp to compile under Windows there will be Windows binaries for this version available later today.

[tompe]

Originally Posted by nrapallo

I noticed the same thing and have compensated for poorly constructed anchors (as used in SpaceEncyclopedia.mobi and a lot of feedbooks.com .prc's) in version 3 of my 'mobi2imp.pl' perl script.

Please let me know if you see some more strange constructions for an anchor.

[nrapallo]

Now that you mention it, the cases where I got the 'Not an anchor' message, that truly did not have any anchors, were:

1. <m - as you mentioned for <mp: pagebreak> (Why would you link to BEFORE a pagebreak? Great sample!).
2. <b - for '<b>' just before an anchor
3. <d - for '<div' like in many feedbooks.com .prc files that I converted

They all ended up being valid links to insert a '<a name' tag; just that the ACTUAL 'filepos' was poorly positioned. My thinking was that I would go ahead and insert it as long as it was not in the middle of something. The start of a tag "<" was indeed a good choice to overlook your warning.

If this turned out wrong, then the original .prc had it wrong too! Your code is right, just the anchors are poorly positioned!

Just my thoughts.

Also, thanks for including the 'mobi2imp' in version 0.0.29. That script is version 2; whereas, the fix mentioned above is in version 3 previously posted. However, version 3 also adds the ability to 'fix' corrupt images within the .prc as this is often the case when using the ebook Publisher software. You may want to just comment out this Windows-specific 'fix' line for your distribution, namely:

system "nconvert.exe", "-quiet", "-q", "85", "-resize", "100%", "100%", "$explodedir/$filename";

I wanted to update 'mobi2imp' to include your latest revisions to mobi2html for the 'huffdic' issue, but I couldn't find that fix in version 0.0.29; is it there?

-Nick

[tompe]

Originally Posted by nrapallo

Also, thanks for including the 'mobi2imp' in version 0.0.29. That script is version 2; whereas, the fix mentioned above is in version 3 previously posted. However, version 3 also adds the ability to 'fix' corrupt images within the .prc as this is often the case when using the ebook Publisher software. You may want to just comment out this Windows-specific 'fix' line for your distribution, namely:

system "nconvert.exe", "-quiet", "-q", "85", "-resize", "100%", "100%", "$explodedir/$filename";

I wanted to update 'mobi2imp' to include your latest revisions to mobi2html for the 'huffdic' issue, but I couldn't find that fix in version 0.0.29; is it there?

I changed my code to also insert an anchor before "<". I did not test it but hopefully it works...

I could not find nconvert.exe in my version...

The huffdic issue is much more work. And as i understood it it did not work entirely correct. I have not decided yet if I need a written description of the algorithm or if the Python code is enough to avoid contamination issues...

[nrapallo]

Originally Posted by tompe

I could not find nconvert.exe in my version...

It is a freely distributable program that was installed on my PC a few years ago. I did upload that program to my thread in the Fictionwise forum 'Using perl scripts to...'

I think of this line of code as a 'frill' and should be commented out for your distribution, thereby removing the need to include it.

Is there any way to re-write out any .jpg/.png/.gif images using perl libs so that I can do away with this external program?

-Nick

[tompe]

Originally Posted by nrapallo

I think of this line of code as a 'frill' and should be commented out for your distribution, thereby removing the need to include it.

Is there any way to re-write out any .jpg/.png/.gif images using perl libs so that I can do away with this external program?

I meant that I did not find this line in the Perl code.

Yes, maybe the library I use (GD) will work? Look at how I handle images.

[Gudy]

Originally Posted by tompe

There is a 0.0.30 available and if I can get mobi2imp to compile under Windows there will be Windows binaries for this version available later today.

Getting mobi2imp from version 0.0.31 to compile under Windows is not really a problem (see attached Makefile(.txt) and .zip), but when I try to run the resulting .exe on a .prc, I get an OLE warning, probably because I don't have eBook Publisher installed.

[nrapallo]

Originally Posted by tompe

I meant that I did not find this line in the Perl code.

Yes, maybe the library I use (GD) will work? Look at how I handle images.

Sorry, now I know what you meant (I hope). You have version 2 of 'mobi2imp' included in your distribution. That line of code is in version 3 posted below.

I had looked at the GD.pm but didn't see anything promising. Usually, after the conversion, if I just re-write (and recompress) the images out using nconvert.exe or even the popular irfanview.exe, then the 'corrupt' images issue goes away.

-Nick

p.s. you can see from my script that I commented out

#use strict;

I did so because I was getting compile erros due to my setup/code not being 100% accurate. Do you know what breaks when I use:

use strict;

[tompe]

Originally Posted by Gudy

Getting mobi2imp from version 0.0.31 to compile under Windows is not really a problem (see attached Makefile(.txt) and .zip), but when I try to run the resulting .exe on a .prc, I get an OLE warning, probably because I don't have eBook Publisher installed.

Yes, it was easy. Just tested it and put the Windows binaries on the web page.