Quote:
Originally Posted by AaronShep
Quote:
Originally Posted by mattmc
(Any way to turn off the hyphenation, if you don't want it?)
|
Use Webkit's CSS to control the hyphenation.
-webkit-hyphens: manual;
Don't say "none," or you won't get a break at hard hyphens either.
To turn hyphenation back on:
-webkit-hyphens: auto;
I use the first one for the body, then the second for individual styles.
Aaron |
That's amusing, I was wondering how you could respond to my question so promptly and so authoritatively, and then realized I was just reading your blog entries about KFX. Hi, Aaron.
So, Amazon is using Webkit?
Missed the memo on that one.
Or, are you giving this solution because I was talking about K4iOS in my post? (And K4iOS is going to be using a UIWebView, of course.)
I am looking for a way to stop any KFX-related automatic hyphenation across the whole Kindle family, so if that webkit style works, then great.
Quote:
|
In practical terms, this means there is no longer any effective way to proof your book before or after publication. You can get it looking absolutely perfect in a KDP proof, and even right after it goes on sale, only to have it skewered a few weeks later. You are asked to blindly entrust the formatting of your books to a team that has shown near-zero sensitivity and competence in typographic matters.
|
Quoting your blog, this is what I find most disturbing about the whole KFX thing. I have some books with very specific formatting requirements, and the inability to proof them reliably is a serious concern for me.
You mention spacing issues between paragraphs (obviously talked about more in this thread) and the apparent conversion of images to opaque JPEGs, but have you noticed anything else off about KFX?
It's this concern that may lead me into getting my hands dirty with the KFX format. Something I'd really rather not do, but I have to be able to proof my books.