Does compiling to Markdown mean bold and italics are transformed?

What it says on the title. A friend of mine and I will be using Scrivener to co-write (we use Discord as a communication/sharing platform), and this just struck me. I wonder if anyone has an answer.

Yes, it does compile to Markdown formatting.

Make sure that

checked

is checked, though.

1 Like

I’ll check my compile settings. Thanks.

1 Like

A much better, but slightly more convoluted way to do this:

  1. Make a strong and emphasis character styles.
  2. Bind them to ⌘b and ⌘i so they are applied easily.
  3. In compile you use the style to prefix / suffix strong and emphasis markdown.

This is better because you are using semantic markup (separation of content and style), and it means you can utilise other markdown without problems down the road


3 Likes

Good advice, and also remap bold and italic to something else.

I never figured out why, but if I don’t, sometimes the style gets applied, other times just italic. Almost as if something is competing for this shortcut that’s not obvious from the menus.

1 Like

This is kind of scary because IDK if it messes with other shortcuts in different apps.

The shortcuts are app-specific (unless you add them under “all apps”, which would be less helpful).

1 Like

I should explain I’m on Windows too.

They are even more app-specific on Windows, where Scrivener manages them directly (see “B.7 Keyboard” in the manual).

2 Likes

Oh, so you can create your own shortcuts?

Kind of.

Limitations
At this time, not all of the menu commands have been supplied to you in this list. Adding entries to this list requires individual care, and the list of commands you can customise will continue to grow in future updates.

At least they won’t affect other programs, so either it works or not, but nothing to be afraid of.

2 Likes

I see. Thanks.

So how would I go about making styles?

1 Like

There should be an “Emphasis” style available by default (I hope), try to assign a custom shortcut to that first. That’s where I would start.

2 Likes

For markdown workflows, styles really make the differences, so I definitely would go through the manual in detail. My Windows user manual is a bit old but Section 17 is a great read and 17.4.3 in particular to understand:

Scrivener’s style feature has been carefully designed to not only provide a traditional look and feel for those coming from word processors, but a powerful platform for defining ad hoc semantic types into the editor and then exporting those types into meaningful plain-text variants in the compile phase. The heavy lifting is entirely done in the compiler, leaving the particular style system itself largely to the domain of aesthetics, while writing.

5 Likes