Markdeep has some very nice features. I love to be able to have more expressiveness than in regular markdown.<p>But I am not so sure about the diagramming feature. Writing diagrams as ascii art seems like a PITA to me, especially when you need to update a diagram with new shapes, etc.<p>For this I prefer PlantUML markdown integration: <a href="http://plantuml.com" rel="nofollow">http://plantuml.com</a><p>I use VS Code and it has a nice plugin to handle this.
To go beyond generic Wiki syntax, SGML lets you define context-specific token replacement rules. For example, to make SGML format a simplistic markdown fragment into HTML, you could use an SGML prolog like this:<p><pre><code> <!DOCTYPE p [
<!ELEMENT p - - ANY>
<!ELEMENT em - - (#PCDATA)>
<!ENTITY start-em '<em>'>
<!ENTITY end-em '</em>'>
<!SHORTREF in-p '*' start-em>
<!SHORTREF in-em '*' end-em>
<!USEMAP in-p p>
<!USEMAP in-em em>
]>
<p>The following text:
*this*
will be put into EM
element tags</p></code></pre>
Something I haven't seen in any markdown editor so far (suggestions welcome) is extended table support.<p>Say I have a table with a 'name' and 'value' column and 100 entries. And I'd like names to be alphabetically sorted. So far so good.<p>But this table is too long and too small, so I want to have 4 columns and 50 rows, where the name/value continue in column 3, 4. Out of luck. This is unmanageable, as you have to shift many cells when adding a new entry.<p>A proposal for something like this: <a href="https://github.com/github/markup/issues/1189" rel="nofollow">https://github.com/github/markup/issues/1189</a><p>Also mentions multi-line cell contents, which are hard in regular markdown (require inline html)..
Hartl’s Tenth Rule of Typesetting:<p>"Any sufficiently complicated typesetting system contains an ad hoc, informally specified, bug-ridden, slow implementation of half of LATEX."<p>Markdeep is no exception.<p><a href="http://manual.softcover.io/book/softcover_markdown#cha-softcover_flavored_markdown" rel="nofollow">http://manual.softcover.io/book/softcover_markdown#cha-softc...</a>
Well the whole point of markdown is that it is simple enough so that devs easily document whatever necessary. As you know documentation is notoriously neglected by the developers. But this is not that simple. I doubt it will be adopted that much.
I really like the idea of a new markup format. To me markdown has been very unintuitive in some ways. I can never remember whether more # means higher or deeper header level. Or which of - - - or === makes a first or second level header. But since markdown is first class citizen at github, I don’t think we’ll ever be able to see any real competition rise up (even though github has first class support for others, markdown is the clear winner). And I’ve never heard anyone else mention these confusions so maybe everyone else is fine with it and I’m the only one who wants an alternative.
I really wish people would simply forget about markdown and restart with a slightly more sensible and extensible markup. I personally always thought that some sort of latex/context with a simple markup for common commands would be more useful.
This sounds pretty cool. My own workflow is so pandoc-dependent though that I don't think I could use it unless someone who is much better at Haskell than I am works the markdeep extensions into pandoc :-(
The day I find one of these mark* languages that supports poetry -- which simply means, a section in which it respects literal indents and line-breaks, but not by dropping into monospace font -- I'll use it.<p>N.B. the online publishing platform Leanpub has its own mark* variant, "markua"[1] which actually does recognize a poem section -- although as implemented it has minor formatting issues.<p>[1] <a href="https://leanpub.com/markua/read" rel="nofollow">https://leanpub.com/markua/read</a>
I think anyone would agree that Markdown the sna bit too simplistic, and while Markdeep looks cool, it seems like it ends up at the opposite extreme with too much complexity.
Similar <a href="https://ivanceras.github.io/svgbob-editor/" rel="nofollow">https://ivanceras.github.io/svgbob-editor/</a>
From 2015: <a href="https://news.ycombinator.com/item?id=10402121" rel="nofollow">https://news.ycombinator.com/item?id=10402121</a>
Shameless plug: <a href="http://write.pub" rel="nofollow">http://write.pub</a> supports most of the features of MarkDeep, and allows WYSIWYG writing.<p>It also shows with built in version control, you don't have to know git to use it
Markdown is cool because it's minimalistic.<p>Markdeep might be a good idea, but if you start adding more and more feature you reimplement HTML, at that point why not simply use HTML? Isn't HTML plain text, too?