Quote:
Originally Posted by Quoth
If Amazon supported epub on their devices and didn't use proprietary formats at all, then it would be better. But Mobi as such makes no difference to publishing at Amazon. Recommended upload for years to KDP has been epub 1st, docx 2nd and not to use mobi at all.
I've an open mind if disabling Publisher fonts on 3rd party content is a bug or deliberate. Anyone rich enough could sue them for NOW crippling Kindles to content not from Amazon. Pay TV Satellite box makers got forbidden in EU to block FTA content not from the box supplier. They might be allowed do this deliberately in some countries. Other places might take a dim view of such anti-consumer behaviour.
|
Oh Bollocks. I love ya, but get real. "Crippling" them
how? Amazon has never guaranteed that any embedded fonts would work. And they've never said "oh, hear ye, hear ye, these eInks are tablets and you can do whatever you want with them."
What, so Suzie can't see the headings in Trajan Pro, and is "stuck" with Baskerville, instead? I'll bet you Amazon can make a factual use case that 98% of its customers don't use Publisher Fonts any-damned-way. So....
For that matter, you can't put a MOBI into iBooks. You think anybody is going to sue iBooks, for "crippling" the app to not accept content from other vendors?
Nyah. It's not the same thing as blocking FTA content. It's just saying that their own content has more possible features. HUUUGE difference and they could also argue that the MILLIONS of Word-built ebooks don't have publisher fonts,
either.
Sorry, old buddy mine, but I don't think that argument even has big
toes, never mind
legs.
Hitch