Thread: Need some help with Fonts on 5.6.5
View Single Post
Old 11-02-2015, 11:01 AM   #17
Enor
Enthusiast
Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'Enor knows the difference between 'who' and 'whom'
 
Posts: 31
Karma: 10002
Join Date: Oct 2015
Device: none
Quote:
Originally Posted by shamanNS View Post
What is your input format when you're doing Calibre conversion?
I've tested this literally 8 days ago on 2 different books for a friend who wanted to use WiFi delivery using Kindle Cloud but have both custom font and soft hyphens added.

So I've hyphenated the epub first, thet done epub> "dual" mobi conversion where I've chosen font family to embed . Then I've sent it via email (didn't have Send to Kindle app installed) to the email address of the Kinde I wanted it to get delivered to.

My PW3 got aw3 file with "Publisher font", only problem was that when turning on Publisher font there where empty squares in places where soft hyphens were added to words (subsetted font files probably miss that character). So the conclusion for the next book I should probably deselect "subset all embedded fonts". Calibre probably did subseting based on "old mobi" portion of the file that didn't have soft hyphens. I did't test this because I was lazy. But since everything was displaying as it should (visible hyphens on the end of a row where needed) when Publisher font was turned off, I guess that must be it, font subset problem...

Maybe there are some problems in CSS code of your book that caused Amazon conversion service to drop all the embedded fonts. That certainly did/does happen for some people who were publishing books.

Try another book, in epub format and check CSS code to make sure that there's no font-family declaration "junk code" (Times New Roman etc) outside of body tag code.

Test the same epub by converting it using KindleGen (which by default also outputs "dual mobi" instead of Calibre just to check if you will still get "old mobi".
Thanks. I don't know a single thing about css and that. It's way beyond my realm of understanding. It does seem that I may just have to wait for the jailbreak to put the fonts directly on the pw2. Unless there is an easy tutorial to understand that css stuff. I greatly appreciate all the help here, though. I did try with a couple different books with the same result.
Enor is offline   Reply With Quote