From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [Spam] "Source Code" style not found in generated reference docx
Date: Fri, 30 Dec 2022 09:29:24 -0500 [thread overview]
Message-ID: <e2269640-2ac8-ac34-f5c3-0c980efb5062@usa.net> (raw)
In-Reply-To: <83c5bd22-976e-4d05-87a9-461d60215b42n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 12/30/22 2:48 AM, Solever Lee wrote:
> Hi,
> I'm trying to modify the style of code block in reference document, I
> followed the manual and used pandoc -o custom-reference.docx
> --print-default-data-file reference.docx to generate a default reference
> document.
>
> However, I could find any style for the source code, should there be a
> style named "Source Code", or a code block inside the document?
>
> BTW, I'm using the latest pandoc version 2.9.12.
>
> Thanks!
As I understand it, the source code is basically styled by a separate
plugin that's been integrated:
https://pandoc.org/MANUAL.html#syntax-highlighting
So if you want to style it, either use it's styling themes, or override
and handle entirely yourself - either way it's basically just a
preformatted block, and is probably in that style in the Docx.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
prev parent reply other threads:[~2022-12-30 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 7:48 Solever Lee
[not found] ` <83c5bd22-976e-4d05-87a9-461d60215b42n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-30 14:29 ` Daniel Staal [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=e2269640-2ac8-ac34-f5c3-0c980efb5062@usa.net \
--to=dstaal-jdbf3xikgs8@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).