Hi
I am developer and i decided to write a export odt to mobi plugin for the software (Calligra Author) that i am working on it. After attempts i succed to write it or better to say not succed because now calibre can open and show the files but kindle can't.

I check the differences between my file and other files ( mobi files that i had created them with mobi packet creator and calibre). I don't know where is the problem and where i am working wrong.

I attached my file. I really like to do to make my file work because i am working on it for month, and i realy need help.

The problem is that you've not converted the html from your original source (whatever that may be) into any kind of valid mobi markup. It's a MOBI by all external appearances (the binary database structure is valid), but that's about it. Your internal mobi markup frankly looks like straight-up HTML4 -- complete with inline CSS. That'll never fly on any MOBI app/device. Calibre views it because calibre's viewer doesn't really render MOBIs. It extracts the contents of all ebooks into an OEBPS-compliant format for viewing.

Hit up the MOBI WIKI here, and use something like Mobi_Unpack.py to see what the markup looks like inside some valid MOBIs.

Thanks for all of your answers.
DiapDealer i will use Mobi mark up and will back again.
but i have used Mobi_unpack to unpack my mobi files its html is ok but in its debug
ther are some thing that i think should be the problem.
These are the part of unpack debug:

Use calibre or kindlegen to convert your source material to a MOBI. Then use Mobi_Unpack to examine the raw markup they produce as compared to the raw markup in your mobi. The difference will be quite apparent. MOBI-markup is more akin to HTML3.2 -- all inline attributes and no styles/classes.

Hi all
again me and my mobi converter problem.
The problem is now about image, its html is standard as i know and think header is ok too.

But Kindle desktop previewer can not open it. :/
Again no idea why!!

I have attached file.

Moji

I don't know precisely what you've got wrong or missing that Kindle wants, but here's your file after running through mobiunpack and kindlegen 2.7 and then mobiunpack again to get the non-KF3 format portion.

By comparing the files (use mobiunpack in dump mode) and tweaking the file you generate, you should be able to find out which bits you need.

But bear in mind that there's no guarantee. The Mobi file format is officially undocumented.

when i get diff from my ebook and one of calibre ebook (mobi) in headers
There is an attribute "Extra Record Data Flags"
( http://wiki.mobileread.com/wiki/MOBI#MOBI_Header) in mobi header
That for calibre is "1". This attribute is important? and it can be the problem?

when i get diff from my ebook and one of calibre ebook (mobi) in headers
There is an attribute "Extra Record Data Flags"
( http://wiki.mobileread.com/wiki/MOBI#MOBI_Header) in mobi header
That for calibre is "1". This attribute is important? and it can be the problem?

The Extra Record Data Flags indicate whether there is extra info at the end of each text section in the book. The multibyte bytes flag indicates that in utf8 files the text sections include the extra bytes making up a utf-8 character if it happens to break between sections, so that complete characters can still be obtained without decoding two sections at once. (The mobiunpack code handles these).

The other two bits indicate other stuff that can be at the end of the text sections. Since you're creating the file, and it only currently has one small text section, this is not your problem.