Have you tried one of these two methods:
1) used the "As Is" Section Layout?


or

2) Changed the section layout formatting to justify the text?

Should this topic be stickied until Codeweavers fixes v20?

You're welcome - and best of luck! Yes, thank you so much. I was finally able to upgrade to 20.0.2. I tried multiple times with v20 and RC11/12/13 on two distros (Fedora 33 and Mint 20). I also filed a bug with Codeweavers, but as noted above, they wouldn't do much because it is a Beta product. As ...

xiamenese wrote:Just a further update. You need to do the same to run RC12 under CrossOver on Mac … presumably also CrossOver on Linux too.



Mark

No wonder I haven't been able to run Crossover 20. I reported it to CodeWeavers they wouldn't touch the Scrivener Betas. I'll give this a try today.

your problem is most likely caused by a file inside your "Notes' folder. As per my email, I'm not sure how much my log files will do because of my environment. However, I did a bit more troubleshooting on my end. The LoDPI version would also crash, it just took longer. The same happened with b...

I have a folder "Notes" at the same level in the Binder as "Characters" and other non-compiled folders. When trying to access it, Scrivener crashes. It does not crash when accessing Characters, Places, Front Matter, Research, etc. Since this is where I keep things like my critiqu...

I configured a header and a footer for my novel and wanted it to begin on page 2. If I compile in PDF, it works perfectly. In doc or docx, it begins on page 1. In odt… there is neither header nor footer. Final docs and screenshot of header and footer configuration: https://drive.google.com/drive/fo...

I experience the same issue.

This error [std::bad_alloc bad array new length] now pops up when I try to change the font of a selected portion of text in the editor using the pull-down menu. When I then go through Format | Font | Show Fonts menu or using F4 I am able to without issue. Since I don't have a box to test this under ...

This seems to be a new bug in RC11. I never saw it happen in the previous Betas. Is this peculiar to the HiDPI version or is it also present in the standard version?

I'll also add my agreement. I don't know when the last time I fired 1.9.x. I use Scrivener almost every day as my primary writing tool. It's open more than my web browser (and I write historical novels, so I'm constantly doing research!). The product is solid -- more so than a lot of SW I've beta'd ...

I just tested this on both my Mint 20 and my Fedora 32 installs. I was able to compile to ODT without issue.

You can add third party grammar checkers like Grammarly. Grammarly claims that it has a desktop app that will work with other desktop apps.

If I ran Windows I would definitely try it -- but alas Grammarly doesn't have the same for Linux.

With each new Beta and RC I lose my customized substitutions (File | Options | Corrections | Edit Substitutions). Where are these stored so I can copy them, but not options like the theme. I know themes get updated frequently, and those I want to test, so saving and importing the entire options file...

When the same project, newly created in 2.9.9.7, is compiled using the same template in .rft and .odt formats, the standard manuscript header <$surname> / <$ABBR_PROJECTTITLE> / <$p> is not included in the .odt output file whereas it is in the .rft file. No change was made in the template other than...