From: K4zuki <k.yamamoto.08136891-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to improve .docx output?
Date: Thu, 22 Aug 2019 06:04:46 -0700 (PDT) [thread overview]
Message-ID: <32bb05e7-9d7b-47d8-8729-dd7b42281839@googlegroups.com> (raw)
In-Reply-To: <RC5rhmsP_qtblfskRIcPZHhdVlJt76IbH1X0a1IN_iFZ_-Q1fwRtQUS16-5M0zfTI0J54Wi9vk5Z8xzTRfAyYrOwpmlUzosE-rH9C1UcK7c=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]
Hello,
I have also been working for docx output.
[...]
- With a custom-reference.docx modified to number section headings,
`# References {-}` came out numbered, too; i.e., `{-}` was ignored.
(A proper fix would probably require pandoc to attach a docx style
like "Heading (unnumbered) 1" to such headings.)
[...]
This Lua filter might help you:
https://github.com/pandocker/pandocker-lua-filters/blob/master/lua/docx-unnumberedheadings.lua
Your guess is correct; you have to prepare unnumbered custom heading
styles(up to 4th level) in your reference.docx,
also need to point them in YAML frontmatter (or dedicated extra YAML file).
--
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/32bb05e7-9d7b-47d8-8729-dd7b42281839%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1692 bytes --]
next prev parent reply other threads:[~2019-08-22 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 12:24 'Nick Bart' via pandoc-discuss
2019-08-22 13:04 ` K4zuki [this message]
[not found] ` <32bb05e7-9d7b-47d8-8729-dd7b42281839-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-22 13:44 ` BP Jonsson
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=32bb05e7-9d7b-47d8-8729-dd7b42281839@googlegroups.com \
--to=k.yamamoto.08136891-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).