<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.pandoc">
    <title>gmane.text.pandoc</title>
    <link>http://blog.gmane.org/gmane.text.pandoc</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6440"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6437"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6435"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6433"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6432"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6430"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6421"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6420"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6418"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6414"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6413"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6412"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6408"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6406"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6400"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6391"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6388"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6387"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6386"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.pandoc/6385"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6440">
    <title>using pandoc over ssh</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6440</link>
    <description>&lt;pre&gt;I've written a shell script for using pandoc over ssh: 
https://github.com/dsanson/ssh-pandoc-wrapper

If you are on a system that does not have pandoc installed, but have ssh 
access to a system that does, you can install this script, give it the name 
`pandoc`, and give yourself the illusion of having a (slow) local 
installation of pandoc.

For example, instead of typing

    $ cat example.md | ssh example.com 'pandoc -o example.docx; cat 
example.docx; rm example.docx' &amp;gt;&amp;gt; example.docx

you can type

    $ pandoc example.md -o example.docx

and the script will handle the messy details (well, not all the messy 
details: you need to make sure that templates and bibliography files and 
mages and so on are available as needed on the remote server).

&lt;/pre&gt;</description>
    <dc:creator>David Sanson</dc:creator>
    <dc:date>2013-05-18T02:21:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6437">
    <title>Internal links for non headers</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6437</link>
    <description>&lt;pre&gt;Hi,

I want to link within a document to any arbitrary position within the
same document. I only find how to link to headers. Is there a way to
link to arbitrary positions?

http://johnmacfarlane.net/pandoc/demo/example19/Internal-links.html

&lt;/pre&gt;</description>
    <dc:creator>Peng Yu</dc:creator>
    <dc:date>2013-05-17T03:06:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6435">
    <title>Indent paragraph</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6435</link>
    <description>&lt;pre&gt;Hi,

I want to have each paragraph indented in the generated output (such
as pdf or html). Is there a way to denote such information in pandoc
document? Thanks.

&lt;/pre&gt;</description>
    <dc:creator>Peng Yu</dc:creator>
    <dc:date>2013-05-17T02:59:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6433">
    <title>pandoc digest cannot be open by thunderbird</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6433</link>
    <description>&lt;pre&gt;Hello

I just realized that, but the digest format the pandoc mailing list
software uses cannot be really opened, by thunderbird in separated
messages as can be done by digest send by other mailing list software.

How do people read the digest?

Uwe Brauer

&lt;/pre&gt;</description>
    <dc:creator>Uwe Brauer</dc:creator>
    <dc:date>2013-05-16T21:32:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6432">
    <title>nested tables II, latex import/export</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6432</link>
    <description>&lt;pre&gt;
Hello 

I realized that there is another issue. I am not really sure whether the
following table is really nested or just not simple since it contains 
split and merged cells.


+-----+-----+-----+
|     |     |     |
+-----+-----+-----+
|     |     |     |
|     +-----+     |
|     |     |     |
+-----+-----+-----+
|     |           |
+-----+-----------+



which I can for example generate with emacs table.el package, I can even
export it to latex as:

\begin{tabular}{|l|l|l|}
\hline
 &amp;amp; &amp;amp; \\
\hline
 &amp;amp; &amp;amp; \\
\cline{2-2}
 &amp;amp; &amp;amp; \\
\hline
 &amp;amp; \multicolumn{2}{l|}{} \\
\hline
\end{tabular}

So the feature proposal  is: 
could pandoc import the above latex construct and
export it to markdown or rst. 

(Or even rtf, but in principle latex2rtf
can this also).

Uwe Brauer 

&lt;/pre&gt;</description>
    <dc:creator>Uwe Brauer</dc:creator>
    <dc:date>2013-05-16T21:29:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6430">
    <title>Line breaks in multiline tables for docx writer</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6430</link>
    <description>&lt;pre&gt;It seems that the docx writer is not honoring line breaks in cells for 
multiline tables:

~~~
---------
Foo  Bar
---- ----
One  A\ 
     B

Two
---------
~~~

This works in HTML, LaTeX and PDF at least.

-Ryan


&lt;/pre&gt;</description>
    <dc:creator>Ryan Gray</dc:creator>
    <dc:date>2013-05-16T18:45:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6421">
    <title>partial solution found via perl</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6421</link>
    <description>&lt;pre&gt;Hello

Ok ok I asked this question already some time ago. (Ah memory) There is
a partial solution using a perl script, partial since it leaves nested
tables out. But ok better than nothing.

Sorry for the noise

Uwe Brauer 

&lt;/pre&gt;</description>
    <dc:creator>Uwe Brauer</dc:creator>
    <dc:date>2013-05-14T20:46:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6420">
    <title>import html (to markdown or rst) with tables.</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6420</link>
    <description>&lt;pre&gt;Hello


I have a html document with a table (it is nested) and tried the
following commands 

andoc -f html table.html -t markdown  -o dia4.txt

andoc -f html table.html -t rst  -o dia4.txt

I escpected to see something like this 


+---------------+---------------+--------------------+
| Fruit         | Price         | Advantages         |
+===============+===============+====================+
| Bananas       | $1.34         | - built-in wrapper |
|               |               | - bright color     |
+---------------+---------------+--------------------+
| Oranges       | $2.10         | - cures scurvy     |
|               |               | - tasty            |
+---------------+---------------+--------------------+

Or similar, but no the table is completely ignored. I generated a short
html document containing  a simple table and it did not work neither.

Is this feature missing, or do I miss something?

thanks

Uwe Brauer 


&lt;/pre&gt;</description>
    <dc:creator>Uwe Brauer</dc:creator>
    <dc:date>2013-05-14T20:27:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6418">
    <title>Labeled list and hyperlink</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6418</link>
    <description>&lt;pre&gt;Hi,

The following is shown in the document for creating a numbered list.

              (&amp;lt; at &amp;gt;good)  This is a good example.

              As (&amp;lt; at &amp;gt;good) illustrates, ...

But the second (&amp;lt; at &amp;gt;good) does not generate a hyperlink.

Also, I want to manually specify the label instead of using the default number.

Could anybody let me know if these two features are available?

&lt;/pre&gt;</description>
    <dc:creator>Peng Yu</dc:creator>
    <dc:date>2013-05-14T11:13:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6414">
    <title>customized example_lists for latex output</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6414</link>
    <description>&lt;pre&gt;I'm a novice coder and I want to make a script that takes markdown and 
creates a LaTeX, somewhat like the built-in example_lists, but with a more 
elegant native-LaTeX-like solution. I'm thinking I want to implement \label 
and \ref commands, which do better at tracking example numbers, which can 
be done with the (&amp;lt; at &amp;gt;xyz) syntax that example_lists uses. I also want to 
implement at least one level of subexamples, which should probably use a 
new command -- I've got (&amp;lt; at &amp;gt;&amp;lt; at &amp;gt;xyz) in mind. I'm thinking I want to use the 
LaTeX package ExPex's syntax, meaning I want this...


Examples (&amp;lt; at &amp;gt;wah) and (&amp;lt; at &amp;gt;rah) are really cool!


to become this: 


Is this easily achievable?  I've been reading up on Haskell and pandoc (I'm 
new
to both), but I'm not at a point where I can do this on my own.  Does anyone
have any ideas or have suggestions of how to start?

&lt;/pre&gt;</description>
    <dc:creator>btalx</dc:creator>
    <dc:date>2013-05-13T20:04:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6413">
    <title>customized example_lists for markdown to latex</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6413</link>
    <description>&lt;pre&gt;I'm a novice coder and I want to make a script that takes markdown and 
creates a LaTeX, somewhat like the built-in example_lists, but with a more 
elegant native-LaTeX-like solution.

I'm thinking I want to implement \label and \ref commands, which do better 
at tracking example numbers, which can be done with the (&amp;lt; at &amp;gt;xyz) syntax that 
example_lists uses. I also want to implement at least one level of 
subexamples, which should probably use a new command -- I've got (&amp;lt; at &amp;gt;&amp;lt; at &amp;gt;xyz) in 
mind. I'm thinking I want to use the LaTeX package ExPex's syntax, meaning 
I want this...


John thinks the examples in (&amp;lt; at &amp;gt;wah) and (&amp;lt; at &amp;gt;rah) are really cool!


to become this: 


Is this easily achievable?  I've been reading up on Haskell and pandoc (I'm 
new to both), but I'm not at a point where I can do this on my own.  Does 
anyone have any ideas or have suggestions of how to start?

&lt;/pre&gt;</description>
    <dc:creator>btalx</dc:creator>
    <dc:date>2013-05-13T20:00:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6412">
    <title>Numbered sections with `plain` output format</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6412</link>
    <description>&lt;pre&gt;Folks,

I am trying to get HTML5, PDF, and plain text output from the same .md 
source file with numbered sections in all three outputs.

The bash script I am using is:

---
pandoc -f markdown -t html5 --standalone --number-sections $1.md -o $1.html
pandoc -f markdown -t plain --standalone --number-sections $1.md -o $1.txt
pandoc -f markdown -t latex --standalone --number-sections $1.md -o $1.pdf
---

The HTML and PDF outputs are fine and feature numbered sections, but 
there are no numbered sections in the plain text. I think this is by 
design but would like to know if there is a workaround for getting 
numbered sections in plain text as well.

TIA.

Chandra

&lt;/pre&gt;</description>
    <dc:creator>R (Chandra) Chandrasekhar</dc:creator>
    <dc:date>2013-05-13T16:08:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6408">
    <title>converting tex to docx breaks images</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6408</link>
    <description>&lt;pre&gt;For collaboration purposes, I'm trying to fork a tex file to a docx. I've 
followed John's tutorial using

pandoc -s report.tex -o report.docx


however pandoc is unable to find images, that are located in a subfolder 
./figures by giving warning along the lines of

pandoc: Could not find image `./figure/...`, skipping...


I include images via the figure environment

\begin{figure}[H]


and I use what I believe to be the current pandoc version of 1.10.0.5. Any 
hints on how to tell pandoc where to find figures to be included in the 
output will be much appreciated.


Cheers,

Roman

&lt;/pre&gt;</description>
    <dc:creator>Roman Luštrik</dc:creator>
    <dc:date>2013-05-12T18:22:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6406">
    <title>pandoc 1.11.1: cannot decode \xab in OpenDoc document with PUA code points</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6406</link>
    <description>&lt;pre&gt;I'm trying to convert an OpenDoc document to Markdown, and whenever I run

    pandoc -t markdown Call\ of\ Cthulhu-QS.odt

I get

    Cannot decode byte '\xab': Data.Text.Encoding.decodeUtf8: Invalid UTF-8 
stream

The error message doesn't tell me where this particular byte is, and when I 
search for "AB" in content.xml using Hex Fiend&amp;lt;http://ridiculousfish.com/hexfiend/&amp;gt;, 
it doesn't find anything.

One oddity about this file is that it makes extensive use of the Private 
Use Area — byte sequences of EE 99 99 aren't uncommon. While Pandoc is 
quite able to handle text that's been copied from TextEdit to BBEdit and 
put in Markdown, it's not able to handle these .odt files itself.

The problematic file is attached.


&lt;/pre&gt;</description>
    <dc:creator>bonusfrogs-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-12T17:28:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6400">
    <title>Script for checking for overly long footnotes</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6400</link>
    <description>&lt;pre&gt;I sometimes go on at too much length in footnotes or the footnotes
gradually accrete to too much length, so I decided to augment my
existing `markdown-lint` suite of checks with a new one, a call to a
Pandoc script which checks for footnotes &amp;gt;2300 characters in length
(judged by looking at existing footnotes I consider to be close to the
acceptable limit). The script seems to work, but came out rather ugly
- for some reason, functions which I thought should import without a
problem like `def::WriterOptions` refused to be imported so I had to
inline them:

    #! /usr/bin/env runhaskell
    {-# OPTIONS_GHC -fno-warn-warnings-deprecations #-}
    -- example usage: $ find ~/wiki/ -name "*.page" -exec runhaskell
markdown-footnote-length {} \;
    -- default: looks for footnotes &amp;gt;2300 characters long (too long on
my screen)
    import System.Environment (getArgs)
    import Text.Pandoc (bottomUpM, defaultParserState, readMarkdown,
writeMarkdown,
                        CiteMethod(Citeproc),
HTMLSlideVariant(NoSlides), HTMLMathMethod(PlainMath),
                        Inline(Note), Meta(..), Pandoc(..), WriterOptions(..))
    import Control.Monad (void, when)
    import Text.Pandoc.Highlighting (pygments)

    main :: IO ()
    main = do (file:_) &amp;lt;- getArgs
              void (readFile file &amp;gt;&amp;gt;= processLint file)

    -- 'drop 3' to avoid the near-infinite loop when files start with
Hakyll metadata
    processLint :: FilePath -&amp;gt; String -&amp;gt; IO Pandoc
    processLint f x = bottomUpM (footNoteCheck f) (readMarkdown
defaultParserState (drop 3 x))

    footNoteCheck :: FilePath -&amp;gt; Inline -&amp;gt; IO Inline
    footNoteCheck f x&amp;lt; at &amp;gt;(Note cntnts) = do let md = writeMarkdown def
(Pandoc nullMeta cntnts)
                                         when (length md &amp;gt; 2300) $
error (f ++ ": " ++ md)
                                         return x
    footNoteCheck _ x = return x

    nullMeta :: Meta
    nullMeta = Meta { docTitle = []
                    , docAuthors = []
                    , docDate = [] }

    def :: WriterOptions
    def = WriterOptions { writerStandalone         = False
                          , writerTemplate         = ""
                          , writerVariables        = []
                          , writerTabStop          = 4
                          , writerTableOfContents  = False
                          , writerSlideVariant     = NoSlides
                          , writerIncremental      = False
                          , writerHTMLMathMethod   = PlainMath
                          , writerIgnoreNotes      = False
                          , writerNumberSections   = False
                          , writerSectionDivs      = False
                          , writerReferenceLinks   = False
                          , writerWrapText         = True
                          , writerColumns          = 72
                          , writerIdentifierPrefix = ""
                          , writerSourceDirectory  = "."
                          , writerUserDataDir      = Nothing
                          , writerCiteMethod       = Citeproc
                          , writerBiblioFiles      = []
                          , writerHtml5            = False
                          , writerBeamer           = False
                          , writerSlideLevel       = Nothing
                          , writerChapters         = False
                          , writerListings         = False
                          , writerHighlight        = False
                          , writerSetextHeaders    = True
                          , writerTeXLigatures     = True
                          , writerEPUBMetadata     = ""
                          , writerStrictMarkdown   = True
                          , writerLiterateHaskell  = False
                          , writerEmailObfuscation = undefined
                          , writerHighlightStyle   = pygments
                          , writerXeTeX = False
                          }

&lt;/pre&gt;</description>
    <dc:creator>Gwern Branwen</dc:creator>
    <dc:date>2013-05-11T19:13:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6391">
    <title>Retrieving an AST from markdown with Cite nodes intact</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6391</link>
    <description>&lt;pre&gt;Hi everyone,

I want to write some custom extensions to pandoc's LaTeX output but cannot 
quite figure out how to read a markdown file and have markdown-style 
citations represented in the resulting AST.

main = interact (
    writeNative def 
  . bottomUp singleCitation
  . bottomUp multipleCitations
  . readMarkdown def { readerExtensions = Set.fromList [Ext_citations] })

For input...

[&amp;lt; at &amp;gt;ABC123; &amp;lt; at &amp;gt;ABC456]

... this gives me th following AST node:

Para [Str "[&amp;lt; at &amp;gt;ABC123;",Space,Str "&amp;lt; at &amp;gt;ABC456]"]

Any hints?

TIA

Antonio

&lt;/pre&gt;</description>
    <dc:creator>Antonio Navarro Pérez</dc:creator>
    <dc:date>2013-05-11T06:06:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6388">
    <title>proposal for new metadata</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6388</link>
    <description>&lt;pre&gt;See https://github.com/jgm/pandoc/issues/851
Comments welcome, there or here.

&lt;/pre&gt;</description>
    <dc:creator>John MacFarlane</dc:creator>
    <dc:date>2013-05-10T05:51:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6387">
    <title>How to make $$ ... $$ left aligned in html?</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6387</link>
    <description>&lt;pre&gt;I use the following command to generate html file.

pandoc -f markdown --toc --mathjax -S -s README.mkd -o README.html

$$ ... $$ is centered in html by default. Is there a way to make $
$ ... $$ left aligned? Thanks.


&lt;/pre&gt;</description>
    <dc:creator>Peng Yu</dc:creator>
    <dc:date>2013-05-10T16:30:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6386">
    <title>nav.xhtml - How to not have it created</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6386</link>
    <description>&lt;pre&gt;So it appears that whether or not I specify --toc ... a nav.xhtml gets 
created and inserted into the ePub.

It just appears that the difference, is whether it's listed as a linear 
spine element, or whether it's 'hidden' away.

Is there a way to tell pandoc to not even create the nav.xhtml?   I'm not 
wanting it, because I'm building my own manual TOC.   And when I take the 
epub and convert it to a MOBI.   The MOBI conversion software is seeing the 
nav, and even though it's not a linear element, it's injecting it into the 
output mobi.

I can unzip the files and remove it.  But that's messy.   Would rather just 
not have the nav.xhtml created, if I didn't specify --toc.

Thoughts? / Help?

Eli

&lt;/pre&gt;</description>
    <dc:creator>Eli White</dc:creator>
    <dc:date>2013-05-10T14:03:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6385">
    <title>minor note: --self-contained, reveal.js, fonts, and https</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6385</link>
    <description>&lt;pre&gt;
Just wanted to note that when I went to build an offline version of my 
slides pandoc complained it didn't support https, which is what the 
default reveal.js slides use for custom fonts at Google. (Many of these 
styles import other things as well, and it's not reasonable for pandoc 
to fetch all of those as well...)

&lt;/pre&gt;</description>
    <dc:creator>Joseph Reagle</dc:creator>
    <dc:date>2013-05-10T12:57:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.pandoc/6379">
    <title>Tex to HTML - listings code conversion</title>
    <link>http://comments.gmane.org/gmane.text.pandoc/6379</link>
    <description>&lt;pre&gt;Hi,

I am new to pandoc. I have a lot of tutorials written in LATEX and I want 
to convert it into HTML to post it in my blog. So I am looking for an 
automated tool and I found pandoc. First impression is great. 

Currently the only problem I am facing is about some Python codes which are 
part of tutorials. Currently they are written using listings package in 
latex. And I want to convert them to HTML as some fancy codes, something 
like this : 
http://opencvpython.blogspot.in/2013/03/histograms-4-back-projection.html

I know in that blog, I am using some javascript to make that code look like 
what it is, which is taken from CraftyFella's Blog: Syntax Highlighting 
with Blogger Engine. 
&amp;lt;http://www.craftyfella.com/2010/01/syntax-highlighting-with-blogger-engine.html&amp;gt;I 
also saw some interesting formats in pandoc docs which uses pygments, kate 
etc. 

So can you suggest me a simple method which make my listings code look like 
that?

Regards
Abid K


&lt;/pre&gt;</description>
    <dc:creator>abid rahman</dc:creator>
    <dc:date>2013-05-09T02:16:35</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.pandoc">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.pandoc</link>
  </textinput>
</rdf:RDF>
