Re: Pandoc 2.0 and slides

[Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 3639 bytes --]

I am using 2.0.1.1.  

However, the problem may be unrelated to Pandoc 2.0.  The Markdown source 
file somehow got all its linefeed characters replaced by carriage returns. 
This was not evident in my editor (Aquamacs).  It showed up when I did 
"more" on the fil.

On macOS the Markdown reader takes the entire file as the title metadata 
line. So all I got was a file of bold centered text. I do not know if the 
behavior changed from pre-2.0 to 2.0 because I no longer have the old 
system installed. (I rely on homebrew.)

I am not sure how this happened to several of my slide source files. (I 
have these files in a Box synched folder that allows me access from my 
office, laptop, and home Macs.)

On Monday, November 6, 2017 at 11:01:54 AM UTC-6, John MacFarlane wrote:
>
> Try with 2.0.1.1.  We fixed a problem with --self-contained 
> + S5, and it could be that the same issue affects slidy. 
>
> Also, does it work without --self-contained? 
>
> You say the metadata is not being parsed correctly.  It 
> would help if you gave more details about why you think 
> that. 
>
> +++ Conrad Cunningham [Nov 06 17 06:44 ]: 
> >   Since homebrew updated Pandoc to 2.0 on my macOS (High Sierra) system 
> >   last week, my creation of slidy slides from markdown no longer works. 
> >   Here is the command that seemed to work well before 2.0 for input in 
> >   file xxx.md 
> >       pandoc --self-contained --latexmathml --slide-level=2  -t slidy -s 
> >   -o xxx.html xxx.md 
> >   Now, --latexmathml does not seem to work with other builds, so I 
> >   switched to --mathml.  But that does not seem to be the issue. 
> >   Given the output, it seems that metadata in my file is not being 
> parsed 
> >   correctly.  But I have not seen that issue with other markdown-to-html 
> >   conversions. 
> >   I no longer have a working pre-2.0 version installed, so I have not 
> had 
> >   time to construct a short test case that works in the old but not the 
> >   new. 
> > 
> >   -- 
> >   You received this message because you are subscribed to the Google 
> >   Groups "pandoc-discuss" group. 
> >   To unsubscribe from this group and stop receiving emails from it, send 
> >   an email to [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To post to this group, send email to 
> >   [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To view this discussion on the web visit 
> >   [3]
> https://groups.google.com/d/msgid/pandoc-discuss/d189aef8-ec04-4cc1- 
> >   abe2-ee41c283e32a%40googlegroups.com. 
> >   For more options, visit [4]https://groups.google.com/d/optout. 
> > 
> >References 
> > 
> >   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   3. 
> https://groups.google.com/d/msgid/pandoc-discuss/d189aef8-ec04-4cc1-abe2-ee41c283e32a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer 
> >   4. https://groups.google.com/d/optout 
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/eb566a7d-4d40-46bd-9554-f8392ec4ad86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 7884 bytes --]