06-07-2009, 01:44 AM | #1 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
The Art of War--problems with ePub, LRF, and Mobi
Greetings!
I would like some wise recommendations as to how to fix up the attached ePub, LRF, and Mobi files so they will be as professional as their respective format's limitations allow. The Mobi one seems to be the best quality of the lot--I suspect even without help I could tweak it into shape somehow. Though help would certainly be welcome. One thing all three formats deal poorly with are my two "faked" ordered list items. The Art of War--or, at least, this translation of it--has two list items that are labelled "5, 6." and "13, 14." respectively. HTML has no support for such arbitrary numbering (i.e.: two numbers for the label of a single list item) of <LI> unless one uses an image (which, I imagine, is as wrong as it is inelegant a solution). For your convenience, I also include the source HTML file (i.e.: taowde_for_epub.zip) wherefrom I converted to ePub, and subsequently to the LRF and Mobipocket formats. As inelegant as my "faked" list items are... thus far I have been only able to think of even more inelegant/stupid/manually-intensive solutions that I'd like to avoid (i.e.: give up using ordered lists, and use tables with invisible borders and manually entered numbers for the "list" labels). The ePub would have been second-best, was it not for the fact that it literally lets some text run off the visible page, beyond the margins... for no valid reason that I can tell. (i.e.: it's not a PRE encased section) It, unfortunately, also seems to have no concept of small capitals (or at least does not use them when an EM tag with a specific class attribute mandates that it do so). There are, I think, also other minor formatting snafus. The LRF is messed up here and there and everywhere... but at least, unlike the ePub, does not seem to render any portion of the book literally unreadable. ---------- To be clear, I am asking for suggestions that would put me on the right track quicker and will result in the files improving in ways that might not occur to a beginner like me. I don't necessarily need too much hand-holding or verbatim instructions, as I am reasonably handy. I will be very curious to see whether either of these three can reasonably approach the quality of the custom-sized PDFs... the mobi file seems most likely so far, from a Sony PRS-505 perspective at least. Thanks in advance! - Ahi |
06-07-2009, 04:43 AM | #2 | |||
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Quote:
Quote:
Quote:
In the toc.ncx files the titles seem wrong, for instance, one can see: X. Terrain Sun Tzu said: We may… shouldn't it be just "X. Terrain"? |
|||
06-07-2009, 04:58 AM | #3 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Tables are certainly a good solution for things like this. I've used them in a number of my books.
|
06-07-2009, 09:44 AM | #4 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
Thanks for the explanation, Jellby and HarryT.
I'll try tables instead of the DIV/CSS fakery I've got presently going. Is Mobipocket and LRF as readily editable (via some trickery) as ePub's HTML files? - Ahi |
06-07-2009, 09:57 AM | #5 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Mobi can be "expanded" to HTML, but you don't get your "original" HTML back - Mobi Creator "re-writes" it.
LRF cannot, to the best of my knowledge, be easily "decompiled". |
06-07-2009, 10:31 AM | #6 |
Resident Curmudgeon
Posts: 73,998
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
06-07-2009, 11:40 AM | #7 |
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Note that when I said CSS-tables, I meant using the "display: table-*" properties of CSS, that would make it look like a table while not explicitly marking it up as a table. The advantage is maybe not clear, but I feel the code would look more friendly that way.
|
06-07-2009, 01:13 PM | #8 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
Here's the painfully manually constructed ePub. My appreciation for the format is definitely not growing the more I work with it.
It now looks pretty good, but it's still cutting off text for me on my Sony PRS-505 in Chapter 1, quote 13. Even though the fault is without a doubt in the rendering engine, if I cannot fix that, the ePub (of this book) is not exactly professionally viable. I could still make it available for free download, with a notice... but it's not something that could be sold, seeing as how it is guaranteed to be broken for a sizeable subset of purchasers. Any ideas what I could try? I still see no reason/cause/justification in the HTML for the renderer not to simply do a line-break instead of running words off the page... so don't really know where to go from here. I'm guessing though, Jellby, that it should be pretty close to perfect on your Cybook. Of course, for some reason this far cleaner and better looking ePub converts considerably worse into LRF and Mobipocket format. - Ahi |
06-07-2009, 01:30 PM | #9 | ||
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Quote:
But the .epub does not validate in http://www.threepress.org/document/epub-validate. It uses <center>, mimetype is not the first file in the archive, uses entities in the ncx file, etc. (In chapter 1, point 4, (2) is missing) Quote:
I see you are using an independent table for each point (although the first 4 points use a normal list)... I'd say a single table for the whole chapter is better, for the layout, at least. Also, inline "style=..." are not recommended, use classes instead. Oh, and the epub has all those chapter*.xhtml~ files (backups from vim, I guess). Last edited by Jellby; 06-07-2009 at 01:33 PM. |
||
06-07-2009, 01:37 PM | #10 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
Thanks for the tips, Jellby. I'll play around a bit more...
Mobipocket is a bit better when generated via mobigen.exe (see attached). - Ahi |
06-07-2009, 01:39 PM | #11 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
How do I make the mimtype file the "first" in the archive?!
- Ahi |
06-07-2009, 01:42 PM | #12 |
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
|
06-07-2009, 01:44 PM | #13 | |
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
Quote:
(or just create a zip of the mimetype, and add the other files in a second operation). |
|
06-07-2009, 01:52 PM | #14 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
Thanks. Here's the valid ePub.
- Ahi |
06-07-2009, 01:58 PM | #15 |
Wizard
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
|
Making it a valid ePub seemed to have adversely affected its display on my Sony Reader... sigh. The text still cuts off just fine though. =)
By trying it in ADE, did you mean Adobe's free downloadable software? - Ahi |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problems converting LRF to EPUB | rbur | Calibre | 2 | 06-21-2010 06:28 PM |
Problems with LRF from converted epub | ficbot | Calibre | 4 | 12-16-2009 03:12 PM |
PDF -> LRF, ePUB, MOBI? | krischik | Calibre | 12 | 07-23-2009 11:37 PM |
Epub to LRF no problem, Epub to Mobi indexerror | Rogier | Calibre | 3 | 06-09-2009 11:42 AM |
Converting PDF to ePub/MOBI/LRF | jasonb57 | Workshop | 0 | 02-16-2009 03:58 PM |