Possible bug with defaults and raw latex in header

Possible bug with defaults and raw latex in header

[Lyndon Drake]

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

Hi,

When I put the following in a YAML block in my Markdown file:

  header-includes:
  - |
    ```{=latex}
    \usepackage{imakeidx}
    ```

it works fine. The same text in a defaults file, in the metadata: section, 
ends up in the LaTeX file after being backslash-escaped.

Is that intended behaviour? If not I'll put a bug report in the issue 
tracker.

Best,
Lyndon

-- 
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/bd07e9d0-e3f8-481b-9a3f-3c952b11499c%40googlegroups.com.

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

Re: Possible bug with defaults and raw latex in header

[John MacFarlane]

Yes, this is intended. In a markdown file YAML fields are parsed
as Markdown.  So if you want raw LaTeX you need to indicate this
as you do.  In a defaults file metadata section, it works just
like with --metadata-file or --metadata on the command line:
the contents are interpreted as plain strings.

Lyndon Drake <lyndon-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org> writes:

> Hi,
>
> When I put the following in a YAML block in my Markdown file:
>
>   header-includes:
>   - |
>     ```{=latex}
>     \usepackage{imakeidx}
>     ```
>
> it works fine. The same text in a defaults file, in the metadata: section, 
> ends up in the LaTeX file after being backslash-escaped.
>
> Is that intended behaviour? If not I'll put a bug report in the issue 
> tracker.
>
> Best,
> Lyndon
>
> -- 
> 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/bd07e9d0-e3f8-481b-9a3f-3c952b11499c%40googlegroups.com.

Re: Possible bug with defaults and raw latex in header

[Lyndon Drake]

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

For clarity, this is what ends up in the LaTeX file:

\textbackslash usepackage\{imakeidx\}

Is there a way to include raw LaTeX in the defaults file, and avoid having 
it escaped (the \textbackslash etc. in there)?

What's the best way to include raw LaTeX using a defaults file?

Best,
Lyndon

On Tuesday, 21 April 2020 04:31:19 UTC+12, John MacFarlane wrote:
>
>
> Yes, this is intended. In a markdown file YAML fields are parsed 
> as Markdown.  So if you want raw LaTeX you need to indicate this 
> as you do.  In a defaults file metadata section, it works just 
> like with --metadata-file or --metadata on the command line: 
> the contents are interpreted as plain strings. 
>
> Lyndon Drake <lyn...-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org <javascript:>> writes: 
>
> > Hi, 
> > 
> > When I put the following in a YAML block in my Markdown file: 
> > 
> >   header-includes: 
> >   - | 
> >     ```{=latex} 
> >     \usepackage{imakeidx} 
> >     ``` 
> > 
> > it works fine. The same text in a defaults file, in the metadata: 
> section, 
> > ends up in the LaTeX file after being backslash-escaped. 
> > 
> > Is that intended behaviour? If not I'll put a bug report in the issue 
> > tracker. 
> > 
> > Best, 
> > Lyndon 
> > 
> > -- 
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/bd07e9d0-e3f8-481b-9a3f-3c952b11499c%40googlegroups.com. 
>
>

-- 
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/28a7dbf5-113c-4287-be57-96996e083406%40googlegroups.com.

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

Re: Possible bug with defaults and raw latex in header

[John MacFarlane]

Put it in header-includes in variables. Anything in variables in
the defaults file will be passed verbatim to the template. This
material is not really metadata, anyway, so it doesn't
conceptually belong there.

Lyndon Drake <lyndon-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org> writes:

> For clarity, this is what ends up in the LaTeX file:
>
> \textbackslash usepackage\{imakeidx\}
>
> Is there a way to include raw LaTeX in the defaults file, and avoid having 
> it escaped (the \textbackslash etc. in there)?
>
> What's the best way to include raw LaTeX using a defaults file?
>
> Best,
> Lyndon
>
> On Tuesday, 21 April 2020 04:31:19 UTC+12, John MacFarlane wrote:
>>
>>
>> Yes, this is intended. In a markdown file YAML fields are parsed 
>> as Markdown.  So if you want raw LaTeX you need to indicate this 
>> as you do.  In a defaults file metadata section, it works just 
>> like with --metadata-file or --metadata on the command line: 
>> the contents are interpreted as plain strings. 
>>
>> Lyndon Drake <lyn...-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org <javascript:>> writes: 
>>
>> > Hi, 
>> > 
>> > When I put the following in a YAML block in my Markdown file: 
>> > 
>> >   header-includes: 
>> >   - | 
>> >     ```{=latex} 
>> >     \usepackage{imakeidx} 
>> >     ``` 
>> > 
>> > it works fine. The same text in a defaults file, in the metadata: 
>> section, 
>> > ends up in the LaTeX file after being backslash-escaped. 
>> > 
>> > Is that intended behaviour? If not I'll put a bug report in the issue 
>> > tracker. 
>> > 
>> > Best, 
>> > Lyndon 
>> > 
>> > -- 
>> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/bd07e9d0-e3f8-481b-9a3f-3c952b11499c%40googlegroups.com. 
>>
>>
>
> -- 
> 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/28a7dbf5-113c-4287-be57-96996e083406%40googlegroups.com.