Quote:
Originally Posted by Quoth
Yes, that's it. There is a completely separate issue that their print preview margin detection doesn't work and they have crazy table of inner margin vs page count.
|
Crazy table of inner margin? I've never had a problem with it, UNLESS I used the minimum--and then, of course, if you have any italics, particularly Garamond, the italicized descenders (like a lower-case F, for example) will trigger the margin error message, but that's easy enough to fix. (I've found that true with any printer, private or POD. Haven't you?)
For the minimum 0.75, for example, we just use 0.76 or 0.77, as the minimums and so on. I mean...that's pretty minor.
Quote:
|
Print Preview Margin Detection doesn't work?
|
It has in my experience, which now, isn't insignificant. What do you mean? Are you talking about full bleed and white gaps or something else?
Quote:
|
A once off DIY that doesn't want to invest any time learning. Yet considering time to research, write & proof content?
|
Well, the once-off takes authors and hand-walks them through what they ought to have done in Word, in the first place--assigning styles. Paragraph/body styles, heading styles, etc. It gives them a fairly decent outcome.
I'd agree with you, but given what I've seen, over the past dozen years--it's simply accepting the fact that authors a) don't want to read, b) don't want to learn to use Word, c) or any other word-processor; d) can't be bothered, generally and e) want something FREE and relatively easy.
IME, while I may have no use for KC, Amazon is simply accepting that which is. I haven't seen anything that tells me that they are doing something other than that.
Hitch