Disadvantages of "As Is" Formatting?

Today I have concluded that if I want the several hundred images in my document to be centered (compiling to MOBI format), then I have to turn on the “As Is” option for all my documents.

Is that correct (I hope you’ll tell me “no”)?

If that is true, it seems that I will miss out on some of the most important features of Scrivener. For example, if I wanted to change the paragraph formatting (e.g. first line indent), I’d have to go in and manually change the paragraph format for thousands of paragraphs.

Please help me with this issue.

Thanks,

Al

The formatting quandary aside, a better option would be to just disable the formatting override in the Formatting compile option pane if you have things preformatted in the editor. The “As-Is” flag is a little too aggressive for this because it will cause each document marked as such to ignore everything in the Formatting pane, meaning you won’t get titles or any other options for this section—just the text as typed into the editor. Consequently it is a better tool for specialised sections like the title page or a dedication—or perhaps your images, now we get to the quandary.

The problem right now, as you’ve noted, is that it is all or nothing. You either get the conveniences of the compiler for tidying up the manuscript into a uniform look, or you have to turn it off if you have special formatting like block quotes and such. Now as a part of the actual intended design, images (and a few other things) should never be touched by override formatting. They are a special class of object that rarely follows the standard formatting rules. Unfortunately this waiver hasn’t been coded in yet, so images become a similar constraint as block quotes: if you need them centred, then you’ll have to format correctly in the editor.

The second option is what I alluded to above: you could put each image into its own “As-Is” marked section, leaving everything else exposed to the Formatting pane. Whether that is a convenient way of working to you will depend on your preferences in how the Binder is used. That may not be an acceptible work-around if you prefer longer documents and a shorter outline.

We have multiple tools on the way for making this much, much more flexible in the future. It’s a temporary problem, growing pains you might say.

There is a third alternative, if you have the technical inclination, and that is cleaning up the e-book after you’ve compiled using something like Sigil. There is actually a bug in the Mac version right now that causes images to left-align when compiling to ePub or Mobi, so we have a help document available with instructions on how to get images centre-aligned again. You’ll want to skip down to the work-arounds section, second option. These instructions will not apply verbatim, the HTML/CSS output is different between platforms on account of the text engine being different. To me it looks like you’ll have to do a global HTML file search and replace for “scrivener6”><img (where the precise number here is arbitrary) to: “image”><img and then create a line in all of the CSS files like this:

.image { text-align: center }

Let me know if you run into snags. In my testing I was able to quickly centre all images in the ePub with one search & replace, but I was careful to keep all of my images formatted identically so they ended up in the same CSS class.

Thanks Amber.

OK, I’ve unchecked the “Override text…” checkbox, and that works pretty well, except that now I have no control over the format of the chapter title. I’d like to make it just a little bigger, but unless you have a trick for that, I will have to accept it as normal text.

Making changes after compiling is not acceptable to me. When I find a single typo in my final proofreading, I want to be able to create a new version quickly and simply.

One reason I moved to S was that I had to do too much kludgy stuff when creating a MOBI file from the OpenOffice file.

I’m assuming you’ve got that figured out now from the other thread.

Well, presumably this sort of thing would only be done once, right before you upload to Amazon or wherever. For most (maybe all, with e-books, since it’s not like finalising a pamphlet) proofing in between, one needn’t have a “camera ready” output.

Hmm, that’s not exactly Scrivener’s primary focus. I would say that at the moment we do all right with the e-book output, especially for a program that isn’t specifically focussed on making e-books, like Sigil. It’s a bit rough, and while we are working to make it better on multiple fronts, the primary development focus will remain on the writing tools themselves. How well Scrivener handles itself as a publishing platform isn’t really within its scope.

I’m experiencing this same issue with not being able to centre images in the compiled pdf.

I notice in AMBERV’s comment above from 2014 that this was deemed a temporary problem with new tools around the corner. Could anyone share what the resolution was in the end please?

EDIT: setting the image to use the verse style seems to have rsolved.