Pulling {{content}} into Obsidian has issues.

[achampion]

There are several issues when pulling {{content}} into Obsidian. The Markdown conversion of websites struggles with special characters, e.g. here's small section of a website that shares some obsidian templates:

```yaml
---
when: <% tp.date.now("YYYY-MM-DD", 0, tp.file.title, "YYYY-MM-DD") %>
tags:
  - note
---
<% tp.file.cursor(0) %>

```

There are similar issues with image URLs they are full of html special characters, this is an example link to a cached image: https://proxy-prod.omnivore-image-cache.app/1000x420,sOX7WD0NWkM_lJMJ9Ymys259QWICy82-kZ1feISC8Yuo/https://res.cloudinary.com/practicaldev/image/fetch/s--JrYnSCUR--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/78ffg3gv7ldjslallyj0.jpg). Which of course doesn't render.

There doesn't seem to be an option to pull down local copies of the images so this can be read offline.

[jacksonh]

Hi @achampion can you try {{& content }} that will fix the escaping.

[achampion]

That was quick and thank you - yes it seems to have fixed things.

Note: the reference link in the Options page in Obsidian sends you to https://docs.omnivore.app/obsidian.html#customizing-which-data-is-synced-from-omnivore-to-obsidian which is a 404.

[jacksonh]

Thanks! Working on updating docs now!

[jacksonh]

Hey the docs for this have been updated now so I am going to close it out. Let us know if you have any other issues.