Quote:
Originally Posted by Hitch
The font survived the first build (KG). It survived the 2nd (mobi then loaded at KDP). We sent the post-step-7 "Preview mobi" to the client, as previously, that's been ironclad. Baked in. Immutable.
And now...it's not. And they've confirmed that this type of thing CAN CHANGE at the PW. And obviously, it's not being changed in any way that we want, not thus far. We now can't know. CAN'T know, not for sure, not before it's published. That part makes me ever so slightly nauseous, thinking about the repercussions. I can't imagine how this is going to play out. Not for us. I really can't.
|
At this point, I think we need to send this thread and the embedded fonts thread to
jeff@amazon.com. KDP's publishing workflow causing content breakage has been an ongoing problem for three years now. It is well past time to light a fire under someone's you-know-what.
As a publisher, when I deliver content, I expect my customers to get precisely what I delivered to the content distributor. If Amazon's publishing workflow makes further changes (beyond trivial stuff like inserting a review page at the end or changing the start-reading marker), then our entire QA process becomes a waste of time and effort.
No other content distributor makes radical, content-altering changes to content during their ingest. That's just not acceptable in a delivery partner.