‘As-Is’ implies, even promises, that text will be formatted identically in the compiled doc as it appears in the editor.
But when I try to compile for KF8/mobi and then preview that in the Mac Kindle app (which I must imagine is how it appears in a Kindle) there are significant differences.
Line spacing inside narrative paragraphs and dialog paragraphs is changed. Inexplicably! Trailing points after paragraphs are changed. Indentations are changed, sometimes just for narrative paragraphs following a line of dialog. Non-breaking spaces are replaced with normal spaces. There’s more.
As I format my text very specifically, my expectation would be that the formatting translates precisely for something referred to as ‘As-Is’. It does not. It does not manifest ‘As Is’, at all.
But where is the problem? It is either a problem with Scrivener itself, or it is a problem with possible CSS default changes that Amazon applies.
And what is the solution? Or workaround? It seems that if the problem is internal to Scrivener, L&L should fix it. If the problem is in Amazon, it also seems they should fix it, and it also seems they should not assume that their default formatting is better than that of people who want their formatting to be a particular way. There should be a way to turn default off. It also seems that using an external editor such as the one in Calibre would have no effect, if the post-edited CSS is overwritten by Amazon.
So I have three questions: A) where is the problem? B) Is there a workaround I am missing? C) if there is a solution that could be implemented by L&L, why have we not seen it?
It also seems that L&L should find a more accurate term than ‘As-Is’, because it is not at all ‘as-is’. Not even close.