View Single Post
Old 01-20-2010, 11:27 PM   #270
ficbot
Wizard
ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.ficbot ought to be getting tired of karma fortunes by now.
 
Posts: 2,409
Karma: 4132096
Join Date: Sep 2008
Device: Kindle Paperwhite/iOS Kindle App
I am having a lot of trouble with my mobi conversions. The conversion to LRF was much easier and more reliable. Specifically:

1) On books downloaded from here which are already in mobi, it is not always loading to the Kindle with correct metadata. So if I download it and it says something like 'author unknown' and I use the 'edit metadata' command to fix this and add in the author, it won't use that as the author when transferred to the Kindle. This has happened with maybe 4 out of 50 books.

2) It cannot justify the text when converting an LRF file. I badly want the text to be justified. I can't stand reading it with the ragged edges. I have tried ticking and unticking every box in there to no avail. I wish there was a checkbox to over-ride whatever the file says and force it to always justify the text when it converts.

3) On my 'liberated' eReader files, all of which have been converted to HTML using the exact same process: some of them convert with no glitches. Some have the 'do not justify' box pre-checked when I go into the options and some don't. Some will not justify at all no matter what I do. I am baffled. These files were all created the same way so why should they have different options and some will convert properly and some will not? What I am doing is running the decoder script, taking the resulting HTML file and opening it in a web browser. I select all, copy and paste into a Neo Office document. Then I save that as HTML, open THAT in a web browser and select all/copy again (to get HTML that is free from the funky coding you get from an Office suite), then paste that into Kompozer, an HTML program. I save the file, fun Text Wrangler to search for extra line breaks and remove them, then do a last save. These all are clean HTML files with no extra frills and all converted to LRF beautifully. But to mobi, it is hit or miss and I am just baffled as to why.

Can anyone help me? I just want plain, simple book files where everything is justified. Why is this so hard? What am I doing wrong? I am on a mac fwiw.
ficbot is offline   Reply With Quote