As you can see, there are some deleted words at the end of the first paragraph, but the deletion does not include the pilcrow, which means it still should be two separate paragraphs.
So either I am doing something wrong, and I need your help in order to fix that, or there is something Scrivener is doing wrong, and someone else needs to fix that.
I wouldn’t say you’ve done something wrong, you’ve just done something you don’t want, without realising it. It is certainly possible to mark newlines for deletion and have the text around them sewn together, and that is what you did.
To not do that, position the cursor at the end of the line, press Shift→ to select the newline, and then hit the shortcut to toggle strike-through. You won’t see a difference, probably because visible whitespace symbols aren’t really there, but with a recompile you should see the difference.
But, while you are selecting, there is a very visual difference (the selection bar going all the way to the end of the line, beyond the visible text), so it’s at least something that is easy to avoid doing, if you mistakenly select beyond the visible part of the line.
I’m not quite sure I understand what you’re saying, and I’m not quite sure I know exactly what to do.
So what I did is I removed the strikethrough, then I pressed ‘Shift > Right Arrow’ twice (it would not select the next line until I pressed it twice—the first time it would only select the pilcrow), then I added back in the strikethrough.
And that worked.
But that’s really confusing. This was originally one paragraph. I guess it means if I want to turn it into two paragraphs and strikethrough the last few words of the first one (then add a quote mark to the new paragraph), the strikethrough should happen last (after it’s been broken into two paragraphs) rather than first.
One would assume you could do the strikethrough first, but apparently, Scrivener ‘don’t play that’.
But thank you. It’s likely just a quirk that we have to realize, and likely one that can’t be addressed any other way (and can’t be fixed within the coding of the application).
The good news is this only affects the spec copy for my collaborator, should she want to compile that to get an idea of what it looks like for a reader, and would never be a problem in a finished copy for a reader.
