View Single Post
Old 02-10-2016, 03:06 AM   #16
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,556
Karma: 93383099
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by NIRC View Post
Yes, yes. This is exactly the point. Until Amazon decides to accept the font-embedding function of their own formats and not mess itup when they DMR files, no amount of converting will fix the problem. Don't they get it? I mean, there are lots of books that need special characters. I have been trying every available workaround for the past 2 years and find the Amazon technical help of no help, and telephone calls to "supervisors" a dead end. No one seems to understand . . . and it is such a basic question.
Are you saying that you're only having problems with fonts if you opt to have DRM applied to your book?

If you rely on fonts for special characters in your book, what happens when someone reads it on a device that doesn't support embedded fonts? Have you considered alternative solutions that don't rely on fonts?
HarryT is offline   Reply With Quote