As an alternative to Pandoc, you might consider Kramdown. It's a Ruby gem that
converts Markdown to several other formats, including LaTeX. It's not difficult
to write new backends for it, and has the advantage of being way less
intimidating than Haskell. I've written a simple backend that generates
InDesign tagged text, and it was pretty easy.
http://kramdown.rubyforge.org
--John
On 19 Dec 2012, at 1:05 PM, Behdad Esfahbod <[email protected]> wrote:
> On 12-12-19 12:59 PM, Werner LEMBERG wrote:
>>
>>> Didn't know about pandoc. Thanks for the pointer.
>>
>> Well, it's written in Haskell, even more intimidating than Scheme :-)
>>
>> Its author, however, is very responsive, and I can imagine that he can
>> add support for features you probably need $(Q#|(B or help you in writing a
>> JSON filter as described in the documentation.
>>
>> For example, I've done this to make a Markdown document insert SVG
>> images if converted to HTML and PDF `images' if converted to LaTeX.
>
> Interesting. Reminds me that... we don't have any docs in HarfBuzz. For API
> reference I think we're good using gtk-doc. But for developer documentation
> (more like a book), I don't know what the best toolchain is these days. I
> sure don't like writing XML.
>
> Markdown sure looks the cleanest.
>
> Shaun, any ideas? What do you guys do for GNOME these days? Whatever that
> is, does pandoc output that format?
>
> behdad
>
>> Werner
>>
>
> --
> behdad
> http://behdad.org/
> _______________________________________________
> HarfBuzz mailing list
> [email protected]
> http://lists.freedesktop.org/mailman/listinfo/harfbuzz
_______________________________________________
HarfBuzz mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/harfbuzz
