From: mf <massifrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Customize CodeBlock font size in docx
Date: Sat, 1 Jul 2023 12:34:33 +0200 [thread overview]
Message-ID: <3fe3c11f-bed0-fa56-4c2a-a4a96793f4a3@gmail.com> (raw)
In-Reply-To: <71cbadfc-e399-4cd2-becd-95fc94278adfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Il 01/07/23 11:07, Sylvain Hubert ha scritto:
> Hi all,
>
> Does anyone know how to reduce the font size of code blocks in the docx
> output?
You may try this:
- export the code block in a, say, reference.docx
- open reference.docx with Word and customize the paragraph style of the
code block, then save
- export again the code block in another docx file, using the option
--reference-doc=reference.docx
Pandoc should use the styles it finds in reference.docx, so the block
code should look the way you customized it with Word.
>
> I know I could customize the Verbatim style in the reference doc,
> but that would also unwantedly affect the inline code.
>
> Ideally it should be done with custom styles, without too much hacks of
> raw docx.
>
> Thanks!
>
next prev parent reply other threads:[~2023-07-01 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 9:07 Sylvain Hubert
[not found] ` <71cbadfc-e399-4cd2-becd-95fc94278adfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-01 10:20 ` Bastien DUMONT
2023-07-01 10:34 ` mf [this message]
[not found] ` <3fe3c11f-bed0-fa56-4c2a-a4a96793f4a3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-11 6:51 ` Sylvain Hubert
[not found] ` <cff22eb0-a9d4-4e03-aa77-b83c42c04a57n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 7:16 ` Bastien DUMONT
2023-07-11 9:39 ` Sylvain Hubert
[not found] ` <7e333365-fe50-4652-8274-aa83c66e213an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 11:13 ` mf
[not found] ` <782d9773-1c50-9b79-b05f-361a9df87127-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-11 12:24 ` Sylvain Hubert
[not found] ` <1244cd1b-72a6-4c8b-9b15-830bbd36ab6dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 12:51 ` mf
[not found] ` <5303aa80-f729-f4c2-0e38-96e3d90a80af-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-11 14:00 ` Sylvain Hubert
[not found] ` <a99ab2f9-e808-4d9d-a510-aea4e9348b46n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 15:22 ` Bastien DUMONT
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=3fe3c11f-bed0-fa56-4c2a-a4a96793f4a3@gmail.com \
--to=massifrg-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).