Why copy and paste instead of using compile or export to Word, going through the editing process, and then use import and split to get the edited manuscript back into Scrivener?

 

For single scenes, compiling into Word isn't any faster than copy and pasting. Importing it back isn't any better, as it keeps the original formatting from the source.

So far, the work-around is to copy and paste back from word normally, allowing the formatting from Word to be retained, then select all and apply the Scrivener format again.

I guess I'm just whining. It seems such an easy thing to fix for the developer. But, considering how many other bugs I've found in Scrivener, I'm not surprised.

 

Then use export. It's not the same as compile and you can even do it with a simple hot-key command (shift-command-E on Mac). I've exported literally hundreds of scenes to Word this way and it always retains whatever my Scrivener default formatting is. Why are you changing the formatting between editing in Word and then importing back into Scrivener? When you compile the completed manuscript, it'll change the formatting to whatever preset you want any way. Maybe I'm missing something, but that formatting change seems like a completely unnecessary extra step in the process.

 

I've had this same issue for as long as I've used Scrivener.
What I do now is manually add the changes back to my Scrivener document… time consuming.

 

The problem is not in the export, its in the import. Specifically, one of my proofreaders uses a different font. (She likes TNR, I like Courier.) When you cut and paste a scene from Word BACK into Scrivener, that's where the problem occurs.

And like I said, this problem didn't use to occur. It's only started happening since the last update. That's my problem with Scrivener. Every time they update it, they fix one thing and break another.

 

.

 

Could you just go back to a version of Scrivener that did what you want? If the problem only started recently it must be the last update you did that did it.

 

The problem is not in the export, its in the import. Specifically, one of my proofreaders uses a different font. (She likes TNR, I like Courier.) When you cut and paste a scene from Word BACK into Scrivener, that's where the problem occurs.

And like I said, this problem didn't use to occur. It's only started happening since the last update. That's my problem with Scrivener. Every time they update it, they fix one thing and break another.

But you're not importing. You're copying and pasting. Importing is using the File > Import command. All your styles will be preserved that way. And if you're still annoyed by the font your proofreader uses, then just select all and choose a different font. Your formatted text will still retain its formatting. I know this because I just tested it this instant. Copy and paste is not a good way to transfer text from one program to another, because there's all sorts of invisible formatting that could muck things up. That's why the import command exists in so many programs.

 

The problem is they don't want to retain the formatting in the word doc, they want to use the Scrivener basic formatting, but not lose italics.

To be honest, I never knew this was possible. (If you'd care to say how it was possible, I'd love to know!)

L&L probably don't regard it as an issue because you can reformat in compile, but the Windows version doesn't have the option to exempt indents and centering from the compile for scene and chapter breaks. That's a really big deal for ebooks, but L&L don't seem to care much about ebooks.

 

I have the exact same problem.

My workaround is annoying but it worked for me.
I tried to import the doc file as rtf and then was able to copy paste without the damn changes in font sizes.

Hope this works for you too.