[Feature request]: Internal Evernote Link Redirector

[oboehlk]

Suggestion

Internal Evernote links are one of the biggest problems when backing up or migrating from Evernote.
Actually, "evernote-backup" extracts all the necessary information to be able to rewrite internal Evernote links. An automatic "rewrite" feature for Evernote links would be a great feature.
For this, it would be additionally necessary to implement a "link redirector" that might somehow "translate" incoming "Evernote note links", for example, into Markdown links…

[dgreen]

Unless I misunderstand the request, a workaround is that YARLE can generally handle providing markdown (or WikiLink) linkage, provided the name of the destination note has not changed since the Evernote Link was made.

To me, the bigger problem is that if one has to import both the .enex with the link and the destination back into Evernote, things don't work because Evernote assigns new numbering to re-imported destination note.

[AltoRetrato]

The issue with YARLE and other conversion tool from Evernote to Markdown is that they often can't correctly convert Evernote internal links (i.e., links in a note to other notes).

Evernote internal links (e.g., <a href="evernote:///view/aaaaaaa/bbb/cccccccc-cccc-cccc-cccc-cccccccccccc/dddddddd-dddd-dddd-dddd-dddddddddddd/">Evernote alternatives</a>) use a note GUID that is not included in the note attributes within .enex files exported by Evernote (or evernote-backup), see #66 . Therefore, any program relying solely on the data in the .enex files can only "guess" which note to link to based on the text inside the anchor tag, which is not necessarily the actual title of the note it points to. When the link text matches the note title (and there is only one note with that title), the link can be created correctly; otherwise, it either points to a wrong note or to a non-existing one.

I plan to write a Python script to export from the evernote-backup to Markdown with correct internal links to import them into Obsidian.

[oboehlk]

That would be a very good solution, of course. Thank you very much for your feedback!