https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet This page is misleading for tables in a couple particulars: No whitespaces is required around | delimiter characters Page has been updated to cover these, but to stress important points: Parser looks for internal pipes. Leading and trailing pipes are unnecessary Need just 3 hyphen characters for header/body separation : outside of dashes specifies L/R/C justification Contemplating supporting Markdown syntax http://daringfireball.net/projects/markdown/syntax#list Implementations https://sourceforge.net/p/forge/documentation/markdown_syntax/ http://stackoverflow.com/editing-help https://help.github.com/articles/github-flavored-markdown Operator to specify my customization values Like stackoverflow.com's syntax highlighting operation :::metadata Like Sourceforge's code language specifier [[macroname attr1=val1 attr2=val2]] Used generally on Sourceforge Perhaps biggest diff from Creole is that is generally permitted. Markdown text is scanned for angle brackets of HTML tags, and they are not escaped. # not for lists nor for . There are conflicting differences between https://help.github.com/articles/github-flavored-markdown and http://stackoverflow.com/editing-help E.g. syntax highlighting. Github style (don't indent): ```ruby ... ``` vs. non-Github style (must indent) Biggest diff for GFM (GitHub-Format) format is that internal newlines are significant. For regular, end line with " " to generate a
. Sourceforge only has [TOC] for the obvious purpose. Sourceforge only has [[include ref=SamplePage]] List List operators must be followed by blank line. This distinguishes from inlines. Must be preceded by a blank line. Says this, but untrue. UNTRUE Blank lines between items cause items to be

-wrapped. (How many and where blank lines are required seems unspecified) Follow-up paragraphs must begin with 4 spaces To embed code or blockquotes, just add 4 spaces before your operator. Ident "another" 4 spaces for nested list elements No way to do non-code pre-formatting. :( Looks like Sourceforge Markdown does not assume code. Need to check what HTML gets created. Code Non-Github: Prefix every line by 4 spaces, which will be subtracted. vs: Github "```[type]" line to "```" line. Markdown disabled in here. Blockquotes are just offset and marked. No Markdown disabling. Paired operators must be closed and may not span block elements. An `inline code` span. Aka console. similar to monospaced font, but also disables Markdown interpretation. Can also use ``double backticks/quotes``, which is required for an embedded backtick. Escaping generally \, but ` escaped with ``. Check how to escape HTML tags on the others. Sourceforge requires you to enter character entity codes. URLs inside of <> to make explicit (for self-labeled). [implSpecificArtifactLinks] Tables. Dashes and pipes and MUST FULLY UNDERSCORE HEADER LINE FIELDS. (What do I mean by that??? I think need 3 ---s for each column is all.) No initial pipe. Header line and underscore line required. prefix and/or suffix the ---s with : to specify justification for that col. Headers # style generally. == and -- underscore for h1 and h2. --- or more for hr. Must follow a blank line. [URL label](http://url "Tool tip text") The URL may just be a case-insensitive reference defined elsewhere like: [reference]: http://the.url "tool tip" Image same but preceded by ! Label is used for alt text. file: URLs don't work, but plain non-URL paths work right. GitHub style footnotes (also work for NPM) use [^x] where x may be any arbitrary distinctive digit or letter (don't know if multiple characters would work). The system re-numerates them to be indexes beginning with 1.