The Parsedown library has been patched to prevent tab indentations from being converted to spaces:

For example, if you had used the markdown syntax for displaying source code in your post, Parsedown had replaced your semantically correct tab indentations with hard spaces. This behavior meant that the code that was displayed after parsing was no longer exactly the code you inserted into the content editor. If someone had copied source code from your post into his IDE, then your tab indentations were gone because of the spaces.

That's why I hacked the Parsedown library and created a patch:
https://github.com/erusev/parsedown/issues/508

0 files changed, 0 insertions, 0 deletions