kindle previewer special fonts not trnaslating

#Kindle previewer special fonts not trnaslating how to#
#Kindle previewer special fonts not trnaslating pdf#

In the Format As drop-down, choose the desired format for your finished file. Simple Compileįor a quick, easy export method, stick to the Scrivener presets.Ģ.

In a nutshell, the Compile feature lets you choose which documents to export and in what format. But when you need to export your jumble of files into one coherent work-say for printing, or formatting in a word processor-it’s time to compile. But they don't tell you that you won't be able to sell it anywhere but your own website in that format.Part of Scrivener’s beauty is that it lets you build your project in your own way.

#Kindle previewer special fonts not trnaslating pdf#

otherwise I could have saved myself a bunch of time and started with Sigil!Ī lot of resources for blogger self publishers (I mean like ProBlogger, CopyBlogger etc.) tell you to create PDF ebooks. I didn't even know that an EPUB was basically a little website. Indesign is great for PDFs but you need special knowledge to make it work for EPUB, and 2.

#Kindle previewer special fonts not trnaslating how to#

So, I think I followed the workflow you suggest, I just didn't know how to use Indesign properly to avoid a ton extra work. I didn't actually convert the PDF to EPUB. Now I'm in Sigil working with the HTML and CSS (which I am far more familiar with than Indesign). Not wanting to spend more money on unusable services, I went back, cleaned up the INDD and finally got it to the point that I could export a n EPUB that I could work with. So I payed a company $100 to convert it for me, and they left it an even worse mess. Worked great for the PDF, but then when I exported the INDD to EPUB it was a total mess. None of my objects were anchored - I used a lot of local override styles etc (I had no prior experience with Indesign so I didn't know these were not good practices). I made the INDD in Indesign and designed it with a PDF in mind. It's hard to imagine a worse source format than PDF.I think I explained my workflow incorrectly. Then used Sigil or a text editor to tweak the ePub and feed the ePub to Kindle Previewer. To be honest, I would have skipped the PDF step altogether and just exported an ePub from InDesign (if I was using InDesign). I'll gladly include any additional information that will help solve this mystery for me. I'm just terrified that I'll upload the book and get a slew of negative reviews from people who are upset that they can't change the font to Courier (however bad that may look.) Is this an issue with KP? Is it potentially a problem with my book/html/css/conversion? I thought Kindle Fire had the option to change font face as well, but it's grayed out when I preview those devices. But, when I open the book in KP and click through the devices, and the only one that has the option to change the Font Face is Kindle Paperwhite. So, I'm hoping to avoid negative reviews for locking the font. (Please correct me if I'm wrong!) I don't have any embedded fonts, because the typefaces I would have used may not have been strictly legal to 'redistribute'. There are still some p classes and headers with defined font-family, but I am under the impression that Amazon allows this. I've also removed font-size, alignment, and color, as per Amazon's HTML guidelines for 'normal' text. I'm currently going back and forth between Sigil and KP to clean up discrepancies.Īfter finally coming to grips with the notion that e-book readers want to control the font face themselves, I've removed the font-family style from my tag.

Then I used KindleGen (via KindlePreviewer) to create a Mobi and view the results. I used InDesign CS6 to typeset a PDF, converted to epub (which was a nightmare.), and cleaned up the HTML and CSS in Sigil. I don't own a Kindle, so I've been using Kindle Previewer to figure out what works and what doesn't. I'm converting my self published e-book to mobi to sell on Amazon.