public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Phil <phillipruppert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Trouble with custom styles for docx output
Date: Mon, 11 Feb 2019 08:49:37 -0800	[thread overview]
Message-ID: <yh480kftsufexq.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <d8b5e3a4-671e-4468-b967-c71f92e39c72-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Phil <phillipruppert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Thank you for the reply, John, and for this awesome tool.
>
> Originally, I was not using the styles extension because the User Guide 
> makes it seem like that extension is used when docx is input, not output.
>
> Regardless, I have tried now again with -t docx+styles as you suggest and 
> am getting the same results. I have also tried adding the styles to my 
> input: -f markdown+styles but get the same results. Side question, does it 
> matter whether  extensions are added to the -f or -t formats?

Answer to side question is yes.  Extensions can be
applied separately to reader and writer formats.

As for the main question, perhaps someone who uses
custom styles could answer better than I.


  parent reply	other threads:[~2019-02-11 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10  6:19 Phil
     [not found] ` <b8fd20bf-bb08-46e5-a6d7-7decfd41e91a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-10 15:29   ` John MacFarlane
     [not found]     ` <m2k1i71x2u.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-02-10 23:37       ` Phil
     [not found]         ` <d8b5e3a4-671e-4468-b967-c71f92e39c72-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-11 16:49           ` John MacFarlane [this message]
     [not found]             ` <yh480kftsufexq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-02-12 13:11               ` BPJ

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