Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question from guide: Blockquotes, escaping special characters, and blockquote prefix #30

Open
jongreig opened this issue May 17, 2019 · 1 comment
Labels

Comments

@jongreig
Copy link

I had a question about one part of your guide, though I don't know if this is pertinent specifically to Scrivomatic. I imported the compile/styles preset from your guide, and while it works well, for block quote-styled sections of my paper (e.g.), the prefixed > character in each block quote-styled paragraph gets escaped as \> . I currently have the 'escape characters' option set here:

Screen Shot 2019-05-17 at 4 40 19 PM

And currently the prefix for the block quote style:

Screen Shot 2019-05-17 at 5 01 16 PM

It seems like Scrivener escapes whatever is in the 'prefix' field, regardless if it's not supposed to be (I would think...). Any idea to turn off escaping for this, or will I just need to disable character escaping or any Markdown transformation for this style?

@iandol
Copy link
Owner

iandol commented May 19, 2019

Yes, you need to disable Escape special characters as it is incompatible with using Styles for generation of Markdown. In my own workflow I never activate Convert rich text to Multimarkdown, so it is not an issue for me. I use rich text in the editor only for comfortable visualisation linked to styles. (so the Strong style shows text bolded), but the RTF bold is ignored on compile, and the Strong style is what is transformed.

But if you enable Convert rich text to Multimarkdown and disable Escape special characters then you may be able to mix RTF conversion and Pandoc, but be aware that things may go wrong if you use important markdown characters like [ or } etc. out of context...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants