gmane.text.pandoc

tex_math_double_backslash: are spaces important?

2013-05-23T16:03:41

I have been experimenting with the tex_math_double_backslash extension, 
trying to get math to show up within a paragraph rather than as its own 
centered paragraph. In the process of this, I found what might be a bug 
when rendering to latex, but I'm not sure. This line of markdown:

Blah \\[\hat{p}\\] Blah \\[ \hat{p} \\] Blah \\(\hat{p}\\) Blah \\( \hat{p} 
\\) Blah

is rendered as the latex:

Blah \[\hat{p}\] Blah \[ \hat{p} \] Blah $\hat{p}$ Blah \textbackslash{}( \
hat{p} \textbackslash{}) Blah

The problem is with the \\( syntax. If I write it this way:

\\(\hat{p}\\)

it renders as expected:

$\hat{p}$

But when spaces are included after the ( and before the ), like so:

\\( \hat{p} \\)

then \textbackslash{} is inserted instead:

\textbackslash{}( \hat{p} \textbackslash{})

That ultimately causes pdflatex to fail with "! Package amsmath Error: \hat 
allowed only in math mode."

Is this a bug in pandoc, or am I violating the rules of tex math by 
inserting the spaces? Thanks for your help and for making pandoc freely 
usable. I am using pandoc 1.11.1.

Jason

Re: typeset algorithm in pandoc

John Gabriele — 2013-05-23T14:25:56


Interesting. I wonder if anyone's come up with a "generic algorithm" Kate
syntax highlighting file...

Automatic line numbering for Literate Haskell?

Björn Peemöller — 2013-05-23T07:44:37

Hi,

I recently rediscovered the line numbering facilities for code of pandoc
and I'm wondering if there is support for automatically numbering the
code lines in a literate Haskell file.

That is, I want a file like

~~~~
This is `f`:


And this is `g`:


That's it.
~~~

to be converted to Markdown as:

~~~~~~~~~~~~
This is `f`:

~~~~ {.sourceCode .literate .haskell .numberLines startFrom="1"}
f x = x * x
~~~~

And this is `g`:

~~~~ {.sourceCode .literate .haskell .numberLines startFrom="2"}
g x = 2 * x
~~~~

That's it.
~~~~~~~~~~~~

(note the increased startFrom attribute)

If there is no support for this, I will just write my own plugin for it,
but wanted to ask first.

Kind Regards,
Björn

Re: proposal for new metadata

John Gabriele — 2013-05-21T21:04:35

Ooof. Right. It would be good if

    pandoc -s -o out.html a.txt b.txt c.txt

worked where a.txt, b.txt, and c.txt all contain metadata.

Re: proposal for new metadata

John MacFarlane — 2013-05-21T19:57:41

+++ Tillmann Rendel [May 21 13 21:43 ]:

Yes, though it needs to be defined what counts as merging.
(Does a subsequent field replace the earlier one's value,
or somehow get merged with it?)


Sorry, yes, I meant YAML.  (The Haskell library for YAML uses the
JSON types, which explains my slip.)

Re: proposal for new metadata

Tillmann Rendel — 2013-05-21T19:43:00

Hi,

John MacFarlane wrote:

Another argument: Merging files would automatically merge the metadata 
from each of the files.

Also, wasn't it YAML metadata blocks, or is this about something else?

   Tillmann

Re: Generate list labels like (a)?

Pablo Rodríguez — 2013-05-21T18:31:57

Hi Peng,

copied from
http://stackoverflow.com/questions/1632005/ordered-list-html-lower-alpha-with-right-parentheses:

    CSS:

    ol {
      counter-reset: list;
    }
    ol li {
      list-style: none;
    }
    ol li:before {
      content: counter(list, lower-alpha) ") ";
      counter-increment: list;
    }

    HTML:

    <ol>
      <li>Number 1</li>
      <li>Number 2</li>
      <li>Number 3</li>
      <li>Number 4</li>
      <li>Number 5</li>
      <li>Number 6</li>
    </ol>

It might not work in all browsers. And it won't work in Adobe Reader
Mobile (just in case you're aiming at ePub).

I hope it helps,


Pablo

Generate list labels like (a)?

Peng Yu — 2013-05-21T16:04:35

Hi,

If I use (a) in a list in a pandoc file, the generate html file has
the label "a". How to get the label as "(a)"? Thanks.

Re: nav.xhtml - How to not have it created

Eli White — 2013-05-21T15:11:30

Very true, but still seems like it should be a simple option to pandoc to 
just not make it in the first place, so I was hoping.   But then again, I 
haven't looked at the source code of pandoc to see how ingrained the 
building of the TOC is.

Thanks,
Eli


On Sunday, May 12, 2013 1:33:02 PM UTC-4, bonus...-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org wrote:

typeset algorithm in pandoc

Peng Yu — 2013-05-21T14:27:51

Hi,

I don't find a structure for typesetting algorithm. Something like the
following from latex is desire. Is there anything available in pandoc?

http://en.wikibooks.org/wiki/LaTeX/Algorithms

Re: proposal for new metadata

David Sanson — 2013-05-21T05:46:41

The point of embedding bibliography data in the markdown document is to allows for a self-contained markdown source: 

    pandoc example.md --bibliography example.md

Actual presentation of a bibliography would be done by processing the file.

Are there other practical use cases for embedded structured data? I don't know. Question pools for embedding into SCORM compliant HTML and LaTeX quizzes and exams? I can dream!

How do extant tools handle YAML blocks in files? My understanding was that the YAML standard allows data blocks anywhere, but I don't know if existing tools respect that. If the data blocks anywhere option is too expensive, processing-wise, and doesn't work with existing tools, then I don't see a compelling reason to allow it at this point.

Re: proposal for new metadata

Eric Watson — 2013-05-20T21:45:21


On May 20, 2013, at 4:25 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:


Absolutely!

Re: proposal for new metadata

John MacFarlane — 2013-05-20T21:25:36

+++ Eric Watson [May 20 13 15:34 ]:

If you come up with a nice way of using pandoc to produce impress.js
slide shows, please let us know about it here!

Re: proposal for new metadata

Eric Watson — 2013-05-20T20:34:26


On May 20, 2013, at 1:32 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:


Cool! I'll give it a whirl!

Re: proposal for new metadata

Chris Lott — 2013-05-20T19:48:58

I hear you, but I don't want a tool enforcing standards I (or others)
don't necessarily share. Which isn't to say there aren't good
arguments  for only allowing metadata in a few specific places, just
that I don't think disallowing me from putting metadata blocks at the
beginning of, say, each major section in a doc, should be Pandoc's
privilege...

c
--
Chris Lott <chris-qMDBG1KJBpwBXFe83j6qeQ< at >public.gmane.org>

Re: Windows - new location?

Fedor Sheremetyev — 2013-05-20T18:55:41

Hi Pierre,

You can install Pandoc to a different directory by setting APPLICATIONFOLDER parameter, for example:

    msiexec /i pandoc-1.11.1.msi ALLUSERS=1 APPLICATIONFOLDER="C:\Pandoc"

Best regards,
Fedor

On 19 May 2013, at 18:29, prouleau001-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org wrote:

Re: proposal for new metadata

John MacFarlane — 2013-05-20T18:32:23

+++ Eric Watson [May 20 13 13:17 ]:

Well, you don't need metadata for this, since pandoc already allows you
to put attributes on headers, and headers can turn into divs if you use
--section-divs.

# See it rotate!  {#my-impressive-slide .step data-x="850" data-y="3000" data-rotate="90"}

Re: proposal for new metadata

John Gabriele — 2013-05-20T18:31:57



I think "metadata anywhere" would lead to docs with metadata strewn about
the place. Also, I'd rather not need to use a special tool to show me all
the metadata in a given doc.

I like the idea of metadata only at the beginning of a doc because it seems
the neatest and cleanest way to go.

Sidenote: I don't have any experience using BibTeX. Could you please give
an example of what it would look like to include a bibliography (in, bibtex
format) in the (proposed) document metadata?

BTW: Instead of using metadata for bibliographic info, might it be better
to instead extend Pandoc to specifically have support for raw BibTeX (or
maybe create a special block syntax for a bibliography)? I mean, it seems
to be a pretty common need, and Pandoc already supports LaTeX math...

Thanks,

embedding multiple fonts in ePub

Pablo Rodríguez — 2013-05-20T18:21:24

Hi,

would it be possible to embed multiple fonts in an ePub file using the
argument only once? I mean something like:

--epub-embed-font=fonts/FreeSerif*.ttf

So it would be easier for the user.

Many thanks for your help,


Pablo

Re: proposal for new metadata

Eric Watson — 2013-05-20T18:17:47

On May 20, 2013, at 11:32 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:


I secretly want pandoc to be able to produce HTML slides using [impress.js][1], which requires setting `data-*` attributes on each slide, like this: 

    <div id="my-impressive-slide" class="step" data-x="850" data-y="3000" data-rotate="90" data-scale="5">
<p>See it rotate! See it scale! See it <em>move!</em></p>
    </div>

    <div id="my-next-big-slide" class="step" data-x="3500" data-y="2100" data-rotate="180" data-scale="6">
        <p>Look, new metadata values!</p>
    </div>


If you could sprinkle metadata throughout a pandoc document, this might work nicely :)

    ---
    x: 850
    y: 3000
    rotate: 90
    scale: 5
    ...


    ## My Impressive Slide

    See it rotate! See it scale! See it *move!*


    ---
    x: 3500
    y: 2100
    rotate: 180
    scale: 6
    ...

    ## My Next Big Slide

    Look, new metadata values!



This is a pretty specialized use case, but the general idea of being able to provide (and change?) metadata at any point in the document seems like it could enable lots of cool new use cases.

Thanks for the great thinking on this tricky problem!

Eric


[1]https://github.com/bartaz/impress.js

Re: proposal for new metadata

Fedor Sheremetyev — 2013-05-20T17:41:16

Are there other real use cases for additional metadata at the end of the document besides bibliography?

I think bibliography is use case on it own and has nothing to do with title, authors etc. It would probably make sense to have Markdown-like markup for bibliography (not BibTeX inside YAML) — so that document is readable “as is”. Also one might want to have bibliography items embedded in text near the place they are used (like footnotes).


Relying on Pandoc to extract metadata might be too restrictive. One might want to parse document with metadata via JavaScript code in web browser, for example.