You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now AnkiLink has already supported import from markdown, and in the long run, will support export to markdown.
However, it is worth thinking that while exporting, the original structure may be disturbed.
The ideal approach is to append an ID for each block just like #11 said. I'd think it over.
Another problem is that some text may be lost after converting the note to Anki and transform it back. It can be avoided by linking each markdown block with an Anki card and only perform updates to the original file.
Additionally, the original markdown text of a card should be somewhere saved.
I'm considering integrating this with the Anki add-on [anki-auto-markdown[(https://github.com/natfarleydev/anki-auto-markdown).
The text was updated successfully, but these errors were encountered:
Now AnkiLink has already supported import from markdown, and in the long run, will support export to markdown.
However, it is worth thinking that while exporting, the original structure may be disturbed.
The ideal approach is to append an ID for each block just like #11 said. I'd think it over.
Another problem is that some text may be lost after converting the note to Anki and transform it back. It can be avoided by linking each markdown block with an Anki card and only perform updates to the original file.
Additionally, the original markdown text of a card should be somewhere saved.
I'm considering integrating this with the Anki add-on [anki-auto-markdown[(https://github.com/natfarleydev/anki-auto-markdown).
The text was updated successfully, but these errors were encountered: