> I don't see how Markdown and plain text are equivalent. Sure, Markup is done using plain text (so is HTML), but that's not what it represents. You don't get Markdown automatically if you have plain text (ask my text editor). It has to be interpreted. You can store Markdown and HTML in a note already. Is that what's wanted? I don't think so
This is mixing two things again, storing markdown is the same as storing text which is the same as storing the current HTML content. Like I said above this shouldn't be a problem (you can do it now). The other thing is how, as I said above, to displaying it. Here you have to differ between three different markups:
Plain text - already possible
HTML - already possible
It's the last one where I'm a bit different from many others who ask for Markdown support. I have no need for built-in rendering of markdown I'm fine with a plain text display of markdown notes. I just want an efficient way of working with plain text files in Evernote (so in reality I don't need any special markdown support at all). From my experience with other programs (for example VoodooPad, Devonthink), the most efficient way of working with an external editor is to use the ODB Editor protocol (on the Mac).
> ENML Format: XHTML subset, with augmentation. See http://dev.evernote.com/doc/articles/enml.php.
> More than one note can be stored per file (easy enough to do, at least in the Windows client, and probably the Mac. Select some notes and export them -- they'll come out as one file.
Yes, it looks like then the separate notes are stored as XML notes "within" the multinote file ... interesting.
> I believe it's a practical decision, based on technical reasons. See, e.g., post #5 in this topic: http://discussion.evernote.com/topic/33759-markdown-wysiwyg-support-plz/?p=40681, post #14 http://discussion.evernote.com/topic/33759-markdown-wysiwyg-support-plz/?p=64718 and so on. They can't provide a full editing experience with Markdown, so it's unlikely to happen. That could change, I do understand.
That I understand and I'm OK with that (others might not like it), as I said above, I just want to use Evernote as a "storage database" for text. Of course, this can be done by any text editor by implementing support for Evernotes API - which is unlikely to happen. However, on the Mac many text editors support the ODB Editor protocol which would mean that if Evernote implemented support for it, these editors would all get the ability to work efficiently with text files (= click a button in Evernote to edit with external editor, when I save in my text editor Evernote sees the changes and updates the note).
As for iOS, the text editor would have to implement support for the Evernote API.
I'm pretty sure that we will never see support for the ODB Editor protocol for reasons given in a previous post. Some iOS editor might implement support for using Evernote as the storage backend (there are a couple of note takers but I haven't seen a text editor). I haven't seen a Mac text editor that uses the Evernote API (does one exist?).
In short, I'll probably never see what I'm looking for ... but I can dream