<feed xmlns='http://www.w3.org/2005/Atom'>
<title>asciideck.git/test, branch master</title>
<subtitle>Asciidoc for Erlang.
</subtitle>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/'/>
<entry>
<title>Fix table cells containing blocks</title>
<updated>2018-06-12T16:35:54+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2018-06-12T05:45:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=9224a497d79acbb8ce5690bf8dd9e19855e50586'/>
<id>9224a497d79acbb8ce5690bf8dd9e19855e50586</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add source-highlight support to HTML output</title>
<updated>2018-06-11T20:21:36+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2018-06-11T20:21:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=dbb935a5972350f734d4abcf31c03f9e54bbd1d4'/>
<id>dbb935a5972350f734d4abcf31c03f9e54bbd1d4</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Rewrite the project</title>
<updated>2018-06-08T12:49:09+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2018-06-08T12:49:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=524777054be30c848c1883ffd15b245c29f73004'/>
<id>524777054be30c848c1883ffd15b245c29f73004</id>
<content type='text'>
The new code is much more readable and easier to extend. I took
inspiration from Haskell's Parsec project which seems to only
write the happy-path and applied the idea to Erlang's exceptions.
When the parser tries to parse, say, a list, and crashes, it
tries with a table next, and so on until something matches.
Normal paragraphs always match so there can be no parsing
failures.

The parser now has a number of passes: first the block parser,
then lists and tables passes to build a proper tree out of
them and finally an inline pass to apply inline formatting.
The resulting AST can then be modified at will and passed on
to translator modules which output a different format.

The man page translator was also rewritten and has been tested
against both Cowboy and Gun. Numerous issues were fixed as a
result of this rewrite.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The new code is much more readable and easier to extend. I took
inspiration from Haskell's Parsec project which seems to only
write the happy-path and applied the idea to Erlang's exceptions.
When the parser tries to parse, say, a list, and crashes, it
tries with a table next, and so on until something matches.
Normal paragraphs always match so there can be no parsing
failures.

The parser now has a number of passes: first the block parser,
then lists and tables passes to build a proper tree out of
them and finally an inline pass to apply inline formatting.
The resulting AST can then be modified at will and passed on
to translator modules which output a different format.

The man page translator was also rewritten and has been tested
against both Cowboy and Gun. Numerous issues were fixed as a
result of this rewrite.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix an issue in Ranch manual</title>
<updated>2016-11-26T15:58:49+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2016-11-26T15:58:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=074e21e93abf0eec59973cc35c9d2755d4a921f9'/>
<id>074e21e93abf0eec59973cc35c9d2755d4a921f9</id>
<content type='text'>
Solution is a hack for now, unfortunately.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Solution is a hack for now, unfortunately.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add a check for mandatory name section for man pages</title>
<updated>2016-10-31T17:30:26+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2016-10-31T17:30:26+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=00a7d8d6e6125c171c46190bdb40ecaa08347cca'/>
<id>00a7d8d6e6125c171c46190bdb40ecaa08347cca</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix the AST and add tests for formatting</title>
<updated>2016-10-18T16:04:35+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2016-10-18T16:04:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=b534d457c3813c4c2d905a04f6183e7317d66720'/>
<id>b534d457c3813c4c2d905a04f6183e7317d66720</id>
<content type='text'>
Also opened the way to making configurable quoted text elements,
like the original Asciidoc allows. We could potentially end up
allowing users to define different types of quotes producing
custom AST.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Also opened the way to making configurable quoted text elements,
like the original Asciidoc allows. We could potentially end up
allowing users to define different types of quotes producing
custom AST.
</pre>
</div>
</content>
</entry>
<entry>
<title>Initial commit</title>
<updated>2016-10-17T17:28:40+00:00</updated>
<author>
<name>Loïc Hoguin</name>
<email>essen@ninenines.eu</email>
</author>
<published>2016-10-17T17:09:01+00:00</published>
<link rel='alternate' type='text/html' href='http://git.ninenines.eu/asciideck.git/commit/?id=df08a3f430bf7727921873ab262294a054e2ae7b'/>
<id>df08a3f430bf7727921873ab262294a054e2ae7b</id>
<content type='text'>
This is still very much in a proof of concept state, though
the project should be in a good enough state that future
additions are relatively painless.

Text formatting nodes are not using the proper form in the
AST at the moment. They should not be relied upon just yet.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is still very much in a proof of concept state, though
the project should be in a good enough state that future
additions are relatively painless.

Text formatting nodes are not using the proper form in the
AST at the moment. They should not be relied upon just yet.
</pre>
</div>
</content>
</entry>
</feed>
