Markdown: separate options to exclude fenced code blocks and inline code blocks

Currently, translateCodeBlocks controls both fenced code blocks (delimited with 3x backtricks) and inline code blocks (delimited with single backticks).

In our experience, these would be better off as two separate options. In most of the content we see, fenced code blocks represent large code samples that are not meant to be translated, while inline code blocks are often individual words that may or may not be translatable depending on the context.

I propose that we split this option in two. The existing translateCodeBlocks option will continue to govern fenced code blocks, while a new one (`translateInlineCodeBlocks`) controls inline codes.

Comments (3)