From: Henning Schwentner <henning.schwentner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Configurable default styles for docx reader and writer as extension to custom styles
Date: Fri, 16 Apr 2021 03:59:25 -0700 (PDT) [thread overview]
Message-ID: <a548419c-194f-4b31-9f49-fa0ebafab7fbn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1495 bytes --]
The custom style mechanism of the docx writer is great and makes my life as
author much easier. A further improvement could be the following. What do
you think?
So far, when converting to and from docx, a fixed set of styles is used by
both the reader and writer. So we have styles “Body Text”, “Heading 1”,
“Caption”, “Figure”, and so on. These correspond (of course) to the
Markdown elements. This works great with using Pandoc’s standard
reference.docx. But most publishers provide templates with their their
own styles and their own names for them. Example: Pearson uses CHAP_TTL for
chapter titles and CHAP_BM for body text.
My idea is to make the styles (in fact style names) configurable. So we
could have a config file that defines the mapping. Something like:
Body Text = CHAP_BM
First Paragraph = HEADFIRST
Heading 1 = CHAP_TTL
Heading 2 = H1
Footnote Text = FN
…
This mapping file could then be used by both the reader and writer for
convenient conversion.
Would that make sense to you?
Best,
Henning
--
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/a548419c-194f-4b31-9f49-fa0ebafab7fbn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2176 bytes --]
reply other threads:[~2021-04-16 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a548419c-194f-4b31-9f49-fa0ebafab7fbn@googlegroups.com \
--to=henning.schwentner-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).