Adjust the formatting of code

[sojusnik]

This script currently converts inline code with two `` and code blocks with tabs, whereas it should do it as mentioned here or according to the following examples:

Zim: An example ''with code'' inside a sentence.
Obsidian: An example `with code` inside a sentence.

A Zim code block:

'''
This is a code block, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is, a code block this is.
'''

The upper and lower ''' from above should be converted to ``` in Obsidian.

While the manual says that a code block can also start with a tab (or 4 spaces), it's rendered weirdly, so therefore the formatting with ``` should be preferred, as shown here:

While with a tab at the beginning, it looks like

[peter88213]

To be precise, the zim2obsidian script does not change at all the inline code formatting as exported by Zim.
I guess, the problem is that Zim doesn't export "fenced" code blocks, see issue 1718
At the moment, it is marked as an "open issue" in the code.

If you want to do it with zim2obsidian, you have to enhance the code for placing the "fences" around lines beginning with a tab character. This works only, if the tab characters that signify code block lines are not already escaped by subst_indent.py.

I think, this problem is best solved by converting the original Zim notes as discussed in #8.

[peter88213]

With version 0.11.6, the zim2obsidian.py script supports code blocks that are "fenced" with backticks (see #21). This is not specified with Zim, but it may used as a workaround. Same for "inline code" embraced with single backticks (see #22).

[peter88213]

Version 0.12.0 converts blocks that are indented with tabs to Obsidian code blocks that are fenced with three backticks.

This is actually the correct method. However, it is in contrast to the behavior required with #11 and #21.
You could consider implementing different operating modes that can be selected via command line parameters.

[peter88213]

Solved with version 0.13.0, see: #15 (comment)