Closed GoogleCodeExporter closed 8 years ago
Would have created this as an "Enhancement" if I could figure out how, sorry.
Anyway,
it appears that to convert the Markdown reader for basic Textile features would
in
some cases be a matter of changing which characters are interpreted as strong,
emph,
bulleted lists, ordered lists, etc. I may use this particular desire of mine as
an
impetus to learn some Haskell and work on it myself. ;-)
Original comment by buzzinea...@gmail.com
on 23 Jan 2008 at 9:52
I agree, this would be nice (both a reader and a writer). Textile
supports some features that are not currently possible in Pandoc,
and vice versa, but most things should work fine, and in many ways
Textile syntax will be easier to parse than Markdown.
It's not a high priority for me, because I never use Textile.
But if you want to give it a shot, feel free! I can answer questions
you might have in understanding the code.
Original comment by fiddloso...@gmail.com
on 24 Jan 2008 at 4:11
The easiest way to do this would be to modify the MediaWiki writer. MediaWiki
treats
lists similarly, and like the MediaWiki writer, a Textile writer would have to
revert
to HTML for complicated nested things. All the logic is already in place in
the
MediaWiki writer, so producing a Textile writer should be pretty easy.
Original comment by fiddloso...@gmail.com
on 11 Nov 2008 at 3:37
Textile reader available on this branch :
http://github.com/paul-r-ml/pandoc/tree/textile-reader
(not fully complete as of today)
Original comment by paul.riv...@gmail.com
on 16 Sep 2010 at 2:33
Glad to see there's progress! A test suite will be essential if this is to be
included in pandoc. You can use the existing reader and writer tests as a
model.
Original comment by fiddloso...@gmail.com
on 25 Sep 2010 at 6:55
I have pushed the thing a bit further, and it now handles most of the syntax,
with the notable exception of footnotes. I may add support anytime soon if
someone asks for it, I just avoided it so far because I don't know yet how to
play well with the parser threaded state.
Also, I am not sure I really understand how to use the test suite, but at least
there is something to test. Let me know if it must be more polished.
Original comment by paul.riv...@gmail.com
on 5 Oct 2010 at 2:29
Reader and writer have both been added to master.
There is still room for improvement -- some features remain to be implemented
in the reader -- but since this bug was for adding textile support, I'll close
it.
Original comment by fiddloso...@gmail.com
on 7 Dec 2010 at 6:49
Original issue reported on code.google.com by
buzzinea...@gmail.com
on 23 Jan 2008 at 9:46