Quote:
Originally Posted by JSWolf
That will not work at all. Not one bit. Nope, nada. Not a hope in heck.
Why won't it work? because you cannot modify a KFX file to change the CSS.
|
We're not talking about modifying a KFX file; we're talking about putting CSS in your ePub, which will then run through Kindlegen and eventually Kfxgen.
Quote:
Originally Posted by jhowell
No, I do mean 4.9. The current version is 4.10, not 4.1. (Version numbers often use a period as a separator, not a decimal point.)
|
Wow, I missed that. You're right, it's 4.10 now.
Quote:
Originally Posted by jhowell
ETA: I see upon further reading that you are looking at hyphenation control from the point of view of an author/publisher rather than a reader.
|
Yes.
Quote:
Originally Posted by jhowell
I just did a test using a personal document I have in my account, created by emailing a combined MOBI/KF8 file from kindlegen.
Sending it to my PW2 results in an AZW3 file. But doing the same to my iPad with the Kindle app results in a MOBI file.
So it seems that Amazon doesn't deliver an AZK file for personal documents as it does for purchased books.
|
That is interesting.
At the risk of being nitpicky, AZK is not, to my knowledge, delivered by Amazon. It's an intermediate file format that Kindle Previewer produces, using a piece of software called
azkcreator. When you load it into K4iOS, the app converts it into a .KCR file, which I believe stands for "kindle cloud reader". (I suppose that format is what's used for Amazon's browser-based reader of the same name.)
Anyway, that was what I found after a series of tests, both sideloading AZK and downloading books from Amazon into K4iOS, and then inspecting the downloaded files.
The real point here is that Amazon's Send-To-Kindle delivers a MOBI to K4iOS instead of a KCR, so that's not a valid proofing method. Doing an AZK side-load may be more accurate, but Hitch has claimed that even that method will not reproduce the final product you'll get when downloading straight from Amazon.
(Speaking of Hitch, has she weighed in on this discussion? I'm curious to know if she's talked to Amazon about the KFX hijinks.)
Odamizu, have you tested any hyphenation settings with AZK side-loading? MOBI certainly doesn't support that kind of thing, but KCR may.
Quote:
Originally Posted by DiapDealer
Even if one could turn off hyphenization, I would never support putting that control into the hands of the ebook designers. Not for normal body text anyway. The power to control normal body text hyphenization/justification should lie solely in the hands of the end user. Between designers having the control and no one having control, I choose no one.
|
I get your concern, but I think the middle path is better. The best way would be to allow the designer to have control, but let the reader override if they really want to.
For example, in iBooks, if you have the "Original" font selected, the creator's CSS settings for justification, hyphenation and all that will apply. If you change to another font, iBooks' settings takes over (which the user can change).
Amazon's approach is just a heavy-handed dictatorship of the typography settings.