From: Mike Hynes <91mbbh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: LaTeX Headers/Macros in pandoc conversion
Date: Fri, 9 Jan 2015 12:22:49 -0800 (PST) [thread overview]
Message-ID: <40a476ba-e1a8-413e-ab7e-584f21f70101@googlegroups.com> (raw)
In-Reply-To: <039f5de8-68e3-42a7-9f9c-cdc6bde24bc4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 5868 bytes --]
I should also mention that even just concatenating my header and body files
into the classic latex slurry produces the same effect: no \FIG macros.
I've also defined a simple, no-parameter testing macro:
\newcommand{\varName}{TESTMACRO!}
This does not get converted correctly using pandoc; the macro is removed
entirely if it is contained simply in text, as in \varName\ in the current
sentence. If I write $\varName$, my macros appears as: the following in the
output file: \(\varName\).
This seems like a strange bug to me---is no \newcommand supported? Or have
I not supplied the correct flags to pandoc?
On Friday, January 9, 2015 at 3:12:58 PM UTC-5, Mike Hynes wrote:
>
> Version:
>
> >> pandoc -v
> pandoc 1.13.2 Compiled with texmath 0.8.0.1, highlighting-kate 0.5.11.1.
> Syntax highlighting is supported for the following languages: abc,
> actionscript, ada, agda, apache, asn1, asp, awk, bash, bibtex, boo, c,
> changelog, clojure, cmake, coffee, coldfusion, commonlisp, cpp, cs, css,
> curry, d, diff, djangotemplate, dockerfile, dot, doxygen, doxygenlua, dtd,
> eiffel, email, erlang, fasm, fortran, fsharp, gcc, glsl, gnuassembler, go,
> haskell, haxe, html, ini, isocpp, java, javadoc, javascript, json, jsp,
> julia, latex, lex, lilypond, literatecurry, literatehaskell, lua, m4,
> makefile, mandoc, markdown, mathematica, matlab, maxima, mediawiki,
> metafont, mips, modelines, modula2, modula3, monobasic, nasm, noweb,
> objectivec, objectivecpp, ocaml, octave, opencl, pascal, perl, php, pike,
> postscript, prolog, pure, python, r, relaxng, relaxngcompact, rest, rhtml,
> roff, ruby, rust, scala, scheme, sci, sed, sgml, sql, sqlmysql,
> sqlpostgresql, tcl, tcsh, texinfo, verilog, vhdl, xml, xorg, xslt, xul,
> yacc, yaml, zsh Default user data directory: /home//mike/.pandoc Copyright
> (C) 2006-2014 John MacFarlane Web: http://johnmacfarlane.net/pandoc This
> is free software; see the source for copying conditions. There is no
> warranty, not even for merchantability or fitness for a particular purpose.
>
> >> uname -a
> Linux seuss 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014
> x86_64 GNU/Linux
>
> As for running
> >> pandoc -s --listings header.tex main.tex -o output.tex
> I get the same problem (with or without the -s flag) that my macros are
> not processed.
>
> I also commented out the lines:
> \documentclass{article}
> and
> \input{header}
> in the respective files when supplying the files on the commandline to be
> concatenated. The same problem occurs: my macros are not expanded. With the
> -s flag, I will see my macro definitions in the output file, but any
> reference to them in the body is obliterated.
>
> Thank you for your time---any ideas you have are appreciated.
>
>
> On Friday, January 9, 2015 at 2:33:21 PM UTC-5, John MacFarlane wrote:
>>
>> What pandoc version are you using?
>>
>> `\input` should be supported, but you'd need `header.tex` to be in the
>> working directory.
>>
>> You can also try simply putting `header.tex` on the command line:
>>
>> pandoc header.tex main.tex
>>
>> This produces the same output as if you had the contents of
>> `header.tex` at the beginning of `main.tex`.
>>
>>
>> +++ Mike Hynes [Jan 09 15 10:27 ]:
>> >Hello,
>> >
>> >I am trying to use pandoc to convert my latex files into other doc
>> types,
>> >mainly html and doc.
>> >
>> >My latex documents generally have the following format:
>> >
>> >\input{header}
>> >\begin{document}
>> > body text as usual
>> >\end{document}
>> >
>> >The file header.tex is either contained in the same directory, or in
>> >~/texmf/tex/latex/headers/. In my headers, I have frequently-used macros
>> >such as:
>> >
>> >\newcommand{\FIG}[3]{
>> >\begin{figure}[h!]
>> >\centering
>> >\includegraphics[width=#2\columnwidth,angle=0]{#1}
>> >\caption{#3}
>> >\label{fig:#1}
>> >\end{figure}
>> >}
>> >
>> >That is, I use almost *no* latex commands in my writing, and make
>> frequent
>> >use of macros to simplify inclusion tables, figures, algorithms,
>> >mathematical formulae, etc.
>> >
>> >I would like to run pandoc on such documents, but am having trouble. My
>> >macros are not getting parsed, and when I run pandoc with
>> >--template=$USER/texmf/tex/latex/report.tex (or with an -H flag), I
>> often
>> >just have the file echoed back to with, without any conversion of the
>> >specified input files.
>> >
>> >Can someone please direct me to the most efficient way of processing my
>> tex
>> >files, given their macro-heavy format? I can't seem to find the correct
>> >flags in the documentation for what I'm trying to do.
>> >
>> >Thanks
>> >
>> >--
>> >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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> >To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/90cb9924-0ed1-441a-8ef2-f2e3928a165c%40googlegroups.com.
>>
>> >For more options, visit 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/40a476ba-e1a8-413e-ab7e-584f21f70101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 7871 bytes --]
next prev parent reply other threads:[~2015-01-09 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 18:27 Mike Hynes
[not found] ` <90cb9924-0ed1-441a-8ef2-f2e3928a165c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 18:44 ` Matthew Pickering
[not found] ` <CALuQ0m_pvBqPZvXnOjsT8+Ev5+xRKz8osw_zVuhW=sKMGESz9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-09 19:11 ` Mike Hynes
[not found] ` <ef300118-1ee9-4e4e-8cb8-1cc47dc4d192-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 19:13 ` Mike Hynes
2015-01-09 19:33 ` John MacFarlane
[not found] ` <20150109193307.GA90254-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-01-09 20:12 ` Mike Hynes
[not found] ` <039f5de8-68e3-42a7-9f9c-cdc6bde24bc4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 20:22 ` Mike Hynes [this message]
[not found] ` <40a476ba-e1a8-413e-ab7e-584f21f70101-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 22:31 ` Matthew Pickering
[not found] ` <CALuQ0m9YSVo7qSaUZg2nf+3JnUL7aN-tscHMt1xONj2dCUe5fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-09 22:43 ` Mike Hynes
[not found] ` <a7b24022-c931-46ed-a2bf-ae80a3ca79f0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 22:50 ` Matthew Pickering
[not found] ` <CALuQ0m8pi4zuxCiCCoa4uiS=8yAWAPeYoqRoODpJ32KquSgYCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-09 23:06 ` Matthew Pickering
[not found] ` <CALuQ0m8t5ejcyS6mZ05eZn+=JoGoJ8FK4i_mF0Wira7AHcPwjg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-10 0:02 ` Matthew Pickering
[not found] ` <CALuQ0m9f8Zvtnv=eyBGu=3afxZvLb3uCW=-i8cVWLDgxLwhCQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-10 17:00 ` Mike Hynes
[not found] ` <18984b29-d0e1-4f6c-85a3-3de241601d2c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-10 17:48 ` Mike Hynes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40a476ba-e1a8-413e-ab7e-584f21f70101@googlegroups.com \
--to=91mbbh-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).