Obsidian callouts are broken in output #328
Comments
That would definitely be welcome, provided there's tests to go along with it 😄 (CONTRIBUTING has some pointers) Might take me a while to review it or get back to you though, life is keeping me pretty busy at the moment |
zoni
added a commit
that referenced
this issue
Mar 25, 2025
## [25.3.0](https://github.com/zoni/obsidian-export/tree/25.3.0) - 2025-03-25 ### Changes - Support Github-Flavored-Markdown The Github-Flavored-Markdown extension is now enabled in the markdown parser. This ensures Obsidian callouts don't end up mangled by having escaping added to them. ([#328](#328), [#330](#330)) ### Miscellaneous - Dependency updates
zoni
added a commit
that referenced
this issue
Mar 25, 2025
## [25.3.0](https://github.com/zoni/obsidian-export/tree/25.3.0) - 2025-03-25 ### Changes - Support Github-Flavored-Markdown The Github-Flavored-Markdown extension is now enabled in the markdown parser. This ensures Obsidian callouts don't end up mangled by having escaping added to them. ([#328](#328), [#330](#330)) ### Miscellaneous - Dependency updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Source:
Result:
Expected result would look identical to source.
It looks like this was a known issue that couldn't be fixed because of lack of support for CommonMark. However, it seems like there is some support for this syntax in pulldown-cmark?.
I'd be happy to write a PR to preserve the original callout syntax during conversion if it would be welcome.
The text was updated successfully, but these errors were encountered: