What's new in Joplin 2.14

News
2

Thanks for the update Laurent and other contributors!

I've been testing out the Evernote import process and I have some observations and feedback I'd like to share.

  1. It seems that note links are only restored if they point to a note in the same notebook/ENEX file.

    There is the obvious problem of the target note simply not having been imported yet.
    Even so, making sure that the target note has been imported first, the link restoration still does not work.

    The problem of the target note not being present yet, could be tackled by using the import directory of ENEX files feature. But probably the best way would be to allow the user to trigger the restoration of Evernote links manually, after all notebooks have been imported. See also this previous discussion: Evernote ENEX import suggestion (or plugin) re: note links.

  2. There is a small bug in the importer when parsing bullet lists. When placing a new line, within the same bullet point, this is placed in a new paragraph in Joplin. Interestingly, this does not happen with numbered lists.
    I can provide a sample ENEX if you wish, though the forum would not let me upload it as an attachment.

    Original in Evernote:

Result in Joplin:

  1. It is notoriously difficult to export data from Evernote because, among other issues, you can only export one notebook at a time, which is an obvious problems when you have dozens of notebooks.

    Exporting Evernote notebooks can be greatly sped up by using this Python tool: GitHub - vzhd1701/evernote-backup: Backup & export all Evernote notes and notebooks. It will automatically export all notebooks in separate ENEX files. Perhaps it deserves a mention on the importing/exporting wiki page? I'd be happy to try and create a PR for this.

    Of note is that exported notebook stacks are reproduced by folders. If you were to make the folder import function in Joplin recursive, this could allow you to automatically recreate the notebook structure.
    Visually, the exported file structure looks like this:

export\
│  Top level notebook.enex
│
├───Notebook Stack one
│      Notebook 1A.enex
│      Notebook 1B.enex
│
└───Notebook Stack two
        Notebook 2A.enex
        Notebook 2B.enex
  1. Now that colored text is supported, it would be good to have the ENEX importer deal with it too. :slightly_smiling_face:
4 Likes