When I import an Evernote ENEX file as markdown of a note containing a Musescore file (extension MSCZ, compressed file type like DOCX) the extension .zip is added to the filename. When I open the attachment in Joplin it opens Winrar instead of Musescore. I tried to edit the ENEX file to remove any possible zip association but that does not help.
The ENEX contains myfile.mscz
Why is the .zip extention added?
Just did a bit of testing in case it helps anyone who may be able to look into this.
It seems the the ENEX file (original_evernote_example.enex) contains type="application/zip" / <mime>application/zip</mime> where one or both causes Joplin to store the file in resources with a zip file extension.
Right-click "Save as..." will save the file as mscz but clicking on the link to open / edit triggers any app that is assigned to zip files. It seems that the file's actual extension (zip) overrides Joplin's stored extension (mscz).
The example.enex file without the type statement causes Joplin to store the resource without any extension and, when the linked is clicked, Windows asks for an app that can handle mscz files.
Note that I had to reset Joplin to do this otherwise the import of the ENEX file without the type/mime statement reused the existing resources file that already had the zip extension appended to it. The above screengrabs are from two separate, fresh installs using the two different ENEX files, one for each install. Both ENEX files contain the same file as an attachment but I was surprised that the import has generated the same resource ID both times.
EDIT: Realised that the resource ID is just an MD5 hash of the attached file so the duplicate ID is to be expected as they are the same file. EDIT2: Added the mime info as a result of a subsequent post by the OP
Hi Thanks for your quick reply.
So in short, I have to remove the mime tag in the Enex and use a fresh install of Joplin when I do the migration?
Do you think, besides the mime tag, I also have to remove the type=application/zip in the Content tag or even remove the complete content tag?
I did not propose the above as a solution just an indicator of where Joplin may be causing the problem with the import
I did not edit your files at all so whatever you removed from the "original" file to make the "example" file does work as a "work-around" to the import problem.
I didn't notice the removed mime type before so yes, remove it.
Question: Are you just starting out moving notes across and starting over will not be a problem, or would it be a pain to have to start all over again?
At the moment I'm just testing Joplin to see if it is an alternative for Evernote, which I'm using for many years now. So restarting is not an issue. On the other hand I can import on another "fresh" device and export the notes and import the Joplin export to an existing device. Since I have hundreds of MSCZ notes it was worth asking for a workaround.
