From: Phil <phillipruppert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Trouble with custom styles for docx output
Date: Sat, 9 Feb 2019 22:19:55 -0800 (PST) [thread overview]
Message-ID: <b8fd20bf-bb08-46e5-a6d7-7decfd41e91a@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1677 bytes --]
On Pandoc 2.6, I am converting from markdown to docx. I am trying to learn
and use the custom styles for docx output and am getting some odd behavior.
I am using the examples text straight from the Pandoc User Guide. I have
only substituted the name of my custom style that is defined in my
reference.docx.
Just placing the following in my markdown file results in no styled text:
[Get out]{custom-style="greyBackground"}, he said.
But placing this in my markdown file results in styled text:
::: {custom-style="greyBackground"}
| A Bird came down the Walk---
| He did not know I saw---
:::
And placing both of the following contiguously in my markdown file results
in neither having the styled text:
[Get out]{custom-style="greyBackground"}, he said.
::: {custom-style="greyBackground"}
| A Bird came down the Walk---
| He did not know I saw---
:::
Am I doing something wrong with the bracketed span style? Not sure what it
could be since I am copying nearly directly from the example in the user
guide. Is this a bug, or is there some trick or consideration I am not
getting?
Thanks.
Phil
--
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/b8fd20bf-bb08-46e5-a6d7-7decfd41e91a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 5198 bytes --]
next reply other threads:[~2019-02-10 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 6:19 Phil [this message]
[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
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=b8fd20bf-bb08-46e5-a6d7-7decfd41e91a@googlegroups.com \
--to=phillipruppert-re5jqeeqqe8avxtiumwx3w@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).