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
Another case: An image file is extracted from the note, put in the resources folder, but it does not appear in the markdown file. At least I did not find any reference to it, may it be broken or not.
You may look out for file 15744e6612b51875a726e4c664000db3.png in the attached note. Debug.zip
The text was updated successfully, but these errors were encountered:
Hi @Tokolino ,
I don't know whether it is an outdated behaviour as you use a really old Evernote client (v7), or a feature that I missed to support around attachments, but the thing is that the resource (I mean the file) is not referenced by its hash, as usually happens in Evernote, but by an objId.
I resolve it soon, but I think I'd label it as an enhanchement, because I've never seen this behavior.
akosbalasko
changed the title
Webclip extraction: file extracted but not referenced in md-file
Webclip extraction: support files referenced by objId, not hash
Jan 4, 2024
Maybe you could provide a placeholder for all resources that have been extracted but not linked to the note, for whatever reason. Like {unlinked-resources-block}{unlinked-resources}{end-unlinked-resources-block}.
I was wrong, objIds and hashes work and be recognized well, so it is a bug, and the problem is that it is placed within many embedded lists (OL/UL and LI tags), and as Evernote has trouble of storing LI tags, our workaround was to reshape them, and reorganize the content of the li tags.
As I tested it, the problem is in this function:
Another case: An image file is extracted from the note, put in the resources folder, but it does not appear in the markdown file. At least I did not find any reference to it, may it be broken or not.
You may look out for file 15744e6612b51875a726e4c664000db3.png in the attached note.
Debug.zip
The text was updated successfully, but these errors were encountered: