View Single Post
Old 06-07-2013, 02:16 AM   #14
writerkit
Enthusiast
writerkit began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Mar 2013
Device: none
Hitch:
Quote:
Originally Posted by Hitch View Post
writerkit:

Not to be snarky, but you're not helping me much here. First you post complaining that mobi should "...at least accept the directive to use sans-serif rather than serif, if my CSS directs it to?," and then I ask you if you mean MOBI or PRC, then I ask you what type of MOBI you're making, and all I keep getting from you are answers related to Calibre, which quite bluntly has nothing whatsoever to do with making ebooks; it's a library tool, not a conversion and book-making tool. If you don't understand what type of ebook you're making, then how can you possibly expect to understand what type of CSS will or won't work for it?

If your "guess" that you're making a MOBI file for use on Kindles prior to KF8 is accurate, then in short, no, you can't direct it to use a san-serif font.

I don't know what you're feeding to Calibre to "make" a mobi file, but you might consider using Kindlegen or KindlePreviewer, which are the actual tools provided by Amazon with which to genuinely make Kindle books, to work on Kindle devices. The reason that you're being "warned off" using Calibre is because Amazon routinely rejects Calibre-made books. AZW3 has nothing to do with the discussion, actually. If you're capable of making an XHTML file, you should be able to make an ePUB, and with a very small amount of additional learning, you can then feed that ePUB to KindleGen and get a perfectly-crafted MOBI file. Calibre is NOT a book-making tool; it's a library tool. Nothing against it as a library tool, but if you can write that, you should have no problems making a MOBI file correctly, that will, for the most part, do what you want it to (within Mobi's inherent limitations).

Hitch

Hitch: not to be snarky, but you ARE being snarky, and I've been nothing but polite, while you've been totally ignoring the info in my answers to you. One more rehash of what I've already said, and then I'm done:

1) I'm not making this book for distribution on Amazon, so their specifications are of no consequence to me or of relevance to my original question. My ebook is intended to be sold elsewhere and sideloaded.

2) I am using Calibre to create my ebook. I've already created two ebooks with it, by converting my HTML docs into several different ebook formats - lots of authors have. In fact, I learned the process from Guido's blog. This is simply the first time I've converted to the "old mobi" format. If you've never used Calibre, then you don't know what you're talking about, so why not just admit that and let it go?

I've got my answer, from the other perfectly polite people on this thread, so thanks anyway. Sorry to so inconvenience you.
writerkit is offline