fletcher / multimarkdown Goto Github PK

|col1 |col2 |
|:---|:---|
|>hello|blockquote|

# Einleitung #

Welsch räumt in seinem Aufsatz auch eventuelle Einwände
gegen das Konzept, das eine Uniformierung erbringen könnte,
ein. Er geht darauf ein, dass die Vielheit in Form von
Einzelkulturen verschwinden wird.[^fn24] Ein neuer Typus von
Vielheit von Kulturen und Lebensformen würde in
transkulturellen Kombinationen entstehen.[^fn25]



[^fn23]: [71–79][#welsch_transkulturalitat._1997].

[^fn24]: [77][#welsch_transkulturalitat._1997] oder nur als
simulierte Eigenheit, in Form von Folklore vorkommen werden
[72][#welsch_transkulturalitat._1997].

[^fn25]: [78–79][#welsch_transkulturalitat._1997].

\begin{equation}
    E = m c^2
\end{equation}

\begin{equation}
    E = m c<sup>2</sup>
\end{equation}

sh: pdflatex: command not found
sh: bibtex: command not found
sh: makeindex: command not found
sh: kpsewhich: command not found
sh: makeindex: command not found
sh: pdflatex: command not found
sh: pdflatex: command not found
sh: pdflatex: command not found
sh: pdflatex: command not found

 # Chapter Title [] #

 <h1>Chapter Title</h1>

 <h1 id="chaptertitle">Chapter Title</h1>

<!-- 
\begin{table}[h]
\caption{Swanson's dimensions of maintenance}
\centering
\label{tbl:swanson}
\begin{tabular}{c|c}
[body of table]
\end{tabular}
\end{table} 
-->
We can shorten this table to identify the cause of change as either a) the system 
wasn’t       implemented properly; b) some assumption was incorrect; 
c) let’s improve the system.

H~2~O is a liquid.  2^10^ is 1024.

For most cases[^fn1], the procedure will produce sensible results.

[... later in the document ...]

In a few particular cases[^fn1], one should...

[... more of the document follows... ]

We have achieved satisfactory results for the general situation[^fn1].

## Footnotes

[^fn1]: there are a few exceptions: foos, bars, and bazes.

<p>For most cases<a href="#fn:fn1" id="fnref:fn1" class="footnote">1</a>, the procedure will produce sensible results.</p>

<p>[... later in the document ...]</p>

<p>In a few particular cases<a href="#fn:fn1" id="fnref:fn1" class="footnote">2</a>, one should...</p>

<p>[... more of the document follows... ]</p>

<p>We have achieved satisfactory results for the general situation<a href="#fn:fn1" id="fnref:fn1" class="footnote">3</a>.</p>

<h2 id="footnotes">Footnotes</h2>

<div class="footnotes">
<hr />
<ol>

<li id="fn:fn1"><p>there are a few exceptions: ...<a href="#fnref:fn1" class="reversefootnote">&#160;&#8617;</a></p></li>

<li id="fn:fn1"><p>there are a few exceptions: ...<a href="#fnref:fn1" class="reversefootnote">&#160;&#8617;</a></p></li>

<li id="fn:fn1"><p>there are a few exceptions: ...<a href="#fnref:fn1" class="reversefootnote">&#160;&#8617;</a></p></li>

</ol>
</div>

This is BibTeX, Version 0.99c (Web2C 7.5.6)

I found no \bibdata command---while reading file scriv.aux

I found no \bibstyle command---while reading file scriv.aux

%   Bibliography
\bibliographystyle{\mybibliostyle}
\bibliocommand

homepage

:   The official home of this project on the web.

bugtracker
:   This entry describes the bug tracking system for this distribution. It is
    a [Map](#Map) with the following valid keys:

    web
    :   a <a href="#URI">URI</a> pointing to a web front-end for the bug
        tracker

    mailto
    :   an email address to which bug reports can be sent

repository
:   This entry describes the source control repository for this distribution.
    It is a [Map](#Map) with the following valid keys:

    url
    :   a [URI](#URI) pointing to the repository itself

    we
    :   a [URI](#URI) pointing to a web front-end for the repository

    type
    :   a lowercase string indicating the VCS used

:   Because a URI like `http://myrepo.example.com/` is ambiguous as to type,
    producers should provide a `type` whenever a `url` key is given. The
    `type` field should be the name of the most common program used to work
    with the repository, e.g. git, svn, cvs, darcs, bzr or hg.

<dl>
<dt>homepage</dt>
<dd>
<p>The official home of this project on the web.</p>
</dd>

<dt>bugtracker</dt>
<dd>
<p>This entry describes the bug tracking system for this distribution. It is
a <a href="#Map">Map</a> with the following valid keys:</p>
</dd>

</dl>

<pre><code>web
:   a &lt;a href="#URI"&gt;URI&lt;/a&gt; pointing to a web front-end for the bug
    tracker

mailto
:   an email address to which bug reports can be sent</code></pre>

<dl>
<dt>repository</dt>
<dd>
<p>This entry describes the source control repository for this distribution.
It is a <a href="#Map">Map</a> with the following valid keys:</p>
</dd>

</dl>

<pre><code>url
:   a [URI](#URI) pointing to the repository itself

we
:   a [URI](#URI) pointing to a web front-end for the repository

type
:&lt;dl&gt;</code></pre>

<p><dt>a lowercase string indicating the VCS used</dt>
<dd></p>

<p>Because a URI like <code>http://myrepo.example.com/</code> is ambiguous as to type,
producers should provide a <code>type</code> whenever a <code>url</code> key is given. The
<code>type</code> field should be the name of the most common program used to work
with the repository, e.g. git, svn, cvs, darcs, bzr or hg.</p>

<p></dd></p>

<p></dl></p>

<dl>
<dt>homepage
</dt>
<dd>
<p>The official home of this project on the web.</p></dd>

<dt>bugtracker
</dt>
<dd>
<p>This entry describes the bug tracking system for this distribution. It is
 a <a href="#Map">Map</a> with the following valid keys:</p>
<dl>
<dt>web
</dt>
<dd>a <a href="#URI">URI</a> pointing to a web front-end for the bug
 tracker</dd>

<dt>mailto
</dt>
<dd>an email address to which bug reports can be sent</dd>
</dl>
</dd>

<dt>repository
</dt>
<dd>
<p>This entry describes the source control repository for this distribution.
 It is a <a href="#Map">Map</a> with the following valid keys:</p>
<dl>
<dt>url
</dt>
<dd>a <a href="#URI">URI</a> pointing to the repository itself</dd>

<dt>we
</dt>
<dd>a <a href="#URI">URI</a> pointing to a web front-end for the repository</dd>

<dt>type
</dt>
<dd>a lowercase string indicating the VCS used</dd>
</dl>
</dd>

<dd>
<p>Because a URI like <code>http://myrepo.example.com/</code> is ambiguous as to type,
 producers should provide a <code>type</code> whenever a <code>url</code> key is given. The
 <code>type</code> field should be the name of the most common program used to work
 with the repository, e.g. git, svn, cvs, darcs, bzr or hg.</p></dd>
</dl>

Processing: ./foo.tex

Document Class: memoir 2013/05/22 v3.7 configurable book, report, article document class

Latex Error: /usr/local/texlive/2013/texmf-dist/tex/latex/manuscript/manuscript.sty:66 Undefined control sequence.

Latex Error: /usr/local/texlive/2013/texmf-dist/tex/latex/manuscript/manuscript.sty:79 Undefined control sequence.

Latex Error: /usr/local/texlive/2013/texmf-dist/tex/latex/manuscript/manuscript.sty:84 Extra \else.

Latex Error: /usr/local/texlive/2013/texmf-dist/tex/latex/manuscript/manuscript.sty:90 Extra \fi.

Latex Error: /Users/fonnescj/.texmf/tex/latex/mmd/mmd-manuscript-begin-doc.tex:33 Undefined control sequence.

Latex Error: /Users/fonnescj/.texmf/tex/latex/mmd/mmd-manuscript-begin-doc.tex:34 Undefined control sequence.

Latex Error: /Users/fonnescj/.texmf/tex/latex/mmd/mmd-manuscript-begin-doc.tex:36 Undefined control sequence.

Latex Error: /Users/fonnescj/.texmf/tex/latex/mmd/mmd-manuscript-begin-doc.tex:40 Undefined control sequence.

Latex Error: /Users/fonnescj/.texmf/tex/latex/mmd/mmd-manuscript-begin-doc.tex:62 Font \body="Courier New" at 12.0pt not loadable: Metric (TFM) file not found.

pdfTeX warning (ext4): destination with the same identifier (name{page.1}) has been already used, duplicate ignored

LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.

(see the transcript file for additional information)pdfTeX warning (dest): name{section.1.1} has been referenced but does not exist, replaced by a fixed one

pdfTeX warning (dest): name{section*.1} has been referenced but does not exist, replaced by a fixed one

 This is the first footnote.[^note1] Here's some text.

 This is the second footnote.[^note2] Here's some other text.

 This is the third footnote.[^note3]  Here's some other text again.

 This is the fourth footnote.[^note4]  Here's some other text many more times.

[^note1]: Hello.
[^note2]: World.
[^note3]: See you later.
[^note4]: Good bye.

1. Hello. [^note2]: World. [^note3]: See you later. [^note4]: Good bye.  ↩

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna[^2] aliqua. Ut enim ad minim [veniam][test1], quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla [pariatur][test2]. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

[test1]: www.example1.com
[test2]: www.example2.com

Lorem ipsum[^1] [dolor][test3] sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna[^2] aliqua. Ut enim ad minim [veniam][test1], quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla [pariatur][test2]. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

[test1]: www.example1.com
[test2]: www.example2.com
[^1]: This is a footnote  
[^2]: This is another footnote
[test3]: www.example3.com

[test1]: www.example1.com
[test2]: www.example2.com

[^1]: This is a footnote 

[^2]: This is another footnote

[test3]: www.example3.com

[name]_[first word of title]_[year]

[][#_frei_2009]

-:502: parser error : Unescaped '<' not allowed in attributes values
<li id="fn:fn40"><p><span class="externalcitation"> (<a id="<em>frei</em>2009"><
                                                            ^
-:502: parser error : attributes construct error
<li id="fn:fn40"><p><span class="externalcitation"> (<a id="<em>frei</em>2009"><
                                                            ^
-:502: parser error : Couldn't find end of Start Tag a line 502
<li id="fn:fn40"><p><span class="externalcitation"> (<a id="<em>frei</em>2009"><
                                                            ^
-:502: parser error : Opening and ending tag mismatch: span line 502 and a
<span class="externalcitation"> (<a id="<em>frei</em>2009"><em>frei</em>2009</a>
                                                                               ^
-:502: parser error : Opening and ending tag mismatch: p line 502 and span
ass="externalcitation"> (<a id="<em>frei</em>2009"><em>frei</em>2009</a>)</span>
                                                                               ^
-:502: parser error : Opening and ending tag mismatch: li line 502 and p
ef:fn40" title="return to article" class="reversefootnote">&#160;&#8617;</a></p>
                                                                               ^
-:502: parser error : Opening and ending tag mismatch: ol line 422 and li
n40" title="return to article" class="reversefootnote">&#160;&#8617;</a></p></li
                                                                               ^
-:504: parser error : Opening and ending tag mismatch: div line 420 and ol
</ol>
     ^
-:505: parser error : Opening and ending tag mismatch: body line 27 and div
</div>
      ^
-:506: parser error : Opening and ending tag mismatch: html line 5 and body
</body>
       ^
-:507: parser error : Extra content at the end of the document
</html>
^
unable to parse -

| heading | heading | heading |
|--------:|:--------|:--------|
| cell    |   **long cell**   |

&cell&\multicolumn{2}{c}{\textbf{long cell}}\\

&cell&\multicolumn{2}{l}{\textbf{long cell}}\\

echo "<div markdown=\"1\">
# Example

Paragraph wraps closing div tag:
</div>" | ./multimarkdown

<div>
<h1 id="example">Example</h1>

<p>Paragraph wraps closing div tag:</p>
</div>

<div>

<h1 id="example">Example</h1>

<p>Paragraph wraps closing div tag:
</div></p>

<p></div></p>

unless (my $return = eval `cat "$file"`) {

'cat' is not recognized as an internal or external command,
operable program or batch file.
couldn't do C:/Program Files/MultiMarkdown/bin/MultiMarkdown/Support.pm:  
at C:\Program Files\MultiMarkdown\bin\mmd2XHTML.pl line 153.
couldn't run C:/Program Files/MultiMarkdown/bin/MultiMarkdown/Support.pm 
at C:\Program Files\MultiMarkdown\bin\mmd2XHTML.pl line 154.

<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <!-- Processed by MultiMarkdown -->
        <meta name="Format" content="complete
Hello World!" />
    </head>
<body>


</body>
</html>

\chapterstyle{\mychapterstyle}
\pagestyle{\mypagestyle}

 (/usr/local/texlive/2008/texmf/tex/latex/config/color.cfg))
 ! Missing \endcsname inserted.

 Title: Test 
 Author: David Green  
 Date: 07 September 2009  
 Format: complete  
 LaTex xslt: article  
 Base Header Level: 2  

 Task - Model a Digital Logic
 ============================

 The purpose of this program is to model some simple digital logic --
 a register and a counter.

You are not required to use a locator (e.g. p. 23), and there are
no special rules on what can be used as a locator if you choose
to use one.

You are not required to use a locator (e.g. p. 23), and there are
no special rules on what can be used as a locator if you choose
to use one. If you prefer to omit the locator, just use an empty
set of square brackets before the citation:

    This is a statement that should be attributed to its 
    source[][#Doe:2006].

some text [^this is a footnote]

more text [^this is
not]

![Figure 1: Useful technology for the present and the future.[^fn-figure_1]](/image/path)

[^fn-figure_1]: *Big data, Analytics and the Path from Insights to Value*, MIT Solan management review, Winter 2011.

<figure>
<img src="" alt="Figure 1: Useful technology for the present and the future.*Big data, Analytics and the Path from Insights to Value*, MIT Solan management review, Winter 2011.

fn-figure_1" />
<figcaption>Figure 1: Useful technology for the present and the future.<a href="#fn:*Big data, Analytics and the Path from Insights to Value*, MIT Solan management review, Winter 2011.

" title="see footnote" class="footnote">[*Big data, Analytics and the Path from Insights to Value*, MIT Solan management review, Winter 2011.

]</a></figcaption></figure>

![[Figure 1: Useful technology for the present and the future.][^fn-figure_1]](/image/path)

[^fn-figure_1]: *Big data, Analytics and the Path from Insights to Value*, MIT Solan management review, Winter 2011.

<p>![[Figure 1: Useful technology for the present and the future.]<a href="#fn:1" id="fnref:1" title="see footnote" class="footnote">[1]</a>]()</p>

| Año | Facturación |  
| ---- | -----------: |  
| 2011 |     3.000€ |  
| 2012 |    15.000€ |  

[my label][1]

[1]: http://example.com/ "title here" class=myclass

<xsl:template match="html:em">
    <xsl:text>\emph{</xsl:text>
    <xsl:apply-templates select="node()"/>
    <xsl:text>}</xsl:text>
</xsl:template>