public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Phil <phillipruppert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Trouble with custom styles for docx output
Date: Tue, 12 Feb 2019 14:11:38 +0100	[thread overview]
Message-ID: <CADAJKhB9RJvN+XraZKUGvAKjdKN0jep7WONuX5D=bFF7mjXvkA@mail.gmail.com> (raw)
In-Reply-To: <yh480kftsufexq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]

Phil, have you defined both a character style and a paragraph style for
your custom style in your reference docx file? You have to do that because
paragraph styles and character styles are distinct entities even if they
have the same name and the same visual effect.

Den mån 11 feb. 2019 17:50 skrev John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@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.
>
> --
> 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/yh480kftsufexq.fsf%40johnmacfarlane.net
> .
> 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/CADAJKhB9RJvN%2BXraZKUGvAKjdKN0jep7WONuX5D%3DbFF7mjXvkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3617 bytes --]

      parent reply	other threads:[~2019-02-12 13:11 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
     [not found]             ` <yh480kftsufexq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-02-12 13:11               ` BPJ [this message]

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='CADAJKhB9RJvN+XraZKUGvAKjdKN0jep7WONuX5D=bFF7mjXvkA@mail.gmail.com' \
    --to=melroch-re5jqeeqqe8avxtiumwx3w@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).