![]() ![]() (This is one instance where data would be lost, if that # bar was important for some reason.) (NOTE: The MMD metadata base header level allows you to modify the #'s to 's conversion. # bar following # foo), but the newer version effectively corrects it to # bar. Older versions would strip “incorrect” levels (e.g. Markdown headings ( # Foo #) become levels in the outline. When writing more complex documents, it’s trivial for me to have the editor and mind-mapping windows side by side and see changes reflected immediately in both windows. The primary goal for this was to be able to simultaneously work on a single document in MultiMarkdown Composer (for text editing) and an outliner or mind mapping tool (for visualizing the structure of the document and being able to rearrange it quickly and easily). For my needs, the OPML format was more flexible, and allows support for users of Linux and Windows machines.)Īn important requirement for this effort was to be able to take any plain text MultiMarkdown file, convert it to OPML, convert that OPML back to plain text, and end up with an identical file to what one started with. Assuming that format is still similar to the XML format it used to be, that would not be difficult to add. (NOTE: MultiMarkdown-6 supports OPML but does not currently support the native OmniOutliner file format directly. I wanted OPML to become a “first class” document format for MMD, and this required a couple of “tricks”. This newer spec allows safe “round-tripping” between plain text and OPML without losing information, assuming a “valid” document. The same conventions were further refined in MultiMarkdown version 6, which has built-in read/write support for OPML (as well as iThoughts’ ITMZ format). In 2005 I wrote a plugin for OmniOutliner to export as Markdown/MultiMarkdown. Stumbled across this thread, and figured I would add that MultiMarkdown does have an official MMDOPML “spec.” I don’t think I’ve likely said anything particularly new here, but wanted to keep the conversation alive, perhaps provide some clarity to people at Omni Group, and give other Markdown users something with which to agree or disagree ) Again, I imagine this would call for some configuration options. (And, in my opinion, bonus points if the tag characters are hidden, except when the node is being edited.)Įxporting of OO outlines to Markdown files, regardless of column types. A Markdown column could behave much as a Rich Text column, but adding support for **bold** and _italic_ tags. ![]() I haven’t considered this deeply, but perhaps it could be handled with a new “Markdown” column type, which is essentially how Outlinely handles it. ![]() Importing of Markdown text into OO, which will likely call for some configuration options, much as discussed above regarding iThoughts. Some users would be happy with one or two of these, while many are going to want all three: I love working with Markdown, as it is certainly a powerful-but-simple “lingua franca” for passing somewhat-structured, lightly-formatted data amongst various software packages and platforms.Īs I see it, when someone says “I want Markdown support,” they can mean three different things. Here’s my $.02 worth regarding Markdown support, for what it’s worth. It seems like including a markdown export feature would be pretty simple, in the grand scheme of things-why not just believe your customers when they say this would be a desirable feature? The fact that people are resorting to pairing Hazel with Pandoc should tell you something about how much a simple export feature would help. The richtext and Docx exports are actually extremely useless to me, and the plaintext with tab indentation even more so. A direct export to markdown would make it much more useful for me, because I want to be able to get my rough outline (written in OO) into Ulysses and then fill it out there, with minimal rigmarole in export. I basically love the look and feel of your product. As far as I can see, the response has been to basically skirt those concerns and blame the fact that no single set of preferences exist for how they would be implemented. There seem to be a lot of customers basically saying, “this is an important feature and would make my experience of this product better”. I’ll be honest, the developer replies in this forum have been really discouraging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |