public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: docx to pdf conversion error
Date: Thu, 9 Nov 2017 23:44:13 -0500	[thread overview]
Message-ID: <20171110044412.GI70590@MacBook-Air-2.local> (raw)
In-Reply-To: <9256e740-7530-4dc2-9acd-5d14eca6fc07-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

YAML metadata only works with Markdown.

When you specify multiple files on the command line,
pandoc concatenates them together and treats them as
if they were one big file.

That works when one is yaml and the other is Markdown
(as long as the yaml has proper begin and end delimiters).

It doesn't work when one is yaml and the other is docx.

Related issue;
https://github.com/jgm/pandoc/issues/1960


+++ sclarke-DpHT0TjK6O80n/F98K4Iww@public.gmane.org [Nov 09 17 15:32 ]:
>   OK not sure if this is by design or a bug ;)
>   Relatively new to pandoc and coversion, and am coming from the Windowz
>   world.
>   We have a variety of OSs and editors in use and want to ensure a
>   commonality of  output format with standardised frontice pages etc.
>   Version: pandoc 2.0.1.1 Compiled with pandoc-types 1.17.2, texmath
>   0.10, skylighting 0.4.3.2
>   We have created our own style file for formatting in latex, and our own
>   pandoc.latex to generate the coverpage etc.
>   We have been extending into using a yaml metadata file to include
>   variables and elements (email address, mulitple authors etc) for our
>   reports.
>   We have a problem with the yaml metadata file causing failures with the
>   conversion from docx to pdf.
>   The file works correctly when used against a markdown file to produce a
>   pdf.
>   Behaviour:
>   This fails -
>   >pandoc --standalone --toc --number-sections --pdf-engine=xelatex
>   --template pandoc.latex test.docx metadata.yaml -o test10.pdf
>   couldn't parse docx file
>   This works without issue -
>   >pandoc --standalone --toc --number-sections --pdf-engine=xelatex
>   --template pandoc.latex test.docx -o test10.pdf
>   Now either I'm doing something I'm not supposed to (and it will be very
>   annoying to have to go through the intermediary step of converting to
>   markdown file first then to pdf), or something is wrong with my syntax.
>   The same command when used for a markdown file works without issue and
>   draws the variables we want from the markdown.yaml.
>
>   --
>   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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/9256e740-7530-4dc2-
>   9acd-5d14eca6fc07%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/9256e740-7530-4dc2-9acd-5d14eca6fc07-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-11-10  4:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 23:32 sclarke-DpHT0TjK6O80n/F98K4Iww
     [not found] ` <9256e740-7530-4dc2-9acd-5d14eca6fc07-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10  3:58   ` John Muccigrosso
     [not found]     ` <ac6b1f81-80bf-4e92-a65c-db089def2c19-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10  4:02       ` sclarke-DpHT0TjK6O80n/F98K4Iww
     [not found]         ` <d1935dae-097e-447c-bd10-a8265ba169db-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10  4:02           ` sclarke-DpHT0TjK6O80n/F98K4Iww
2017-11-10  4:44   ` John MacFarlane [this message]
     [not found]     ` <20171110044412.GI70590-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-11-10  5:10       ` sclarke-DpHT0TjK6O80n/F98K4Iww
     [not found]         ` <e741d764-809b-422b-aee1-75b4e4351569-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10 22:02           ` Kolen Cheung
2017-11-10 22:06           ` Kolen Cheung
     [not found]             ` <4710734d-f71c-45c9-b65f-27ebf81e29e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-12 21:34               ` sclarke-DpHT0TjK6O80n/F98K4Iww
     [not found]                 ` <85643608-a189-4407-8a21-37e5d75074fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-13  9:19                   ` albert.krewinkel-stqabkCVF6SGlKaCpJGLJw
     [not found]                     ` <323e407c-d9ae-429a-b951-1dc5b87a624b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-13 23:37                       ` Kolen Cheung
     [not found]                         ` <2b1dba89-0544-49a0-954d-cad4c269fc78-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-13 23:53                           ` sclarke-DpHT0TjK6O80n/F98K4Iww
2017-11-14  7:50                           ` albert.krewinkel-stqabkCVF6SGlKaCpJGLJw
     [not found]                             ` <600cb80b-0753-4823-acd3-a05cae7577e8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-14 12:12                               ` Kolen Cheung
     [not found]                                 ` <17d771db-6489-402c-afa6-d948ca8e9cac-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-15 13:38                                   ` albert.krewinkel-stqabkCVF6SGlKaCpJGLJw
     [not found]                                     ` <b8cdcc3a-105a-405f-b2a2-188cdc053abb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-15 17:43                                       ` Kolen Cheung

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=20171110044412.GI70590@MacBook-Air-2.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).