Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend ENML converter API to allow for for importing ENEX from file as well as string #62

Open
d1vanov opened this issue Jul 10, 2018 · 0 comments
Assignees

Comments

@d1vanov
Copy link
Owner

d1vanov commented Jul 10, 2018

See d1vanov/quentier#179: due to wrong encoding the ENEX file contents were not read correctly. It appears than currently all ENEX files use UTF-8 encoding, however, there's seems to be no official Evernote documentation which would guarantee that would always be the case. If, for example, the file is encoded using UTF-16, the only correct way to process it would be to pass it to QXmlStreamReader inside ENMLConverter in its original form, so the encoding can be detected automatically. For this to be doable the extension of existing ENML conversion API is required: it needs to accept not only ENEX string but also ENEX file i.e. QFile handle for the actual file.

@d1vanov d1vanov self-assigned this Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant