Known Issues

A few known issues have longer articles:

If applicable, the macOS version number will be printed before the bug title, such as the following, "[10.13]", which means this bug should only appear in macOS 10.13 "High Sierra". "[10.12.4+]" would indicate any version since Mac OS X 10.12.4 "Sierra".

Spell Check Stops Working

Symptoms

Misspelled words will not be highlighted in red, straight quotes will not automatically switch to smart quotes, double-hyphens and triple periods will not switch to em-dashes and ellipsis (respectively). This may happen immediately after installation, or it may happen after years of the spell-check working correctly.

Cause

This is caused by a timing error where individual elements of the editor window are initialised in the wrong order, resulting in a disconnection with the operating system's spell-checking system. The timing is so sensitive that it impacts very few systems, and when it does, it may not impact them all of the time. For example, a system that was working for years may suddenly experience this problem after a system update or the installation of new software, because the overall timing of the system has shifted just slightly.

The actual triggers involved are unknown at this time. We only can speculate that they are consistently done, and in a unique fashion, so since those that experience this bug do frequently, while most users of Scrivener will never see it.

Workaround

At this time, the only known way to get the text engine's substitution and checking engine working again is to close and reopen the project.

System Text Preferences button does not work

Symptoms

When using the Mac App Store version of Scrivener, clicking on the System Text Preferences... button in the Corrections preference pane will do nothing. This is not a problem when using the direct-sale version.

Cause

Apple no longer allows software that has been sandboxed to request System Preference panes to be opened, using the existing methods of doing so. We will continue to look for alternative methods as time goes by.

Workaround

One can of course simply load System Preferences from the Apple menu and navigate into the Keywords pane, to click on the "Text" tab.

Lists export with extra numbers or bullets/numbers appear where they shouldn't

Symptoms

There are two common symptoms for this same underlying problem:

  • Only when exported or compiled, areas of your work obtain list numbering or bullets. There is no sign of this in the editor, though you may see some odd paragraph formatting in the affected area that is difficult or impossible to remove.
  • Lists look fine in Scrivener, but when compiled produce additional bullets or numbers, such as "2. 2. The second line item".

Cause

List formatting can be fragile, and sometimes when copying and pasting between different programs, the list markers themselves can be lost or made physical (in the sense that they are just characters in the editor as though you typed them in).

Workaround

Fixing this problem is easy and should be permanent:

  1. Select all of the affected text in the editor, and use the Format ▸ Lists ▸ None menu command to strip out any latent list formatting.
  2. If necessary, manually delete any visible itemisers left behind. As described above, these are not part of the list any more and are normal text.
  3. Select the text that should be a list, if any, and apply your preferred listing format.