@rwfranz, thanks for the compile file; that solves it. The underscore is coming from your Text Section with Heading layout, which includes it as the section prefix. You can delete this from the Prefix tab to remove it, or add a carriage return after it if you had intended it to be there but on its o...

OK, I've now also got the bug with the uppercase placeholders ($R, $L, and $W) coming out lowercase if they don't have an assigned stream (so <$R:chapter> compiles correctly but <$R> does not). Thanks! I saved the offending project as its own project and stripped text. A new behavior has begun; it's...

Thanks, both! It's a big help to have the sample projects to work with. I've filed tickets for the issues of the <$rst_keyword> tag not working in ebooks, the Roman numerals using title case in the ebook auto-generated TOC, and the title case option resetting to normal. I still need to look into the...

Answering in somewhat backward order, it sounds like the file and folder name are OK except for that .docx extension. The docs.checksum and the folders in the Data directory all sound fine; the folders would be named things like `37330BD9-0D35-4B33-A93B-EB8C793AFC7E` and could be empty--the folder m...

Hope it helps! "Select Similar Formatting" is also available directly via the menu under Edit > Select; if you're not going to be reapplying styles or doing anything else with them, that might be simpler than the Styles Panel. I just always think of it from that, as it's how I usually use ...

Once you've imported the text, you can load it in the editor (in Scrivenings mode, if it's more than one document), then open Format > Styles > Show Styles Panel. Select some of the bold text within the editor, then in the styles panel, click the gear menu at bottom and choose Select Similar Formatt...

Could you share a sample project with the $R placeholder coming out wrong? The capitalised Roman numerals are working fine in the title prefix of my test project, as I said earlier, and given all the possible combinations of settings, it would be helpful to have a specific project that is producing ...

Thanks for the follow up. Even using the $R placeholder following your images, I'm still not reproducing this, so the sample project would be helpful. You can use File > Back Up > Back Up To... to create a zipped backup of the project, and the zip file can be attached to your forum post by clicking ...

Synopses and titles are (and have always been) plain-text; they are used throughout the interface and in many ways which make the rich-text format impossible for these areas. For emphasizing words and such in these areas, asterisks or double asterisks, underscores, and all caps work well. Each docum...

I wasn't able to reproduce this. Using a sample project with a binder containing two folders in the Draft, each with two documents, I edited the Manuscript (Times) compile format to add the `<$rst_chapter>` placeholder to the end of the "Part Number" section layout's title prefix, then ass...

As Jestar explained, right-clicking in the inspector field will allow you to edit the data metadata. I've also filed this as a bug, though, because it is inconsistent with the other fields or the way it works in the outliner, and I think that should be fixable. We'll see!

JimRac had some excellent suggestions, but just for the record, the binder selection changing when using the Next/Previous Document commands (and automatically opening when using these if it is closed) is filed as a bug. Rather than the main selection changing, switching the editor document this way...

If you have an automatic backup with your most recent changes, as Katherine suggested, that's the easiest solution. If not, however, it sounds as though your project files are all present, just not matching up correctly to the project's index file. I've seen cases in the past where files downloaded ...

Glad to hear it's been solved!

Although you can't list the inline annotations the same way that you do the inspector comment, Scrivener has other tools that will help you work with them efficiently. Find by Formatting allows you to search through your documents for inline annotations, so you can easily jump from one occurrence to...