Quote:
Originally Posted by dgatwood
From what I'm reading, it seems very likely that Amazon uses a single ingest process for all content, whether it was translated from Word or not, and that it recognizes all the standard Windows fonts, and if it sees them in large swaths of CSS, it assumes that the CSS is junk that Word produced automatically and tosses the fonts out. If that's the case, then your best bet is to avoid any of the fonts that ship on systems by default. :-)
|
See? What'd I say?
Steely-eyed missile man.
Dag, that is downright
inspired. Never crossed my mind. I mean, crappity, they seem to never balk at TNR, so...<shrug>.
I agree that it's a single intake process, via KDP. No argument. I don't know if there's anything else, once it moves to the PW (Publishing Workflow), but...I wouldn't be completely surprised if they had different "checks" in place for all sorts of qualifiers, whether by genre (presumably, they check things like Cookbooks for "freely available on the web" and erotica for, well...stuff) or input format.
Never even
thought of that.
Still no update, by the way, my brethren. We asked "Are you sure...?" and we've not heard a whisper since. Makes me suspect an ePUB was loaded,
but... I can't prove that the dead silence is due to
mens rea. (And, man, they
RIPPED our client about how "dreadful" it looked, too!)
Hitch