6 replies to this topic

[David Chevenement]

Dear Evernote team

We're currently doing some try and research using your API to export Beesy's notes to Evernote.

What we do is use the Beesy HTML export format to generate ENML for Evernote.
It's going quite OK except that we have some question regarding the ENML format validation scheme on you side.

Indeed, when using HTML, we did used standard and widely available HTML tags such as BR, B, TABLE and things like that.
We tend to use upper case strings in our code to distinguish HTML tags from the actual message we display.
Unfortunately, it looks like your ENML validation is waiting for lower case strings as ENML valid tags.

Could you confirm this is the case ?

If this is so, you should update the ENML page for valid tags and put lower case tags instead of upper case ones.

Thanks for your help,

Kind regards,
David

[AndyDent]

Yes, that's a good suggestion, the uppercase tags on that page are a bit misleading.

As the ENML page says: ENML is formally defined in http://xml.evernote.com/pub/enml2.dtd which as you point out, uses lowercase tags.

[David Chevenement]

Thanks Andy.
Sure, that what we thought by having a look at it, but we weren't sure if there was any typo conversion in the process.
This should be stressed out in the docs as currently it's UPPER CASE mentioned

Anyhow, it's just a matter of not loosing time trying to discover how things are done behind the scene.

Also, it should be mentioned that you MUST close any OPENING TAG with a CLOSING TAG.
not so obvious when you're used to implement <BR> and <HR> for instance.

I just thought we might share the info if it can help some others and maybe update the doc on ENML.

[jefito]

Also, it should be mentioned that you MUST close any OPENING TAG with a CLOSING TAG. not so obvious when you're used to implement <BR> and <HR> for instance.

ENML, being based on XHTML, rather than HTML, required tags to be closed.

[David Chevenement]

Thanks Jeff for this precision.
No pb, just thought that we should share our early mistakes with XHTML validation and how it could differ from HTML for those of us less familiar with the first one.

Thanks to both of you for clearing this out anyhow.

David

[SethH]

David, thanks for the feedback. I updated the capitalization in the list of permitted and prohibited items on the ENML page, and added a couple of notes at the top of the page. As the others have said, because ENML is based on XHTML, it's much more strict than, say, the HTML accepted by a browser.

[David Chevenement]

thank you for that, I was not that familiar with XHTML so spent some time with the validation process when posting notes.
Just thought might be worth sharing, thanks for the info and the update

David