View Single Post
Old 12-25-2022, 06:53 AM   #10
Nightjar
Member
Nightjar began at the beginning.
 
Nightjar's Avatar
 
Posts: 14
Karma: 10
Join Date: Dec 2022
Location: Bologna, Italy
Device: Kindle Paperwhite, Fire HD8, 4, iPad 1st, 2th, 3th, 5th gen
Quote:
Originally Posted by JSWolf View Post
You are wrong. Mobi does not support embedded or side loaded fonts on a Kindle. What you are doing is creating a dual-format file that contains Mobi & KF8. The KF8 is what's displaying the embedded fonts. You are best to create a separate mobi and KF8 then a dual-format file. Most will look at it and think it's a Mobi.
Ok, I agree that Amazon made a mess out of the .mobi file specs, but when their main conversion software saves a file with .mobi extension, I call it "mobi", even if does contain KF8.

However, my problem is still standing: when we offer our readers the option to buy a .mobi (+embedded KF8) version, everything is fine, whereas now that Amazon has officially discontinued .mobi support, forcing us to switch to ePub3 instead, there seems to be no way to allow Kindle Readers – even the most recent Paperwhite versions – to display any "Publisher font" correctly. Which is puzzling.
Nightjar is offline   Reply With Quote