[`BlogLiterately`][] is a tool for uploading blog posts to servers that support the [MetaWeblog API][metaweblog] (such as [WordPress][]-based blogs and many others). Blog posts to be published via `BlogLiterately` are written in [markdown][] format, with extensions supported by [pandoc][]. Posts may be actual "bird-style" literate Haskell files, with commentary in markdown. Though `BlogLiterately` offers special support for literate Haskell in particular, it is also useful for writing posts including code written in other languages, or even no code at all. `BlogLiterately` includes support for syntax highlighting, $\LaTeX$ (including special support for WordPress blogs), and automatic generation and formatting of `ghci` sessions. Each of these features is explained in more detail below. Markdown and pandoc ------------------- `BlogLiterately` takes as input files written using the [markdown][] format. See the [markdown website][markdown] for detailed documentation. `BlogLiterately` uses [pandoc][] for reading markdown, which also [supports a few extensions](http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown) to the basic format. Code blocks and syntax highlighting ----------------------------------- Code segments (including actual source lines from literate haskell files, as well as markdown code blocks) may be syntax highlighted. Two different syntax highlighting libraries are supported: * [hscolour][] is specifically for syntax highlighting of Haskell code, and is the standard highlighter used on [Hackage][] and elsewhere. * [highlighting-kate][] is a general syntax highlighting library that can be used for highlighting a wide range of languages (including Haskell). You may independently specify whether to use `hscolour` or `highlighting-kate` to highlight Haskell code; other languages will be highlighted with `highlighting-kate`. In basic markdown, a generic code block is set off from normal text by indenting at least four spaces: -- This is a code segment, but what language is it? foo :: String -> String However, markdown has no way of specifying the language used in a code block, making support for syntax highlighting problematic. Pandoc offers [an alternative syntax](http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown) for code segments which does allow specifying the language: ~~~~ { .haskell } -- This is a Haskell code segment! foo :: String -> String ~~~~ `BlogLiterately` also supports one additional style, consisting of a normal markdown indented code block with an extra tag at the top, enclosed in square brackets: [haskell] -- This is also a Haskell code segment! foo :: String -> String Of course, languages other than Haskell may be specified as well. By default, `hscolour` will be used for highlighting Haskell code, using "inline" CSS style attributes. The default styling is similar to that used for source code in documentation on [Hackage][]. You can also specify a configuration file containing a Haskell value of type [(String,String)] which specifies a CSS style for each syntax class. An example (corresponding to the default configuration) is provided in the package archive (`hs-style`). With `highlighting-kate`, the style for syntax segments is specified using "class" attributes, so the stylesheet must be provided separately. You may optionally use a similar scheme with `hscolour`. Sample stylesheets are provided in the package archive file (`kate.css`, `hscolour.css`). LaTeX ----- LaTeX can be included in documents using single dollar signs to enclose inline LaTeX, and double dollar signs to enclose "display-style" LaTeX. For example, `$\pi^2 / 6$` produces $\pi^2 / 6$, and `$$\sum_{k=0}^\infty 1/k^2$$` (when put by itself in its own paragraph) produces $$\sum_{k=0}^\infty 1/k^2.$$ By default, LaTeX is processed with Pandoc, meaning that a certain subset of LaTeX expressions (such as those above) will be transformed into [MathML][], and anything Pandoc cannot parse will be passed through as literal LaTeX enclosed in dollar signs. Blogs hosted on [wordpress.com](http://www.wordpress.com), however, have built-in support for LaTeX, compiling LaTeX expressions to embedded images on-the-fly. Passing the `--wplatex` option to `BlogLiterately` causes any embedded LaTeX to be output in the format expected by WordPress. Note that an extra `$latex...` won't be added to the beginning of LaTeX expressions which already appear to be in WordPress format. When working with other blogging platforms that do not directly support LaTeX, it might be nice for `BlogLiterately` to have some sort of [MathJax][] support. This is future work; drop a note (or a patch!) if you would like to see this added. `ghci` sessions --------------- When writing literate Haskell documents, it is often useful to show a sample `ghci` session illustrating the behavior of the code being described. However, manually pasting in the results of sample sessions is tedious and error-prone, and it can be difficult keeping sample sessions "in sync" when making changes to the code. For these reasons, `BlogLiterately` supports special `[ghci]` code blocks, consisting of a list of Haskell expressions (or, more generally, arbitrary `ghci` commands), one per line. These expressions/commands are evaluated using `ghci`, and the results typeset along with the original expressions in the output document. The entire literate Haskell document itself will be loaded into `ghci` before evaluating the expressions, so expressions may reference anything in scope. Note also that all expressions in the entire document will be evaluated in the *same* `ghci` session, so names bound with `let` or `<-` will also be in scope in subsequent expressions, even across multiple `[ghci]` blocks. For example, consider the following definition: > hailstone x > | even x = x `div` 2 > | otherwise = 3*x + 1 Now, given the input [other] [ghci] :t hailstone hailstone 15 takeWhile (/= 1) . iterate hailstone $ 7 txt <- readFile "BlogLiteratelyDoc.lhs" length txt `BlogLiterately` will generate the following output: [ghci] :t hailstone hailstone 15 takeWhile (/= 1) . iterate hailstone $ 7 txt <- readFile "BlogLiteratelyDoc.lhs" length txt There are currently a few known limitations of this feature: * The code for interfacing with `ghci` is not very robust. In particular, expressions which generate an error (*e.g.* ones which refer to an out-of-scope name, or do not typecheck) will simply lack any accompanying output; it would be much more useful to display the accompanying error message. * If the literate document itself fails to load (*e.g.* due to improper formatting) `BlogLiterately` may hang. * The formatting of `ghci` sessions currently cannot be customized. Suggestions for customizations to allow are welcome. Uploading embedded images ------------------------- A planned feature for a future release of `BlogLiterately` is the ability to automatically upload images embedded in a blog post to the server, replacing local image file names with the appropriate URL. However, this feature is currently [blocked on a baffling bug](http://stackoverflow.com/questions/11277788/errorclosed-exception-from-network-http-simplehttp-trying-to-upload-images-vi). If you know anything about HTTP, TCP/IP, XML-RPC, WordPress, and/or the `HTTP` and `haxr` libraries, please help! Command-line options -------------------- The options for `BlogLiterately` are hopefully self-explanatory, given the above background: BlogLierately v0.4, (c) Robert Greayer 2008-2010, Brent Yorgey 2012 This program comes with ABSOLUTELY NO WARRANTY BlogLiterately [OPTIONS] FILE Common flags: -s --style=FILE style specification (for --hscolour-icss) --hscolour-icss highlight haskell: hscolour, inline style (default) --hscolour-css highlight haskell: hscolour, separate stylesheet --hs-nohighlight no haskell highlighting --hs-kate highlight haskell with highlighting-kate --other-kate highlight other code with highlighting-kate -w --wplatex reformat inline LaTeX the way WordPress expects -g --ghci run [ghci] blocks through ghci and include output --category=ITEM post category (can specify more than one) --tag=ITEM tag (can specify more than one) --blogid=ID Blog specific identifier --blog=URL blog XML-RPC url (if omitted, html goes to stdout) -u --user=USER user name --password=PASSWORD password -t --title=TITLE post title --postid=ID Post to replace (if any) --page create a "page" instead of a post (WordPress only) --publish publish post (otherwise it's uploaded as a draft) -? --help Display help message -V --version Print version information Example usage ------------- If you do not specify a blog URL, by default `BlogLiterately` simply prints the generated HTML to stdout. So, to preview the generated HTML before uploading requires merely something like BlogLiterately Sample.lhs To actually post to, say, a WordPress blog, a basic command line would be something like BlogLiterately --blog http://blogurl.example.com/xmlrpc.php \ --user myname --password mypasswd --title "Sample" Sample.lhs (which creates a new post). If, for example, the post id of that post (which `BlogLiterately` prints when it uploads a new post) is '37', then to update the post, the command would be: BlogLiterately --postid 37 --blog http://blogurl.example.com/xmlrpc.php \ --user myname --password mypasswd --title "Sample" Sample.lhs and the post will be updated with the new text. Getting Help ------------ For questions, support, feature suggestions, etc., feel free to contact me (Brent Yorgey): `byorgey` on IRC (freenode), or `byorgey` at gmail. [`BlogLiterately`]: http://hackage.haskell.org/package/BlogLiterately [markdown]: http://daringfireball.net/projects/markdown/ [pandoc]: http://johnmacfarlane.net/pandoc/ [hscolour]: http://www.cs.york.ac.uk/fp/darcs/hscolour/ [highlighting-kate]: http://johnmacfarlane.net/highlighting-kate/ [metaweblog]: http://www.xmlrpc.com/metaWeblogApi [WordPress]: http://wordpress.org/ [Hackage]: http://hackage.haskell.org/ [MathML]: http://www.w3.org/Math/ [MathJax]: http://www.mathjax.org/