public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Pranesh Prakash
	<the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Hiding TeX headers from HTML output
Date: Tue, 25 Aug 2020 14:44:20 -0700	[thread overview]
Message-ID: <m28se2v1sb.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <a669b6a7-167e-4056-b0fa-546e4fe53d7fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


header-includes is the field name to use.

Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi all,
> I use the TeX files paragraphs.tex and footnotes.tex to style the 
> paragraphs and footnotes in PDFs.  (The input file is in pandoc-flavour 
> markdown.)  I use them via a defaults files using "include-in-header: \n - 
> paragraphs.tex \n - footnotes.tex".  When I convert the file to HTML, the 
> TeX component shows up.  (It is in the <head> </head> part, before <body>, 
> but still shows up on the screen when I open the file.)
>
> I've tried using the modified TeX files where I enclose them in code fences 
> with {=pdf} and {=latex} as well. Each time I do this, I get the error:
>
>> Error producing PDF.
>> ! LaTeX Error: Missing \begin{document}.
>> 
>>  See the LaTeX manual or LaTeX Companion for explanation.
>> Type  H <return>  for immediate help.
>>  ...                                              
>>                                                   
>> l.43 `
>> 
>
> I get this same error if I try to include the headers using 
> "header-include:" instead of "include-in-header:". 
>
> I've tried marking the input format as "markdown+raw_attribute" and as 
> "markdown+raw_tex", but that doesn't change anything.
>
> What am I doing wrong?  How do I prevent the PDF/LaTeX-specific headers 
> from being used for outputs like HTML?
>
> Regards,
> Pranesh
>
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a669b6a7-167e-4056-b0fa-546e4fe53d7fn%40googlegroups.com.
> ```{=pdf}
> \usepackage{parskip}
> \setlength{\parskip}{5pt plus1pt}
> \setlength\parindent{1.5em}
> ```
> ```{=latex}
> \usepackage{microtype,parskip,bookmark,setspace,xurl,secdot}
> \usepackage[hang,bottom,multiple]{footmisc}
> \setlength{\footnotesep}{3mm}
> ```
> \usepackage{parskip}
> \setlength{\parskip}{5pt plus1pt}
> \setlength\parindent{1.5em}
> \usepackage{microtype,parskip,bookmark,setspace,xurl,secdot}
> \usepackage[hang,bottom,multiple]{footmisc}
> \setlength{\footnotesep}{3mm}
> ```{=pdf}
> \usepackage{microtype,parskip,bookmark,setspace,xurl,secdot}
> \usepackage[hang,bottom,multiple]{footmisc}
> \setlength{\footnotesep}{3mm}
> ```
> ```{=latex}
> \usepackage{parskip}
> \setlength{\parskip}{5pt plus1pt}
> \setlength\parindent{1.5em}
> ```


  parent reply	other threads:[~2020-08-25 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 18:20 Pranesh Prakash
     [not found] ` <a669b6a7-167e-4056-b0fa-546e4fe53d7fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-25 19:53   ` Pranesh Prakash
2020-08-25 21:44   ` John MacFarlane [this message]
     [not found]     ` <m28se2v1sb.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-25 22:06       ` Pranesh Prakash
     [not found]         ` <95f7f71e-6af3-4d73-b47e-dd7bd28585e9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-26  6:18           ` John MacFarlane
     [not found]             ` <m2r1ruszed.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-26 10:48               ` Pranesh Prakash

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=m28se2v1sb.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@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).