Error importing notes from format: enex

Support
1

Operating system

macOS

Joplin version

3.7.18

Desktop version info

Joplin 3.7.18 (prod, darwin)

Device: darwin, Apple M1
Client ID: dcae1c02de1b4710b36fac910e1991d0
Sync Version: 3
Profile Version: 53
Keychain Supported: Yes
Alternative instance ID: -
Sync target: Joplin Server
Editor: Rich Text

Revision: ce25482

Backup: 1.5.1
Freehand Drawing: 4.3.0

What issue do you have?

Body

  • Input format: enex
  • Output format: md

Errors

Error: Line 65183:210: "260914 Journal": Invalid character in entity name
Line: 65183
Column: 210
Char:  
    at error (file:///Applications/Joplin.app/Contents/Resources/fork-sax/lib/sax.js:651:10)
    at strictFail (file:///Applications/Joplin.app/Contents/Resources/fork-sax/lib/sax.js:677:7)
    at SAXParser.write (file:///Applications/Joplin.app/Contents/Resources/fork-sax/lib/sax.js:1498:13)
    at SAXStream.u.write (file:///Applications/Joplin.app/Contents/Resources/fork-sax/lib/sax.js:239:18)
    at ReadStream.ondata (node:internal/streams/readable:1012:24)
    at ReadStream.emit (node:events:509:28)
    at addChunk (node:internal/streams/readable:563:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:514:3)
    at ReadStream.Readable.push (node:internal/streams/readable:394:5)
    at node:internal/fs/streams:293:14
2

Hello, are you able to share an example of ENEX file that fails with this error message?

3

The ENEX file that threw the error when I tried to import it is 1.74 GB in size, so sharing it is impractical. However, the error message refers to a specific note in that notebook, which is much smaller (but at 17 MB exceeds the upload capacity here).

4

If you can replicate it with this 17 MB file that would be interesting for us. Feel free to upload it on something like OneDrive, Mega, etc, and we'll get it from there

5

Great, thanks! I uploaded it to Google Drive on https://drive.google.com/file/d/1NQ0fIIOtuBOUlhgkBx6J1nfnfeYe9tcX/view?usp=sharing. Please let me know if you have any trouble accessing the file.

6

Thank you, I have added a fix there which will be part of the next 3.7 version:

7

In other notebooks imported as ENEX files I am getting errors like "Found a link_close without a link_open". It's unclear whether it just stops the import there or ignores the error and continues on. I have to click on the message to dismiss it. Is this a known issue? (This is again for a very large notebook of many GB, so I can't tell on which specific note it is throwing this error.)

8

Does the message provide any additional information that could help locate the note or notebook?

9

That is the complete error message. It doesn't say which note in the notebook caused it.