public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Shane Liesegang <liesegang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Manually apply styles to output docx?
Date: Sun, 15 May 2022 05:28:19 -0700 (PDT)	[thread overview]
Message-ID: <2a9a59ee-359b-4670-a140-234fb4c52311n@googlegroups.com> (raw)


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

I've customized a reference.docx file for applying styles to an exported 
Word document, and am attempting to follow the instructions from the Custom 
Styles <https://pandoc.org/MANUAL.html#custom-styles> section of the 
manual. If I'm reading the documentation right (and I may not be!) if I 
attempt to apply a custom style that is already defined in the reference 
document, it will not redefine it but apply the existing style. 

However, when I do something like this in markdown+bracketed_spans: 

[my strong text]{custom-style="Strong"}

And there is already a "Strong" style in the reference file, I find the 
span instead has a new style applied to it called "Strong1". 

Is there any way I can manually apply styles to Markdown text for docx 
output? 

Thanks for any help / letting me know where I misunderstand. 

-- 
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/2a9a59ee-359b-4670-a140-234fb4c52311n%40googlegroups.com.

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

             reply	other threads:[~2022-05-15 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHYaFdG0wl3fC04FE2XyAGiW0Bttq0hQeiA>
2022-05-15 12:28 ` Shane Liesegang [this message]
     [not found]   ` <2a9a59ee-359b-4670-a140-234fb4c52311n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-16  9:43     ` AW: " denis.maier-NSENcxR/0n0
     [not found]       ` <3b8d1a41518f4384a6087ac54b826b3c-NSENcxR/0n0@public.gmane.org>
2022-05-19  3:33         ` Shane Liesegang
     [not found]           ` <56357d0c-ae70-44bc-8e53-25c686fa73f0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-25 20:18             ` Shane Liesegang

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=2a9a59ee-359b-4670-a140-234fb4c52311n@googlegroups.com \
    --to=liesegang-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).