Convert Haddock
to OpenOffice

Converting from Haddock markup

Haddock is a nice tool to automatically generate documentation from annotated Haskell source code. I’ve never used Haskell and have no idea what it’s for, but I like automatically generated things. BTW this text is handwritten, but I probably should have set up a machine learning deep learning thing to generate those. I bet no one reads them anyway. If you do, clap your hands twice so I know you’re out there. Anyway, let’s get back to Haddock. It’s intended for documenting libraries, but it should be useful for any other kind of Haskell code. Documentations can then be generated to HTML or LaTeX. Or you use Alldocs to convert it to many other text formats for free. Cool, right?

The files end with .txt by default.

More about Haddock markup files

Converting to OpenOffice ODT

Having office files in a proprietary format is a big risk, that you should avoid. Thanks to OpenOffice it’s not even hard to do. With the OpenOffice ODT format we’ve got an open format, that is based on other open formats. Every ODT file is a Zip file, that contains at least a content.xml (an XML file) with the — you might have guessed it already - the content. You can open the XML file in the program of your liking, update the content and re-open it in your office program without worrying to break the file. This enables you to interact with your office files through code. And even more important, you can be pretty sure there will always be software to open and edit those files. That’s a big plus, isn’t it?

The files end with .odt by default. More about OpenOffice ODT files